Backup Exec 2012 Administrators Guide

Symantec Backup ExecTM 12 for Windows Servers
Administrators Guide
12666659 November 2007
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
Administrators Guide - Table of Contents

Chapter 1. Introducing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Whats new in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Whats new in the Advanced Disk-based Backup Option . . . . . . . . . . . . . . . . . . . . . 52 Whats new in the Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Backup Exec agents and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Media server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Client protection options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Groupware agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Online database agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Disaster recovery option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 How Backup Exec works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Chapter 2. Installing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Before you install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Checking your environment before installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 About the Backup Exec services account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Changing Windows security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 About Microsoft SQL Server 2005 Express Edition components installed with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 About Backup Execs standard features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Installing Backup Exec to a local computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Installing Backup Exec options to the local computer . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Installing Backup Exec to remote computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Installing Backup Exec options to remote computers . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Installing the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
3
Installing the Remote Agent and Advanced Open File Option in an Active Directory network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Push-installing the Remote Agent and the AOFO using the command line . . . . 93 Installing the Remote Agent to an x64-based operating system . . . . . . . . . . . . . . 95 Using a command prompt to install the Remote Agent on a remote 32-bit computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Using a command prompt to uninstall the Remote Agent from a remote 32-bit computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Using a command script to install the Remote Agent and AOFO . . . . . . . . . . . . . 97 Using a command script to uninstall the Remote Agent and AOFO . . . . . . . . . . . 98 Installing the Backup Exec Remote Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Installing Backup Exec using the command line (silent mode) . . . . . . . . . . . . . . . . . 101 Command line switches for Backup Exec silent mode installation . . . . . . . . . . . 102 Installing the Remote Administrator using the command line . . . . . . . . . . . . . . 107 Uninstalling Backup Exec using the command line . . . . . . . . . . . . . . . . . . . . . . . . 108 Creating and using installation parameter files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Using a clone CD image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Creating a clone CD image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Installing locally using a clone CD image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Installing to a remote system using a clone CD image . . . . . . . . . . . . . . . . . . . . . . 111 Evaluating Backup Exec agents and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 About the installation log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Repairing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Starting and stopping Backup Exec services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Uninstalling Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Uninstalling Backup Exec options from the local media server . . . . . . . . . . . . . . . . . 116 About updating Backup Exec with LiveUpdate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Scheduling automatic updates using LiveUpdate . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Running LiveUpdate manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Viewing installed updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Viewing license information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
4 Administrators Guide
Adding licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Finding installed licenses in your environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Upgrading from previous versions of Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Upgrading Backup Exec options on remote computers . . . . . . . . . . . . . . . . . . . . . 124 Chapter 3. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Before starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Using the Getting Started with Backup Exec page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Using the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Using Backup Exec dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Backup Exec defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Changing default preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Changing device and media job defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 About storage devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Viewing media server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Viewing a media servers general properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Viewing a media servers system properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Viewing a media servers active job and alert statistics . . . . . . . . . . . . . . . . . . . . . 142 Viewing the location of Backup Exec databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 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
Administrators Guide - Table of Contents 5
Changing your default Backup Exec logon account . . . . . . . . . . . . . . . . . . . . . . . . 153 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 Configuring database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Configuring columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Hiding a column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Displaying a column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Rearranging columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Sorting columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Chapter 5. Managing media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 About media in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Media overwrite protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Default media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Creating media sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Running the Media Set Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Deleting a media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Renaming a media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Changing general media set properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Media overwrite protection levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Setting the search order for overwritable media . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 About overwriting allocated or imported media . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Setting defaults for media management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Auditing media operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Media labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Imported media labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Bar code labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Bar code rules in mixed media libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Renaming media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 About WORM media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Cataloging media while reviewing devices or media . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Creating a restore job while reviewing media or devices . . . . . . . . . . . . . . . . . . . . . . . 198 Media locations and vaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Creating media vaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Configuring vault rules for media sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Finding media in a location or vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Renaming a media vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Deleting a media vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Moving media to a vault or to the offline media location . . . . . . . . . . . . . . . . . . . . . . . 202 Scanning bar code labels to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Scheduling a job to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Using the Vault Wizard to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Using the drag and drop method to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Using the Move to vault task to move media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Removing damaged media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Deleting media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Associating media with a media set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Viewing general media properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Viewing media in storage devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Viewing media statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Media rotation strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Son media rotation strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Father/son media rotation strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Grandfather media rotation strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Chapter 6. Preparing for backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 About backup strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Choosing a backup strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Understanding backup methods and their advantages . . . . . . . . . . . . . . . . . . . . . 224 Understanding the archive bit and backup methods . . . . . . . . . . . . . . . . . . . . . . . 228 Understanding modified time and backup methods . . . . . . . . . . . . . . . . . . . . . . . . 229 Selecting data to back up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 About using fully qualified computer names in backup selections . . . . . . . . . . . . . . 232 About the Computer Name node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 About the Favorite Resources node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Adding a Windows system to the Favorite Resources node . . . . . . . . . . . . . . . . . 235 Deleting a Windows system from the Favorite Resources node . . . . . . . . . . . . . . 236 About the Domains node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Adding an Active Directory domain to the Active Directory Domains node . . . 237 About the Oracle Real Application Clusters node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 About the NDMP Devices node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 About the Microsoft SharePoint Server Farms node . . . . . . . . . . . . . . . . . . . . . . . . . . 238 About the User-defined Selections node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Adding a user-defined selection to the User-defined Selections node . . . . . . . . 238 Selecting Distributed File System (Dfs) links for backup . . . . . . . . . . . . . . . . . . . . . . . 240 Including or excluding files for backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 About selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Creating selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Holding jobs that back up a selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Merging and replacing selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Deleting selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Editing selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Editing the Excludes selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Setting priority and availability windows for selection lists . . . . . . . . . . . . . . . . . 250 Creating separate selection lists for each computer or resource . . . . . . . . . . . . . 252
Creating a custom filter for Backup Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . 252 Filtering backup selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Searching selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Viewing the history for backup selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Viewing a summary for a selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Using resource discovery to search for new resources . . . . . . . . . . . . . . . . . . . . . . . . . 255 About the Backup Exec Shadow Copy Components file system . . . . . . . . . . . . . . . . . 258 How the Shadow Copy Components file system is affected by upgrades . . . . . . 259 About backing up virtual machines and the Virtual Server Host . . . . . . . . . . . . . 260 Chapter 7. Backing up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Creating a backup job by using the Backup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Preventing the Backup Wizard from launching from the Backup button . . . . . 266 Creating a backup job by setting job properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Selections options for backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 Changing the order for processing backup selections . . . . . . . . . . . . . . . . . . . . . . . 269 Changing and testing logon accounts for resources . . . . . . . . . . . . . . . . . . . . . . . . 270 Device and media options for backup jobs and templates . . . . . . . . . . . . . . . . . . . 272 General options for backup jobs and templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Advanced options for backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Pre/post commands for backup or restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Scheduling jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 About the scheduling calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Scheduling a job to run on specific days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Scheduling a job to run on recurring week days . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Scheduling a job to run on recurring days of the month . . . . . . . . . . . . . . . . . . . . 291 Scheduling a job to run on a day interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Setting the effective date for a job schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Setting the time window for a scheduled job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Restarting a job during a time interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Excluding dates from a schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Configuring default schedule options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Archiving data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Duplicating backed up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Backing up virtual machines and the Virtual Server Host . . . . . . . . . . . . . . . . . . . . . 301 Verifying a backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Creating a test run job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Setting test run default options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Chapter 8. Customizing backup options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307 Setting default backup options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Setting default pre/post commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Specifying backup networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 About using IPv4 and IPv6 in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Setting default backup network and security options . . . . . . . . . . . . . . . . . . . . . . 318 Changing the backup network and security options for a job . . . . . . . . . . . . . . . . 322 About using Backup Exec with Symantec Endpoint Protection . . . . . . . . . . . . . . . . . 324 Creating automatic backup jobs for use with Symantec Endpoint Protection . 325 Using Backup Exec with firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Browsing systems through a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 About enabling a SQL instance behind a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . 330 About encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 About software encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 About hardware encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Encryption keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Restricted keys and common keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Pass phrases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 About encryption key management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Creating an encryption key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Selecting an encryption key for a backup job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
10
Replacing an encryption key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Deleting an encryption key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 About restoring encrypted data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 About cataloging media that contains encrypted backup sets . . . . . . . . . . . . . . . 338 Chapter 9. Managing tape drives and robotic libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Configuring storage devices by using the Device Configuration Wizard . . . . . . . . . 340 Adding devices by using the Hot-swappable Device Wizard . . . . . . . . . . . . . . . . . . . . 341 Installing Symantec device drivers by using the Symantec Device Driver Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Viewing storage device properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Viewing a devices general properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Viewing a devices configuration properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Viewing a devices SCSI information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Viewing a devices statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Viewing a devices cleaning properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Viewing and specifying types of media for a device . . . . . . . . . . . . . . . . . . . . . . . . 353 Pausing and resuming devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Renaming a robotic library or device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 About robotic libraries in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Enabling robotic library support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Configuring a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Viewing robotic library properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Creating robotic library partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Redefining robotic library partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 About creating utility jobs to help manage devices and media . . . . . . . . . . . . . . . . . . 367 Inventorying media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Inventorying all drives when Backup Exec services start . . . . . . . . . . . . . . . . . . . 370 Erasing media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Retensioning a tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Formatting media in a drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Labeling media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Ejecting media from a drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Setting up cleaning jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Importing media to a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Exporting media from a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Locking the robotic librarys front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Initializing the robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Unlocking the robotic librarys front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Exporting expired media from a robotic library . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Chapter 10. Managing backup-to-disk folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .387 About backup-to-disk folders and files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 Requirements for creating a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . 389 Requirements for creating a removable backup-to-disk folder . . . . . . . . . . . . . . 390 Creating a backup-to-disk folder by using the Backup-to-disk Wizard . . . . . . . . . . 391 Creating a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Configuring advanced options for a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . 395 Setting defaults for new backup-to-disk folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Sharing an existing backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Renaming a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Changing the path of a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Deleting a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Recreating a backup-to-disk folder and its contents . . . . . . . . . . . . . . . . . . . . . . . . . . 401 Pausing and resuming a backup-to-disk folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Changing the status of a backup-to-disk folder to online . . . . . . . . . . . . . . . . . . . . . . 402 Renaming a backup-to-disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Deleting a backup-to-disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 Recreating a deleted backup-to-disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Erasing backup-to-disk files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 About using a backup-to-disk folder for GRT-enabled backup operations . . . . . . . 406
12
Requirements for using backup-to-disk folders with GRT-enabled backup operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 Recommendations for using backup-to-disk folders with GRT-enabled backup operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 About reclaiming disk space for GRT-enabled backup operations . . . . . . . . . . . . 409 Chapter 11. Managing device pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 About device pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Creating device pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 Adding devices to a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Setting priorities for devices in a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Deleting devices from a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Deleting device pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Retargeting a scheduled job from a deleted device pool or media set . . . . . . . . . 416 Renaming a device pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Viewing device pool properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 About cascaded drive pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 Requirements for using cascaded drive pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 Creating a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Adding drives to a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Deleting drives from a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Deleting a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Renaming a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Viewing properties of a cascaded drive pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Chapter 12. Policies and templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Creating a new policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 Editing a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 Deleting a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 Using an example policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Using templates in policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
13
Adding a backup template to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 Setting the schedule for a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Adding an export media template to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Importing a template into a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Editing a template in a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Deleting a template from a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Setting template rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Changing template rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Deleting template rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Creating jobs using policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Viewing the policies that protect selection lists . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Editing the next occurrence of a policy-based job . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Deleting a job created from a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Renaming a job created from a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 About duplicate backup set templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Adding a duplicate backup template to a policy . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Chapter 13. Administrating Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .447 Copying jobs, selection lists, and policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 Monitoring jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Viewing and changing active jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Canceling an active job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 Placing all scheduled occurrences of an active job on hold . . . . . . . . . . . . . . . . . . 455 Viewing and changing scheduled jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Viewing and changing completed jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 Filtering jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 About managing custom filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Creating a custom filter for jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 Creating a custom filter for current jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 Creating a custom filter for jobs in the job history . . . . . . . . . . . . . . . . . . . . . . . . . 479
14
Deleting custom filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Editing custom filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Viewing the job workload for a media server from the Calendar tab . . . . . . . . . . . . . 483 Viewing jobs for specific days on the calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 Managing jobs from the Calendar tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 Viewing the System Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 Viewing the Symantec Endpoint Protection Security Summary . . . . . . . . . . . . . . . . 485 Error-handling rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 Creating a custom error-handling rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Custom error-handling rule for recovered jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Cluster failover error-handling rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Setting thresholds to recover jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Chapter 14. Restoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 Restore jobs and the catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Setting catalog defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 Catalog levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Restoring data by using the Restore Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 Preventing the Restore Wizard from launching from the Restore button . . . . . 497 Restoring data by setting job properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 Selections options for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 Device options for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 General options for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 Advanced options for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 Running pre and post commands for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 508 About restoring file permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Restoring System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 About restoring Shadow Copy Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 Restoring virtual machines and the Virtual Server Host . . . . . . . . . . . . . . . . . . . . 514 About restoring utility partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
15
Restoring Distributed File System (Dfs) links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 About restoring media created with other backup software . . . . . . . . . . . . . . . . . 517 Selecting data to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 Creating a restore selection list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 Including or excluding files for restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 Searching for files to restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 Name and resource options for catalog search . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 Date modified options for catalog search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 Restore jobs and media libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 Changing and testing resource credentials for restore jobs . . . . . . . . . . . . . . . . . . . . 527 Redirecting a restore job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 Using redirected restore for Active Directory, Active Directory Application Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 Setting defaults for restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 Specifying the restore network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 Canceling a restore job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 Chapter 15. Alerts and notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .537 Viewing alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 Filtering alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539 Creating custom filters for alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 Viewing alert properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542 Viewing the job log from an alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544 Responding to active alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 Configuring automatic responses for alert categories . . . . . . . . . . . . . . . . . . . . . . 547 Clearing informational alerts from the Active Alerts pane . . . . . . . . . . . . . . . . . . 549 Configuring alert category properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550 Enabling or disabling alerts from the Active Alerts pane . . . . . . . . . . . . . . . . . . . 552 Deleting alerts from the alert history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 Setting up notification for alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 Configuring SMTP for email or mobile phone text message notification . . . . . 553
Configuring MAPI email for notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Configuring VIM email for notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 Configuring a pager for alert notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556 Configuring recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557 Configuring SMTP email or mobile phone text messaging for a person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Configuring MAPI mail for a person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 Configuring VIM mail for a person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 Configuring a pager for a person recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 Configuring a net send recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565 Configuring a printer recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Configuring a group recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Scheduling notification for recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569 Editing recipient notification properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 Editing recipient notification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 Removing recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Assigning recipients to alert categories for notification . . . . . . . . . . . . . . . . . . . . . . . 572 Assigning notification recipients for completed jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 573 About SNMP notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 Installing and configuring the SNMP system service . . . . . . . . . . . . . . . . . . . . . . . 579 Adding Windows Management Instrumentation capability . . . . . . . . . . . . . . . . . . . . 580 Uninstalling WMI providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Chapter 16. Reports in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 Viewing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Running a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Running and viewing a new report job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 Scheduling report jobs and setting notification recipients . . . . . . . . . . . . . . . . . . 591 About custom reports in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 Filter criteria and filter expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 Creating a custom report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Setting filters for custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 Grouping fields in custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600 Sorting fields in custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 Setting graph options in custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602 Example graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604 Previewing custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608 Copying custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608 Editing custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609 Deleting custom reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609 Setting default options for reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610 Viewing report properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611 Available reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613 Active Alerts Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 Active Alerts by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 Alert History Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 Alert History by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620 Application Event Log Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621 Audit Log Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621 Backup Job Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622 Backup Resource Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 Backup Set Details by Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 Backup Sets by Media Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624 Backup Size By Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 Configuration Settings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626 Current Job Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627 Daily Device Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 Device Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 Device Usage by Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629 Error-Handling Rules Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630 Event Recipients Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Failed Backup Jobs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632 Job Distribution by Device Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633 Jobs Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 Machines Backed Up Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634 Managed Media Servers Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635 Media Audit Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637 Media Errors Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637 Media Required for Recovery Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638 Media Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638 Media Vault Contents Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639 Missed Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640 Move Media to Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641 Operations Overview Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642 Overnight Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643 Policy Jobs by Resource Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644 Policy Jobs Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645 Policy Properties Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Policy Protected Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Problem Files Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648 Recently Written Media Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 Resource Backup Policy Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 Resource Risk Assessment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650 Resources Protected by Policy report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651 Restore Set Details by Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651 Retrieve Media from Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652 Robotic Library Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653 Scheduled Server Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654 Scratch Media Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654 Selection Lists Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655 Test Run Results Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Chapter 17. Disaster preparation and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .659 Key elements of a disaster preparation plan (DPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 Returning to the last known good configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661 Creating a hardware profile copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662 Creating an emergency repair disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 Using Windows Automated System Recovery and System Restore to recover a Windows XP or Windows Server 2003 system . . . . . . . . . . . . . . . . . . . . 664 Manual disaster recovery of Windows computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 Manual disaster recovery of a local Windows computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665 Disaster recovery of a remote Windows computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669 Chapter 18. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .673 Hardware-related questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674 Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677 Backup questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678 Restore questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680 Improving Backup Exec performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680 Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685 Before calling Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685 Finding version and revision information for your Backup Exec installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685 Backup Exec diagnostic utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685 Chapter 19. Using Symantec Backup Exec with Server Clusters . . . . . . . . . . . . . . . . . . .691 How Backup Exec works in a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . 692 Requirements for installing Backup Exec on a Microsoft Cluster Server . . . . . . . . 693 Installing Backup Exec on a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . 694 Upgrading Backup Exec on a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695 Installing additional Backup Exec options on a Microsoft cluster . . . . . . . . . . . . 696
Uninstalling Backup Exec from a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . 696 Creating device pools for Microsoft Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 698 Using checkpoint restart on Microsoft Cluster Server failover . . . . . . . . . . . . . . . . . 699 Enabling or disabling checkpoint restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700 Specifying a different failover node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701 Designating a new SAN SSO primary server and central administration server in a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702 Configurations for Backup Exec and Microsoft Cluster Servers . . . . . . . . . . . . . . . . . 704 Two-node cluster with locally attached storage devices . . . . . . . . . . . . . . . . . . . . . 704 Two-node cluster with tape devices on a shared SCSI bus . . . . . . . . . . . . . . . . . . . 706 Multi-node clusters on a fibre channel SAN with the SAN SSO . . . . . . . . . . . . . . 709 Using the Central Admin Server Option with Microsoft clusters and SAN SSO . . . 712 Backing up Microsoft Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Backing up local disks in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Backing up shared disks in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Backing up database files in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 About restoring data to a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 About restoring Windows 2000 and Windows Server 2003/2008 features to a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Restoring the cluster quorum for Windows 2000 and Windows Server 2003/2008 computers to a Microsoft cluster . . . . . . . . . . . . . . . 718 Restoring the cluster quorum to a Windows 2000 and Windows Server 2003/2008 node running Active Directory to a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Specifying a new drive letter for the cluster quorum disk . . . . . . . . . . . . . . . . . . . 721 Using Backup Exec with Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Requirements for installing Backup Exec with the CASO option on a Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723 Installing Backup Exec with the CASO option on a Veritas Cluster Server . . . . . . . 723 Requirements for clustering Backup Exec using Veritas Cluster Server . . . . . . . . . 724 Clustering Backup Exec using Veritas Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . 725 About backing up Veritas Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
About backing up Windows 2000 and Windows Server 2003/2008 features in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727 Backing up local disks in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728 Backing up shared disks in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728 Backing up database files in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 About restoring data to Veritas Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730 About restoring Windows 2000 and Windows Server 2003 features to a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730 About backup job failover with Veritas Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . 730 Disaster recovery of a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 Using IDR to prepare for disaster recovery of a cluster . . . . . . . . . . . . . . . . . . . . . 732 Recovering nodes on the cluster using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732 Recovering Backup Exec on a Microsoft Cluster using IDR . . . . . . . . . . . . . . . . . . 733 Recovering the entire cluster using a manual disaster recovery procedure . . . 734 Restoring the Microsoft Cluster data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735 Recovering all shared disks in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 736 Recovering all shared disks in a Veritas cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737 Recovering Backup Exec in a Microsoft cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 Troubleshooting clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 Appendix A. Symantec Backup Exec Central Admin Server Option . . . . . . . . . . . . . . . . .743 How CASO works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743 Requirements for installing CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747 Choosing the location for device and media data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749 Installing the central administration server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750 Installing a managed media server from the central administration server . . . . . . 751 Installing a managed media server across a firewall . . . . . . . . . . . . . . . . . . . . . . . 757 Upgrading an existing CASO installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760 Upgrading an existing central administration server . . . . . . . . . . . . . . . . . . . . . . 761 Upgrading an existing managed media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763 Changing a Backup Exec media server to a central administration server . . . . . . . 764
Changing a media server to a managed media server . . . . . . . . . . . . . . . . . . . . . . . 766 Changing a managed media server to a stand-alone media server . . . . . . . . . . . . . . 767 Running the Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767 Uninstalling Backup Exec from the central administration server . . . . . . . . . . . 768 Uninstalling Backup Exec from a managed media server . . . . . . . . . . . . . . . . . . . . . . 768 Configuring CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769 About reducing network traffic in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770 Setting defaults for managed media servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770 Setting communication thresholds and active job status updates . . . . . . . . . . . . 773 Copying logs and histories to the central administration server . . . . . . . . . . . . . 776 Configuring alerts in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778 Configuring notification in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 Enabling managed media servers to use any available network interface card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 About catalog locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780 Changing the catalog location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781 About job delegation in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 Grouping managed media servers in pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 Restricting the backup of a selection list to specific devices . . . . . . . . . . . . . . . . . 785 Creating a media server pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785 Adding managed media servers to a media server pool . . . . . . . . . . . . . . . . . . . . . 786 Renaming a media server pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787 Deleting a media server pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787 Removing a managed media server from a media server pool . . . . . . . . . . . . . . . 788 Viewing general properties for a media server pool . . . . . . . . . . . . . . . . . . . . . . . . 788 Viewing active job and alert statistics for a media server pool . . . . . . . . . . . . . . . 789 Applying settings to all managed media servers in a pool . . . . . . . . . . . . . . . . . . . 790 Copying jobs instead of delegating jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791 Requirements for duplicate backup data and synthetic backup jobs in CASO . . . . 792 How centralized restore works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
23
How CASO restores data that resides on multiple devices . . . . . . . . . . . . . . . . . . 793 Best practices for centralized restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795 Restoring from the central administration server . . . . . . . . . . . . . . . . . . . . . . . . . 796 Administering managed media servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797 Managing jobs in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800 Recovering failed jobs in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800 Pausing and resuming a managed media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802 Displaying the actual state of a paused storage device . . . . . . . . . . . . . . . . . . . . . 803 Disabling and enabling communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803 Stopping and starting Backup Exec services for CASO . . . . . . . . . . . . . . . . . . . . . 804 Connecting to a remote managed media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 Viewing managed media server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 Disaster Recovery in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806 Appendix B. Symantec Backup Exec Advanced Open File Option . . . . . . . . . . . . . . . . . .809 About the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809 Supported snapshot technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812 Requirements for using Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . 813 Installing the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814 Installing and uninstalling the Advanced Open File Option to remote windows computers using the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815 Setting defaults for the Advanced Open File Option for backup jobs . . . . . . . . . . . . 816 Using Snap Start on a Veritas Storage Foundation volume . . . . . . . . . . . . . . . . . 821 Best practices for using the Symantec Volume Snapshot Provider . . . . . . . . . . 822 Symantec Volume Snapshot Provider cache file location . . . . . . . . . . . . . . . . . . . 822 Adjusting the Symantec Volume Snapshot Provider cache file size . . . . . . . . . . 824 Changing the default settings for the Symantec Volume Snapshot Provider . . . . . 824 Checking the job log when using AOFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828 Appendix C. Symantec Backup Exec Advanced Disk-based Backup Option . . . . . . . . . .831 Installing the Advanced Disk-based Backup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
About the synthetic backup feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832 What you can back up with synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834 Requirements for synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835 Best practices for synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836 Collecting additional information for synthetic backup and true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837 Creating a synthetic backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838 Creating a synthetic backup by using the Policy Wizard . . . . . . . . . . . . . . . . . . . . 838 Creating a synthetic backup by copying the example policy . . . . . . . . . . . . . . . . . 839 Creating a synthetic backup by adding templates to a policy . . . . . . . . . . . . . . . . 840 About true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846 Requirements for running true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849 Best practices for true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849 Creating a policy for true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850 Creating a policy for true image restore by using the Policy Wizard . . . . . . . . . . . . 851 True image catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851 Restoring a backup set enabled for true image restore . . . . . . . . . . . . . . . . . . . . . . . . . 852 Troubleshooting tips for true image restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853 About offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855 Requirements for offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857 Requirements for offhost backup when using the Veritas Storage Foundation for Windows Provider . . . . . . . . . . . . . . . . . . . . . . . . . 858 Best practices for using offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859 Browsing remote computers for installed snapshot providers . . . . . . . . . . . . . . . 860 Setting offhost backup options for a backup job . . . . . . . . . . . . . . . . . . . . . . . . . . . 861 Setting default offhost backup options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863 Configuring a GRT-enabled offhost backup for Exchange resources . . . . . . . . . . . . 865 Restoring offhost backup data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866 Troubleshooting the offhost backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867 Offhost backup failures when using VSFW as a provider . . . . . . . . . . . . . . . . . . . . 869 Offhost backup issues when using a hardware provider . . . . . . . . . . . . . . . . . . . . 870
Appendix D. Symantec Backup Exec Active Directory Recovery Agent . . . . . . . . . . . . .873 Requirements for the Active Directory Recovery Agent . . . . . . . . . . . . . . . . . . . . . . . 873 Installing the Active Directory Recovery Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875 About the Active Directory Recovery Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875 Setting default backup and restore options for the Active Directory Recovery Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876 Backing up Active Directory or ADAM/ AD LDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878 About restoring individual Active Directory and ADAM/AD LDS objects . . . . . . . . 879 Restoring individual objects from an Active Directory backup . . . . . . . . . . . . . . 881 Restoring individual objects from an ADAM/AD LDS backup . . . . . . . . . . . . . . . 882 About recreating purged Active Directory and ADAM/AD LDS objects . . . . . . . . . . 883 Recreating purged Active Directory objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884 Recreating purged ADAM/AD LDS objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885 Resetting the Active Directory computer object account . . . . . . . . . . . . . . . . . . . 886 Appendix E. Symantec Backup Exec Remote Agent for Windows Systems . . . . . . . . . .887 Requirements for the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . . . . . 888 About installing the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . . . . . . 889 Stopping and starting the Remote Agent for Windows Systems . . . . . . . . . . . . . . . . 889 The Remote Agent Utility for Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889 Starting the Remote Agent Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891 Viewing activity on the remote computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891 Publishing the remote Windows computer to media servers . . . . . . . . . . . . . . . . 892 About the Remote Agent Utility Command Line Applet . . . . . . . . . . . . . . . . . . . . . . . 895 Using the Remote Agent Utility Command Line Applet . . . . . . . . . . . . . . . . . . . . . 898 Appendix F. Symantec Backup Exec Remote Agent for NetWare Systems . . . . . . . . . .899 Requirements for installing the Remote Agent for NetWare Systems on a NetWare server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900 About installing the Remote Agent for NetWare Systems on a NetWare server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901 Publishing NetWare servers to the NetWare agents list . . . . . . . . . . . . . . . . . . . . 901
Adding BESTART to the Autoexec.ncf file on the NetWare server . . . . . . . . . . . 903 Unloading the Remote Agent for NetWare Systems . . . . . . . . . . . . . . . . . . . . . . . . 903 About backing up NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904 About backing up the NetWare Directory Services (NDS) . . . . . . . . . . . . . . . . . . . 905 Backing up NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907 About restoring NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 Restoring NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 Setting default options for the Remote Agent for NetWare Systems . . . . . . . . . . . . 910 Saving configuration information for the NetWare server . . . . . . . . . . . . . . . . . . . . . 912 Disaster recovery of NetWare servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913 Appendix G. Symantec Backup Exec Remote Agent for Linux or UNIX Servers . . . . . . 915 Requirements for the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . . . . . . 916 Installing the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . . . . . . . . . . . . . 917 About creating the beoper group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917 Installing Remote Agent for Linux or UNIX Servers by using the installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918 Installing Remote Agent for Linux or UNIX Servers using the SSH (Secure Shell) protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920 Publishing Linux and UNIX hosts to a media server . . . . . . . . . . . . . . . . . . . . . . . . . . . 922 About editing the ralus.cfg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922 About ralus.cfg format components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922 About file and directory exclusions in ralus.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923 Creating a Linux or UNIX logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924 Backing up Linux and UNIX servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925 About protecting Novell Open Enterprise Server components on SUSE Linux Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927 Requirements for Novell Open Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . 928 Backing up OES components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928 Restoring Novell OES components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929 Setting Linux/UNIX properties for Remote Agent restore jobs . . . . . . . . . . . . . . 929
27
Uninstalling the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . . . . . . . . . . 930 Manually uninstalling the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . 931 Manually starting the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . . . . . 932 Manually stopping the Remote Agent for Linux or UNIX Server daemon . . . . . . . . 933 Troubleshooting the Remote Agent for Linux or UNIX Servers . . . . . . . . . . . . . . . . . 933 Appendix H. Symantec Backup Exec Remote Agent for Macintosh Systems . . . . . . . .935 Requirements for the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . 936 Installing the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . . . . . . . . 936 Installing the Remote Agent for Macintosh Systems using the installation script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937 Installing the Remote Agent for Macintosh Systems by using the SSH (Secure Shell) protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938 Publishing Macintosh computers to a media server . . . . . . . . . . . . . . . . . . . . . . . . 940 About editing the ralus.cfg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940 About ralus.cfg format components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941 About file and directory exclusions in ralus.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942 Creating a Macintosh logon account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942 Backing up Macintosh computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943 Uninstalling the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . . . . . 945 Manually starting the Remote Agent for Macintosh Systems daemon . . . . . . . 946 Manually stopping the Remote Agent for Macintosh Systems daemon . . . . . . . 947 Troubleshooting the Remote Agent for Macintosh Systems . . . . . . . . . . . . . . . . . . . 947 Appendix I. Backup Exec Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . . . . .949 How the Desktop and Laptop Option Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949 Before you install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952 System Requirements for the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . 955 Installing the Backup Exec Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . 956 Desktop Agent Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958 Preparing for a Manual Push Deployment of the Desktop Agent . . . . . . . . . . . . 960
28
Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962 Setting a Recovery Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962 Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962 Changing DLO Service Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964 About Administrator Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965 DLO Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969 Configuring DLO to Use a Specific Port for Database Access . . . . . . . . . . . . . . . . 974 Using Backup Exec Retrieve With DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975 Updating DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976 Updating the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976 Updating the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977 About upgrading to Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979 Upgrading From NetBackup Professional to DLO . . . . . . . . . . . . . . . . . . . . . . . . . . 979 Using the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982 Showing the Task Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983 Using the DLO Overview View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983 Connecting to DLO on a different Backup Exec Media Server . . . . . . . . . . . . . . . . . . . 985 Configuring DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987 About DLO Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988 Creating a New Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988 Copying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000 Modifying a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001 About Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001 Default Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 Adding a Backup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004 Defining General Backup Selection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005 Including and Excluding Files or Folders from a Backup Selection . . . . . . . . . . 1006 Revision Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008 Setting Options for a Backup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010 Using DLO Macros in Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
Modifying a Backup Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014 Deleting Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015 Using Delta File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016 Enabling Delta File Transfer for a Backup Selection . . . . . . . . . . . . . . . . . . . . . . 1017 Adding a new Maintenance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017 Configuring a Maintenance Server for Delegation . . . . . . . . . . . . . . . . . . . . . . . . 1018 Changing the Default Maintenance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020 Reassigning a File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020 About DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021 Supported Storage Location Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021 Using Hidden Shares as Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022 Creating DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023 Configuring a Remote Windows Share or NAS Device for DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025 Deleting DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027 About Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027 Creating Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028 Modifying Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030 Changing the Priority of Automated User Assignments . . . . . . . . . . . . . . . . . . . 1031 Viewing Automated User Assignment Properties . . . . . . . . . . . . . . . . . . . . . . . . . 1031 Deleting Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032 Configuring Global Exclude Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032 Specifying Files and Folders to Exclude from all Backups . . . . . . . . . . . . . . . . . . 1033 Specifying Email to Exclude from All Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034 Specifying Files and Folders to Exclude from Compression . . . . . . . . . . . . . . . . 1036 Specifying Files and Folders to Exclude from Encryption: . . . . . . . . . . . . . . . . . 1037 Specifying Files and Folders to Exclude from Delta File Transfer . . . . . . . . . . . 1038 Excluding Files that are Always Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039 Using DLO Macros to Define Global Excludes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040 Managing Desktop Agent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
30
Manually Creating New Network User Data Folders . . . . . . . . . . . . . . . . . . . . . . . 1041 Adding a Single Desktop User to DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042 Importing Multiple Desktop Users Who Have Existing Network Storage . . . . 1043 Modifying Desktop Agent User Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044 Enabling or Disabling DLO Access For a Desktop User . . . . . . . . . . . . . . . . . . . . . 1044 Deleting a User from DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045 Moving Desktop Agent Users to a new Network User Data Folder . . . . . . . . . . 1046 Migrating A Desktop User to a New Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047 Viewing a List of Desktop Agent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048 Managing Desktop Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048 Modifying Computer Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048 Enabling or Disabling a Desktop Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052 Deleting a Desktop Computer from DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052 Backing up a Desktop from the Administration Console . . . . . . . . . . . . . . . . . . . . . . 1053 Setting Blackout Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053 Restoring Files and Folders from the DLO Administration Console . . . . . . . . . . . . 1055 Searching for Files and Folders to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058 How to Recover DLO Servers and User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060 Recovering Data for a Single User Using DLO Emergency Restore . . . . . . . . . . 1061 Recovering Data for a Single User without Using DLO Emergency Restore . . 1062 Recovering a Damaged or Corrupt media server . . . . . . . . . . . . . . . . . . . . . . . . . . 1063 Recovering a damaged or corrupt File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063 Monitoring DLO Job Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065 Viewing the DLO Job History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065 Setting Job History View Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066 Viewing History Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068 Searching History Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069 Monitoring Alerts on the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . 1071 Configuring Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074 Managing DLO Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
Configuring Alerts for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076 Configuring Alert Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077 Configuring Recipients for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081 Configuring SMTP Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081 Configuring MAPI Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082 Configuring VIM Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084 Configuring a Pager for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085 Configuring a SNMP Trap Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088 Configuring a Net Send Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089 Configuring a Printer Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091 Configuring a Group Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092 Scheduling Notification for Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093 Editing Recipient Notification Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094 Editing Recipient Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095 Removing Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095 DLO Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096 Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097 Viewing Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098 Maintaining the DLO Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100 Clustering the Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100 DLO Command Line Interface Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103 DLO Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103 Commands in Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104 About the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121 Features and Benefits of the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121 System Requirements for the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1122 Installing the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1122 Configuring the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124 Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124 Using local accounts on desktop computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
Using Alternate Credentials for the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . 1125 Resetting Dialog Boxes and Account Information . . . . . . . . . . . . . . . . . . . . . . . . . 1127 Changing Your Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127 Disabling the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128 Enabling the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128 About the Desktop Agent Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129 Using the Desktop Agent to Back Up Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1130 Managing Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131 File Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132 Modifying Backup Selections in the Standard View . . . . . . . . . . . . . . . . . . . . . . . 1132 Adding Backup Selections in the Advanced View . . . . . . . . . . . . . . . . . . . . . . . . . . 1134 Modifying Backup Selections in the Advanced View . . . . . . . . . . . . . . . . . . . . . . . 1138 Deleting Backup Selections in the Advanced View . . . . . . . . . . . . . . . . . . . . . . . . 1139 Backing up Outlook PST files Incrementally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139 Backing Up Lotus Notes NSF Files Incrementally . . . . . . . . . . . . . . . . . . . . . . . . . 1141 Using the Desktop Agent when Lotus Notes is not Configured for the Current User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142 Deleting Lotus Notes E-mail Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142 Modifying Desktop Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142 Changing Backup Job Schedule Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143 Setting Customized Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146 Moving the Desktop User Data Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148 Customizing Connection Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149 Synchronizing Desktop User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151 How Synchronization Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152 Resolving Conflicts with Synchronized Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154 Viewing the Desktop Agent Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155 Starting a Pending Job in the Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156 Suspending or Cancelling a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156 Viewing Usage Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
33
Restoring Files Using the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159 Searching for Desktop Files to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161 Restoring Microsoft Outlook Personal Folder Files . . . . . . . . . . . . . . . . . . . . . . . . 1162 Restoring Deleted Email Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163 Restoring Files with Alternate Stream Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163 Restoring files using Backup Exec Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163 Monitoring Job History in the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164 Viewing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 Searching for Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 Log file grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Using DLO with Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Troubleshooting the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . 1168 Troubleshooting the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172 Accessibility and DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174 Glossary of Terms for DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176 Appendix J. Symantec Backup Exec Agent for Microsoft Exchange Server . . . . . . . . 1179 About the Backup Exec Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179 Requirements for using the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180 Installing the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183 Recommended configurations for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183 Exchange mailbox access requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185 Backup strategies for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186 Automatic exclusion of Exchange data during volume-level backups . . . . . . . 1189 Reviewing the circular logging setting for Exchange . . . . . . . . . . . . . . . . . . . . . . 1189 About using GRT-enabled backups to restore individual items from the Information Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1190 Snapshot and offhost backups with the Exchange Agent . . . . . . . . . . . . . . . . . . . . . 1191 Troubleshooting Exchange Agent snapshot and offhost jobs . . . . . . . . . . . . . . . 1193 Configuring a snapshot backup for Exchange resources . . . . . . . . . . . . . . . . . . . 1195
Configuring an offhost backup with the Exchange Agent . . . . . . . . . . . . . . . . . . 1196 About continuous protection for Exchange data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197 Requirements for installing components for CPS Exchange backup jobs . . . . 1198 Requirements for configuring continuous protection for Exchange data . . . . 1200 Best practices for continuous protection of Exchange . . . . . . . . . . . . . . . . . . . . . . . . 1202 About managing the CPS Exchange backup job for Exchange data . . . . . . . . . . 1203 Review disk space availability for CPS Exchange backup jobs . . . . . . . . . . . . . . 1204 Temporarily stopping CPS Exchange backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . 1204 Viewing the CPS console from Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205 About using recovery points to restore individual items to a point in time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206 Troubleshooting CPS Exchange backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207 Setting default backup and restore options for Exchange data . . . . . . . . . . . . . . . . 1207 Backing up Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211 About selecting individual mailboxes for backup . . . . . . . . . . . . . . . . . . . . . . . . . . 1217 Backing up individual Exchange mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219 About restoring Exchange data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223 Requirements for restoring Exchange 2000, 2003, and 2007 . . . . . . . . . . . . . . . 1224 Requirements for restoring Exchange Server 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . 1224 About restoring Exchange 2003 and Exchange 2007 data using the recovery storage group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225 About restoring Exchange data from snapshot backups . . . . . . . . . . . . . . . . . . . 1227 Restoring Exchange data from continuous protection backups . . . . . . . . . . . . . 1228 About restoring individual items from Information Store backups . . . . . . . . . . 1229 About restoring Exchange mailboxes and public folders from mailbox backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230 Restoring Exchange data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1232 About redirecting Exchange restore data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238 About redirecting Exchange storage group and database restores . . . . . . . . . . 1238 About redirecting Exchange Server 5.5 database restores . . . . . . . . . . . . . . . . . . 1239 About redirecting restores of mailboxes or public folders
that were backed up separately from the Information Store . . . . . . . . . . . . . . . 1240 Redirecting Exchange restore data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1242 Preparing for disaster recovery of Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . 1245 Disaster recovery for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246 Disaster recovery for Exchange Server 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248 Appendix K. Symantec Backup Exec Agent for Microsoft SharePoint . . . . . . . . . . . . 1251 Requirements for the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252 Installing the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252 Using the SharePoint Agent with SharePoint Portal Server 2001 . . . . . . . . . . . . . . 1253 Backing up SharePoint Portal Server 2001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254 Backing up the SharePoint Portal Server database . . . . . . . . . . . . . . . . . . . . . . . . 1254 Backing up folders and documents from a SharePoint Portal workspace . . . . 1255 About restoring SharePoint Portal Servers and SharePoint Portal workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255 Restoring a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256 Restoring a SharePoint Portal workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256 Restoring previous versions of documents from workspace backups . . . . . . . 1257 Redirecting SharePoint Portal Server restore jobs . . . . . . . . . . . . . . . . . . . . . . . . 1258 Redirecting restored workspace data to another workspace . . . . . . . . . . . . . . . 1259 Redirecting restored workspace data to a file path . . . . . . . . . . . . . . . . . . . . . . . . 1260 Disaster recovery of a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1260 Uninstalling and reinstalling the SharePoint Portal Server software . . . . . . . 1262 Best practices for SharePoint Portal Server 2001 . . . . . . . . . . . . . . . . . . . . . . . . . 1262 Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263 Selecting SharePoint resources for backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1263 Adding a server farm to the backup selections list . . . . . . . . . . . . . . . . . . . . . . . . 1264 Disabling or enabling communication between a Web server and Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1265 Changing the name of a farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266
36
Deleting a farm from the Microsoft SharePoint Server Farms node . . . . . . . . . 1266 Backing up SharePoint resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1267 About selecting SharePoint resources for restore . . . . . . . . . . . . . . . . . . . . . . . . . 1268 Restoring SharePoint resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269 Restoring SharePoint document libraries (Web storage system-based) . . . . . . 1271 Restoring previous versions of documents from document library (Web storage system-based) backups . . . . . . . . . . . . . . . . . . . . 1271 Restoring individual documents (Microsoft SQL Server-based) from full database backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1272 Redirecting a restore job for SharePoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273 Redirecting the restore of document library (Web storage system-based) data to another document library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274 Redirecting the restore of individual documents to a file path . . . . . . . . . . . . . . 1275 Setting default options for SharePoint Portal Server 2003 and later . . . . . . . . 1276 About using the SharePoint Agent with SharePoint Server 2007 and Windows SharePoint Services 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278 About adding a server farm to the backup selections list . . . . . . . . . . . . . . . . . . . 1280 Backing up a Microsoft Office SharePoint Server 2007 or a Windows SharePoint Services 3.0 farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280 Backing up individual Web applications in a Windows SharePoint Services Application node . . . . . . . . . . . . . . . . . . . . . . . . . . 1281 About selecting SharePoint resources for restore . . . . . . . . . . . . . . . . . . . . . . . . . 1283 Restoring SharePoint resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283 Restoring a Microsoft Office SharePoint Server 2007 Shared Services Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285 Restoring a Microsoft Office SharePoint Server 2007 Web application to its original location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286 Restoring individual documents from full database backups to their original locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1287 Redirecting the restore of a Microsoft Office SharePoint Server 2007 Web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1288 Redirecting the restore of individual documents to a file path . . . . . . . . . . . . . . 1290
37
Appendix L. Symantec Backup Exec Agent for Lotus Domino Server . . . . . . . . . . . . . 1293 Lotus Domino Agent requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294 Installing the Lotus Domino Agent on the media server . . . . . . . . . . . . . . . . . . . . . . 1295 Viewing and selecting Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1296 Configuring default Lotus Domino options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298 Backing up Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299 Automatic exclusion of files during volume-level backups . . . . . . . . . . . . . . . . . 1299 Supported Lotus Domino database configurations . . . . . . . . . . . . . . . . . . . . . . . . 1300 About Lotus Domino transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300 Selecting backup options for Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . 1301 Restoring Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1303 Selecting Lotus Domino databases for restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304 Selecting restore options for Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . . . 1306 Redirecting restore jobs for Lotus Domino databases . . . . . . . . . . . . . . . . . . . . . 1307 Preparing for disaster recovery on a Lotus Domino server . . . . . . . . . . . . . . . . . . . . 1308 Disaster recovery of a Lotus Domino server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1309 Disaster recovery of a Lotus Domino server using archive logging . . . . . . . . . 1310 Disaster recovery of a Lotus Domino server using circular logging . . . . . . . . . 1312 Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313 Appendix M. Symantec Backup Exec Agent for Microsoft SQL Server . . . . . . . . . . . . 1315 Requirements for using the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317 Installing the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317 About using Backup Exec logon accounts for SQL resources . . . . . . . . . . . . . . . . . . 1317 Backup strategies for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319 Consistency checks for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1322 Using snapshot technology with the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323 Using AOFO with the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324 Using the ADBO with the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1325 Setting backup options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326
38
Automatic exclusion of files during volume level backups . . . . . . . . . . . . . . . . . 1331 Backing up SQL databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1331 About backing up SQL filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333 Displaying filegroups on the backup selections pane . . . . . . . . . . . . . . . . . . . . . . 1334 Backing up SQL filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334 Backing up SQL transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336 About SQL 2005 database snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337 Creating database snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1339 Setting restore options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340 About restoring SQL databases and filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344 Restoring from SQL database backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345 Restoring from SQL transaction logs up to a point in time . . . . . . . . . . . . . . . . . 1346 Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347 Restoring from SQL filegroup backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348 Restoring the entire database, a missing primary filegroup, or a filegroup containing a deleted or changed table . . . . . . . . . . . . . . . . . . . . . . 1350 Restoring a missing or corrupted nonprimary filegroup . . . . . . . . . . . . . . . . . . . 1351 Restoring the SQL master database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1352 Redirecting restores for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354 Reverting SQL 2005 databases using database snapshots . . . . . . . . . . . . . . . . . . 1359 Setting default backup and restore options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . 1361 Preparing for disaster recovery of SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367 How to prepare for disaster recovery of SQL 2000 or SQL 2005 . . . . . . . . . . . . . 1367 How to prepare for disaster recovery of SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . 1368 Requirements for SQL disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1368 Creating copies of the SQL 7.0 master and model databases . . . . . . . . . . . . . . . . 1369 Disaster recovery of SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1369 Recovering SQL manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1370
39
Appendix N. Symantec Backup Exec Agent for Oracle on Windows or Linux Servers . . . . 1375 About the Backup Exec Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375 Installation and configuration requirements for the Oracle Agent . . . . . . . . . . . . 1376 Configuring the Oracle Agent on Windows computers . . . . . . . . . . . . . . . . . . . . . . . 1377 Configuring the Oracle Agent on Linux computers . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382 Configuring database access on the media server for Oracle operations . . . . . . . . 1386 Editing an Oracle server name or logon account on the media servers list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . . . . . 1387 Deleting an Oracle server name or logon account from the media servers list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . 1388 About upgrading the Backup Exec Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1389 What to do when Oracle instance information changes . . . . . . . . . . . . . . . . . . . . . . 1390 About backing up Oracle resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1390 About backing up Oracle RAC resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391 Backing up Oracle resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392 About performing a DBA-initiated backup job for Oracle . . . . . . . . . . . . . . . . . . 1394 Configuring DBA-initiated job settings for Oracle . . . . . . . . . . . . . . . . . . . . . . . . 1396 Deleting a job template for DBA-initiated jobs for Oracle . . . . . . . . . . . . . . . . . . 1397 Setting application defaults for Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398 About restoring and recovering Oracle resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1399 About DBA-initiated restore and recovery for Oracle . . . . . . . . . . . . . . . . . . . . . . . . 1401 Restoring Oracle data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1401 Redirecting a restore of Oracle data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405 Restoring from a legacy GRFS Oracle Agent database backup . . . . . . . . . . . . . . . . . 1407 Troubleshooting the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408 Disaster recovery of the Oracle instance or database . . . . . . . . . . . . . . . . . . . . . . . . . 1410 Disaster recovery scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1411 Disaster recovery scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413
40
Appendix O. Symantec Backup Exec Agent for SAP Applications . . . . . . . . . . . . . . . . . 1417 About the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418 How the SAP Agent works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418 About using the SAP Agent with RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1419 Requirements for using the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1420 About installing the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421 About SAP Agent security and privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422 About encrypting SAP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1422 Generating alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423 About preserving the integrity of the SAP Agent catalog . . . . . . . . . . . . . . . . . . 1423 Before backing up SAP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424 Configuring biparam.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425 Configuring DBA-initiated job settings for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426 About system level backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428 About backing up and restoring with the SAP Agent . . . . . . . . . . . . . . . . . . . . . . . . . 1428 Requirements for submitting jobs from remote computers . . . . . . . . . . . . . . . . 1429 Restoring data with BRRESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429 About redirecting SAP restore jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429 Backing up with RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1430 Restoring with RMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1432 Migrating the SAP Agent catalog from _backint.mdb to _backint.xml . . . . . . . . . . 1433 Backing up a clustered SAP database on Microsoft Cluster Server . . . . . . . . . . . . . 1434 Backing up MaxDB databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435 Restoring MaxDB databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1436 About performing disaster recovery using the SAP Agent . . . . . . . . . . . . . . . . . . . . 1437 SAP disaster recovery prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1437 Recovering a remote SAP database server from a disaster . . . . . . . . . . . . . . . . . 1438 Recovering a combination SAP database server and media server . . . . . . . . . . 1439
41
Appendix P. Symantec Backup Exec Agent for DB2 on Windows Servers . . . . . . . . . 1441 About the Backup Exec DB2 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1441 Installation and configuration requirements for the DB2 Agent . . . . . . . . . . . . . . . 1442 Configuring the DB2 Agent on Windows computers . . . . . . . . . . . . . . . . . . . . . . 1443 Configuring database access on the media server for DB2 operations . . . . . . . 1448 Editing a DB2 server name or logon account on the media servers list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . . . . . 1449 Deleting a DB2 server name or logon account from the media servers list of authentication credentials . . . . . . . . . . . . . . . . . . . . . . . . . . 1450 Backing up DB2 resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451 About DBA-initiated jobs for DB2 operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453 Using the DB2 database archive logging methods . . . . . . . . . . . . . . . . . . . . . . . . . 1455 About the db2.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456 Editing a db2.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456 Example db2.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457 Configuring DBA-initiated job settings for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1459 Deleting a job template for DBA-initiated jobs for DB2 . . . . . . . . . . . . . . . . . . . . 1460 Setting application defaults for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461 Restoring DB2 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1462 Redirecting a restore of DB2 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464 About troubleshooting DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467 Appendix Q. Symantec Backup Exec Agent for Enterprise Vault . . . . . . . . . . . . . . . . . 1469 About the EV Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469 EV Agent notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1471 About installing the EV Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1471 About the EV Agent and the Backup Selections pane . . . . . . . . . . . . . . . . . . . . . . . . . 1472 About selecting a backup method for Enterprise Vault backup jobs . . . . . . . . . . . . 1473 Setting a default backup method for Enterprise Vault backup jobs . . . . . . . . . 1474 Backing up an open partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1475 Backing up vault store closed partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1476
Backing up the Directory database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477 Backing up the Monitoring database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478 Backing up a vault store database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479 Backing up a vault store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1480 Backing up an Enterprise Vault server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1481 Backing up an Enterprise Vault site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1482 Backing up index locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1483 About restoring Enterprise Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485 About automatic redirection of Enterprise Vault components under an Enterprise Vault server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486 Restoring the Directory database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486 Restoring the Monitoring database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487 Restoring an open partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1489 Restoring a closed partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490 Restoring a vault store database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1491 Restoring index locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1492 Restoring an Enterprise Vault server to its original location . . . . . . . . . . . . . . . 1493 Redirecting an Enterprise Vault restore job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1494 Redirecting the restore of the Directory database to a different Microsoft SQL Server computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496 Appendix R. Symantec Backup Exec Intelligent Disaster Recovery Option . . . . . . . . 1499 Requirements for using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1500 Installing the IDR option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501 Using an evaluation version of the IDR option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501 Preparing computers for IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1502 Getting started with IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503 Manually setting data paths for the *.dr files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504 About creating and updating recovery media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1507 Requirements for running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . 1508 About running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508
About creating recovery media after a disaster . . . . . . . . . . . . . . . . . . . . . . . . . . . 1509 Creating the Intelligent Disaster Recovery nonbootable CD image only . . . . . 1513 Updating bootable media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515 Copying the disaster recovery files to a diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516 Preparing IDR media by using other media servers . . . . . . . . . . . . . . . . . . . . . . . 1518 About preparing to recover from a disaster by using IDR . . . . . . . . . . . . . . . . . . . . . 1519 About changing hardware in the computer to be recovered . . . . . . . . . . . . . . . . 1520 About using IDR to recover IBM computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521 About recovering a computer and using the Disaster Recovery Wizard . . . . . . . . 1522 About encrypted backup sets and the Disaster Recovery Wizard . . . . . . . . . . . 1522 Performing an automated restore by using the Disaster Recovery wizard . . . 1523 Installing network drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1530 About altering hard drive partition sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1531 Performing a manual restore by using the Disaster Recovery Wizard . . . . . . . 1531 About Microsoft SQL Server recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534 About Microsoft Exchange recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534 About SharePoint Portal Server recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . 1534 About Citrix Metaframe recovery notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535 About using IDR with the Central Admin Server Option . . . . . . . . . . . . . . . . . . . 1535 About using IDR with Veritas Storage Foundation for Windows . . . . . . . . . . . . 1535 Best Practices for IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536 Appendix S. Symantec Backup Exec Library Expansion Option . . . . . . . . . . . . . . . . . . 1537 Setting up robotic library hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538 Configuring multi-drive robotic libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538 Installing the Library Expansion Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539 Starting Backup Exec after installing the Library Expansion Option . . . . . . . . . . . 1540 Viewing robotic libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541 Appendix T. Symantec Backup Exec SAN Shared Storage Option . . . . . . . . . . . . . . . . 1545 Requirements for the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
Installing the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548 About devices in the shared storage environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549 Monitoring drives in the shared storage environment . . . . . . . . . . . . . . . . . . . . . 1550 Viewing media in the shared storage environment . . . . . . . . . . . . . . . . . . . . . . . . 1550 Using drive pools with the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . 1551 Using device operations with the SAN Shared Storage Option . . . . . . . . . . . . . . 1552 Sharing robotic libraries between Backup Exec for NetWare Servers and Backup Exec for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553 Scheduling and viewing jobs in a SAN SSO environment . . . . . . . . . . . . . . . . . . . 1557 Sharing media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558 Cataloging media in SAN SSO environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558 Media rotation in SAN SSO environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1559 Designating a new database server and setting up servers . . . . . . . . . . . . . . . . . . . . 1559 Tips for maintaining the database server and the ADAMM database . . . . . . . . 1560 Creating a standby primary database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1560 Starting and stopping Backup Exec Services on multiple servers . . . . . . . . . . . 1562 Reconfiguring the SAN SSO Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562 Troubleshooting and recovering failed components . . . . . . . . . . . . . . . . . . . . . . . . . . 1563 Checklist for troubleshooting devices that have gone offline . . . . . . . . . . . . . . . 1563 Resetting the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565 Bringing devices online after an unsafe device removal event . . . . . . . . . . . . . . 1565 Best practices for SAN SSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1566 Appendix U. Symantec Backup Exec NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569 Requirements for using the NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569 About installing the NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1570 Configuring Backup Exec to use the NDMP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 1570 Backing up NDMP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1571 Restoring NDMP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573 Setting default backup and restore options for NDMP . . . . . . . . . . . . . . . . . . . . . . . . 1574 Viewing NDMP server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576
Appendix V. Accessibility and Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577 Keyboard navigation and shortcuts in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . 1578 General keyboard navigation within the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578 Keyboard navigation within dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1579 Keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1580 Support for accessibility settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595
46
Chapter
Introducing Backup Exec
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 the following configurations that can accommodate multi-platform networks of all sizes.
Table 1-1 Backup Exec configurations for multiple platforms Description Installs on and protects many Microsoft operating systems. See System requirements on page 69. The Backup Exec suite includes agents and options for backing up and restoring data on heterogeneous networks of all sizes. See Backup Exec agents and options on page 53. Backup Exec workstation agent software protects unlimited remote workstations that run on Windows XP/2000 Professional. 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.
Backup Exec Edition Symantec Backup ExecTM for Windows Servers
47
Table 1-1
Backup Exec configurations for multiple platforms (continued) Description Supports Microsoft Small Business Server for Windows 2000/2003 R2 Standard and Premium Editions. SBSE also includes Backup Exec agent software for the workstations that run on Windows 2000/XP Professional. The Standard Edition includes the following Backup Exec agents and options:

Backup Exec Edition Small Business Server Editions (SBSE)
Exchange Agent Intelligent Disaster Recovery Option Advanced Open File Option Desktop and Laptop Option
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. The Premium Edition includes the Standard Edition agents and options. It also includes the SQL Server Agent. All other agents and options that are offered in the Backup Exec suite are also available for purchase with SBSE. QuickStart Edition (QSE) (OEM release only) Installs on and protects any supported version of Microsoft Windows Server 2000/2003. Also includes Backup Exec agent software for the workstations that run on Windows 2000/XP Professional. 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.
Related Topics: Whats new in Backup Exec on page 49 Whats new in the Advanced Disk-based Backup Option on page 52 Whats new in the Desktop and Laptop Option on page 52 Backup Exec agents and options on page 53. How Backup Exec works on page 59
48
Whats new in Backup Exec

This release of Backup Exec includes the following new features and capabilities:
Table 1-2 New feature Support for Microsoft Windows Server 2008 New features and capabilities in Backup Exec Description Lets you do the following:
Back up and restore the Internet Information Services (IIS), encrypted volumes, compressed volumes, and terminal services. Back up and restore Active Directory, which includes Read-only domain controllers (RODC), and restartable Active Directory domain services. Protect NTFS for Windows Server 2008. Use the Windows Server 2008 new implementation of Next Generation TCP/IP networking. Support the Windows Limited User Access mode. To comply with Windows security, you may be prompted for Administrator privileges to access some restricted components. This prompting can occur if you are not logged in as an administrator on Windows Vista/Server 2008 when you use the Backup Exec user interface. Use the volumes that run Windows BitLocker Drive Encryption.
Support for the Server Core installation option of Windows Server 2008
Lets you install the Backup Exec Remote Agent for Windows Systems on the Server Core installation for backup and restore operations. The Remote Agent also installs the Remote Agent Utility command line applet. This applet lets you monitor Backup Exec operations on the remote computer. See Installing Backup Exec options to remote computers on page 82. See About the Remote Agent Utility Command Line Applet on page 895.
VSS snapshot availability for Performs a VSS snapshot backup for volume resource data on Windows Vista/Server 2008 Windows Vista/Server 2008. You are not required to configure the volumes snapshot or to enter a license key for the Advanced Open File Option (AOFO). Note You must enter an AOFO license key to perform AOFO-related operations and configuration on operating systems other than Windows Vista/Server 2008.
Chapter 1, Introducing Backup Exec
49
Whats new in Backup Exec Table 1-2 New feature New features and capabilities in Backup Exec Description
Support for Microsoft Virtual Backs up Virtual Server data by using Microsofts Volume Shadow Server Copy Service (VSS). Backup Exec takes a snapshot of the Virtual Server Host while applications and services run. The host in turn takes snapshots of all the guest virtual machines it contains. See About backing up virtual machines and the Virtual Server Host on page 260. Support for the T10 hardware encryption standard Support for hardware failure trending Provides additional options to secure your data. See About hardware encryption on page 331. Provides a new report named Media Errors. You can use this report to detect a failing tape or tape device. See Media Errors Report on page 637. Support for larger block sizes Provides the ability to choose a block size that is larger than 64K for select tape devices for select tape devices. This support may increase performance in the devices that are designed to support this capability. See Viewing a devices configuration properties on page 346. Simplified installation wizard Provides a simpler wizard to add license keys, to evaluate options, and to install options. You can add license keys or evaluate Backup Exec agents and options at any time after the core product has been licensed. Each agent and option has its own independent evaluation period. When an agent or options evaluation period is about to expire, Backup Exec warns you with an alert. You can also view which agents and options are available for evaluation and how much time is left in each individual evaluation period. See Evaluating Backup Exec agents and options on page 112. See Viewing license information on page 120. See Adding licenses on page 122. Integrated Symantec Endpoint Protection Lets Symantec Endpoint Protection users monitor the Security Summary in the Backup Exec Job Monitor. You can configure Backup Exec to automatically back up important data when the Symantec ThreatCon level is elevated. See Viewing the Symantec Endpoint Protection Security Summary on page 485. See About using Backup Exec with Symantec Endpoint Protection on page 324.
50
Whats new in Backup Exec Table 1-2 New feature Links to the Symantec Technical Support Web site from alerts New features and capabilities in Backup Exec Description Provides access to the technical notes that are related to alerts. A Unique Message Identifier (UMI) code, which is a hyperlink to the Symantec Technical Support Web site, appears on some alerts. See Responding to active alerts on page 545. History of operations on each Lists all of the media that is required for a restore job. Additional media device and media audit log categories are enabled for the audit log by default. See Auditing media operations on page 190. Improved Calendar view Provides the following new features on the Calendar tab on the Job Monitor:
The month and week views list job counts and job instances. You can see at a glance what the scheduled work load may be for any day. The day view provides a graphical view of the scheduled work load, and lists jobs for that day in chronological order. A preview pane provides more information for each job. This information includes the final status, the rate and byte count for job histories, and when the next run of a scheduled job occurs.
See Viewing the job workload for a media server from the Calendar tab on page 483. Agent for Enterprise Vault Provides robust data protection for key Enterprise Vault items such as sites, servers, databases, indexes, and vault partitions. The Enterprise Vault Agent can help provide a disaster recovery solution for Enterprise Vault archived data. Recovery of the archived data is not dependent on the archive source, such as Exchange Server or a specific file system. See About the EV Agent on page 1469.
Related Topics: Whats new in the Advanced Disk-based Backup Option on page 52 Whats new in the Desktop and Laptop Option on page 52 Backup Exec agents and options on page 53
51
Whats new in the Advanced Disk-based Backup Option

You can enable the Backup Exec Granular Recovery Technology (GRT) option for offhost backups of Exchange resources. When you select the GRT option for a backup, Backup Exec collects additional information for the catalog. This information lets you restore individual mailboxes, mail messages, and public folders from Information Store backups. See Configuring a GRT-enabled offhost backup for Exchange resources on page 865.
Whats new in the Desktop and Laptop Option

The Desktop and Laptop Option includes the following enhancements:
Table 1-3 New feature Support for Microsoft Windows Server 2008 Desktop and Laptop Option enhancements Description Lets you install the DLO Administration Console on a computer that runs Microsoft Windows Server 2008. In addition, the following services can run on a computer where Windows Server 2008 is installed:

DLO Administration Server DLO Maintenance Server
Support for Microsoft Windows Vista
Lets you install both the Desktop Agent and the Change Log Service on a computer that runs Microsoft Windows Vista. You can run the DLO Administration Console on a computer that meets the following criteria:

Runs Microsoft Windows Vista Runs the Backup Exec Remote Administration Console
Then, you can use the DLO Administration Console to connect to a Backup Exec and DLO media server. New pre-defined folders for backup selections Accommodates the following folders in the Windows Vista Backup Selections dialog box:

Pictures Music Video
52
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 53 Groupware agents on page 56 Online database agents on page 57 Disaster recovery option on page 58 Storage options on page 58
Media server options

The following options allow greater control of storage resources and alternate backup techniques on Backup Exec media servers.
Table 1-4 Option Symantec Backup Exec Central Admin Server Option Backup Exec media server options Description 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 How CASO works on page 743. Symantec Backup Exec Advanced Open File Option 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 About the Advanced Open File Option on page 809.
53
Backup Exec agents and options Table 1-4 Option Backup Exec media server options (continued) Description
Symantec Backup Exec Advanced Provides the following features: Disk-based Backup Option (ADBO) Synthetic backup assembles, or synthesizes, data from one previous full or incremental backup and subsequent incremental backups. This feature eliminates the need to run full backups. 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.
True image restore enables Backup Exec to restore the contents of directories to what they were at the time of a full backup or incremental backup. You choose restore selections from a view of the directories as they existed at the time of the backup. Files that were deleted before then are not restored. Only the correct versions of files are restored from the appropriate full or incremental backups. Previous versions are not restored and then overwritten.
Offhost backup moves the backup operation away from the remote computer to a Backup Exec media server in a fiber-connected SAN environment. When the backup is moved to the media server, the remote computer is free for other operations. Offhost backup for Exchange Server backups that have the Granular Recovery Technology (GRT) option enabled are also supported.
See Whats new in the Advanced Disk-based Backup Option on page 52. See About the synthetic backup feature on page 832. See About true image restore on page 846. See About offhost backup on page 855. Symantec Backup Exec Active Directory Recovery Agent (ADRA) Lets you restore the objects and attributes from the following Microsoft applications without having to perform an authoritative or non-authoritative full restores:

Active Directory Active Directory Application Mode Active Directory Lightweight Directory Services
See About the Active Directory Recovery Agent on page 875.
54
Client protection options

The following 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.
Table 1-5 Option Symantec Backup Exec Remote Agent for Windows and NetWare Systems Backup Exec client protection options Description 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 About backing up NetWare servers on page 904. Symantec Backup Exec Remote Agent for Linux or Unix Servers (RALUS) Lets Windows Server network administrators perform backup and restore operations on Linux and Unix 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 Backing up Linux and UNIX servers on page 925. Remote Agent for Macintosh Systems Enables Windows Server network administrators to perform backup and restore operations on Macintosh computers that are connected to the network. See Backing up Macintosh computers on page 943. Symantec Backup Exec Desktop and Laptop Option 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 Whats new in the Desktop and Laptop Option on page 52. See How the Desktop and Laptop Option Works on page 949.
55
Groupware agents
The following Groupware agents provide non-disruptive protection for corporate email messaging and knowledge base applications.
Table 1-6 Agent Symantec Backup Exec Agent for Microsoft Exchange Server Backup Exec groupware agents Description Provides backups for your Exchange Server data. You can restore individual mailboxes, mail messages, and public folders from the Information Store backups that have Backup Execs Granular Recovery Technology (GRT) option enabled. Use Backup Exec Continuous Protection Server (CPS) to provide complete recovery to any point in time of the Information Store, including the latest complete transaction log. See About the Backup Exec Exchange Agent on page 1179. Symantec Backup Exec Microsoft Agent for SharePoint Protects all of the files and attributes associated with a SharePoint installation. You can use the GRT option to restore individual workspaces and documents from a backup of the entire farm. You can restore data to the original Information Store or redirect it to another Information Store without affecting other workspaces. See Using the SharePoint Agent with SharePoint Portal Server 2001 on page 1253. See Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services on page 1263. Symantec Backup Exec Agent for Lotus Domino Server Provides seamless online backup protection for Lotus Domino servers. The Lotus Agent uses Lotus Domino APIs to support transactional logging, which protects the entire Lotus Domino server. See Symantec Backup Exec Agent for Lotus Domino Server on page 1293.
56
Online database agents

The following options allow for protection and recovery of mission-critical database applications.
Table 1-7 Agent Symantec Backup Exec Agent for Microsoft SQL Server Backup Exec online database agents Description Protects active databases and verifies all of your SQL data automatically. You can customize your 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 Backup strategies for SQL on page 1319. Symantec Backup Exec Agent for Oracle on Windows and Linux Servers Provides the ability to initiate backup and restore operations from Backup Exec or from the RMAN console as a Database Administrator (DBA). 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 About the Backup Exec Oracle Agent on page 1375. Symantec Backup Exec Agent for SAP Applications 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 About backing up and restoring with the SAP Agent on page 1428. Symantec Backup Exec Agent for DB2 on Windows Servers 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 About the Backup Exec DB2 Agent on page 1441. Symantec Backup Exec Agent for Enterprise Vault Provides a disaster recovery solution for Enterprise Vault archived data. Recovery of the archived data is not dependent on the archive source, such as Exchange Server or a specific file system.
57
Disaster recovery option

Backup Execs Intelligent Disaster Recovery Option (IDR) provides a recovery solution for both local and remote Windows computers. This option eliminates the need to manually re-install the entire operating system after a computer failure. IDR lets you use diskettes, CD-R/CD-RW, or bootable tape to restore from your last complete backup set to get back online fast. See Getting started with IDR on page 1503.
Storage options
The following options allow you to extend Backup Execs capabilities to use larger media storage devices or share storage resources over a SAN.
Table 1-8 Option Symantec Backup Exec Library Expansion Option (LEO) Backup Exec storage agents Description 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 Installing the Library Expansion Option on page 1539. Symantec Backup Exec SAN Shared Storage Option (SAN SSO) 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 Installing the SAN Shared Storage Option on page 1548. 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 devices. See About installing the NDMP Option on page 1570
58
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 computer. After jobs are created, the Backup Exec server components on the media server process the jobs. All interaction with Backup Exec, such as submitting jobs, viewing results, and performing device and media operations, is done through the Administration Console.
Backup and restore functionality for the entire network Tape storage Disk or NAS Backup-to-disk folders, storage arrays, or network-attached storage provides fast backups and restores. Tape drives or libraries provide long term storage, disaster recovery, and a method for archiving data.
Backup Exec media server
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.
Desktops & laptops (local or remote) Protect the critical business information that is not contained on corporate servers.
59
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 jobs progress through the Job Monitor, or use Backup Execs 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 Execs 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 medias 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 jobs results are stored in a job history database. A record of the data that was backed up is kept in Backup Execs 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.
60
Chapter
Installing Backup Exec
Several methods are available for installing Backup Exec. You can do the following:

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. 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, 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 do the following:
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.
61
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. Check the computer name of the computer on which you want to install Backup Exec. It should only use standard ANSI characters. You may receive errors if you install Backup Exec on a computer with a name that uses non-standard characters. You should only use hostnames that are visible to the Internet. 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. See System requirements on page 69. 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.
62
Before you install
One of the following results are reported for each item:

Table 2-1 Result Passed Environment Check results Description There are no incompatibilities to prevent the Backup Exec installation. For hardware, this result indicates that the hardware configuration is recognized by Backup Exec. An incompatibility with Backup Exec exists, but can be resolved during the Backup Exec installation. An incompatibility with Backup Exec exists, and it will cause the installation to fail. Action is required before you can successfully install Backup Exec.
Warning Failed
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. Click Next. Do any of the following:
To check the Check Local Environment Check. configuration of the local computer To check the Check Remote Environment Check. configuration of a remote computer
2 3
4 5
Click Next. If you checked Remote Environment Check in step 3, do one of the following:
To select the name of a computer from a list

Click Add Server From List. Select the computer from the list, and then click Next.
Chapter 2, Installing Backup Exec
63
Before you install
To add the name of a computer manually
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.
To remove the name of a computer from the list of computers on which the Environment Check runs
6 7
To save the results of the Environment Check, check Save Results To. To change the location where the Environment Check results are saved, click Change Path to browse to a new location. 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. Administrative rights (provides complete and unrestricted rights to the computer). Backup operator rights (provides rights to restore files and directories).
64
Before you install
Manage auditing and security log.
Due to security implementations in Microsoft Small Business Server, the service account must be Administrator. You cannot install Backup Exec with an account that has a blank password on Windows Server 2003/2008 or XP computers unless Windows is configured to allow it. If you try 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, however, 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. Use the Active Directory Users and Computers tool and Domain and Trusts tool in the Active Directory administrative tools group to change Windows security properties. 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.
65
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. Ensure that on each workstation in the domain you want to back up, the Global Domain Admins group is a member of the workstations 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). Do the following in the order listed:

In the Host Domain, permit the Target Domains to trust the Host Domain. In each Target Domain, trust the Host Domain.
In each Target Domain, add the Host Domains 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. Do the following in the order listed:

In the Host Domain, permit the Target Domains to trust the Host Domain. In each Target Domain, trust the Host Domain.
In each Target Domain, add the Host Domains name of an existing or new Service Account (for example, Administrator) in the Local Administrators group. On each workstation to back up, add the Host Domains 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.
Before you install
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 install Backup Exec on a computer that runs Windows Server 2008, you must select a SQL Server 2005 SP2 instance.
During the installation process and upgrade process, Backup Exec stops and starts the SQL service several times. Other user-created databases that use the SQL Server instance are unavailable during the process. To avoid such conflicts, you should install Backup Exec into its own SQL instance. 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. Caution Backup Exec may not function properly if you install it into an existing SQL instance that uses case-sensitive collation. Symantec recommends that you avoid installing Backup Exec to a SQL instance that uses case-sensitive collation. 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. You cannot install multiple Backup Exec databases on the same SQL Server instance. Note If you are installing a managed media server, it is recommended that you select a local Microsoft SQL Server 2000 (SP3a) instance or later 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.
67
Before you install
About Backup Execs 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:
Table 2-2 Feature Tape Device Drivers Online Documentation Enable Robotic Library Support Create Clone CD Backup Execs standard features Description Installs the Symantec tape device drivers for all supported tape devices that are attached to the server. Installs the Backup Exec Administrators Guide in a pdf file format. Enables support for multi-drive tape or optical robotic libraries and library storage systems. 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. See Using a clone CD image on page 110. 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.
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. If you have a licensed version of Backup Exec, you can evaluate most options and agents for a specified period of time. See Evaluating Backup Exec agents and options on page 112.
68
System requirements
System requirements
The following are the minimum system requirements for running this version of Backup Exec:
Table 2-3 Item Operating system Minimum system requirements Requirements You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 Note You cannot install a Backup Exec media server on a computer that runs the Windows Server Core installation option of Windows Server 2008. You can only install the Backup Exec Remote Agent for Windows Servers on Server Core computers. You cannot install SQL Express or SQL Server 2005 on a Windows Server 2008 computer that is configured in a Read Only Domain Controller (RODC) role. The Read Only Domain Controller role does not allow you to use the local accounts which are required for SQL Express and SQL Server 2005. When you install Backup Exec on an RODC computer you must select a remote SQL instance for the Backup Exec database. Additional application support Internet browser Processor Memory You can use Backup Exec with Microsoft Windows Microsoft Operations Manager (MOM) 2005. Internet Explorer 6.0 or later. Service Pack 1 is required for SQL Server 2005 Express. Intel Pentium, Xeon, AMD, or compatible. 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). Refer to your Microsoft Windows help documentation for instructions on how to view or set the paging file size.
69
System requirements Table 2-3 Item Installation disk space Minimum system requirements (continued) Requirements 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 The following hardware is recommended:

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. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2 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.
70
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 123. If you want to install Backup Exec to a non-English version of Windows, you must download the SQL Express SP2 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 SP2 setup file for that language 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. On the Welcome panel, click Next. Click I accept the terms of the license agreement, and then click Next. Check Local Install, and then click Install Backup Exec software and options. Click Next For first-time installations and upgrade installations, the Backup Exec Environment Check runs automatically after you click Next. 6 7 Review the results of the Environment Check. Do one of the following:
2 3 4 5
If the Environment Check does not reveal any issues that may prevent a successful installation of Backup Exec, click Next.
71
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.
Do one of the following:

If you have serial numbers 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.
If you have license keys for Backup Exec and its options
Go to step 9.
Select one of the following methods to enter license keys:

To enter license keys Do the following in the order listed: manually 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.
To import license keys from a file
Do the following in the order listed:

Click Import. Select the besernum.xml file.
To install an evaluation version

Leave the license key field blank. Proceed to step 10.
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 Check any additional features to install. For a description of the standard features that are available for installation with Backup Exec: See About Backup Execs standard features on page 68.
72
12 Do one of the following:

To change the directory where the Backup Exec files are installed Click Change to select a new directory.
To accept the default Proceed to step 13. 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. 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 64 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. The Symantec Backup Exec Database panel does not appear for upgrades. You cannot change the database location during the upgrade process. If you want to change the database location after the upgrade, use BEUtility.
To create a local Backup Exec SQL Express instance Do the following in the order listed:
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.
73
To use an existing SQL Server 2000 or SQL Server 2005 instance
Click Use an existing SQL Server 2000 (SP3a or later) or SQL Server 2005 (SP2 or later) instance on the network to store the database on. Select the instance.
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. Caution During the installation process and upgrade process, Backup Exec stops and starts the SQL service several times. Other user-created databases that use the SQL Server instance are unavailable during the process. To avoid such conflicts, you should install SQL into its own instance.
16 Click Next. Backup Exec attempts to connect to the instance. 17 If the Symantec Backup Exec Database panel appears, perform the following steps to identify the location of the SQL Express SP2 setup file:

Click Browse. Navigate to the location where you downloaded the SQL Express SP2 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 run LiveUpdate, view the readme, and create a shortcut to Backup Exec on the desktop.
Installing Backup Exec options to the local 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. The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113. Related Topics: Before starting Backup Exec on page 125

You can install additional options, such as the Library Expansion Option, when you install Backup Exec. See Installing Backup Exec to a local computer on page 71. 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 installed the Evaluation version or the Not For Resale (NFR) edition of Backup Exec, you can install evaluation versions of the additional options. If you have a licensed version of Backup Exec, you can evaluate most options and agents for a specified period of time. See Evaluating Backup Exec agents and options on page 112. 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
75
installation is complete, un-pause, or resume, the managed media server. See Pausing and resuming a managed media server on page 802. To install Backup Exec options to the local computer 1 2 3 Start Backup Exec for Windows Servers or verify that it is running. On the Tools menu, click Install Options and License Keys on this Media Server. Select one of the following methods to enter license keys:
To manually enter license keys Do the following in the order listed:

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.

4 5 6
Click Next. Verify that the additional options are selected for installation, and then click Next. If you are prompted, enter information or choose settings for additional options that you want to install. Click Next after each selection. 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.
Click Finish.
Related Topics: Installing Backup Exec to remote computers on page 77 Installing Backup Exec options to remote computers on page 82
76
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 Microsofts Add or Remove Programs utility to install Backup Exec to a remote computer. See your Microsoft documentation for more information. There are special considerations that you should be familiar with before you install Backup Exec to remote computers. Review the following table:
Table 2-4 Item Special considerations for installing Backup Exec to remote computers Consideration
Windows XP To push-install Backup Exec to a Windows XP SP2/Server 2003 computer, SP2/Server 2003 SP1 you must enable File and Printer Sharing on the Windows Firewall Exceptions list for the following ports:

135 (RPC) 445 (TCP) 103X (mostly 1037) 441 (RPC)
For more information about the Windows Firewall Exceptions list, refer to your Microsoft Windows documentation. During the installation process, Backup Exec sets the Remote Launch and Remote Access security permissions for the Administrators group. Windows Server 2008 To push-install Backup Exec to a computer that runs Windows Server 2008, you must enable certain items on the destination computers Windows Firewall Exceptions list. You must enable the following items:

File and Printer Sharing Windows Management Instrumentation (WMI)
For more information refer to your Microsoft Windows documentation.
77
To install Backup Exec to a remote computer 1 Do one of the following:

To install Backup Do the following in the order listed: Exec for the first time 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. Check Remote Install. Click Next.
To install Backup Exec to a remote computer after you have already installed it on the local computer
On the Tools menu, click Install Agents and Media Servers on Other Servers. Click Next.
2 3
Click Backup Exec Servers, and then click Add. Do one of the following:
To browse to the remote computer on which you want to install Backup Exec Do the following in the order listed:

Click Browse. Browse the list to select all of the remote computers to which you want to install an option. Click OK.
To add a remote computer Do the following in the order listed: manually Type the computer name or IP address and domain.
Click OK.
On the Remote Computer Logon Credentials panel, complete the fields as follows:
User Name Password Domain Type the user name for an account that has administrative rights on the remote computer. Type the password for an account that has administrative rights on the remote computer. Select the domain in which the remote computer is located.
78
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.
5 6
Click OK. 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 7 on page 80. Remote install using the Select this option to install remotely using all of the installation same install settings as options that are installed on the local computer. When you use this the local computer 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 8 on page 80. Remote install from clone file settings 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 109. When this option is selected, you can browse to a parameter file. After selecting this option, continue with step 8 on page 80.
79
Select one of the following methods to enter license keys:

To manually enter license keys Do the following in the order listed:

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.


8 9
Verify that the additional options are selected for installation. 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
10 Click Next. 11 On the Symantec Backup Exec Services 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 Domain Type the password for an Administrator account that the Backup Exec services can use. 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.
12 Click Next.
13 On the Symantec Backup Exec Database panel, do one of the following to select a location on which to store the Backup Exec database and then click Next:
To create a local Backup Exec SQL Express instance Do the following in the order listed:
Click Create a local Backup Exec SQL Express instance to store the database on. To change the location of the database, type the new location in the Destination Folder field.
To use an existing SQL Server 2000 or SQL Server 2005 instance
Click Use an existing SQL Server 2000 (SP3a or later) or SQL Server 2005 (SP2 or later) instance on the network to store the database on. Select the instance.
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. Caution During the installation process and upgrade process, Backup Exec stops and starts the SQL service several times. Other user-created databases that use the SQL Server instance are unavailable during the process. To avoid such conflicts, you should install SQL into its own instance.
Backup Exec attempts to connect to the instance. 14 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 19. 15 If you are prompted, enter information or choose settings for additional options being installed. Click Next or OK after each selection. 16 Review the features to be installed, and then click Next. 17 Read the Backup Exec installation review, and then click Install. The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113.
81
Installing Backup Exec options to remote computers
18 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. 19 (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 340. Related Topics: About the Backup Exec services account on page 64

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 Desktop and Laptop Maintenance Option
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:
Table 2-5 Item AOFO Special considerations for installing Backup Exec options to remote computers Consideration 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.
82
Installing Backup Exec options to remote computers Table 2-5 Item Remote Agent for Windows Systems Special considerations for installing Backup Exec options to remote computers Consideration You cannot push-install the Remote Agent for Windows Systems when the remote computer is in the ForceGuest configuration and it is not in a domain. ForceGuest is an operating system configuration that limits incoming users to Guest-level access. Instead, use the installation CD or the network to install the Remote Agent on the Windows computer. See Installing Backup Exec using the command line (silent mode) on page 101. You can also turn off ForceGuest. In Windows XP, ForceGuest is configured by the Use simple file sharing option. In Windows Vista, ForceGuest is configured by the Network Access: Sharing and security model for local accounts settings. Refer to your Microsoft Windows documentation for more information. Backup Exec installs a command line version of the Remote Agent on the computers that run the Server Core installation option of Windows Server 2008. The Remote Agent Utility command line applet is installed with the Remote Agent. This applet lets you monitor Backup Exec operations on the remote computer. See About the Remote Agent Utility Command Line Applet on page 895. 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 To push-install Backup Exec options to a Windows XP SP2/Server 2003 SP2/Server 2003 SP1 SP1 computer, you must enable File and Printer Sharing on the Windows Firewall Exceptions list for the following ports:

135 (RPC) 445 (TCP) 103X (mostly 1037) 441 (RPC)
For more information about the Windows Firewall Exceptions list, refer to your Microsoft Windows documentation. During the installation process, Backup Exec sets the Remote Launch and Remote Access security permissions for the Administrators group.
83
Installing Backup Exec options to remote computers Table 2-5 Item Windows Vista/Server 2008 Special considerations for installing Backup Exec options to remote computers Consideration To push-install Backup Exec options to a computer that runs Windows Vista/Server 2008, you must enable certain items on the destination computers Windows Firewall Exceptions list. You must enable the following items:

File and Printer Sharing Windows Management Instrumentation (WMI)
For more information refer to your Microsoft Windows documentation. To push-install to a Windows Vista computer, the destination computer must be part of a domain. For more information, refer to the Microsoft Knowledge Base.
84
To install a Backup Exec option to a remote computer 1 Do one of the following:

To install Backup Do the following in the order listed: Exec for the first time 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.
To install Backup Exec to a remote computer after you have already installed it on the local computer
On the Tools menu, click Install Agents and Media Servers on Other Servers. Click Next.

To install the following:
Click Windows Remote Agents, and then click Add.
Backup Exec Remote Agent for Windows Systems Advanced Open File Option Desktop and Laptop Optionss Desktop Agent
To install the Backup Exec Click NetWare Remote Agents, and then click Add. Remote Agent for NetWare Servers
85

To browse to the remote computer on which you want to install Backup Exec options Do the following in the order listed:

Click Browse. Browse the list to select all of the remote computers that you want to install an option to. Click OK.
To add a remote computer Do the following in the order listed: manually Type the name or IP address of the computer, and the domain. The domain is not necessary for NetWare systems.
Click OK.
On the Remote Computer Logon Credentials panel, complete the options as follows:
User Name Password Domain Use this user name and password when attempting to connect to additional computers during the installation Type the user name for an account that has administrative rights on the remote computer. Type the password for an account that has administrative rights on the remote computer. Select the domain in which the remote computer is located. This option is not available for NetWare systems. 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.
5 6 7
Click OK. In the Features pane, click the options that you want to install, and then click Finish. Do one of the following:
If you are installing the Remote Agent for Windows or NetWare Systems, or AOFO If you are installing DLO
Go to step 8.
Go to step 11.
86
When the Publish Remote Agent Information dialog box appears, select the appropriate options as follows:
Enable the Remote If you want this remote computer to display in the media servers Agent to publish backup selection list, verify that Enable the Remote Agent to information to the publish information to the media servers in the list is checked. media servers in the list Names or IP addresses Add Edit Remove Verify the media server that uses an alternate network to back up the computer on which the Remote Agent is installed. Click Add to add the name or IP address of the media server to which you want to publish. To change a media server name or IP address, select the media server in the displayed list, and then click Edit. 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.
Click OK.
10 Click Next. 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. The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113. 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 96.
Chapter 2, Installing Backup Exec 87
Installing the Remote Agent for Windows Systems
Related Topics: Push-installing the Remote Agent and the AOFO using the command line on page 93
Installing the Remote Agent for Windows Systems

You can install the Remote Agent for Windows Systems by using many methods, depending on your environment. Before you install the Remote Agent, you should review the special considerations in the following topic: See Special considerations for installing Backup Exec options to remote computers on page 82. The methods for installing the Remote Agent and the Advanced Open File Option (AOFO) are listed in the following table:
Table 2-6 Methods for installing the Remote Agent Do the following:
To use this method:
Install the Remote Agent from the See Installing Backup Exec options to the local Backup Exec installation CD by taking computer on page 75. 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. 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. See Installing Backup Exec options to the local computer on page 75. See Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections list on page 89. See Installing the Remote Agent and Advanced Open File Option in an Active Directory network on page 90.
See Push-installing the Remote Agent and the AOFO using the command line on page 93.
88
Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections Table 2-6 Methods for installing the Remote Agent (continued) Do the following: See Installing the Remote Agent to an x64-based operating system on page 95.
To use this method: 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 See Using a command prompt to install the Remote operating system through a command Agent on a remote 32-bit computer on page 96. prompt. Install the Remote Agent and the See Using a command script to install the Remote Agent Advanced Open File Option (AOFO) by and AOFO on page 97. using command script files.
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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 Do the following in the order listed:

Expand Favorite Resources. Expand Windows Systems.

Expand Domains. Expand Microsoft Windows Network. Expand the appropriate domain.
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.
89
Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections
5 6
On the Installation wizard, click Next. Continue with step 4 on page 86.
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. If you install the Backup Exec Remote Agent in an Active Directory network by using a Group Policy Object, when you configure the Group Policy Object you must use the Advanced Option, and you must specify a valid transform file. Otherwise, the Group Policy deployment may prevent users from logging on for more than an hour. Note Review your organizations deployment plans before you implement a rollout of the Backup Exec Remote Agent and Advanced Open File Option to client computers. 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 Agents 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 as follows:
The computer on which you want to create the transform must have Microsoft Windows 2000 or later.
90
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.
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 3
On the Welcome panel, click Next. On the Install Type panel, click Create a Transform to use Active Directory to install the Remote Agent, and then click Next. 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.
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.
Click Add to 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. Click Next. The computer that the Remote Agent is installed on is displayed in the media servers backup selection tree under the Favorite Resources node.
Enter a file name and a path where the transform will be created, and then click Next. To change the default path, click Change. 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.
To create the transform, click Create.

91
10 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. 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. Copy the transform from the path where it was created to the RAWS32 or RAWS64 directory on the shared folder. Continue with the next procedure to configure a Group Policy Object to deploy the source files.
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 3 4 Under Computer Configuration, expand Software Settings. Right-click Software Installation, click New, and then click Package. 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. Select the package file Symantec Backup Exec Remote Agent for Windows Systems.msi, and then click Open. When prompted, apply the Advanced Option. After Active Directory checks the msi package, click the General Properties tab, and make sure the correct versions of the options are being installed. Click the Deployment tab, and set up the configuration for your environment.
6 7
92
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.
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.
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 2 3 4 Open a Windows command prompt. Change to the drive containing the Backup Exec CD. Change directories to \WINNT\INSTALL\BE. To use a command file to read a list of remote computers to install to, go to step 6; otherwise, continue with step 5. Type one of the following:
To install the Remote Agent, type:
93
SETUP /PUSHRAWS: /USER:<user> /DOM:<domain> /PASS:<password> /SVR:<server name> -S
To install the Advanced Open File Option, type: SETUP /PUSHRAWS: /USER:<user> /DOM:<domain> /PASS:<password> /SVR:<server name> /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 <ServerList.txt> do call :sub1 %%I goto :eof :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. The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113.
94
Installing the Remote Agent to an 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 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 can be a local- or push-install to a remote computer. You can install the Remote Agent to an x64-based system locally, or you can install it remotely 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. To install the Remote Agent to an 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 the following path: \Program Files\Symantec\Backup Exec\Agents\RAWSX64 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
Click Complete.

Click Custom. Select the Remote Agent. Click Next.
4. Click Install. The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113.
95
Using a command prompt to install the Remote Agent on a remote 32-bit computer
You can install the Remote Agent by using a command prompt. To use a command prompt to install the Remote Agent on a remote 32-bit 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 3 Open a command prompt and type the drive letter that you mapped in step 1. Do one of the following:
To install the Remote Run the following command: Agent without publishing setup.exe /RAWS32: -s -boot enabled To install the Remote Agent with publishing enabled Run the following command:
setup.exe /RAWS32: -s /ADVRT: <media server name 1> <media server name 2>
The Remote Agent is installed on the remote computer in the following directory: \Program Files\Symantec\Backup Exec\RAWS32 The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113.
96
Using a command prompt to uninstall the Remote Agent from a remote 32-bit computer
You can uninstall the Remote Agent by using a command prompt. 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 3 Open a command prompt, and then type the drive letter that you mapped in step 1. 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 892
Using a command script to install the Remote Agent and AOFO

You can use command script files to install the Remote Agent and the Advanced Open File Option (AOFO). The command script files are included in the Remote Agent installation directory. To use a command script to install the Remote Agent and AOFO 1. Map a drive letter to the Backup Exec media server by using one of the following paths:
To a 32-bit computer To a 64-bit computer \Program Files\Symantec\Backup Exec\Agents\RAWS32 \Program Files\Symantec\Backup Exec\Agents\RAWSX64
Scripts do not support UNC paths.
97
2. Do one of the following:

To install the Remote Agent on a 32-bit computer To install the Advanced Open File Option on a 32-bit computer Double-click setupaa.
Double-click setupaofo. The command script installs the option automatically on the remote server in the following directory: \Program Files\Symantec\Backup Exec\Agents\RAWS32
To install the Remote Agent on a 64-bit computer To install the Advanced Open File Option on a 64-bit computer
Double-click setupaa64.
Double-click setupaofo64. The command script installs the option automatically on the remote server in the following directory: \Program Files\Symatnec\Backup Exec\Agents\RAWSX64
3. If you installed the Advanced Open File Option, you must restart the remote computer. The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113.
Using a command script to uninstall the Remote Agent and AOFO

One command script file 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.
98
Installing the Backup Exec Remote Administrator
To use a command script to uninstall the Remote Agent and Advanced Open File Option 1. Map a drive letter to the Backup Exec media server by using one of the following paths:
To a 32-bit computer To a 64-bit computer \Program Files\Symantec\Backup Exec\Agents\RAWS32 \Program Files\Symantec\Backup Exec\Agents\RAWSX64
2. Do one of the following:

For a 32-bit computer For a 64-bit computer Double-click Removeaaofo. Double-click Uninstallaaofo64.
Both the Remote Agent and the Advanced Open File Option are removed from the computer. 3. Restart the remote computer.

The Backup Exec Remote Administrator allows you to administer the media server from a remote Windows server or workstation. To support the Remote Administrator, the media server requires that the Backup Exec system services must be running. To install the Backup Exec Remote Administrator 1 2 3 4 From the installation CD browser, select the option to install Symantec Backup Exec. Click Next to continue with the installation. Select I accept the terms of the license agreement, and then click Next. To install the Administration Console as a Remote Administrator, select Install
Remote Administration Console only, and then click Next.
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. Click Install. Click Finish.
6 7
99
The Remote Administrator is installed. You can begin using Backup Exec. See Before starting Backup Exec on page 125. To run the Remote Administrator 1 2 Click Start. 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 server in the domain that has Backup Exec installed automatically appears in the list box. 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 want to connect. You cannot log on to the remote administration console with a user name that has a blank password on Windows Server 2003/2008 and XP/Vista computers. You must configure Windows to allow blank passwords. Otherwise, the error message Logon failure: user account restriction appears. For more information, see your Windows documentation. Password Domain Type the password. 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.
100
Installing Backup Exec using the command line (silent mode)
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.

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 the following:

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 2 3 4 Open a Windows command prompt. Change to the drive containing the Backup Exec CD. Change directories to \WINNT\INSTALL\BE. Type setup /TS: and the appropriate switches. For example:
101
setup /TS: /USER:<user> /DOM:domain /PASS:password /SNO:license key -S See Command line switches for Backup Exec silent mode installation on page 102. 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. The installation process creates a job log named bkupinst.htm 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. See About the installation log on page 113.
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.

Table 2-7 Switch /TS: Command line switches for silent mode installation of Backup Exec Additional Switches Description Installs Backup Exec using the options specified with the additional switches. The /USER:"user" /DOM:"dm" /PASS:"pw" is required.
102
Installing Backup Exec using the command line (silent mode) Table 2-7 Switch Command line switches for silent mode installation of Backup Exec (continued) Additional Switches /USER:"user" /DOM:"dm" /PASS:"pw" Description 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. Installs online documentation. 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. 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
/DOCS: /NOINSTALL:
/SNO:license key
103
Installing Backup Exec using the command line (silent mode) Table 2-7 Switch Command line switches for silent mode installation of Backup Exec (continued) Additional Switches /TD:NEW or ALL Description /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:"path\filename.cpf " Creates a file containing all of the installation parameters provided. This file is encrypted. 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. /DBSERVER:<server\instance> Installs the Backup Exec database to the specified SQL server. /DBINSTPATH: <SQL Express destination folder> /NOUPDATE: /DISADVRT /SQLXSETUP:<SQL Express Install Package> Installs the default instance of SQL Express in the specified folder. Skips the installation of Symantec LiveUpdate. Installs the Remote Agent without publishing it. Specifies the location of the language-specific install package for Microsoft SQL Server 2005 Express Edition.
/XML:"path\filename.xml"
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.
104
Installing Backup Exec using the command line (silent mode) Table 2-7 Switch Command line switches for silent mode installation of Backup Exec (continued) Additional Switches /IDR: /R3: /AOFO: /SSO: /SSO:server name Description Installs the Intelligent Disaster Recovery Option. Installs the Backup Exec Agent for SAP Applications (SAP Agent). Installs the Advanced Open File Option. Installs the SAN Shared Storage Option with this server as the primary server. Installs the SAN Shared Storage Option with this server as the secondary and the <server name> as the primary. Installs the Agent for Microsoft SharePoint. Installs the Agent for Microsoft Exchange Server. Installs the Agent for Lotus Domino. Installs the Agent for Oracle on Windows or Linux Servers. Installs the Agent for Microsoft SQL Server. Installs the Agent for Enterprise Vault. Installs the Remote Agent for Windows Systems. Installs the Remote Agent for NetWare Servers. Installs the Backup Exec Desktop and Laptop Option. Installs the five-user version of the Backup Exec Desktop and Laptop Option. Installs the Advanced Disk-based Backup Option.
/SHAREPT: /EXCH: /LOTUS: /ORACLE: /SQL: /EV: /NTA: /NWA: /DLO: /DLO5: /ADBO:
105
Installing Backup Exec using the command line (silent mode) Table 2-7 Switch Command line switches for silent mode installation of Backup Exec (continued) Additional Switches /CASO: /MMS:<CAS server name> /CASOPVLLOCAL: <1 or 0> Description Installs the Central Admin Server Option. Creates a managed media server for use with the Central Admin Server Option. /CASOPVLLOCAL:<1> indicates that device and media data will be stored locally on the managed media server. Use this switch with /MMS:. /CASOPVLLOCAL:<0> indicates that device and media data will be stored on the central administration server. Use this switch with /MMS:. /ADR: /NDMP: /DB2: /MAC: /CLONE: Installs the Active Directory Recovery Agent. Installs the NDMP Option. Installs the Agent for DB2. Installs the Remote Agent for Macintosh Servers. Installs the Clone CD option to the default location, which is <Backup Exec installation path>\clonecd. Installs the Clone CD option to the location that you specify. Installs the Copy Server Configuration option. Provides help on all command line operations, usage, and special switches.
/CLONE:<clone path> /COPYCONFIG: -?
106
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 2 3 4 Open a Windows command prompt. Change to the drive containing the Backup Exec CD. Change directories to \WINNT\INSTALL\BE 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. 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 Additional Switches Description Installs Remote Administrator using the options specified with the additional switches. /DEST:"path" Specifies the path where Remote Administrator will be installed. Otherwise, the default path Program Files\Symantec\Backup Exec is used. Installs online documentation. 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.
Table 2-8 Switch /RA:
/DOCS: /NOINSTALL:
107
Installing Backup Exec using the command line (silent mode) Table 2-8 Switch Command line switches for Remote Administrator silent mode installation (continued) Additional Switches /CPF:"path\filename.cpf " Description Creates a file containing all of the installation parameters provided. This file is encrypted.
/XML:"path\filename.xml" 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. -? Provides help on all command line operations, usage, and special 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 2 3 4 Open a Windows command prompt. Change to the drive containing the Backup Exec CD. Change directories to \WINNT\INSTALL\BE. 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:
108
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 2 3 4 Open a Windows command prompt. Change to the drive containing the Backup Exec CD. Change directories to \WINNT\INSTALL\BE. 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 2 3 4 Open a Windows command prompt. Change to the drive containing the Backup Exec CD. Change directories to \WINNT\INSTALL\BE. Type: SETUP /PARAMS:"A:\file name" -S
109
Using a clone CD image
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 101 Command line switches for Backup Exec silent mode installation on page 102

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 110 Installing locally using a clone CD image on page 111 Installing to a remote system using a clone CD image on page 111
Creating a clone CD image

Create a clone CD image to capture the Backup Exec installation program and your installation settings. After you create the CD image, copy it to a CD. To create a clone CD image 1 Begin installing Backup Exec. See Installing Backup Exec to a local computer on page 71. 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
110
When the list of features being installed appears, select Create Clone CD.
3 4
Click Next and continue with the installation procedures. 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. 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.
Installing to a remote system using a clone CD image

You can used a clone CD image to install a remote system. To install to a remote system using a clone CD image 1 Begin the Backup Exec installation. See Installing Backup Exec to remote computers on page 77. 2 Add the remote systems to which you are installing.
111
Evaluating Backup Exec agents and options
When the Remote Installation Types dialog box appears, select from one of the following options:
Remote install with licensed options 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.
Remote install using the Select this option if you want to install remotely using all of the same install settings as installation options installed on the local system. When this option the local computer 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. Remote install from clone file settings 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 109. When this option is selected, you will be able to browse to a parameter file.
Follow the on-screen prompts.
Evaluating Backup Exec agents and options

You can evaluate most Backup Exec agents and options at any time after the core product is licensed. Each agent and option has its own independent evaluation period. When an evaluation period is about to expire, Backup Exec warns you with an alert. You can also view a list of agents and options that are available for evaluation, as well as how much time is left in each individual evaluation period. See Viewing license information on page 120. To evaluate agents and options 1 2 3 4 5 On the Tools menu, click Install Options and License Keys on this Media Server. Click Next. Select the agents or options you want to evaluate. Click Next. If you are prompted, enter information or choose settings for the additional options that you want to install. Click Next after each selection.
112
About the installation log
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 in progress, you are prompted to stop them, or to wait for the jobs to finish. When the installation is complete, the services restart.
Click Finish.
Related Topics: Viewing license information on page 120
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:
Table 2-9 This color Black Orange Red Installation log colors Indicates Normal operations Warning messages Error messages
For most versions of Windows, 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. On Windows Vista/Server 2008 computers, Bkupinst.htm is saved in: \\Users\All Users\Symantec\Backup Exec\Logs
113
Repairing Backup Exec
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 2 3 Close the Backup Exec application. From the Windows Control Panel, double-click Add or Remove Programs. At the Add or Remove Programs dialog box, select Symantec Backup Exec for Windows Servers, and then click Change. On the Welcome panel, click Next. Select Local Install and Repair, and then click Next. Make sure the option Remote Install is not selected. 6 7 Select Install. Click Finish.
4 5
Starting and stopping Backup Exec services

You can start, stop, and restart Backup Exec services. To start or stop Backup Exec services 1 2 On the Tools menu, click Backup Exec Services. 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. Click this to start all Backup Exec services for the selected server.
Start all services
114
Uninstalling Backup Exec
Stop all services Restart all services Services credentials Refresh Remove Servers
Click this to stop all Backup Exec services for the selected server. Click this to stop all Backup Exec services and then restart the services for the selected server. Click this to change service account information or to change startup options. Click this to refresh this dialog box. Click this to remove a selected server or servers from the server list.
Uninstalling Backup Exec

Use Microsofts 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 2 3 Close Backup Exec. From the Windows Control Panel, double-click Add or Remove Programs. At the Add or Remove Programs dialog box, select Symantec Backup Exec for Windows Servers, and then click Remove. When prompted to confirm the deletion of Backup Exec from your computer, click Yes. 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.
115
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 2 On the Tools menu, click Install Options and License Keys on this Media Server. On the Backup Exec license keys dialog box, select the license key of the option that you want to uninstall, and then click Remove. Click Next. On the Symantec Backup Exec Options dialog box, verify that the option you want to remove is not checked, and then click Next. Review the Installation Review, and then click Install to start the process. When the install wizard has completed, click Finish. Corresponding files, registry keys, and configuration will be uninstalled.
3 4
5 6
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. The automatic update option only searches for Backup Exec updates. It does not show updates for other Symantec products that use LiveUpdate. Likewise, when LiveUpdate is scheduled to automatically update other Symantec products, it does not search for Backup Exec updates. Note By default, LiveUpdate checks for updates every Sunday night at 10pm. If there is an update, LiveUpdate notifies you with an alert.
116
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. If you run LiveUpdate manually, it searches for updates for all Symantec products that use LiveUpdate. You can select which updates you want to install. Caution During the installation and upgrade processes, Backup Exec stops and starts the SQL Server service several times. Other user-created databases that use the SQL Server instance are unavailable during the installation or upgrade process. To avoid such conflicts, you should install Backup Exec into its own SQL instance. Backup Exec installs the latest version of LiveUpdate. If a previous version of LiveUpdate is detected on the computer, Backup Exec upgrades it. Note To quickly view any hot fixes or service packs that are installed on the media server: See Viewing installed updates on page 120. LiveUpdate installs updates on the Backup Exec media server. You can then push-install or manually copy those updates to Backup Exec Remote Agents. 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 118 Running LiveUpdate manually on page 119 About the installation log on page 113
117
Scheduling automatic updates using LiveUpdate

You can schedule LiveUpdate to check for updates as follows:

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:
Table 2-10 LiveUpdate alerts
Backup Exec sends this alert When LiveUpdate Informational Alert LiveUpdate Warning Alert LiveUpdate Error Alert An update is installed successfully. An update is installed successfully. However, you must restart the computer. An update fails to install.
To schedule automatic updates using LiveUpdate 1 2 3 On the Tools menu, click Options. On the properties pane, under Settings, click LiveUpdate. Complete the options as follows:
Enable scheduled automatic updates Automatically download and install all 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.
118
Only notify me of available updates
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 Daily Weekly
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. 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. 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. 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.
Monthly
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. Note By default, LiveUpdate is configured for Express mode. If you change it to Interactive mode you must cancel the LiveUpdate session and restart it before the change takes place.
119
Viewing license information
To run LiveUpdate manually 1 2 On the Tools menu, click LiveUpdate. Do one of the following:
If LiveUpdate is set for Express mode If LiveUpdate is set for Interactive mode Click Start. Click Next.
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. To view installed updates 1 2 3 On the Help menu, click About Symantec Backup Exec for Windows Servers. Click Installed Updates. To install hot fixes and service packs, select Click here to run LiveUpdate.

You can view information about the Backup Exec options that are licensed and installed on a media server. You can also view a list of agents and options that are available for evaluation, as well as how much time is left in each individual evaluation period.
120
To view license information

To view license information from the Help menu Do the following in the order listed:
On the Help menu, click About Symantec Backup Exec for Windows Servers.
Click License Information.

On the navigation bar, click Devices. Select the media server from the tree view. Under General Tasks in the task pane, click Properties, and then click License Information.
To view license information from the media server properties

The License Information dialog box provides the following information:

Option Licensed Installed Name of the available Backup Exec options. Displays Yes if the option is licensed on the media server. Displays No if the option is not licensed. 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. Evaluation Lists the following statuses:

Available Expired N/A
If the option is under evaluation the remaining number of days in the evaluation period appears.
Related Topics: Evaluating Backup Exec agents and options on page 112 Adding licenses on page 122 Finding installed licenses in your environment on page 123
121
Adding licenses
Adding licenses
You can add licenses to activate additional agents or options at any time. If the evaluation period runs out on an agent or option, you need to enter a license key to continue to use it. Go to the Symantec Licensing Portal at the following URL to obtain license keys: https://licensing.symantec.com To add licenses 1 2 On the Tools menu, click Install Options and License Keys on this Media Server. Select one of the following methods to enter license keys:
To manually enter license keys Do the following in the order listed: 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. To import license keys from a file Do the following in the order listed: Click Import. Select the besernum.xml file.
3 4 5
Click Next. Verify that the additional options are selected for installation, and then click Next. If you are prompted, enter information or choose settings for the additional options that you want to install. Click Next after each selection. Read the Backup Exec installation review, and then click Install. The Backup Exec services stop while the agents or options are installed. If any active jobs are in progress, you are prompted to stop them, or to wait for the jobs to finish. When the installation is complete, the services are restart.
Click Finish.
Related Topics: Viewing license information on page 120 Evaluating Backup Exec agents and options on page 112
Finding installed licenses in your environment
Finding installed licenses in your environment on page 123
Finding installed licenses in your environment

The Backup Exec License Assessment Tool scans the Backup Exec media servers that you specify. For each media server, the tool finds the license keys that are installed and the number of resources that are backed up. The License Assessment Tool creates a license key scan report that lets you compare the number of resources with the number of license keys. The License Assessment Tool does not ensure compliance with Symantec licensing agreements. For more information about licenses, contact your reseller or go to the following URL: https://licensing.symantec.com To find installed licenses in your environment 1 2 On the Tools menu, click Backup Exec License Assessment Tool. Follow the on-screen prompts.
Related Topics: Adding licenses on page 122 Viewing license information on page 120
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. At the end of the installation, the upgrade process is summarized. Only Backup Exec version 10d 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. 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.
123
Upgrading from previous versions of Backup Exec
To upgrade from previous versions of Backup Exec 1 Perform steps 1 through 5 in the following topic: Installing Backup Exec to a local computer on page 71. 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. You cannot change the database location during the upgrade process. If you want to change the database location after the upgrade, use BEUtility
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. See Installing the Remote Agent for Windows Systems on page 88. Backup Exec NetWare Agent. For more information. See About installing the Remote Agent for NetWare Systems on a NetWare server on page 901 and Installing Backup Exec options to remote computers on page 82.
Backup Exec Advanced Open File Option. For more information. See Installing the Advanced Open File Option on page 814.
To reinstall these options, repeat the installation steps for each option.
124
Chapter
Getting Started
In Getting Started, youll find the following:
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. Description of device management in Backup Exec. Details of media server properties.
Before starting Backup Exec

For best results before starting Backup Exec, do the following: Make sure that your storage devices are connected and configured properly. See About storage devices on page 138. 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. Note the following:
If youre 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 youre 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 wont be included in the backup jobs and that has enough free space to contain the backup job.
125
Starting Backup Exec
See About backup-to-disk folders and files on page 387. Understand how Backup Exec provides overwrite protection for your media. See Media overwrite protection on page 172. Understand the default media set and its infinite overwrite protection period. See About media in Backup Exec on page 169. Learn about creating new media sets with weekly, monthly, or quarterly retention periods. See Default media set on page 175. 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. 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. See Setting default options for reports on page 610.
Starting Backup Exec

After you install Backup Exec, you can start it. 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 128 Using Backup Exec dialog boxes on page 131
126
Using the Getting Started with Backup Exec page
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. Additionally, you can access the Backup Exec Assistant, which has links to documentation, technical support assistance, additional wizards, and configuration options. You can also 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. To access the Getting Started with Backup Exec page
Click Help > Getting Started.
Chapter 3, Getting Started
127
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
Columns Task pane
Status bar Selection pane Preview pane Results pane
The main Administration Console screen includes the following components:

Table 3-1 Item Menu bar Getting Started page options Description Backup Execs 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.
128
Using the Administration Console Table 3-1 Item Navigation bar Getting Started page options (continued) Description The navigation bar appears under the menu bar and enables you to navigate to Backup Execs views. Views that can be accessed through the navigation bar include the following:

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.
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.
129
Using the Administration Console Table 3-1 Item Selection pane Results pane Getting Started page options (continued) Description The Selection pane is where you select items to work with, such as files to back up or restore. 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. 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. 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. 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.
Preview pane
Status bar
Columns
130
Frequently asked questions
Using Backup Exec dialog boxes

Most of Backup Execs 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.
Dialog box
Nodes Subnodes
Properties pane

If you are a new Backup Exec user, read the frequently asked questions to become familiar with the basic functions of Backup Exec. 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.
131
Use one of the following to run a backup job:

Table 3-2 If you are a New user Experienced user Ways to run a backup job Do this Use the Backup Wizard, which guides you through the setup of a backup job. 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. On the navigation bar, click Job Setup to create a policy to use for multiple backup jobs.
See Creating a backup job by setting job properties on page 267. Where can I find the wizards? You can find wizards in the following locations:
Table 3-3 Location of wizards Do this On the Help menu, click Backup Exec Assistant. On the Tools menu, click Wizards.
To access wizards On the Backup Exec Assistant On the Tools menu
Where can I find the Readme file? You can find the readme in the following locations:
Table 3-4 Location of readme Do this
To access the readme In the Backup Exec directory On the Help menu
In the directory where Backup Exec was installed. The default

directory is C:\Program Files\Symantec\Backup Exec. On the Help menu, click ReadMe File.
132
Where can I find the online documentation for Backup Exec? You can find the online documentation in the following locations:
Table 3-5 To access the documentation On the Backup Exec Assistant Location of documentation Do this On the Help menu, click Backup Exec Assistant. Under Documentation, click View Symantec Backup Exec Administrators Guide.
On the Help menu
On the Help menu, click Administrators Guide.
How do I get in touch with Technical Support? You can contact technical support the following ways:
Table 3-6 Ways to contact Technical Support Do this On the Help menu, click Backup Exec Assistant. Under Technical Support, click Backup Exec Technical Support.
To contact technical support On the Backup Exec Assistant On the Help menu
On the Help menu, click Symantec on the Web > Online Support.
133
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:
Table 3-7 Item Jobs Backup Exec default options Description Setting default backup options on page 307 Setting defaults for restore jobs on page 531 Setting test run default options on page 305 Setting catalog defaults on page 494 Creating separate selection lists for each computer or resource on page 252 Setting priority and availability windows for selection lists on page 250 Customizing Backup Exec Setting default pre/post commands on page 314 Setting default backup network and security options on page 318
Configuring Backup Exec Configuring database maintenance on page 162 Reports Administrating Backup Exec Setting default options for reports on page 610 Configuring default schedule options on page 297 Using checkpoint restart on Microsoft Cluster Server failover on page 699 Setting thresholds to recover jobs on page 491 Scheduling automatic updates using LiveUpdate on page 118 Device and Media Changing default preferences on page 136 Media locations and vaults on page 199 Bar code rules in mixed media libraries on page 193
134
Backup Exec defaults Table 3-7 Item Options Backup Exec default options (continued) Description Setting offhost backup options for a backup job on page 861 Setting defaults for the Advanced Open File Option for backup jobs on page 816 Setting default backup and restore options for SQL on page 1361 Preparing for disaster recovery of Exchange Server on page 1245 Configuring default Lotus Domino options on page 1298 Setting default options for the Remote Agent for NetWare Systems on page 910 Setting default options for SharePoint Portal Server 2003 and later on page 1276
135
Changing default preferences

You can set defaults for the way you prefer Backup Exec to display various screens, indicators, and alerts. To set default preferences 1 2 3 On the Tools menu, click Options. On the Properties pane, under Settings, click Preferences. Select the appropriate options as follows:
Show splash screen at startup Include robotic libraries in inventory job when Backup Exec services start up Display the job summary before creating a job Create jobs after a new policy is created 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 Execs services are starting. Depending on the number of storage devices attached to your system, this process may take a few minutes. 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 processes. 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. Due to the time required to scan the target resources, selecting this option when backing up remote resources is not recommended. Enable percentage bars when available 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. If the color depth on your computer is set to 256 or less, this option may appear as unavailable.
Display progress indicators for backup jobs. This requires additional time to pre-scan devices.
136
Show Comments link in Select this option to send a screen shot and comments for Backup dialog title bars to Exec enhancements to Symantec. provide feedback on Backup Exec. You must restart Backup Exec for this setting to take effect. 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. Select this option to have alerts automatically appear on the desktop when they are sent. Alerts that require a response always appear on the Backup Exec console. If you do not choose this option, you are required to view and respond to alerts through the Alerts view. Play sound after receiving alert 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.
Automatically display new alerts
Shade alternate rows in Select this option to enable or disable highlighting on every other Backup Exec views 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. 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.
137
About storage devices
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 2 On the Tools menu, click Options. On the Options - Set Application Defaults dialog box, under Job Defaults, click Device
and Media.
Select the appropriate options as follows:

Device Media set Select the device that you want to use as the default device for jobs. You can change this default for each job individually. 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.
About storage devices

Device management in Backup Exec simplifies how you organize and allocate the storage devices recognized by Backup Exec, including the following:

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 Microsofts Removable Storage Feature. http://entsupport.symantec.com/umi/V-269-2
You can find a list of compatible devices at the following URL: 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.
Viewing media server properties
You can do the following:

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 devices 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 Execs 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 Execs device monitoring to help make sure their devices are working properly.

You can 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. If the Central Admin Server Option is installed, two additional tabs can be viewed. See Setting defaults for managed media servers on page 770. See Changing the catalog location on page 781. To view media server properties 1 2 3 On the navigation bar, click Devices. Select the media server from the tree view. Under General Tasks in the task pane, select Properties, and then click a tab.
Related Topics: Viewing a media servers general properties on page 140 Viewing a media servers system properties on page 141 Viewing a media servers active job and alert statistics on page 142 Viewing license information on page 120
Chapter 3, Getting Started 139
Viewing the location of Backup Exec databases on page 143
Viewing a media servers general properties

On the media servers 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 servers general properties 1 2 3 On the navigation bar, click Devices. Select the media server from the tree view. 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 Communication status The name of the media server. 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 797. 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 491. 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 797.
140
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 797.
Description Version License key
Enter a description of the server. Backup Exec version and revision information. The license key under which Backup Exec is installed. Evaluation Edition is displayed if a license key was not provided during Backup Execs installation. Displays the time zone set for this media server. Date and time Backup Exec was initially installed and launched on this media server. Current date and time. Click to run the Diagnostics utility to a file.
Time zone Start date and time Current date and time Run Diagnostics
Viewing a media servers system properties

On the media servers system properties, you can view information about the operating system, the processor, and memory statistics. To view a media servers system properties 1 2 3 On the navigation bar, click Devices. Select the media server from the tree view. 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 Version Build Operating system currently running on this media server. Version of the operating system. Build number of the operating system.
141
Type Total processors Physical Virtual remaining Page size Page file
Processor installed in this media server. Number of processors on this media server. Amount of hardware RAM installed in the media server. Amount of virtual memory remaining on the media server. Size of a single virtual memory page. Size of the virtual memory paging file.
Viewing a media servers active job and alert statistics

On the media servers 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 servers active job and alert statistics 1 2 3 On the navigation bar, click Devices. Select the media server from the tree view. 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 jobs currently in progress on this media server. Number of active error alerts for this media server. Number of active warning alerts for this media server. Number of active information alerts for this media server.
Number of active jobs Number of error alerts Number of warning alerts Number of informational alerts
142
Viewing the location of Backup Exec databases

On the media servers 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. 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 770. 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 2 3 On the navigation bar, click Devices. Select the media server from the tree view. 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 Instance Name Path Server Instance Name of the Microsoft SQL Server that contains the Backup Exec database. Name of the instance that the Backup Exec database is installed on. MS SQL database name of the Backup Exec database. The path of the Backup Exec database. Name of the Microsoft SQL Server that contains the Advanced Device and Media Management (ADAMM) database. Name of the instance that the Advanced Device and Media Management (ADAMM) database is installed on. 143
Name Path Server Instance Name Path
MS SQL database name for the Advanced Device and Media Management (ADAMM) database. The path of the Advanced Device and Media Management (ADAMM) database. Name of the Microsoft SQL Server that contains the Backup Exec catalog database. Database instance that contains the catalog database. MS SQL database name for the Backup Exec catalog database. The path of the Backup Exec catalog database.
144
Chapter
Configuring Backup Exec settings and options

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

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 following types of logon accounts are included in Backup Exec:
Table 4-1 Type of logon accounts
Type of logon account Description 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
Default Backup Exec logon account

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 About using Backup Exec logon accounts for SQL resources on page 1317. See Exchange mailbox access requirements on page 1185.
Chapter 4, Configuring Backup Exec settings and options
147
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 153
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 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 153 Copying configuration settings on page 156
148
Creating a Backup Exec logon account

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 2 3 On the Network menu, click Logon Accounts. Click New. Enter the appropriate options as follows:
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. 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. Re-type the password for confirmation. The password must match the password you typed in the Password field. 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. Type any comments to describe how the Backup Exec logon account will be used.
Password
Confirm password Account name
Notes
149
This is a restricted logon Select this check box to enable the Backup Exec logon account to be account 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. This is my default logon Select this check box to make this your default Backup Exec logon account account used to browse, make selections, or restore data on your local and remote resources.
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 153 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
150
To edit a Backup Exec logon account 1 2 On the Network menu, click Logon Accounts. 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 4 Modify the Backup Exec logon account properties as needed. 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 153 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 2 On the Network menu, click Logon Accounts. 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 4 Click Change password. In the Password field, type a new password.
151
5 6 7
In the Confirm field, re-type the password, and then click OK. On the Edit Logon Credentials dialog box, click OK. 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 153 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 2 3 On the Network menu, click Logon Accounts. Select the Backup Exec logon account you want to replace, and then click Replace. 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
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 153 Copying configuration settings on page 156
Deleting a Backup Exec logon account

You cannot delete a Backup Exec logon account in the following situations:

It is being referenced by a job. It is owned by a user who is logged on to the media server. It is 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 2 3 On the Network menu, click Logon Accounts. Select the Backup Exec logon account you want to delete, and then click Delete. 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 153 Copying configuration settings on page 156 Copying logon account information on page 159
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.
153
To change your default Backup Exec logon account 1 2 On the Network menu, click Logon Accounts. 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 153 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. 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 2 3 On the Network menu, click Logon Accounts. Click System Account. 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.
154
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. Type any comments to describe how the Backup Exec logon account will be used.
Notes
This is a restricted logon Select this check box to enable the Backup Exec logon account to be account 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. This is my default logon Select this check box to make this your default account used to account 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 153 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

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. To copy configuration settings and logon information to other media servers, the Copy Server Configurations feature must be installed. See step 6 in Installing Backup Exec options to remote computers on page 82. To copy configuration settings 1 2 From the Tools menu, click Copy Settings to Media Servers. Select the appropriate settings to copy as follows.
Default job options Select this option to copy the default job options from this media server to selected servers. See Backup Exec defaults on page 134. Default schedule Select this option to copy the default schedule from this media server to selected servers. See Configuring default schedule options on page 297. Error-handling rules Select this option to copy error-handling rules from this media server to selected servers. See Error-handling rules on page 486. Alert configuration Select this option to copy alert configurations to selected servers. See Configuring alert category properties on page 550.
If the destination media servers appear on the list, select all of the media servers that you want to copy to. Click OK.
To add a destination media server in a non-CASO environment 1 2 3 If a destination media server name does not appear, click Add. Enter the name of the media server. If necessary, click Change Logon Account and select or enter the correct logon account information
156
See Configuring logon accounts on page 146. Changing a logon account does not permanently change the logon account for each selected media server. 4 5 Click OK. Repeat the previous steps, if necessary, to add another media server that you want to copy the configurations to. After all media servers have been selected, click OK.
To add a destination media server in a CASO environment 1 2 If a destination media server name does not appear, click Add. Select one of the following:
Add an individual media This option lets you add an individual media server. Select this server 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. Add the managed media This option lets you add all the managed media servers in a media servers in a media server server pool. Select this option, and then select a media server pool pool in the Media server pool name box to which you want to copy configuration settings and logon information. See Creating a media server pool on page 785. Add all managed media servers 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.
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. If you want to import a list of media servers, click Import List, browse to select the list, and then click Open. After all media servers have been selected, click OK.
157
To edit existing media server information 1 On the Copy Settings dialog box, in the Destination media servers box, select a media server. Click Edit. Make the appropriate changes and then click OK.
2 3
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. Click Remove. Click OK.
2 3
To import a list of media servers 1 2 3 On the Copy Settings dialog box, click Import List. Browse to select the list, and then click Open. 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 153 Creating a new Backup Exec System Logon Account on page 154 Copying logon account information on page 159
158
Copying logon account information
Copying logon account information

You can copy logon account information to a different media server. To copy logon accounts information 1 2 3 From the Network menu, click Logon Accounts. Select the logon account information you want to copy, and then click Copy to Servers. On the Copy Logon Account dialog box, select the appropriate options as follows:
Server Name Add Remove Import List Enter the name of the media server you want to copy the logon account information to, and then click Add. Click this button after entering the name of a media server that you want to copy the logon account to. Select a media server in the list, and then click this button if you want to remove a media server from the 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. Click this to select the logon account to use when connecting to the media servers in the list.
Logon Account
If an account with this Select this option if you want to overwrite logon accounts for an description already existing job having the same name. This option only appears if you exists on the destination are copying a job to another media server. server, overwrite it
Click OK.
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 2 3 On the Tools menu, click Audit Log. Click Configure Logging. On the Audit Log Configuration dialog box, select the check box of the category that you want to display in the audit log.
160
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

You can view audit logs to see when changes were made in Backup Exec and which users made the changes. 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. The date and time that this change was made in Backup Exec. Click the column head to sort the information by date. The domain and user name of the user that made the change. Click the column head to sort the information alphabetically. The item or items that you have selected for audit logging. Click the column head to sort the information alphabetically. The action that was recorded by Backup Exec for the operation that was performed. Click the column head to sort the information alphabetically.
Date/Time User Name Category Message
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. Do any of the following:
161
Configuring database maintenance

Click Refresh to update the audit log with new entries. 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.
Related Topics: Configuring the audit log on page 160 Configuring database maintenance on page 162

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
To configure database maintenance 1 2 3 On the Tools menu, click Options. Under Settings, click Database Maintenance. Select the appropriate options as follows, and then click OK:
Enable Backup Exec database maintenance Last time maintenance was performed Perform database maintenance at Delete aged data 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. 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. 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 Job logs Select this option to keep all job history data for any media that currently has an overwrite protection policy assigned to it. After a medias overwrite protection policy expires, the medias 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. Enter the number of days to keep job logs in the database before they are deleted. Job logs includes detailed information about the job. 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. 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.
Alert history
Reports
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
Select this check box to check the logical and physical consistency of the data in the database. 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.
Save contents of database to the Backup Exec data directory
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. Select this check box to reorganize fragmented pages and decrease the size of the physical database to 10 percent above what is actually used.
Optimize database size
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 columns 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
164
Configuring columns
Hiding a column
You can remove columns that may not interest you. To hide a column 1 Right-click any column title on title bar in the pane where you want column information hidden. 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
You can choose the columns that you want to appear. To display a column 1 2 Right-click any column title on title bar in the pane where you a column to appear. 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
You can rearrange the order in which the columns appear To rearrange columns 1 2 Right-click any column title. Click Configure Columns.
165
Configuring columns
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.
If you want to change the width of a column, do the following:

Select the column. In the Width of selected column (in pixels) field, enter the column width.
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 2 3 4 Right-click any column title on the pane where you want to sort job information. Click Multi-Column Sort. In the Sort by list, select the column titles on which you want to sort information. Click Ascending to sort the information in ascending order or click Descending to sort the information in descending order. Repeat step 3 and step 4 in the Then by lists. Click OK.
5 6
Related Topics: Hiding a column on page 165

Configuring columns
Displaying a column on page 165 Rearranging columns on page 165
167
Configuring columns
168
Chapter
Managing media
With Backup Execs media management tools you can do the following:

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.
Related Topics: About media in Backup Exec on page 169 Media overwrite protection on page 172 Setting defaults for media management on page 186 Creating media sets on page 176 Auditing media operations on page 190 Media labeling on page 191 Media locations and vaults on page 199
About media in Backup Exec

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.
169
About media in Backup Exec
The following table lists and describes the Media nodes in the Media view.
Table 5-1 Media node All Media A description of media nodes in the Media view Media node description Lists 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. See Viewing general media properties on page 210. Media Sets Lists default system media sets and media sets that you create. 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 Media that are 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. See Creating media sets on page 176. Cleaning Media Lists all cleaning media. See Setting up cleaning jobs on page 377. Imported Media Lists all 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. See Setting defaults for media management on page 186. Backup Exec and Windows NT Backup Media Lists all media from another installation of Backup Exec. See Cataloging media while reviewing devices or media on page 196. Lists all media that is used for archive jobs. Lists all media from a product other than Backup Exec. See Cataloging media while reviewing devices or media on page 196.
Backup Exec Archive Media Foreign Media
170
About media in Backup Exec Table 5-1 Media node Retired Media A description of media nodes in the Media view (continued) Media node description Lists all 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. Retired Media protects media from being used (overwritten). 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. See Removing damaged media on page 208. Scratch Media Lists all media that can be overwritten. New, blank, and erased media are automatically associated with the scratch media set. See Media overwrite protection on page 172. Keep Data Infinitely - Do Not Allow Overwrite Lists all media that you use in backup jobs when you use the backup job defaults. Until you create another media set that you associate with the media, the default rules in the media set Keep Data Infinitely - Do Not Allow Overwrite apply to all backup jobs that you create. 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. If you are upgrading from a version of Backup Exec prior to 11d, the default media set name remains Media Set 1. See Default media set on page 175. Media Location Lists the location of media when it is online, offline, or in a user-defined media vault. See Media locations and vaults on page 199.
Related Topics: Running the Media Set Wizard on page 178 Creating media sets on page 176 Associating media with a media set on page 210
Chapter 5, Managing media
171
Media overwrite protection

Each media is associated with a media set, which is a set of rules that manage media. These rules include the following:
Table 5-2 Rule Append period Rules specified in the media set Description 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. 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.
Overwrite protection period
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.
172
Media overwrite protection Append periods and overwrite protection periods

The append period begins when the media is allocated to a media set.
APPENDPERIOD
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. The media cannot be overwritten by another job during this interval. (However, you could erase the media or associate it with scratch media.)
TIME
OVERWRITE PROTECTION PERIOD
TIME
New data
TIME
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).
Old data
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.
173
Media overwrite protection How overwrite protection periods are reset

Time in days Append period = 5 days Time in days Append period = 5 days Time in days Append period = 5 days
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Normal Bkup
Protection period 14 Days
The media can be overwritten at this time
First Day
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Normal Bkup Normal Bkup
Second Day
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Normal Bkup Normal Bkup Normal Bkup Normal Bkup Normal Bkup
1 1 2 1 23 1 234
Fifth Day
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.
174
Default media set

When Backup Exec is installed, the following 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.
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 do the following:
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 176 Deleting a media set on page 179 Renaming a media set on page 180 Associating media with a media set on page 210 Changing general media set properties on page 180
175
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 205. 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 182. To create a media set 1 2 3 On the navigation bar, click Media. Under Media Set Tasks in the task pane, click New Media Set. On the General tab, select the appropriate options as follows, and then click OK:
Name Creation date Type a name for the new media set. Date and time when the media set was created. Backup Exec sets the date and time automatically. You cannot change them.
176
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 - Dont 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. 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.
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.
177
Select the appropriate options as follows, and then click OK.

Select the media vault to use with Click the drop-down arrow to select a media vault. This this media set: 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 205. 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. Move media to this vault x after it Specify a time period after which this media will be is allocated (first written to or reported as ready to be moved to this vault. overwritten) Return media from this vault x after it is last written to Specify a time period after which this media will be reported as ready to be returned from this vault.
Related Topics: Media overwrite protection on page 172 Deleting a media set on page 179 Renaming a media set on page 180 Changing general media set properties on page 180 Configuring vault rules for media sets on page 200 Using the Vault Wizard to move media on page 205
Running the Media Set Wizard

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. See Media overwrite protection on page 172. If you do not need a wizard to set up a new media set, you can create it manually. See Creating media sets on page 176.
To run the Media Set Wizard 1 2 On the Tools menu, point to Wizards. 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 2 On the navigation bar, click Media. In the Media selection pane, under Media Sets, select the media set that you want to delete. Under General Tasks on the task pane, click Delete. 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. If there are scheduled jobs allocated to the deleted media set, you are prompted to redirect the jobs to another media set. 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. 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.
Chapter 5, Managing media 179
3 4
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 2 On the navigation bar, click Media. In the Media selection pane, under Media Sets, select the media set you want to rename. Under General Tasks on the task pane, click Rename. In the Name field, type the new name you want to assign to this media set, and then click OK.
3 4
Changing general media set properties

On general media set properties, you can change the following:

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 2 3 4 5 On the navigation bar, click Media. In the Media selection pane, under Media Sets, select a media set. Under General Tasks on the task pane, click Properties. To change the media set name or overwrite or append periods, click the General tab. 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 180. Creation date 180 Date when the media set was created. Administrators Guide
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 - Dont 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. 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.
181
Media overwrite protection levels

The media overwrite protection level is a global setting that supersedes the media sets overwrite protection period. Although the terms are similar, the media overwrite protection level and the media overwrite protection period are different. The media overwrite protection period is a time interval that changes from one media set to another. The media overwrite protection level specifies whether to overwrite scratch, imported, or allocated media, regardless of the medias overwrite protection period. Use the media overwrite protection level to specify the type of media, 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 as follows:
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 185 illustrates the media overwrite protection level. Related Topics: Media locations and vaults on page 199 Media overwrite protection on page 172
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 one of the following types of media that you want Backup Exec to use first:
Overwrite scratch media before overwriting recyclable media contained in the targeted media set.
182
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.
Table 5-3 How Backup Exec searches for overwritable 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 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
Overwrite protection level and overwrite option: Full + Overwrite scratch media first Note This combination provides the most protection against overwriting media. Full + Overwrite recyclable media first
183
Media overwrite protection Table 5-3 How Backup Exec searches for overwritable media (continued) Media is overwritten in this order: 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. 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
Overwrite protection level and overwrite option: Partial + Overwrite recyclable media first
None - No overwrite protection + overwrite recyclable media first Caution This option is not recommended because it does not protect data from being overwritten.
184
Media overwrite protection Media overwrite protection
1 1 1 2
Media Overwrite Protection Level
Media Overwrite Protection
None
Partial
Full
Media Overwrite Options
2
Recyclable Media (current user media sets) Media Overwrite Option can reverse these, causing the Scratch media set to be examined second rather than first.
Scratch Media
Scratch Media
Recyclable Media (current user media
Recyclable Media (other media sets)
Recyclable Media (other media sets)) Imported Media
Imported Media
Allocated Media
Allocated Media
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).
When Backup Exec is unable to locate usable media, it prompts you to provide one.
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: Setting defaults for media management on page 186
185
Setting defaults for media management
Media locations and vaults on page 199
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. The following 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.
Related Topics: About media in Backup Exec on page 169 Deleting media on page 209 Changing general media set properties on page 180 Setting the search order for overwritable media on page 182

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 2 On the Tools menu, click Options. On the Properties pane, under Settings, click Media Management.
186

Full - protect allocated and Select this option to protect media in media sets and imported imported media media from being overwritten. See Media overwrite protection levels on page 182. This is the safest option to choose because the media being protected cannot be overwritten until the following occurs:

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.
Partial - protect only allocated 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.
Prompt before overwriting Select this option to be prompted before Backup Exec overwrites imported media imported media when Partial has been selected. The job will not run until you respond to this prompt. None Caution This option is not recommended because it does not protect data from being overwritten. 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.
Prompt before overwriting If you selected None (no overwrite protection), it is highly recommended that you select this option to be prompted before allocated or imported media overwriting allocated or imported media. The job will not run until you respond to this prompt.
187
Overwrite scratch media before overwriting recyclable media contained in the targeted media set
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 182. 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.
Overwrite recyclable media contained in the targeted media set before overwriting scratch media
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 183. 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 192. 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.
188
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 204 See Exporting expired media from a robotic library on page 383.
Related Topics: Setting the search order for overwritable media on page 182 Media labeling on page 191
189
Auditing media operations
Auditing media operations

The audit log provides information about media operations, such as when media are overwritten or appended to. This information can help you find all of the media that is required for a restore job. The following options for media operations are enabled by default in the audit log:

Delete media Delete media set Erase media (long) Erase media (quick) Format media Format media (WORM) Label media Move media Overwrite media
To view the audit log entries for media operations 1 2 3 On the Tools menu, click Audit Log. In the Select category to view field, click Devices and Media . View the entries in the Audit Log window.
To configure specific media operations for logging 1 2 3 4 On the Tools menu, click Audit Log. On the Audit Logs dialog box, click Configure Logging. Expand the Devices and Media category. 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. Click OK.
Related Topics: Audit logs on page 160

Media labeling
Media Errors Report on page 637
Media labeling
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. 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 medias 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. The following 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.
191
Media labeling
Edit the label in the medias 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 199 Labeling media on page 374 Bar code labeling on page 192 Renaming media on page 195 Viewing general media properties on page 210
Imported media labeling

Backup Exec does not automatically relabel imported media. The imported medias existing label is read and displayed in the Media view, in one of the Imported Media sets. Additionally, the imported medias 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 medias 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 210
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.
192
Media labeling
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, use the Scan option to quickly update slot information. Related Topics: Media labeling on page 191
Bar code rules in mixed media libraries

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 the following 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 librarys 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. See Viewing and specifying types of media for a device on page 353.
To create bar code rules in a mixed media library 1 2 3 4 On the Tools menu, click Options. In the Properties pane, under Settings, click Bar Code Rules. Click New. Select the appropriate options as follows:
Select a media type Select the media for which you want to add a bar code rule.
193
Media labeling
Vendor
(Optional) Type the name of this librarys manufacturer. You can find the name of the library manufacturer on the librarys property page. This field is not case-sensitive. By typing a vendor name here, you restrict the bar code rule to that vendors 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. 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.
Bar code suffix
5 6
Click OK to save the bar code rule for the media. 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. See Viewing robotic library configuration properties on page 361.
To change a bar code rule 1 2 3 4 On the Tools menu, click Options. In the Properties pane, under Settings, click Bar Code Rules. Click Edit, and then change the options as needed. Click OK to save the changes, and then click OK to exit.
To delete a bar code rule 1 2 3 4 On the Tools menu, click Options. In the Properties Pane, under Settings, click Bar Code Rules. Select a bar code rule to delete, and then click Delete. Click Yes to verify that you want to delete the rule, and then click OK.
194
About WORM media
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 devices property page. The medias 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 medias 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 dont know where the media is, from the navigation bar, click Media, and then click All Media to display all media.
2 3 4 5
Select the media you want to rename. Under General Tasks in the task pane, click Rename. In Name, type a new media label, and then click OK. Write this media label on an external label fixed to the outside of the physical media.
Related Topics: Viewing general media properties on page 210
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.
195
Cataloging media while reviewing devices or media
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 272

Catalog media in order to do the following:
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 368. To catalog media while reviewing devices or media 1 2 On the navigation bar, click Media or Devices. 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. On the task pane, under Media Tasks, click Catalog media. Select the appropriate options as follows:
Device Password Select the device on which this job will run. If this media is password protected and is being cataloged by this system for the first time, enter the password.
3 4
196
Confirm Password
If this media is password protected and being cataloged by this system for the first time, type the password again.
5 6
On the Properties pane, under Settings, click General. Select the appropriate options as follows:
Job name Job priority Type a name for the job or accept the default name. 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. You can choose from the following:

Highest High Medium Low Lowest
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 573.

To run the job now To set the scheduling options you want to use Click Run Now. On the Properties pane, under Frequency, click Schedule. See Scheduling jobs on page 286.
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 378. 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 494
Creating a restore job while reviewing media or devices
Setting catalog defaults on page 494 Selecting data to restore on page 519 Canceling a restore job on page 535
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 2 3 4 5 On the navigation bar, click Media or Devices. Double-click the media set or location that is associated with the data to be restored. Select the media that you want to restore. On the task pane, under Media Tasks, click Restore data. Select restore job properties. See Restoring data by setting job properties on page 498. 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 378. 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 196
198
Media locations and vaults
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.
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 201 Configuring vault rules for media sets on page 200 Using the Vault Wizard to move media on page 205 Renaming a media vault on page 202 Moving media to a vault or to the offline media location on page 202 Deleting a media vault on page 202 Media Vault Contents Report on page 639
199
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 2 3 4 On the navigation bar, click Media. Under Media Location Tasks on the task pane, click New media vault. Type the name and a description of the new vault. Click OK. The new vault is displayed under Media Location in the Media view.
Configuring vault rules for media sets

On the vault rule properties for media sets, you can add or change the following:
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 2 3 4 On the navigation bar, click Media. In the Media selection pane, under Media Sets, select a media set. Under General Tasks on the task pane, click Properties. Click the Vault Rules tab.
200
Select the appropriate options as follows, and then click OK:

Select the media vault to use with Select a media vault. This media vault will be used to store this media set: 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 205. 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. Move media to this vault x after it Specify a time period after this media is first written to or is allocated (first written to or used in an overwrite job when it will be reported as ready to be moved to this vault. overwritten). Return media from this vault x after it is last written to. Specify a time period after this media is last written to when it will be reported as ready to be returned from this vault.
Related Topics: Using the Vault Wizard to move media on page 205 Moving media to a vault or to the offline media location on page 202 Creating media sets on page 176
Finding media in a location or vault

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 2 3 4 On the navigation bar, click Media. On the Media selections pane, click Media Location. Under Media Location Tasks on the task pane, click Find media. 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.
Moving media to a vault or to the offline media location
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 2 3 4 On the navigation bar, click Media. On the Media selections pane, click the media vault that you want to rename. Under General Tasks in the task pane, click Rename. 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 2 3 4 On the navigation bar, click Media. Select the media vault that you want to delete. Under General Tasks in the task pane, click Delete. Click Yes to delete, or if you are deleting multiple vaults, click Yes to All to delete without prompting for each vault.

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.
202
Move media to a vault or to the offline media location using any of the following methods:
Table 5-4 Moving media For more information See Scanning bar code labels to move media on page 203.
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. 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.
See Scheduling a job to move media on page 204.
See Adding an export media template to a policy on page 433. See Using the Vault Wizard to move media on page 205.
Drag and drop media to a vault or See Using the drag and drop method to move media on to the offline media location, and page 206. then export the media from the device. Use the Move to vault option to See Using the Move to vault task to move media on logically move media to a vault or page 207. to the offline media location.
Scanning bar code labels to move media

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 2 On the navigation bar, click Media. In the Media selections pane, select the media location or vault to which you want to move media.
203
In the task pane, under Media Location Tasks in the task pane, click Add media to selected vault. Scan the bar code label, or type the media label, for the media you want to move to this vault. Click OK. Repeat steps 4 and 5 for all the media you want to add. Click OK.
5 6 7
Related Topics: Moving media to a vault or to the offline media location on page 202
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. See Creating media vaults on page 200. To schedule a job to move media 1 2 3 On the navigation bar, click Job Setup. On the task pane, under Backup Strategy Tasks, click New job to move media to a vault. Select the appropriate options as follows:
Job name Type a name for the job or accept the default name.
204
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. The following levels are available:

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. 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 572.
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 286. 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 202
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 383. 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.
205
To use the Vault Wizard to move media to a vault 1 2 3 On the navigation bar, click Media. Select the vault that you want to update. 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 176 Configuring vault rules for media sets on page 200 Moving media to a vault or to the offline media location on page 202
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. Table 5-5 From/To Online location Media Drag-and-Drop Rules Online Location No Offline Location Yes, with a warning that the media is not physically moved from the online location. No Media Vaults Media Pools/Sets Yes, with a No warning that the media is not physically moved from the online location. Yes No All Media No
Offline location
No
No
206
Moving media to a vault or to the offline media location Table 5-5 From/To User-defined vault Media Pools/Sets All Media Media Drag-and-Drop Rules Online Location No No No Offline Location Yes Yes, with a warning Yes, with a warning that the media is not physically moved from the online location. Media Vaults Media Pools/Sets Yes Yes, with a warning No Yes All Media No No No
Yes, with a Yes warning that the media is not physically moved from the online location.
To use the drag and drop method to move media 1 2 3 4 On the navigation bar, click Media. On the Media selections pane, click the vault containing the media. Select the media from the Results pane, and drag it to the new location. 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 202
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.
207
Removing damaged media
To use the Move to vault task to move media 1 2 On the navigation bar, click Media. Expand All Media to display a list of media, and then select the media that you want to move to a media vault. Under Media Tasks on the task pane, click Move to vault. Select a media vault to which you want to move this media, and then click Yes or Yes
to All.
3 4
The media location is updated. Related Topics: Exporting expired media from a robotic library on page 383 Moving media to a vault or to the offline media location on page 202
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 209 Viewing media statistics on page 213 Failed Backup Jobs Report on page 632
208
Deleting media
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 the following occurs:

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 2 On the navigation bar, click Media. Associate the media that you want to delete with the Retired Media set by doing one of the following:

Drag the media to the Retired Media icon. 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.
Double-click the Retired Media icon, and then select the media that you want to delete. 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.
Click Yes or Yes to All to delete the media that are displayed.
Related Topics: Viewing media statistics on page 213 Failed Backup Jobs Report on page 632
209
Associating media with a media set
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 2 3 4 On the navigation bar, click Media. Expand All Media to display a list of media. Select the media that you want to associate with a media set. 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.
Viewing general media properties

You can view the properties for a piece of media. To view media properties 1 2 3 On the navigation bar, click Media. Expand the All Media icon, and then select the media that you want to view. Under General Tasks on the task pane, click Properties.
210
Viewing general media 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. 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 Export pending Media type and subtype (if available). Click the button next to the field to change the media type or subtype. 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 433. Media set Media location Creation date Allocated date Modified date Name of the media set this media belongs to. Name of the device or vault where this media is located. Date and time when the media was first entered into Backup Exec. Date and time when the media was added to a media set as a result of an overwrite operation. 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.
211
Viewing media in storage devices
Related Topics: Media labeling on page 191 Creating a test run job on page 303 Viewing media in storage devices on page 212 Viewing media statistics on page 213

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.
Table 5-6 Item Slot Number Bar Code Media information in the Devices view Description Number of the slot. This field only appears if Slots has been selected. 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 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.
Media Label
212
Viewing media in storage devices Table 5-6 Item Allocated Date Media Set Media Location Overwrite Protected Until Appendable Until Used Capacity Media information in the Devices view Description Date and time when the media was added to a media set as a result of an overwrite operation. Name of the media set this media belongs to. Name of the device or vault where this media is located. Date and time after which the media can be overwritten. Date and time after which the media can no longer be appended to. 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 1537 About devices in the shared storage environment on page 1549
Viewing media statistics

You can view statistics about a piece of media. To view media statistics 1 2 3 4 On the navigation bar, click Media. Expand the All Media icon, and then select the media that you want to view. Under General Tasks in the task pane, click Properties. Select the Statistics tab.
213
The Statistics tab provides the following information:

Hours in use Used capacity The total number of hours that this media has been in use. 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. 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. 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. 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. Number of bytes that have been read from this media. Number of times this media has been mounted. The total number of seek operations (performed when a specific piece of information is being located) that have been performed on this media. The number of errors encountered while trying to locate data.
Compression ratio
Bytes written
Bytes read Mounts Seeks
Seek errors
214
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. The number of unrecoverable write errors encountered. If you receive hard errors, check the media for damage. 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. The number of unrecoverable read errors encountered. If you receive hard errors, check the media for damage.
Hard write errors Soft read errors
Hard read errors
Related Topics: Changing general media set properties on page 180 Creating media sets on page 176
215
Media rotation strategies

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. The most commonly used media rotation strategies include the following:
Son. Uses the same media each day to run a full backup. See Son media rotation strategy on page 217. 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 217. 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 218.
Related Topics: Creating a new policy on page 424
216
Son media rotation strategy

The Son media rotation strategy requires the following:
Table 5-7 Item Number of media required Overwrite protection period Son media rotation strategy Description 1 (minimum) 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 Mon Media 1 Week 1 Tue Media 1 Wed Media 1 Thu Media 1 Fri Media 1
Full Backup
Father/son media rotation strategy

The Father/son media rotation strategy requires the following:
Table 5-8 Item Number of media required Overwrite protection period Father/son media rotation strategy Description
6 (minimum) 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.
217
Media rotation strategies Father/Son Backup Strategy Mon Media 1 Week 1 Media 1 Week 2 Media 2 Media 3 Media 4 Media 6 Tue Media 2 Wed Media 3 Thu Media 4 Fri Media 5
Full Backup
Incremental or Differential Backup
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

The Grandfather media rotation strategy requires the following:
Table 5-9 Item Number of media required Overwrite protection period Grandfather media rotation strategy Description
19 (minimum) 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.
218
Media rotation strategies Grandfather Backup Strategy Mon Mon 1 Week 1 Mon 1 Week 2 Mon 1 Week 3 Mon 1 Week 4 Incremental or Differential Backup Tue 2 Wed 3 Thu 4 Monthly Tue 2 Wed 3 Thu 4 Fri 7 Tue 2 Wed 3 Thu 4 Fri 6 Tue Tue 2 Wed Wed 3 Thu Thu 4 Fri Fri 5
Full Backup
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.
219
220
Chapter
Preparing for backup
Before you back up your data, you should become familiar with how to do the following:

Use backup strategies Select data to back up Create user-defined selection lists Protect specific types of data, such as Windows Server systems and utility partitions
About backup strategies

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 216
221
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 users 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.
222
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. 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.
Table 6-1 Method Advantages and disadvantages of including more than one system in a job 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).
Chapter 6, Preparing for backup
223
About backup strategies Table 6-1 Advantages and disadvantages of including more than one system in a job (continued) Advantages
Method (continued)
Disadvantages
Multiple resources per job
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.
If any of the resources in the job are not available during the backup, the job results in an abnormal completion status.
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 as follows:
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. Perform an additional backup to take off-site. 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.
224
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
225
method in addition to the media rotation scheme selected. The Changed today method backs up all files with todays 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.
Table 6-2 Method Full Backup Method Advantages and Disadvantages Advantages
Disadvantages
Files are easy to find - Since full backups include all data contained on a device, you dont 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).
226
About backup strategies Table 6-2 Method Differential Backup Method Advantages and Disadvantages (continued) Advantages
Disadvantages
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. 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.
Redundant backups - All of the files created or modified since the last incremental backup are included; thus creating redundant backups.
Incremental
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.
227
About backup strategies Table 6-2 Method Working Set Backup Method Advantages and Disadvantages (continued) Advantages
Disadvantages
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.
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.
Understanding the archive bit and backup methods

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:
228
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 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. Heres what happens: Freds 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 Freds 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 Fridays and Wednesdays tapes: Fridays tape because it included all of the data, and Wednesdays tape because it included every file that had been created or changed since Fridays 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 files 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.
229
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 243
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.
230
Selecting data to back up
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 items icon. The items 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.
231
About using fully qualified computer names in backup selections
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. 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.
About the Computer Name node
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 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. The Computer Name node includes the following sub-nodes:
Table 6-3 Sub-node name Local Drives Shadow Copy Components (Windows Server 2003/2008) System State Sub-nodes of the Computer Name node Description Includes hard drives as well as CD-ROM drives that physically reside on the media server. Uses Microsofts Volume Shadow Copy Service to protect critical operating system and application service data, and third-party application and user data on Windows Server 2003/2008 resources. 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 documentation. Active Directory Application Mode 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.
233
About the Favorite Resources node Table 6-3 Sub-node name Backup Exec database Utility Partition Sub-nodes of the Computer Name node (continued) Description Includes job, schedule, job history, notification, alerts, device, media, and catalog indexes data for Backup Exec 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.
Related Topics: About the Active Directory Recovery Agent on page 875
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 the following:

Linux/Unix Servers Macintosh Servers NetWare Agents Windows Systems
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.
234
About the Favorite Resources node
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 computers name. This icon is displayed for 13 days. Some of the reasons why the media server may not receive published information include the following:

The publishing option is disabled on the Remote Agent. A media server is removed from the list to publish to.
See Publishing the remote Windows computer to media servers on page 892.
Adding a Windows system to the Favorite Resources node

To add a Windows system to the Favorite Resources node, you must know the name or IP address of the remote computer. To add a Windows system to the Favorite Resources node 1 2 3 4 5 6 On the navigation bar, click the arrow next to Backup. Click New backup job. On the backup selection tree, expand the Favorite Resources node. Right-click Windows Systems. Click Add Windows Systems. In the System Name box, type the name or IP address of the remote computer that you want to add. Select one of the following:
Install the Remote Agent, Click this option if the Remote Agent for Windows Systems is not and then add to Favorite installed on the remote computer. Backup Exec installs the Remote Resources Agent on the remote computer, and then adds the remote computer to the Favorite Resources node. Add a system that already Click this option if the Remote Agent for Windows Systems is has the Remote Agent already installed on the remote computer. Backup Exec adds the installed remote computer to the Favorite Resources node.
235
About the Domains node
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.
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 86. It may be several minutes before the computer name appears under the node.
Deleting a Windows system from the Favorite Resources node

You can delete a Windows system from the Favorite Resources node at any time. To delete a Windows system from the Favorite Resources node 1 2 3 On the navigation bar, click the arrow next to Backup. Click New backup job. On the backup selection tree, expand the Favorite Resources node, and then expand the Windows Systems node. Right-click the Windows system that you want to delete. Click Delete from Favorite Resources. It may be several minutes before the computer name is removed from the node.
4 5
About the Domains node

The Domains resource includes Active Directory Domains and the 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.
236
About the Oracle Real Application Clusters node
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

You must know the fully qualified domain name of the Active Directory domain. To add an Active Directory domain 1 2 3 4 5 6 7 8 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the backup selections tree, expand the Domains node. Right-click Active Directory Domains. Click Manage Active Directory Domains. In the Name box, type the fully qualified domain name. Click Add. Click Close.
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. See About backing up Oracle RAC resources on page 1391.
237
About the NDMP Devices node
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. See Backing up NDMP resources on page 1571.
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. See Selecting SharePoint resources for backup on page 1263.
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 companys private network, but cannot be located by using just its name or normal browsing methods.
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.
Table 6-4 Format type UNC name User-defined selection formats Example \\mycomputer\shared\temp
238
About the User-defined Selections node Table 6-4 Format type Fully qualified computer name User-defined selection formats (continued) Example \\mycomputer.domain.companyname.com\temp
See About using fully qualified computer names in backup selections on page 232. To add a user-defined selection to the User-defined Selections node 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Right-click User-defined Selections, and then click Manage User-defined Selections. 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 6 Click Add. 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 243 Creating selection lists on page 244 Deleting selection lists on page 247 Editing selection lists on page 248
239
Selecting Distributed File System (Dfs) links for backup
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 Microsofts Distributed File System (Dfs) 1 2 3 4 5 6 On the Tools menu, click Options. On the Properties pane, under Job Defaults, select Network and Security. Check Enable selection of user shares, and then click OK. On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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. Select the Dfs root. Run the backup job.
8 9
Related Topics: Adding a user-defined selection to the User-defined Selections node on page 238 Restoring Distributed File System (Dfs) links on page 517
240
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 do the following:
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. If you exclude files by an attribute that does not exist, all files of that type are excluded. For example, excludes based on SQL database dates result in global SQL excludes since SQL databases do not have date attributes. 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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Select the resource that contains the files you want to include or exclude from the backup. Click Include/Exclude. 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.
4 5
241
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 the following:

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 Exclude Include subdirectories Only modified Files (Default) Select this option to include the files in the job. Select this option to exclude the files from the job. Select this option if you want to select the contents of all the subfolders when a directory is selected. Select this to include or exclude modified files in the path you specify.
242
About selection lists
Only read-only Files Files dated
Select this to include or exclude files that cannot be modified. 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 7 After completing your selections, click OK. Submit the operation using the same procedures as required for other backups. See Creating a backup job by setting job properties on page 267.

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: See Viewing the history for backup selection lists on page 254. Related Topics: Creating selection lists on page 244 Deleting selection lists on page 247 Editing selection lists on page 248
Chapter 6, Preparing for backup 243
Editing selection lists on page 248
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 2 3 On the navigation bar, click Job Setup. In the task pane, under Selection Lists Tasks, select New backup selection list. Select the resources that you want to back up from the backup selections pane. See Selecting data to back up on page 231. 4 Select the appropriate options as follows:
Selection list name Load Selections from existing list Enter the name of 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 246. Selection list description Enter a description for this selection list. 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 241. Include subdirectories Show file details Select this option if you want to select the contents of all the subfolders when a directory is selected. Select this option to display details about the files available for selecting.
244
View by Resource View Selection Details
Click this tab to view resources in a tree view. Click this tab to view selections as a list of files and directories.
(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. (Optional) To change or test a logon account for the resources, on the Properties pane, under Source, click Resource Credentials. See About selection lists on page 243.
(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. See Setting priority and availability windows for selection lists on page 250.
(Optional) To notify users that a job containing this selection list was completed, on the Properties pane, under Source, click Selection List Notification. See Assigning notification recipients for completed jobs on page 573.
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 243 Deleting selection lists on page 247 Editing selection lists on page 248 To edit the Excludes selection list on page 249 Creating separate selection lists for each computer or resource on page 252
245
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 jobs hold status. To hold jobs that back up a selection list 1 2 On the navigation bar, click Job Setup. 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 <Ctrl> or <Shift> 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 2 3 On the navigation bar, click Job Setup. Under Selection Lists Tasks in the task pane, select New backup selection list. On the New Backup Selection List dialog box, select resources to include in the selection list. Click Load selections from existing list. On the Use Selections dialog box, select the selection lists that you want to merge with or replace the previously selected backup selections. Do one of the following: To merge the selection Click Merge. lists To replace the existing Click Replace. selection list
4 5
246
Complete the other options on the New Backup Selection List dialog box. See Creating selection lists on page 244.
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 lists association from the policy before you can delete the selection list. You cannot delete the Excludes selection list. To delete selection lists 1 2 3 4 On the Edit menu, click Manage Selection Lists. Click the selection list that you want to delete. Click Delete. 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 243 Creating selection lists on page 244 Editing selection lists on page 248 To edit the Excludes selection list on page 249 Deleting a job created from a policy on page 442
247
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. If a resource on your selection list no longer exists and you want to delete it, you must use the View Selection Details tab. To edit one selection list 1 2 3 4 5 On the Edit menu, click Manage Selection Lists. Select the selection list that you want to edit. Click Edit. Edit the selection list properties. Click OK.
To edit multiple selection lists 1 2 On the navigation bar, click Job Setup. 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 4 Under General Tasks in the task pane, click Properties. 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 Click Edit each selection list.
To change the priority Click Apply settings to all of the selected selection lists. and availability, notification, and device (for a central administration server only) properties for all of the selected selection lists
248
If the selection list is being used by jobs, any change you make to this selection list will affect all jobs associated with it. 5 6 7 8 Click Yes to continue. Edit the selection list properties. Click OK. Click Close.
Editing the Excludes selection list

You can change the Excludes selection list at any time. To edit the Excludes selection list 1 2 3 4 On the Edit menu, click Manage Selection Lists. On the Manage Selection Lists dialog box, select Excludes. Click Edit. Do one of the following:
If the Excludes list was edited previously

Select the selection rule that you want to edit. Click Edit.
If this is the first time the Click Insert. Excludes list is being edited
5 6
Edit the selection list properties. If you want to delete one of the selection rules:

Select the selection rule that you want to delete. Click Delete.
7 8
Click OK. Click Close.
249
Related Topics: Including or excluding files for backup on page 241 About selection lists on page 243 Creating selection lists on page 244 Assigning notification recipients for completed jobs on page 573 Deleting selection lists on page 247
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 2 3 On the Tools menu, select Options. On the Properties pane, under Job Defaults, click Priority and Availability. Proceed to step 5 of the following topic: To set priority and availability for selection lists on page 251.
250
To set priority and availability for selection lists 1 2 3 4 5 On the navigation bar, click Job Setup. In the task pane, under Selection Lists Tasks, select New backup selection list. Select the data you want to back up. On the Properties pane, under Source, click Priority and Availability. Complete the appropriate options as follows:
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. 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. Select the earliest time when this selection list will be available for backup. Select the latest time when this selection list will be available for backup. 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.
Limit availability of this selection list for backup to the following daily time window
Begin time End time Enable automatic cancellation for this selection list
Cancel backup job if not completed within x
251
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. To create separate selection lists for each computer or resource 1 2 3 On the Tools menu, select Options. On the Properties pane, under Settings, select Selection List. Select one of the following options:
Separate backup selection Select this option to have Backup Exec create a different backup list for each computer selection list for each computer that you select when you create a selection list outside of a backup job. Separate backup selection Select this option to have Backup Exec create a different backup list for each resource selection list for each resource that you select when you create a selection list outside of a backup job. Single backup selection list for all selections 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.
Creating a custom filter for Backup Selection Lists

You can filter backup selection lists based on the following criteria:

Selection list name Selection list description Computers that are backed up by the selection list Resource type Policy Selection lists that are not protected
252
To create a custom filter for Backup Selection Lists 1 2 3 4 On the navigation bar, click Job Setup. On the Backup Selection Lists pane, in the Filter list, click <new custom filter>. Type a unique name and a description for this filter. Do any of the following:
To filter by selection list name To filter by selection list description

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. 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. Under Criteria, click Policy. 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.
To filter by computers backed up by the selection list To filter by resource type
To filter by policy
To filter by selection lists that are not protected
Click OK.
Filtering backup selection lists

Use filters to view backup selection lists that meet certain criteria.
253
To filter backup selection lists 1 2 On the navigation bar, click Job Setup. 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 2 3 On the navigation bar, click Job Setup. On the task pane, under Selection List Tasks, click Search backup selection lists. 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. Click Find Now. 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
254
Using resource discovery to search for new resources

Byte count Job rate
To view the history for backup selection lists 1 2 3 4 On the navigation bar, click Job Setup. Right-click the backup selection list for which you want to view history. Click View History. Click OK.
Viewing a summary for a selection list

You can view the following summary information for a selection list:

Credentials Resource order Priority and availability Notification
To view a summary for backup selection lists 1 2 3 4 On the navigation bar, click Job Setup. Right-click the backup selection list for which you want to view a summary. Click View Summary. Click OK.

Backup Execs 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.
255
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/2008 resources, Backup Execs Resource Discovery feature detects the Shadow Copy Components; it does not detect System State. To use resource discovery to search for new resources 1 2 On the navigation bar, click Job Setup. Under Backup Strategy Tasks in the task pane, select New job to automatically discover resources. 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 5
Select the domain you want Backup Exec to search for new resources. 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. If you want to exclude computers from the search, do one of the following:
To browse for 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. Administrators Guide
To type the computer name
256
On the Properties pane, under Settings, click General and then complete the appropriate options as follows:
Job name Job priority Enter the name for this job. 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:

On the Properties pane, under Settings, click Resources and then complete the appropriate options as follows:
Network administrative Select this option if you want Backup Exec to search for new shares 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.
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 Oracle databases DB2 databases Select this option if you want Backup Exec to search for new System State resources or shadow copy components. Select this option if you want to search for new Oracle databases. Select this option if you want to search for new DB2 databases.
Send separate Select this option if you want Backup Exec to send separate notification for each new notifications when each new resource is found. resource found
257
About the Backup Exec Shadow Copy Components file system
Send one notification for Select this option if you want Backup Exec to send out a single all new resources found notification for all new resources found. Include previously discovered resources when sending notification Select this option if you want Backup Exec to send a notification that includes all resources previously found during resource discovery jobs.
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 573.
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 286.

The Backup Exec Shadow Copy Components file system uses Microsofts Volume Shadow Copy Service to protect critical operating system and application service data, and third-party application and user data on Windows Server 2003/2008 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. 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), 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 nodes if you want to back up those resources.
258
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/2008, 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.
Small Business Server 2003 support

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 or later, Backup Exec automatically updates the backup selection lists that include Shadow Copy Components.
259
The following table shows what is updated:

Table 6-5 Automatic selection list updates for Backup Exec 11d and later Backup Exec does this automatically in 11d and later Adds System State to the selection list. Changes the selection to System state only.
If this was selected in 10d Shadow Copy Components System State (under the Shadow Copy Components node)
Active Directory Application Mode (under the Changes the selection to Active Directory Shadow Copy Components, User Data nodes) Application Mode only. Any specific Active Directory Application Mode instance Changes the selection to Active Directory Application Mode only, with the specific instance selected.
About backing up virtual machines and the Virtual Server Host

When Backup Exec detects Microsoft Virtual Server on a computer, it creates a Microsoft Virtual Server container. The container appears under User Data, which appears under Shadow Copy Components in the backup selections list. The Microsoft Virtual Server container includes each guest virtual machine that resides on the virtual server, which is also called the host. It also contains the Virtual Server Configuration. You can back up the entire host, individual guest machines, or the Virtual Server Configuration. Virtual Server Configuration contains the Virtual Server configuration settings and virtual networks. You should always have a current backup of the Virtual Server Configuration. Back up the Virtual Server Configuration whenever you make changes to configuration files. Backup Exec uses Microsofts Volume Shadow Copy Service (VSS) to back up Virtual Server data. Backup Exec takes a snapshot of the Virtual Server Host while applications and services are still running. The host in turn takes snapshots of all the guest virtual machines it contains. Only the guest virtual machines that run Microsoft Windows Server 2003 or later with virtual machine additions installed are available for backups without downtime. Any other guest virtual machines are briefly placed in a saved state for backups. The amount of downtime that is required depends on your computers resources. When you select a guest virtual machine for backup, the backup is a full image of the entire guest virtual machine. The backup includes the following components:
Differencing virtual hard disk

260

Undo virtual hard disk .vhd files .vmc files .vsv files
If the parent differencing disk is modified after it is backed up, the related child disks do not work. To ensure an accurate restore, the parent differencing disk should be locked so that it cannot be modified after it is backed up. Backup Exec can back up only the files that reside on the virtual server. Virtual machines that have iSCSI or remote .vhd files are excluded from backup jobs. Related Topics: Backing up virtual machines and the Virtual Server Host on page 301 Upgrading existing Shadow Copy Component backup jobs to version 12 on page 261
Upgrading existing Shadow Copy Component backup jobs to version 12

Jobs from Backup Exec versions 11d and earlier may recognize and back up guest virtual machines. Any backup job that is configured to back up the Shadow Copy Components or User Data resource automatically backs up any guest virtual machines. Jobs from previous versions of Backup Exec that specifically back up virtual machine data will no longer back up those files correctly. You should edit the jobs to back up virtual machines using the Shadow Copy Components resource instead. Related Topics: About backing up virtual machines and the Virtual Server Host on page 260 Backing up virtual machines and the Virtual Server Host on page 301
261
262
Chapter
Backing up data
Backups are crucial for data protection, and Backup Exec offers you many choices for creating backup jobs to protect your data, including the following:
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.
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 the following:
A test run of a scheduled backup job to determine whether or not it is likely to complete successfully.
263
Creating a backup job by using the Backup Wizard
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. Create media sets.
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 device pools on page 412 Creating media sets on page 176 Creating a backup job by using the Backup Wizard on page 264 About backup strategies on page 221

If you are new to Backup Exec or are uncertain about how to set up a backup job, you can use the Backup Wizard.
264
You can use the wizard in the following ways:

Table 7-1 Option Back up the media server now using default settings How to use the Backup Wizard Description 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) 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:)
You cannot back up the following types of data with this method:

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. Create a backup job This method guides you through the process of creating a backup job.The with custom settings wizard prompts you to select options. However, many of the backup job settings are based on the default settings.
If you have experience with Backup Exec, you can create a backup job by setting the properties you want. See Creating a backup job by setting job properties on page 267.
Chapter 7, Backing up data
265
To back up the media server now by using default settings 1 2 3 4 5 On the navigation bar, click the arrow next to Backup. Click New Backup Job using Wizard. Click Back up this media server now using default settings. Click Next. Click Finish.
To create a backup job that uses custom settings 1 2 3 4 5 On the navigation bar, click the arrow next to Backup. Click New Backup Job using Wizard. Click Create a backup job with custom settings. Click Next. Follow the on-screen prompts.
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 2 3 On the navigation bar, click Backup. Uncheck Always launch the Backup Wizard from the Backup button. Click Next.
266
Creating a backup job by setting job properties
To set the Backup Wizard to launch from the Backup button 1 2 3 On the Tools menu, click Wizards>Backup Wizard. Check Always launch the Backup Wizard from the Backup button. Click Next.

If you have experience with Backup Exec, you can create a backup job by setting the properties you want. If you are new to Backup Exec or are uncertain about how to set up a backup job, you can use the Backup Wizard. See Creating a backup job by using the Backup Wizard on page 264. To create a backup job by setting job properties 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. From the backup selections pane, select the data you want to back up. See Selecting data to back up on page 231. 4 On the Properties pane, under Destination, click Device and Media. See Device and media options for backup jobs and templates on page 272. 5 On the Properties pane, under Settings, click General. See General options for backup jobs and templates on page 275. 6 If you want to set advanced options for the backup job, on the Properties pane, under Settings, click Advanced. See Advanced options for backup jobs on page 280. 7 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 and security options for a job on page 322.
267
If you want to set commands to run before or after a job, on the Properties pane, under Settings, click Pre/Post Commands. See Pre/post commands for backup or restore jobs on page 283.
If you are using the Advanced Open File Option, on the Properties pane, under Settings, select Advanced Open File. See Setting defaults for the Advanced Open File Option for backup jobs on page 816.
10 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. 11 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 573. 12 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 573. 13 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 286. 14 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 134. 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.
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.
This dialog box includes the following options:

Table 7-2 Item Selection list name Selections options for backup job Description If you are creating a job using an existing selection list, select the selection list you want to use. Otherwise, use the default Selection list name, which creates a new selection list using this name. Click this button if you want to use a previously created selection list or merge existing selection lists.
Load Selections from Existing List
Selection list description Enter a description for the selection list. View Selection Details Include/Exclude Include subdirectories Show file details Select this tab to view selections as a list of files and directories. Click this button if you want to use the Advanced File Selection for selecting files for backing up. Select this option if you want to select the contents of all the subfolders when a directory is selected. Select this option to display details about the files available for selecting.
Related Topics: Selecting data to back up on page 231 About selection lists on page 243 Including or excluding files for backup on page 241 Creating selection lists on page 244 Adding a user-defined selection to the User-defined Selections node on page 238
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.
269
To change the order for processing backup selections 1 2 3 4 5 6 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Select the data you want to back up. On the Properties pane, under Source, click Resource Order. Select an item you want to move. 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.
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. 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). See Creating a Backup Exec logon account on page 149. To change and test a logon account for a resource 1 2 3 4 5 6 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Select the data you want to back up. On the Properties pane, under Source, click Resource Credentials. Select the resource whose logon account you want to edit. Click Change.
270
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. 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.
Click OK.
271
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. This dialog box includes the following options:
Table 7-3 Item Device Device and Media options for backup job Description 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 387). 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 do the following to create more disk space:
Move the backup files to another disk or backing up the files to a tape. Change the location of the backup folder. Erase the backup files. Overwrite 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.
272
Creating a backup job by setting job properties Table 7-3 Item Restrict backup of the selection list to devices on the following media server or media servers in a pool Device and Media options for backup job (continued) Description 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. Select the media set for the backup. 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. See Setting the search order for overwritable media on page 182. If the media in the drive is not overwritable, an alert appears requesting that you insert overwritable media. Append to media, overwrite Select this option to append this backup to the media set listed in if no appendable media is the Media Set field in this dialog box. The backup set is appended if available 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. If the media in the drive is not overwritable, an alert appears requesting that you insert overwritable media.
Media set
273
Creating a backup job by setting job properties Table 7-3 Item Device and Media options for backup job (continued) Description
Append to media, terminate Select this option to append this backup to the media set listed in job if no appendable media the Media Set field in this dialog box. The backup set is appended if is available an appendable media is available in the selected media set; if not, the job is terminated. Eject media after job completes Retension media before backup 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. See About WORM media on page 195. Maximum number of Select the number of devices that this backup job can use. Only one devices to use for resources device per stream can be used. that support multiple data streams Minimum number of devices, terminate job if fewer devices are available 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.
Use Write once, read many (WORM) media
274
General options for backup jobs and templates

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. This dialog box includes the following options:
Table 7-4 Item Job name/Template name Backup set description General settings options Description Enter the name for this backup job or template, or accept the default name that appears. The name must be unique. Type a description of the information you are backing up.
275
Creating a backup job by setting job properties Table 7-4 Item Backup method for files General settings options (continued) Description Select one of the following backup methods:
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 but does not reset the archive bit. It does not affect your backup strategy or media rotation scheme. - 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 is backed up, but not deleted. 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 changed (based on the archive bit) since the last full backup. It does not affect your backup strategy or 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.
276
Creating a backup job by setting job properties Table 7-4 Item Backup method for files (continued) General settings options (continued) Description - 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. See Understanding backup methods and their advantages on page 224. 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. 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. 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.
277
Creating a backup job by setting job properties Table 7-4 Item Collect additional information for synthetic backup and for true image restore General settings options (continued) Description 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. See About the synthetic backup feature on page 832. Verify after backup completes 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.
278
Creating a backup job by setting job properties Table 7-4 Item Compression type General settings options (continued) Description 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.
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.
Related Topics: Creating a backup job by setting job properties on page 267
279
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. This dialog box includes the following options:
Table 7-5 Item Enable single instance backup for NTFS volumes Advanced options for backup job Description This option is only available if you use the Microsoft Windows Single Instance Store (SIS) feature. Single instance backup checks the NTFS volume for identical files. If Backup Exec finds multiple copies of a file, it only backs up one instance of that file, regardless of how many SIS links reference it. Single instance backup can considerably reduce the storage space that is required for your backups. Many applications automatically generate files that have identical content. The actual amount of space you save depends on the number of duplicate files on the volume. 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.
280
Creating a backup job by setting job properties Table 7-5 Item Advanced options for backup job (continued) Description
Back up files and directories Select this check box to back up the information for the junction by following junction points 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 Backup Exec does not follow junction points automatically created by Microsoft Windows Vista/Server 2008 because it can cause the data to be backed up repeatedly. For more information, see the following Symantec Knowledge Base article: http://entsupport.symantec.com/umi/V-269-9 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. Back up files and directories Select this option to back up the information for the symbolic links by following symbolic links and the files and directories to which they are linked. If you do not select this option, only the information for the symbolic links is backed up. The files and directories to which they are linked are not backed up. If the symbolic link points to files and directories on a remote computer, the files and directories on the remote computer are not backed up.
281
Creating a backup job by setting job properties Table 7-5 Item Back up data in Remote Storage Advanced options for backup job (continued) Description 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. 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 servers CPU processing power is used during backup operations. 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. 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. 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.
If closed within x seconds
282
Creating a backup job by setting job properties Table 7-5 Item With a lock Advanced options for backup job (continued) Description 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. 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. 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. 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.
Without a lock
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 <Systemroot>\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. Related Topics: Creating a backup job by setting job properties on page 267 Setting defaults for the Advanced Open File Option for backup jobs on page 816
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.
Chapter 7, Backing up data 283
You can run commands before or after a backup or restore job, and set the following 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. This dialog box includes the following options:
Table 7-6 Item Pre-command Pre- and post-command options Description 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. Commands that require user interaction, such as prompts, are not supported.
284
Creating a backup job by setting job properties Table 7-6 Item Post-command Pre- and post-command options (continued) Description 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. 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 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. Run job only if pre-command is successful 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. Run post-command only if pre-command is successful 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.
285
Scheduling jobs Table 7-6 Item Run post-command even if job fails Pre- and post-command options (continued) Description 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. Run post-command after job verification completes 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.
Cancel command if not Select the number of minutes Backup Exec should wait before completed within x minutes canceling a pre- or post-command that did not complete. The default time-out is 30 minutes. On this media server On each server backed up Select this option to run the pre- and post-commands on this media server only. 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.
Related Topics: Creating a backup job by setting job properties on page 267 Setting default backup options on page 307 Setting default pre/post commands on page 314
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. See Setting the schedule for a template on page 432.
286
Scheduling jobs
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. See Setting priority and availability windows for selection lists on page 250. See Configuring default schedule options on page 297. See Excluding dates from a schedule on page 296. 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. On the Properties pane, under Frequency, click Schedule. Select the appropriate options as follows:
Current date and time Run now Run on Date at Time Displays the current date and time set on this computer. Select Run now to run the job immediately. 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. Select Run according to schedule to configure a schedule for a recurring job. If you are editing an existing job, click Edit Schedule Details to select the run days for a recurring job. If Run according to schedule is selected, the effective date displays the day that the schedule begins.
2 3
Run according to schedule Edit Schedule Details Effective date
287
Scheduling jobs
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, its possible for the task to run on Saturday morning sometime before or at 4:00 AM. If you dont 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. 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 jobs 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. Select this to keep the jobs that were created to run once, and were not created from a template, in the Job Setup view.
Do not delete the job
Click Run Now.
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.
288
Scheduling jobs
Scheduling a job to run on specific days

You can schedule a job to run on a single day or on multiple 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 3 4 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule. Do one of the following:
To select run days for a new job To edit run days for an existing job Continue to step 5. Click Edit Schedule Details.
5 6
On the Calendar Schedule tab, under Edit Calendar schedule by, click Specific Dates. Do one of the following:
To select a single date

Click New. Enter the date. Click OK.
To select multiple dates
Click the dates on the calendar.
Click OK.
289
Scheduling jobs
Scheduling a job to run on recurring week days

Use the recurring week days option to run jobs on the following types of schedules:
Table 7-7 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 For example, every Wednesday.
For example, every day during the second week of the month.
For example, the last Friday of every 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 3 4 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule. Do one of the following:
On the Calendar Schedule tab, under Edit Calendar schedule by, click Recurring Week Days. Do one of the following:
To run a job on a single day Check the check box for that specific day.
290
Scheduling jobs
To run a job on the same day every week To run a job every day of an entire week
Select the name of the day in the matrix. For example, to run a job every Monday, click Mon Select the row number for that week. For example, to select the first week of each month, click 1st.
To run a job the last week Click Last. of the month, regardless of the number of weeks in a month To run a job on all days of Click Select All. the month To clear all existing selections Click Deselect All.
Click OK.
Scheduling a job to run on recurring days of the month

You can schedule jobs to run on specific days of the month, on the last day of the month, or on all 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 3 4 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule. Do one of the following:
On the Calendar Schedule tab, under Edit Calendar schedule by, click Recurring Days
of the Month.
291
Scheduling jobs

To run jobs on specific days of the month To run jobs on the last day of the month, regardless of the actual date Click the button for each day. Check Last Day.
To run a job on all days of Click Select All. the month To clear all existing selections Click Deselect All.
Click OK.
Scheduling a job to run on a day interval

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. 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 3 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule.
292
Scheduling jobs

5 6 7 8
On the Calendar Schedule tab, under Edit Calendar schedule by, click Day Interval Check Every. Enter the number of days on which you want the job to recur. 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.
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 3 4 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule. Do one of the following:
To select run days for a new job To edit run days for an existing job Chapter 7, Backing up data Continue to step 5. Click Edit Schedule Details.
293
Scheduling jobs
5 6 7 8
On the Calendar Schedule tab, under Edit Calendar schedule by, click Effective Date. Verify that the Make the schedule go into effect on check box is checked. Select the date on which you want the schedule to go into effect. 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. 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 3 4 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule. Do one of the following:
5
294
On the Calendar Schedule tab, under Edit Calendar schedule by, click Time Window.
Scheduling jobs
6 7 8
In the Start no earlier than box, select the time after which the job can start. In the and no later than box, select the time by which the job must start. 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. 2 3 4 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule. Do one of the following:
On the Calendar Schedule tab, under Edit Calendar schedule by, click Restart Time
Interval.
6 7 8
Check Restart task every. Select the time interval in hours, minutes, and seconds. Click OK.
295
Scheduling jobs
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 3 4 On the Properties pane, under Frequency, click Schedule. Click Run according to schedule. Do one of the following:
5 6
Click the Exclude Dates tab. 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. To add an excluded date back into the schedule

In the Exclude Dates box, click the date. Click Delete.
Click OK.
296
Archiving data
Configuring default schedule options

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 2 3 4 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Schedule. Click Edit Schedule Details and then select the appropriate options. Click OK.
Archiving data
With Backup Execs 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. 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. 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. The NTFS file system supports the last access date capability.
297
Duplicating backed up data
To archive data 1 2 3 4 5 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Select the data that you want to archive. Click General. In the Backup method for files field, select Working Set - Back up files - Last accessed in
(x) days.
In the Files accessed in x days field, enter the number of days to use as the criteria for selecting the files. Complete the backup job options (see Creating a backup job by setting job properties on page 267.)

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 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.
298
To duplicate backup data 1 2 3 From the navigation bar, click Job Setup. Under Backup Tasks, select New job to duplicate backup sets. If you want to copy existing backup sets to another destination, do the following in the order listed:

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.
If you want to duplicate backup sets created when a scheduled backup job runs, do the following in the order listed:

Select Duplicate backup sets following a job, and then click OK. Select the scheduled backup job to be used as the source.
On the Properties pane, under Destination, select Device and Media. See Device and media options for backup jobs and templates on page 272.
On the Properties pane, under Settings, click General, and complete the appropriate options as follows:
Job name Job priority Type the name for this backup job. 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 can choose the following priorities:

Backup set description Preferred source device
Type a description of the information you are backing up. Select the device used as the destination device for the original backup job.
299
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 (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.
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 type from the list.Select an encryption key from the list or click Manage keys to create a new key.
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 573.
10 If you are duplicating data from a scheduled backup job, click Run Now. The duplicate job will launch immediately following the completion of the scheduled backup job.
300
Backing up virtual machines and the Virtual Server Host
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 286).
Backing up virtual machines and the Virtual Server Host

Backup Exec uses Microsofts Volume Shadow Copy Service (VSS) to back up the Virtual Server Configuration and guest virtual machines. VSS can back up a computer while applications and services are running by creating a copy of the volume when the backup is initiated. You can back up a guest virtual machine no matter which operating system it uses. However, only the guest virtual machines that run Microsoft Windows Server 2003 or later with virtual machine additions installed are available for backups without downtime. Guest virtual machines that use other operating systems are briefly placed in a saved state for backups. The amount of downtime that is required depends on how much memory is allocated to the virtual machine and the operating systems current load. You can use Backup Exec agents, such as the SQL or Exchange Agent, to back up individual files and applications within guest virtual machines. To back up virtual machines and Virtual Server Host settings 1 2 3 4 5 6 7 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the selection list, navigate to the Virtual Server Host. Expand Shadow Copy Components. Expand User Data. Select the set of virtual guest machines you want to back up. To back up the Virtual Server Host settings, check Virtual Server Configuration. You must select the Virtual Server Configuration to back up the Virtual Server Host. 8 Do one of the following:
To start the backup job To select other backup options Chapter 7, Backing up data Click Run Now. Use the properties pane. 301
Verifying a backup
Related Topics: About backing up virtual machines and the Virtual Server Host on page 260 Upgrading existing Shadow Copy Component backup jobs to version 12 on page 261
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. See Setting default backup options on page 307. See Verify after job completes on page 300. To verify a backup 1 2 3 4 5 6 7 On the navigation bar, click Job Setup. In the task pane, under Backup Tasks, click New job to verify backup data. Select the media you want to verify. On the Properties pane, under Destination, click Device. Select the device that contains the media you want to verify. On the Properties pane, under Settings, click General. Select the appropriate options as follows:
Job name Type a name that describes the data you are verifying.
302
Creating a test run 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. You can choose the following priorities:

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 573.
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 286.
After verification has completed, you can check the results in the job log.

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.
303
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. 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 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. See Test Run Results Report on page 656. To create a test run job 1 2 3 4 On the navigation bar, click Job Setup. In the Jobs pane, select the job for which you want to create a test run. Under General Tasks, click Test Run. Select the appropriate General options as follows:
Job name Credentials check Media capacity check to complete individual job Type a name for the test run job. Select this check box to verify that the Backup Exec logon account is correct for the resources being backed up. Select this check box to test if there is enough available capacity on the media to complete the job. 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 Use previous job history, if available Select this check box to test whether the media is online and overwritable. 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.
304
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 Select this option to have the scheduled job placed on hold if any the scheduled job on hold failures are detected during the test run. 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. You can choose the following priorities:

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 573.
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 286).
Setting test run default options

You can set up test run jobs to check the following items:

Whether credentials are correct Whether there is enough available capacity on the media Whether the media is online and overwritable
To set test run default options 1 2 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Test Run.
305

Check credentials Select this check box to verify that the Backup Exec logon account is correct for the resources being backed up.
Check media capacity to Select this check box to test if there is enough available capacity on complete job the media to complete the job. 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, Select this option to use past job histories to determine whether if available 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. Select this option to have the scheduled job placed on hold if any failures are detected during the test run.
Place the scheduled job on hold if any failure occurs during the Test Run job
Click OK.
306
Chapter
Customizing backup options

Customizing backup options consist of the following:

Setting default backup options Setting default pre/post commands Specifying a backup network Using Backup Exec with Symantec Endpoint Protection Using Backup Exec with firewalls Setting up encryption keys
Setting default backup options

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 2 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Backup.
307

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. See Understanding backup methods and their advantages on page 224. Files accessed in x days Use the Microsoft Change Journal if available When the Working Set backup method is selected, use this field to specify the number of days for which to include accessed files. 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.
Collect additional This option displays only for templates. It is used with synthetic information for synthetic backup jobs and true image restore jobs. backup and for true image Select this option if you want Backup Exec to do the following: restore 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. See About the synthetic backup feature on page 832.
308
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. See Media overwrite protection levels on page 182. 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 136. 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. F See Media overwrite protection on page 172. 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 136. The backup set is appended if an appendable media is available in the selected media set; if not, the job is terminated.
Chapter 8, Customizing backup options
309
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). 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.
310
Back up files and directories by following junction points
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 Backup Exec does not follow junction points automatically created by Microsoft Windows Vista/Server 2008 because it can cause the data to be backed up repeatedly. You can find information about junction points at the following URL: http://entsupport.symantec.com/umi/V-269-9 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. 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.
Back up files and directories by following symbolic links
Select this option to back up the information for the symbolic links and the files and directories to which they are linked. If you do not select this option, only the information for the symbolic links is backed up. The files and directories to which they are linked are not backed up. If the symbolic link points to files and directories on a remote computer, the files and directories on the remote computer are not backed up.
311
Back up data in Remote Storage
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. 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.
Enable single instance backup for NTFS
This option is only available if you use the Microsoft Windows Single Instance Store (SIS) feature. Single instance backup checks the NTFS volume for identical files. If Backup Exec finds multiple copies of a file, it only backs up one instance of that file, regardless of how many SIS links reference it. Single instance backup can considerably reduce the storage space that is required for your backups. Many applications automatically generate files that have identical content. The actual amount of space you save depends on the number of duplicate files on the volume. 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.
312
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. 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. 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. See About the Advanced Open File Option on page 809.
Without a lock
If Backup Exec Granular Recovery Technology (GRT) is enabled for backup, enter a path on the NTFS volume of the local media server where Backup Exec can stage temporary data
Ensure that the default location of C:\temp is an NTFS volume, and that it is not a system volume. If C:\temp does not meet these requirements, type another path to an NTFS volume on the local media server where Backup Exec can stage temporary data. Backup Exec deletes the data when the backup completes. At least 1 GB of disk space is required.
313
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 the following:

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 2 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Pre/Post Commands.
314

Allow pre- and post-commands to be successful only if completed with a return code of zero 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. Run job only if Select this option to run the backup or restore job only if the pre-command is successful 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. Run post-command only if Select this option to run the post-command only if the pre-command is successful 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. Run post-command even if Select this option if it is critical to run the post-command job fails 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.
315
Specifying backup networks
Run post-command after job verification completes Cancel command if not completed within x minutes On this media server On each server backed up or restored to
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. Select this option to run the pre- and post-commands on this media server only. 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.
Click OK.
Related Topics: Pre/post commands for backup or restore jobs on page 283

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.
316
Specifying backup networks Example of backup network

backup network network ID: 128.10.0.0 subnet mask: 255.255.0.0
IP address: 128.10.0.1 IP address: 10.67.0.1
router A
router B database server running Remote Agent Backup Exec media server
corporate network network ID: 128.20.0.0 subnet mask: 255.255.0.0
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 users 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.
317
Related Topics: Using Backup Exec with firewalls on page 326 Browsing systems through a firewall on page 329
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. You can also set default security options for Backup Exec jobs. You can select a default encryption type or key for your backup jobs. If you use Symantec Endpoint Protection 11.0 or later, you can configure it to prompt Backup Exec to back up data when global threats arise. The backup settings you select are set as the default for all new backup jobs and templates you create. You can manually change these settings when you create specific jobs or templates.
318
To set the default backup network and security options 1 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Network and Security. Select the appropriate options as follows:
Enable selection of user shares Select this option to enable selection of Windows user shares.
319
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 326.
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. 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. Select the protocol you want to use. The options are as follows:

Interface details
Protocol
Use any available protocol Use IPv4 Use IPv6
Subnet Allow use of any available network interface, protocol, or subnet for remote agents not bound to the above network interface, protocol, or subnet
Displays the 32-bit number that determines the subnet to which the network interface card belongs. 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
320
Use a custom port to Check Use a custom port to receive operation requests from the receive operation requests remote system to change the port used for communications from the remote system 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. Read the following topic 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 1390. Encryption type Select the type of encryption you want to use, if any. See About encryption on page 330. Encryption key Manage keys Run backup immediately when an elevated Symantec ThreatCon level is reached Select the default encryption key you want to use. Click Manage keys to create a new encryption key or delete an existing encryption key. Select whether you want to run automatic backups when the Symantec ThreatCon reaches the level you specify in the Symantec ThreatCon level field. You must have Symantec Endpoint Protection 11.0 or later installed on the same computer as Backup Exec to use this feature.
Symantec ThreatCon level Select the ThreatCon level at which you want automatic backups to run. You can find more information about Symantec ThreatCon levels at the following URL: http://www.symantec.com Time range for Security Summary page Select the time range for which you want to display Symantec Endpoint Protection data on the Security Summary page. You should select the same time range you have specified in your Endpoint Protection preferences. You must have Symantec Endpoint Protection 11.0 or later installed on the same computer as Backup Exec to use this feature. Additionally, you must install the Symantec Endpoint Protection Manager component to use the Security Summary. See the Administrators Guide for Symantec Endpoint Protection for more information about Symantec Endpoint Protection.
321
Related Topics: Changing the backup network and security options for a job on page 322 Specifying the restore network on page 533 About encryption on page 330 Encryption keys on page 332 About using Backup Exec with Symantec Endpoint Protection on page 324 Viewing the Symantec Endpoint Protection Security Summary on page 485
Changing the backup network and security options for a job

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. You can also change your default security options for an individual job. You can choose to encrypt a backup job. If you use Symantec Endpoint Protection 11.0 or later, you can configure the job to run automatically when global threats arise. To change the backup network for a job 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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 267. 4 On the Properties pane, under Settings, click Network and Security.
322

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. Protocol Select the protocol you want to use. The options are as follows:

Subnet Allow use of any available network interface, subnet, or protocol for remote agents not bound to the above network interface, subnet, or protocol
Displays the 32-bit number that determines the subnet to which the network interface card belongs. 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. 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. Select the type of encryption you want to use, if any. See About encryption on page 330.
Interface details
Encryption type
Encryption key Manage keys Run this backup job immediately when an elevated Symantec ThreatCon level is reached Chapter 8, Customizing backup options
Select the encryption key you want to use. Click Manage keys to create a new encryption key or delete an existing encryption key. Select whether you want to run this backup job when the Symantec ThreatCon reaches the level you specify in the Symantec ThreatCon level field. You must have Symantec Endpoint Protection 11.0 or later installed on the same computer as Backup Exec to use this feature. 323
About using Backup Exec with Symantec Endpoint Protection
Symantec ThreatCon level
Select the ThreatCon level at which you want this backup to run automatically. You can find more information about Symantec ThreatCon levels at the following URL: http://www.symantec.com
Complete the backup job as normal.
Related Topics: Specifying backup networks on page 316 Setting default backup network and security options on page 318 Creating a backup job by setting job properties on page 267 About encryption on page 330 Encryption keys on page 332 About using Backup Exec with Symantec Endpoint Protection on page 324

You can use Symantec Endpoint Protection version 11.0 or later with Backup Exec to provide extra security when the threat of viruses or malware is high. You can also view Symantec Endpoint Protection security information from the Backup Exec Security Summary. You must install the Symantec Endpoint Protection Manager component to use the Security Summary. Symantec Endpoint Protection uses a ThreatCon level to provide an overall view of global Internet security. Symantecs ThreatCon levels are based on a 1-4 rating system, with level 4 being the highest threat level. You can find more information about Symantec ThreatCon levels at the following URL: http://www.symantec.com You can configure Backup Exec to automatically run a backup job when the ThreatCon reaches a level that you specify. You may want to configure special jobs for your most crucial data, for example. This strategy helps make sure that your vital data is safely backed up as soon as global threats are detected. You should consider the types of jobs that you want to trigger automatically and the potential impact they can have on your system resources. The ThreatCon level is updated frequently and can be raised at any time without warning. If you configure large or resource-intensive jobs to launch automatically, they may interfere with your normal business operations.
See the Administrators Guide for Symantec Endpoint Protection for more information about Symantec Endpoint Protection. Related Topics: Changing the backup network and security options for a job on page 322 Creating automatic backup jobs for use with Symantec Endpoint Protection on page 325 Setting default backup network and security options on page 318 Viewing the Symantec Endpoint Protection Security Summary on page 485
Creating automatic backup jobs for use with Symantec Endpoint Protection
You can use Symantec Endpoint Protection version 11.0 or later with Backup Exec to provide extra security when the threat of viruses or malware is high. You can configure Backup Exec to automatically run a backup job when the Symantec ThreatCon reaches a level that you specify. You can find more information about Symantec ThreatCon levels at the following URL: http://www.symantec.com Caution The ThreatCon level is updated frequently and can be raised at any time without warning. If you configure large or resource-intensive jobs to launch automatically, they may interfere with your normal business operations. Creating backup jobs for use with Symantec Endpoint Protection 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Select data and set General and Advanced options. See Creating a backup job by setting job properties on page 267. 4 5 In the Properties pane, under Settings, click Network and Security. Check the Run this backup job immediately when an elevated Symantec ThreatCon level is reached check box. In the Symantec ThreatCon level list, select the level at which you want to Backup Exec to launch this job.
325
Using Backup Exec with firewalls
Process the backup job as normal.
Related Topics: Changing the backup network and security options for a job on page 322 Setting default backup network and security options on page 318 About using Backup Exec with Symantec Endpoint Protection on page 324

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
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. The following tables provide more information about which ports Backup Exec for Windows Servers and its agents and options use:
Table 8-1 Backup Exec for Windows Servers Ports Port Port Type TCP TCP TCP TCP UDP
Service or Process
Backup Exec Agent Browser (process=benetns.exe) 6101 Backup Exec Remote Agent for Windows Servers (process=beremote.exe) Backup Exec Server (process=beserver.exe) MSSQL$BKUPEXEC (process=sqlservr.exe) 10000 3527, 6106 1125 1434 (ms-sql-m) Backup Exec Remote Agent for NetWare Oracle Agent for Windows and Linux Servers DB2 Agent for Windows and Linux Servers Remote Agent for Linux or Unix Servers (RALUS)
10000 (Backup Exec 10.x), 6102 TCP (Backup Exec 9.x) Random port unless configured otherwise Random port unless configured otherwise Default NDMP port, typically 10000 TCP
327
Using Backup Exec with firewalls Table 8-1 Backup Exec for Windows Servers Ports (continued) Port 88 135 137 138 139 445 3106 6103 Port Type UDP TCP, UDP UDP UDP TCP TCP TCP TCP TCP TCP
Service or Process Kerberos NETBIOS NETBIOS Name Service NETBIOS Datagram Service NETBIOS Session Service NETBIOS (Windows 2000) DCOM/RPC Backup Exec Remote Agent
Push Install - Check for conflicts in message queue 103x for CASO which is part of beserver.exe Push Install SMTP email notification SNMP 441
25 outbound from media server TCP 162 outbound from media server TCP
When Backup Exec is not running operations, it listens to ports for incoming communication from other services and agents. Backup Exec initially communicates with the Remote Agent using a static listening port to begin an operation. The agent and the media server then use dynamic ports to pass data back and forth. Backup Exec uses the following listening ports:
Table 8-2 Service Backup Exec Agent Browser (benetns.exe) Backup Exec Remote Agent for Windows Server (beremote.exe) Backup Exec Server (beserver.exe) MSSQL$BKUPEXEC (sqlsevr.exe) Backup Exec for Windows Servers Listening Ports Port 6101 10000 3527, 6106 1125 1434 328 Port Type TCP TCP TCP TCP UDP Administrators Guide
Using Backup Exec with firewalls Table 8-2 Service Backup Exec Remote Agent for NetWare Backup Exec for Windows Servers Listening Ports (continued) Port 10000, 6102 Port Type TCP TCP TCP
Remote Agent for Linux and UNIX Servers (RALUS) 10000 DBA-initiated backups for Oracle and DB2 5633
The Backup Exec Desktop and Laptop Option (DLO) additionally uses the following ports:
Table 8-3 Backup Exec Desktop and Laptop Option Ports Port 135-139 445 1434 3999 in listening mode Port Type TCP/UDP TCP/UDP TCP/UDP TCP/UDP
Service or Process Server Message Block (SMB) communication Server Message Block (SMB) communication without NETBIOS SQL DLOAdminSvcu.exe (DLO admin service)
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 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Network and Security. 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.
329
About encryption
About enabling a SQL instance behind a firewall

If you want to connect to a SQL instance behind a firewall, you must enable the SQL instance for communication. To enable the SQL instance for communication, you must make the SQL port static and configure the Windows Firewall. The Backup Exec SQL instance is configured to use a dynamic port by default. Each time SQL Server is started, the port number can change. See Changing the dynamic port on a SQL Express instance to a static port on page 757. See Opening a SQL port for a SQL 2000 or 2005 instance on page 759. You also must configure the Windows Firewall to allow connections to the SQL instance. There may be multiple ways to configure the Windows Firewall based on your system configuration. You can add sqlsvr.exe and sqlbrowser.exe to the Windows Firewall Exceptions list or you can open a port in the Windows Firewall for TCP access. Refer to the Microsoft Knowledge Base for more information or to determine which configuration is best for your network.
About encryption
Backup Exec provides you with the ability to encrypt data. When you encrypt data, you protect it from unauthorized access. Anyone that tries to access the data has to have an encryption key that you create. Backup Exec provides software encryption, but it also supports some devices that provide hardware encryption with the T10 standard. Backup Exec supports two security levels 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. Hardware encryption using the T10 standard requires 256-bit AES. Related Topics: About software encryption on page 331 About hardware encryption on page 331 Encryption keys on page 332
330
About encryption
About software encryption

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 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. 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 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 software encryption. Hardware compression is performed after encryption. Data becomes randomized during the encryption process. Compression does not work effectively on data that is randomized. Related Topics: About encryption on page 330
About hardware encryption

Backup Exec supports hardware encryption for storage devices that use the T10 encryption standard. When you use hardware encryption, the data is transmitted from the host computer to the target device and then encrypted on the device. Backup Exec manages the encryption keys that are used to access the encrypted data. Backup Exec only supports approved devices for T10 encryption. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/v-269-2 Related Topics: About encryption on page 330
331
Encryption keys
Encryption keys
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 1522. Related Topics: About encryption on page 330 Setting default backup network and security options on page 318
Restricted keys and common keys

Backup Exec has the following types of encryption keys:
Table 8-4 Key type Common Types of encryption keys Description Anyone can use the key to encrypt data during a backup job and to restore encrypted data.
332
Encryption keys Table 8-4 Key type Restricted Types of encryption keys (continued) Description 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 keys 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. Note Hardware encryption that uses the T10 standard requires 256-bit AES. Backup Exec does not let you enable hardware encryption for a job unless it uses at least a 16-character pass phrase. 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{|}~ Related Topics: Creating an encryption key on page 334 Selecting an encryption key for a backup job on page 335 Setting default backup network and security options on page 318 Deleting an encryption key on page 337
333
Encryption keys
About encryption key management

When a user creates an encryption key, Backup Exec marks that key with an identifier based on the logged-on users 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. 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 meets the following criteria:

Has the same user accounts as the original media server. Is in the same domain as the original media server.
Related Topics: Pass phrases on page 333 Replacing an encryption key on page 336
Creating an encryption key

When you create an encryption key, you select the type of encryption to use.
334
Encryption keys
To create an encryption key 1 2 3 On the Tools menu, click Encryption Keys. Click New. Complete the appropriate options as follows:
Key name Encryption type Type a unique name for this key. The name can include up to 256 characters. 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. Hardware encryption that uses the T10 standard requires 256-bit AES. 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. See Pass phrases on page 333. Confirm pass phrase Common Restricted Retype the pass phrase. 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. 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.
Click OK.
Selecting an encryption key for a backup job

When you are creating a backup job, you can do the following:
Use an existing key.
335
Encryption keys
Create a new key.
To select an encryption key for a backup job 1 2 3 4 5 6 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Select the data that you want to back up. On the Properties pane, under Settings, click Network and Security. In the Encryption type field, select the type of encryption you want to use. In the Encryption key field, do one of the following:
To use an existing key To create a new key Select the key from the list. Click the arrow, and then click <new encryption key>.
Process the backup job as normal.
Related Topics: Duplicating backed up data on page 298 Adding a duplicate backup template to a policy on page 444 Creating a synthetic backup by adding templates to a policy on page 840 Creating an encryption key on page 334
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 2 3 On the Tools menu, click Encryption Keys. Select the key that you want to replace. Click Replace.
336
Encryption keys
In the Select an encryption key to replace key name box, do one of the following:
To use an existing key To create a new key Select the key from the list. Click the arrow, and then click <new encryption key>.
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 in the following situations:

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 2 3 4 5 On the Tools menu, click Encryption Keys. Select the key that you want to delete. Click Delete. Click Yes. 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.
337
Encryption keys
Related Topics: Replacing an encryption key on page 336
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. Related Topics: Pass phrases on page 333 About encryption key management on page 334 Replacing an encryption key on page 336
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. Related Topics: About encryption key management on page 334 Creating an encryption key on page 334
338
Chapter
Managing tape drives and robotic libraries

When you install Backup Exec, all storage devices that are 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. The view on the Devices tab displays how devices are organized logically into device pools, and how devices are arranged physically on servers. 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. The Device Configuration Wizard is available to help you install Symantec device drivers, and to correct robotic library drives that are inadvertently displayed as unknown devices in the Devices view. Note Backup Exec includes support for a single robotic library device. Licenses for additional robotic library devices are available for purchase. Related Topics: Configuring storage devices by using the Device Configuration Wizard on page 340 Installing Symantec device drivers by using the Symantec Device Driver Installation Wizard on page 342 Viewing storage device properties on page 343 About robotic libraries in Backup Exec on page 355 About creating utility jobs to help manage devices and media on page 367 About devices in the shared storage environment on page 1549
339
Configuring storage devices by using the Device Configuration Wizard
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. Use the Device Configuration Wizard for the following tasks:
Table 9-1 You can Create a backup-to-disk folder Device Configuration Wizard tasks More information 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. See Creating a backup-to-disk folder by using the Backup-to-disk Wizard on page 391. See Requirements for creating a removable backup-to-disk folder on page 390. See Configuring advanced options for a backup-to-disk folder on page 395. See Setting defaults for new backup-to-disk folders on page 396. 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 342.
340
Adding devices by using the Hot-swappable Device Wizard Table 9-1 You can Configure robotic library drives Device Configuration Wizard tasks More information 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 355. See Enabling robotic library support on page 356. See Configuring a robotic library on page 357.
To start the Device Configuration Wizard 1 2 3 On the navigation bar, click Devices. In the task pane, under Device Wizards, click Device configuration wizard. Follow the on-screen prompts.
Related Topics: Adding devices by using the Hot-swappable Device Wizard on page 341
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.
Chapter 9, Managing tape drives and robotic libraries
341
Installing Symantec device drivers by using the Symantec Device Driver Installation Wizard
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. To start the Hot-swappable Device Wizard 1 2 3 On the navigation bar, click Devices. In the task pane, under Device Wizards, click Hot-swappable device wizard. 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. Tapeinst.exe is located in the Backup Exec for Windows Servers installation directory. Tapeinst.exe updates are available in the Device Driver Installer package. You can download the Device Driver Installer package at the following URL: http://entsupport.symantec.com/rd/bews-downloads.htm Note You must run Tapeinst.exe locally at the media server where you want to install tape device drivers. You cannot use tapeinst.exe to push-install tape device drivers to remote media servers.
342
Viewing storage device properties
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 340

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 devices properties 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the device for which you want to view properties. Under General Tasks in the task pane, select Properties. Click any of the tabs, and review the information. See Viewing a devices general properties on page 344.
3 4 5
343
See Viewing a devices configuration properties on page 346. See Viewing a devices SCSI information on page 349. See Viewing a devices statistics on page 350. See Viewing a devices cleaning properties on page 351. See Viewing and specifying types of media for a device on page 353.
Viewing a devices 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 devices general properties 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the device for which you want to view properties. 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.
3 4
344
Status
The following statuses are available:
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 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.
The device is displayed as offline if the following occurs:

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 Product ID Firmware
Name of the vendor of the drive. Product ID from the SCSI Inquiry string. Version of the firmware used in the device.
345
Drive type Media type Date in service Serial number
Media and memory specifications of the device. If the device is a stand-alone drive, the media type used in this drive type is displayed. Date this device was first detected by this installation of Backup Exec. Serial number of the drive.
Related Topics: Viewing storage device properties on page 343 Renaming a backup-to-disk file on page 402
Viewing a devices configuration properties

The Drive Properties Configuration tab lets you do the following:

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 devices configuration properties 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the device for which you want to view properties. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click Configuration.
3 4
346
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 or larger. If you use a device that supports larger block sizes, you can change the devices block size in the Device Configuration tab. However, if the option to change the block size is unavailable, you must configure the device to use a larger size. See the device manufacturers documentation for help in configuring the device. 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.
347
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 Read single block mode
Click this button to return all the Preferred Configuration settings to their defaults, and then click OK. 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.
348
Read SCSI pass-through mode
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.
Write SCSI pass-through mode
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.
Related Topics: Viewing storage device properties on page 343
Viewing a devices SCSI information

The SCSI Information tab provides information about the Small Computer System Interface (SCSI). To view a devices SCSI information 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the device for which you want to view properties. 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 Port Bus Target ID Device information read from the device firmware. Identifying number of the port on the server to which the device is attached. Identifying number of the bus to which the device is attached. Unique SCSI ID number (physical unit number).
3 4
349
LUN
Logical Unit Number of the device.
Viewing a devices 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 devices statistics properties 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the device for which you want to view properties. 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 Total bytes written Total bytes read Total mounts Total seeks Last date that media was mounted by this device. Number of bytes that have been written by this device. Number of bytes that have been read by this device. Number of times media has been mounted by this device. Total number of seek operations (performed when a specific piece of information is being located) that have been performed by this device. Total number of hours that this device has been in use (performing read, write, mount, and seek operations). Number of errors encountered while trying to locate data.
3 4
Total hours in use Seek errors
350
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. 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. 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. 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.
Hard read errors
Soft write errors
Hard write errors
Viewing a devices cleaning properties

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, you can reset the cleaning statistics after the drive has been manually cleaned. To view a devices cleaning properties 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the device for which you want to view properties. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click Cleaning.
3 4
351
The Cleaning tab provides the following information:

Last cleaning date Hours since last cleaning Reset Cleaning Statistics Bytes written Bytes read Total mounts Total seeks Last date a cleaning operation was performed on the device. Number of hours that the device has been in use since the last cleaning. Click this to reset all cleaning statistics to zero (stand-alone drives only). Number of bytes that have been written by this device since the last cleaning. Number of bytes that have been read by this device since the last cleaning. Number of times media has been mounted by this device since the last cleaning. 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. Total number of hours that this device has been in use (performing read, write, mount, and seek operations) since the last cleaning. Number of errors encountered since the last cleaning while trying to locate data. 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. 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. 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. 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.
Hours in use
Seek errors Soft read errors
Hard read errors
Soft write errors
Hard write errors
352
Viewing and specifying types of media for a device

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 Execs 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. This information is 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 devices media type properties 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the device for which you want to view properties. 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. Displays Yes if this media type can be read by the device; otherwise, displays No.
3 4
Read
353
Pausing and resuming devices
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 343 Bar code rules in mixed media libraries on page 193
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 2 3 On the navigation bar, click Devices. Click the server icon. 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 2 3 On the navigation bar, click Devices. Click the robotic library device or stand-alone drive. 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.
354
Renaming a robotic library or device
Related Topics: Pausing and resuming a backup-to-disk folder on page 402
Renaming a robotic library or device

You can rename the media servers storage devices as well as any attached robotic libraries. To rename a robotic library or device 1 2 3 4 On the navigation bar, click Devices. Click the robotic library or device that you want to rename. Under General Tasks in the task pane, click Rename. On the Rename dialog box, type the new name, and then click OK.
Related Topics: Pausing and resuming a backup-to-disk folder on page 402 Renaming a device pool on page 417 Renaming a cascaded drive pool on page 422
About robotic libraries in Backup Exec

Backup Execs 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 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 Execs 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 jobs 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.
Chapter 9, Managing tape drives and robotic libraries 355
Enabling robotic library support
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 356 Importing media to a robotic library on page 378 Configuring a robotic library on page 357 Installing the Library Expansion Option on page 1539
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 2 3 On the Tools menu, click Install Options and LIcense Keys on this Media Server. On the Enter License Keys panel, click Next. On the Symantec Backup Exec Options panel, click 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.
356
Configuring a 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. 4 5 6 Click Next. Review the installation review, and then click Install. 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 Execs 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. To configure a robotic library 1 Start the Device Configuration Wizard by clicking Tools>Wizards>Device Configuration Wizard. On the Welcome screen, click Next. Review the device summary, and then click Next. On the Create and Configure Backup Devices screen, click Configure robotic library drives, and then click Next. 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:
2 3 4
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, enable robotic library support.
357
Viewing robotic library properties
See Enabling robotic library support on page 356.
If your robotic library uses a zero-based slot configuration, be sure the Slot Base field on the Configuration tab of the robots Properties dialog box displays 0.
After completing the configuration of your robotic library, click Next, and then click Finish to exit the wizard. Run an Inventory operation to update Backup Execs media database. See Inventorying media on page 368.
Related Topics: Setting up robotic library hardware on page 1538 Before you install on page 61 Setting up cleaning jobs on page 377

Through the robotic librarys 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 2 3 4 5 On the navigation bar, click Devices. Expand the server icon in the tree view, and then click Robotic Libraries. Select the robotic library. Under General Tasks in the task pane, select Properties. Click any of the tabs, and review the following information: See Viewing robotic library general properties on page 359. See Viewing robotic library configuration properties on page 361. See Viewing SCSI information for a robotic library on page 362. See Viewing statistics for a robotic library on page 362. 6 Click OK.
358
Viewing robotic library general properties

While most of the information appearing on the General tab for a robotic librarys 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 2 3 4 5 On the navigation bar, click Devices. Expand the server icon in the tree view, and then click Robotic Libraries. Select the robotic library. In the task pane, under General Tasks, click Properties. On the Library Properties dialog box, click General. The General tab provides the following information:
Name Name of the robotic library. You can rename the device by typing a new name in this field.
359
Status
The following statuses are available:
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 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 behaves as if the device with its old name or identity no longer exists. To put the device online, try the following:
The device is displayed as offline if the following occurs:

Check to make sure the device has power and that cables are properly attached. Turn on the device and restart 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 Product ID Firmware
Name of the vendor of the robotic library. Product ID from the SCSI Inquiry string. Version of the firmware used in the device.
360
Library type Date in service Serial number
Manufacturer and model number of the robotic library. Date this device was first detected by Backup Exec. Serial number of the robotic library.
Related Topics: Viewing robotic library properties on page 358
Viewing robotic library configuration properties

Through the Configuration tab of a robotic librarys properties dialog box, you can enable start-up initialization for the robotic library. You also can enable bar code rules and specify slot base numbering. To view configuration properties of a robotic library 1 2 3 4 5 On the navigation bar, click Devices. Expand the server icon in the tree view, and then click Robotic Libraries. Select the robotic library. In the task pane, under General Tasks, click Properties. On the Library Properties dialog box, click Configuration. The Configuration tab provides the following information:
Enable startup initialization Enable bar code rules 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. Select this check box to enable bar code rules. See Bar code rules in mixed media libraries on page 193. 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.
361
Viewing SCSI information for a robotic library

You can view the SCSI information for a robotic library. To view SCSI information properties of a robotic library 1 2 3 4 5 On the navigation bar, click Devices. Expand the server icon in the tree view, and then click Robotic Libraries. Select the robotic library. In the task pane, under General Tasks, click Properties. On the Library Properties dialog box, click SCSI Information. The SCSI Information tab of a robotic librarys properties dialog box displays the following information:
Inquiry Port Bus Target ID LUN Device information that is read from the device firmware. Identifying number of the port on the server to which the device is attached. Identifying number of the bus to which the device is attached. Unique SCSI ID number (physical unit number). Logical Unit Number of the device.
Viewing statistics for a robotic library

You can view statistics for a robotic library. To view statistics properties of a robotic library 1 2 3 On the navigation bar, click Devices. Expand the server icon in the tree view, and then click Robotic Libraries. Select the robotic library.
362
4 5
In the tasks pane, under General Tasks, click Properties. On the Library Properties dialog box, click Statistics. The Statistics tab of a robotic librarys properties dialog box provides the following information:
Slot count Drive element count Total mounts Mount errors Number of slots in the robotic library. Number of drive elements contained in the robotic library. Number of times media has been mounted by this device. Number of errors encountered while mounting media in a drive.
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 partitions 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. 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 Execs 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.).
363
To create partitions 1 2 3 4 5 On the navigation bar, click Devices. Expand the server icon, and then click Robotic Libraries. Select the robotic library containing the slots that you want to partition. Under Robotic Library Tasks in the task pane, select Configure partitions. 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. 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.
364
Viewing robotic library properties Configure Partitions dialog box Partition Divider
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 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 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 partition settings.
Move Up
Move Down
Remove All
7 8
Click OK after configuring the partitions. 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.
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.
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 the following:
Table 9-2 Partition Partition 1 Partition 2 Partition 3 Robotic library partition example Slot Slots 1 - 2 Slots 3 - 4 Slots 5 - 10
The library is repartitioned as follows:

Table 9-3 Partition Partition 1 Partition 2 Partition 3 Robotic library repartition example Slot Slots 1 - 4 Slots 5 - 6 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.
366
About creating utility jobs to help manage devices and media
Related Topics: Creating robotic library partitions on page 363 Retargeting a scheduled job from a deleted device pool or media set on page 416

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:
Table 9-4 Utility jobs that can be scheduled For more information See Cataloging media while reviewing devices or media on page 196. See Creating a restore job while reviewing media or devices on page 198. See Inventorying media on page 368. See Erasing media on page 370. See Importing media to a robotic library on page 378. See Exporting media from a robotic library on page 380. See Exporting expired media from a robotic library on page 383. See Locking the robotic librarys front panel on page 381. See Unlocking the robotic librarys front panel on page 383. See Setting up cleaning jobs on page 377.
Utility job that can be scheduled Catalog media Restore data Inventory robotic library or device Erase media in a robotic library or device Import media Export media Export expired media (robotic libraries only) Lock robotic library Unlock robotic library Clean drive
367
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:
Table 9-5 Utility jobs that can run once For more information See Labeling media on page 374. See Formatting media in a drive on page 373. See Retensioning a tape on page 372. See Ejecting media from a drive on page 376. See Initializing the robotic library on page 382.
Utility jobs that can run once: Label media Format media, including WORM media Retension media Eject media Initialize robotic library
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
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 hasnt 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:
368
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 doesnt 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 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the device resides in a robotic library, click Robotic Libraries. If you want to inventory a drive or slot, select the drive or slot containing the media you want to inventory, or select Slots. If you want to inventory a backup-to-disk file, do the following in the order listed:
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 6
Under Media Tasks in the task pane, select Inventory. Select the appropriate options as follows:
Job name Job priority Type a name for the job or accept the default name. Select the priority for the job. Available options are as follows:

Lowest Low Medium High Highest
369
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 573.
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 191 Include robotic libraries in inventory job when Backup Exec services start up on page 136
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 2 3 4 On the Tools menu, click Options. In the Properties pane, under Settings, click Preferences. Click Inventory all drives on Backup Exec services startup. Click OK.
Erasing media
You can erase media by 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.
370
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 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the device resides in a robotic library, click Robotic Libraries. Select the drive or slot containing the media you want to erase. Under Media Tasks in the task pane, select either Erase media, quick or Erase media, long. 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 7 When prompted, click Yes to erase the media. Select the appropriate options as follows:
3 4
371
Job priority
Select the priority for the job. Available options are as follows:

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 553.
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 286. 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.
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. To retension a tape 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the drive or slot containing the media you want to retension. Under Media Tasks in the task pane, select Retension media.
3 4
372


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 573.
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. To format media in a drive 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the drive or slot containing the media you want to format.
373
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 6
To format the media that is displayed, click Yes. Select the appropriate options as follows:

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.
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.
374
To label media 1 2 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. Select the drive or slot containing the media you want to label. 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 6 7 8 Click OK. Type the name you want to use as the recorded media label for this media. Click OK to erase all data on the media and re-label the media. Select the appropriate options as follows:

3 4
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.
375
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 195
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 2 3 4 On the navigation bar, click Devices. Expand the server icon, click Stand-alone Drives, and then select the drive. Under Media Tasks in the task pane, select Eject media. Select the appropriate options as follows:

6
376
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 2 On the navigation bar, click Devices. Click Robotic Libraries, and then click the drive or robotic library for which you are setting up the cleaning. Click Slots to display the librarys slots in the results pane. Select the slot that contains the cleaning tape. Under General Tasks in the task bar, select Properties. 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 2 On the navigation bar, click Devices. Click Robotic Libraries, and then click the drive or robotic library containing the drive, and then select the drive. Under Drive Tasks in the task pane, select Clean. Select the appropriate options as follows:
3 4 5 6
3 4
377
Job priority
Select the priority for the job. Available options are as follows:

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 286. 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. See Viewing storage device properties on page 343.
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.
378
To import media to a robotic library 1 2 3 4 5 6 On the navigation bar, click Devices. Select the robotic library. Click Slots. On the Results pane, select the slots you want to import media to. Under Media Tasks in the task pane, select Import media. Complete the appropriate options as follows:

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. 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 553.

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 286. Related Topics: About robotic libraries in Backup Exec on page 355
379
Exporting media from a robotic library

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 2 3 4 5 6 On the navigation bar, click Devices. Select the robotic library. Click Slots. On the Results pane, select the slots you want to export media from. Under Media Tasks in the task pane, select Export media. Complete the appropriate options as follows:

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. If you want Backup Exec to notify someone when the job completes, on the Properties pane, under Settings, click Notification.
380
See Assigning notification recipients for completed jobs on page 573. 9 Do one of the following:

Schedule.
See Scheduling jobs on page 286.
Locking the robotic librarys front panel

You must create a job to lock the robotic librarys front panel. You can monitor this job on the Job Monitor. To lock the robotic librarys front panel 1 2 3 4 On the navigation bar, click Devices. Select the robotic library. Under Robotic Library Tasks in the task pane, select Lock. Complete the appropriate options as follows:

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 573.
381

Schedule.
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 2 3 4 On the navigation bar, click Devices. Select the robotic library. Under Robotic Library Tasks in the task pane, select Initialize. Complete the appropriate options as follows:

Click Run Now.
382
Unlocking the robotic librarys front panel

You must create a job to unlock the robotic librarys front panel. You can monitor this job on the Job Monitor. To unlock the robotic librarys front panel 1 2 3 4 On the navigation bar, click Devices. Select the robotic library. Under Robotic Library Tasks in the task pane, click Unlock. Complete the appropriate options as follows:


Schedule.
Exporting expired media from a robotic library

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 2 3 4 5 On the navigation bar, click Devices. Select the robotic library. Under Robotic Library Tasks in the task pane, click Export expired media. On the Export Job Properties pane, under Settings, click General. Complete the appropriate options as follows:

To set options for the export expired media job, on the Properties pane, under Settings, click Options. Complete the appropriate options as follows:
Include cleaning media in export Select this check box to include cleaning media in the export of expired media.
Export cleaning media Select the number of times that the cleaning media can be used used more than x times before it is exported by this job.
384
After export, automatically prompt for new media to be imported
Select this check box to be prompted to import new media to the slot after the export expired media operation has completed.
Upon successful export, Select a vault to logically move the media to after the export job move the media to media successfully completes. vault See Creating media vaults on page 200.

Schedule.
385
386
Chapter
10
Managing backup-to-disk folders

Backup-to-disk folders are destination devices for backups that you direct to a hard disk. You can use the Device Configuration Wizard to create backup-to-disk folders, to install Symantec tape device drivers, and to correct the display of robotic library drives. You can also use the Backup-to-disk Wizard to create new backup-to-disk folders or to modify existing backup-to-disk folders. Related Topics: About backup-to-disk folders and files on page 387 Configuring storage devices by using the Device Configuration Wizard on page 340 Creating a backup-to-disk folder by using the Backup-to-disk Wizard on page 391
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 jobs 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
387
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. 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 Granular Recovery Technology (GRT) is selected. A backup-to-disk folder is selected as the backup device.
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 391 Requirements for creating a backup-to-disk folder on page 389 Requirements for creating a removable backup-to-disk folder on page 390 Creating a backup-to-disk folder on page 391 Sharing an existing backup-to-disk folder on page 398 Duplicating backed up data on page 298 Renaming a backup-to-disk folder on page 399 Setting defaults for new backup-to-disk folders on page 396 About using a backup-to-disk folder for GRT-enabled backup operations on page 406
388
Requirements for creating a backup-to-disk folder

You can create a backup-to-disk folder in any of the following locations 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 Granular Recovery Technology (GRT) option is selected. This option is available for Microsoft Exchange databases and storage groups, Microsoft Active Directory, and Microsoft SharePoint content database and Team database. See Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407.
DFS shares FAT/FAT32 partitions (local or remote) Veritas Volume Manager partitions RAID drives with any configuration NFS volumes Network Attached Storage (NAS) devices 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 391 Creating a backup-to-disk folder on page 391 Configuring advanced options for a backup-to-disk folder on page 395
Chapter 10, Managing backup-to-disk folders
389
Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407 Setting defaults for new backup-to-disk folders on page 396
Requirements for creating a removable backup-to-disk folder

A removable backup-to-disk folder works as follows:

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 the following:

CDR-RW DVD-RW ZIP REV Removable hard disk
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 391 Creating a backup-to-disk folder on page 391 Configuring advanced options for a backup-to-disk folder on page 395 Setting defaults for new backup-to-disk folders on page 396
390
Creating a backup-to-disk folder by using the Backup-to-disk Wizard
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 2 3 On the navigation bar, click Devices. In the task pane, under Device Wizards, click Backup-to-disk wizard. Follow the on-screen prompts.
Related Topics: About backup-to-disk folders and files on page 387 Requirements for creating a backup-to-disk folder on page 389 Requirements for creating a removable backup-to-disk folder on page 390 Creating a backup-to-disk folder on page 391 Configuring advanced options for a backup-to-disk folder on page 395 Setting defaults for new backup-to-disk folders on page 396
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. See Requirements for creating a backup-to-disk folder on page 389. See Requirements for creating a removable backup-to-disk folder on page 390. To create a backup-to-disk folder 1 2 On the navigation bar, click Devices. Under Backup-to-Disk Tasks in the task pane, click New folder or New removable folder.
391
Enter or change information as follows:

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. If you do not know the exact path, click the button next to the Path field to browse to the correct path. Pause Enable Check Pause to pause the device, and then click OK. 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. 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. 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 4 GB. Note Backup-to-disk folders that were created with earlier versions of Backup Exec continue to use the default file size of 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 option works with the option Maximum number of backup sets per backup-to-disk file.
Online
Maximum size for backup-to-disk files
392
Allocate the maximum size for backup-to-disk files
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 may want to increase the append period. 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 can 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. Note When you select this option, Backup Exec hides the option Maximum number of backup sets per backup-to-disk file. As a result, all of the space that is allocated to the backup-to-disk file is used.
Maximum number of backup sets per backup-to-disk file
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.
Allow x concurrent jobs This option is not available for a removable backup-to-disk folder. for this backup-to-disk Type the number of concurrent operations that you want to allow to folder this folder. This number can range from 1 to 16.
393
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. 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. Overwrite and append periods for media take precedence over device priority.
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 387 Configuring advanced options for a backup-to-disk folder on page 395 Setting defaults for new backup-to-disk folders on page 396 Changing the path of a backup-to-disk folder on page 399
394
Configuring advanced options for a backup-to-disk folder
Configuring advanced options for a backup-to-disk folder

You can set a low disk space threshold for a backup-to-disk folder so that jobs cannot be submitted or processed 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. This threshold 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. You can also configure Backup Exec to automatically detect preferred settings for a device. To configure advanced options for a backup-to-disk folder 1 2 3 4 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Select the folder that you want to view. Under General Tasks in the task pane, click Properties, and then click the Advanced tab. Enter or change information as appropriate:
Low disk space threshold Check Low disk space threshold to prevent Backup Exec from writing a job to the backup-to-disk folder when the volume reaches the threshold you specify. The low disk space threshold is the amount of free space on the drive at which Backup Exec suspends backup operations to the backup-to-disk folder. When the volumes capacity reaches this threshold, Backup Exec places current jobs on hold until disk space is available. 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.
395
Setting defaults for new backup-to-disk folders
Buffered reads
Check Buffered reads in the following situations:
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 in the following situations:
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.
Related Topics: About backup-to-disk folders and files on page 387 Setting defaults for new backup-to-disk folders on page 396

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 2 3 On the Tools menu, click Options. On the Properties pane, under Settings, click Backup-to-Disk. Set the following defaults as appropriate:
Maximum number of backup sets per backup-to-disk file 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.
396
Maximum size for backup-to-disk files
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 4 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 option works with the option Maximum number of backup sets per backup-to-disk file.
Allocate the maximum size when creating the backup-to-disk file
This default does not apply to removable backup-to-disk folders. Check Allocate the maximum size when creating the backup-to-disk file to create the backup-to-disk file at the maximum size to reduce disk fragmentation. You may want to increase the append period. 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 can 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. Note When you select this option, Backup Exec hides the option Maximum number of backup sets per backup-to-disk file. As a result, all of the space that is allocated to the backup-to-disk file is used.
Allow x concurrent jobs This default does not apply to removable backup-to-disk folders. for this backup-to-disk Type the number of concurrent operations that you want to allow to folder this folder. This number can range from 1 to 16. Low disk space threshold Check Low disk space threshold to prevent Backup Exec from writing a job to the backup-to-disk folder when the volume reaches the threshold you specify. The low disk space threshold is the amount of free space on the drive at which Backup Exec suspends backup operations to the backup-to-disk folder. When the volumes capacity reaches this threshold, Backup Exec places current jobs on hold until disk space is available. 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.
397
Sharing an existing backup-to-disk folder
Click OK.
Related Topics: About backup-to-disk folders and files on page 387 Requirements for creating a backup-to-disk folder on page 389 Configuring advanced options for a backup-to-disk folder on page 395
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 dont 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. In the task pane, under Backup-to-Disk Tasks, click Add Shared Folder. Type or browse to the path of the shared backup-to-disk folder that you want to add to this computer. Click OK. The shared backup-to-disk folder is displayed in the Devices view under the Backup-to-Disk Folders node.
2 3
398
Renaming a backup-to-disk folder
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: See Changing the path of a backup-to-disk folder on page 399. 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 2 3 4 5 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Select the backup-to-disk folder you want to rename. Under General Tasks in the task pane, select Rename. On the Rename Backup-to-Disk Folder dialog box, type the new backup-to-disk folder name, and then click OK. 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. In Windows Explorer, copy and paste the backup-to-disk files from the original backup-to-disk folder to the new folder. On the Backup Exec navigation bar, click Devices.
399
Deleting a backup-to-disk folder
Right-click the new backup-to-disk folder, and then click Scan on the shortcut menu, or select the new folder and press <F5>. Click the new backup-to-disk folder and verify that the backup-to-disk files appear in the results pane. 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 389 Renaming a backup-to-disk folder on page 399 Deleting a backup-to-disk file on page 403
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 2 3 4 5 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Select the backup-to-disk folder that you want to remove. Under General Tasks in the task pane, select Delete. 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.
400
Recreating a backup-to-disk folder and its contents
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. 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 2 3 4 5 6 Add a new folder to Backup Exec using the same name and path as the deleted folder. When you are prompted, click Yes to recreate the folder at the specified path. On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Select the new folder. 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 389 Inventorying media on page 368
401
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. To pause or resume a backup-to-disk folder 1 2 3 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. 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.
Changing the status of a backup-to-disk folder to online

If a backup job fails and the backup-to-disk folder goes offline, you can change the status to online after you correct the problem. To change the status of a backup-to-disk folder to online 1 2 3 4 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Select the backup-to-disk folder that is offline. Under Device Tasks in the task pane, select Online.
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.
402
Deleting a backup-to-disk file
To rename a backup-to-disk file 1 2 3 4 5 6 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Select the folder that contains the file you want to rename. On the results pane, select the file you want to rename. Under General Tasks in the task pane, select Rename. Type a new name for the file, and then click OK.
Deleting a backup-to-disk file

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 2 3 On the navigation bar, click Media. Click the media set that contains the backup-to-disk file. Use the Windows drag-and-drop feature to move the backup-to-disk file into the Retired Media set. On the results pane, select the backup-to-disk file you want to delete. Under General Tasks in the task pane, select Delete. 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.
4 5 6
403
Recreating a deleted backup-to-disk file
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. Right-click the backup-to-disk file. Click Delete, and then click Yes.
8 9
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 2 3 4 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Select the folder where the backup-to-disk file was located before you deleted it. 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 368
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. See Deleting a backup-to-disk file on page 403.
404
Erasing backup-to-disk files
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 2 3 On the navigation bar, click Devices. Expand the icon for the computer where the backup-to-disk folder is located. Under Backup-to-Disk Folders, click the backup-to-disk folder that contains the file you want to erase. On the Results pane, select the file you want to erase. Under Media Tasks in the task pane, select Erase media, quick. Click OK to continue. Click Yes, or if more than one file was selected, click Yes to All. Select the appropriate options as follows:
Job name Job priority Type a name for the job or accept the default name. Select the priority for the job. The following options are available:

4 5 6 7 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 553.
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.
Chapter 10, Managing backup-to-disk folders 405
About using a backup-to-disk folder for GRT-enabled backup operations

Backup Exec uses Granular Recovery Technology (GRT) to enable the restore of certain individual items, such as mail messages and folders. You can restore one or more items without having to restore the entire database. GRT is enabled by default for Active Directory, Active Directory Lightweight Directory Services (AD LDS), Exchange, and SharePoint data. Backup-to-disk folders provide the most efficient method of storage for GRT-enabled backups. You must create a temporary hard disk staging location on a local NTFS volume to restore individual items from GRT-enabled backups on tape. The data is first copied from tape to the temporary staging location before it can be restored. As such, a restore from tape takes more time. For best results, you should specifically select the backup-to-disk folder you want to use for your GRT-enabled backup jobs when you set them up. When you enable GRT for a backup job, Backup Exec creates media with an IMG prefix (IMG00001). IMG media is a specific media type that Backup Exec creates only for GRT-enabled backup operations. When you run a GRT-enabled backup job the IMG media stores the backup data. Related Topics: Requirements for using backup-to-disk folders with GRT-enabled backup operations on page 407 Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407 About reclaiming disk space for GRT-enabled backup operations on page 409 About restoring individual Active Directory and ADAM/AD LDS objects on page 879 About using GRT-enabled backups to restore individual items from the Information Store on page 1190 Backing up SharePoint resources on page 1267 Requirements for creating a backup-to-disk folder on page 389
406
Requirements for using backup-to-disk folders with GRT-enabled backup operations

Following are requirements for using a backup-to-disk folder for GRT-enabled backup jobs:

The backup-to-disk folder must reside on an NTFS volume. The backup-to-disk folder cannot contain junction points. If the backup-to-disk folder is in a device pool that contains other types of devices, the priority of the backup-to-disk folder should be 1. See Creating a backup-to-disk folder on page 391. If the backup-to-disk folder is on a network share, you must specify a path to an NTFS volume on the local media server. Backup Exec must store data at this location temporarily during the backup. See Setting default backup options on page 307.
Related Topics: Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407 About reclaiming disk space for GRT-enabled backup operations on page 409
Recommendations for using backup-to-disk folders with GRT-enabled backup operations

The following recommendations help ensure that you do not run out of space for your Granular Recovery Technology (GRT)-enabled backups:
Table 10-1 Recommendations for using backup-to-disk folders with GRT operations Description You must manage GRT media differently than other backup-to-disk media because of the difference in GRT media types. For best results, you should specifically select the backup-to-disk folder you want to use for your GRT-enabled backup jobs when you set them up. If you do not change the default device setting of All Devices you could accidentally send your GRT job to a tape.
Recommendation Create a separate backup-to-disk folder specifically for all GRT-enabled backup jobs
407
About using a backup-to-disk folder for GRT-enabled backup operations Table 10-1 Recommendations for using backup-to-disk folders with GRT operations Description If you allocate the maximum size for a backup-to-disk file, Backup Exec creates a file that is as large as the amount that you specified. Since GRT information is stored in IMG media, the backup-to-disk file does not hold backup data. The extra space that the file occupies can often lead to failed jobs because of low disk space. The low disk space threshold is the amount of free space on the drive at which Backup Exec suspends backup operations to the backup-to-disk folder. If you assign a low disk space threshold to the backup-to-disk folder it can help prevent you from unexpectedly using all your available disk space. You should be careful with low disk space thresholds. The amount you specify as a low disk space threshold is unavailable to Backup Exec for backup-to-disk backups. If you are not aware of a low disk space threshold setting, backup jobs can fail due to perceived low disk space. You should consider the low disk space threshold when you calculate the total amount of space available to a backup-to-disk device. Remember to also consider any other data that exists on the volume. As the amount of other data that is contained on the volume increases, the amount of space available to the backup-to-disk device decreases. See Configuring advanced options for a backup-to-disk folder on page 395. Do not fill up a drive that hosts a backup-to-disk device that is used for GRT operations When you calculate the total amount of available space on a volume, remember to consider the size of any other data that resides on it. This amount can include other backup-to-disk data or data from other applications. If the drive fills up or if the low disk space threshold is met, the backup-to-disk device displays a low disk space condition.
Recommendation Do not allocate the maximum size for backup-to-disk files
Calculate your disk space requirements carefully before you assign a low disk space threshold
Related Topics: Creating a backup-to-disk folder on page 391 Configuring advanced options for a backup-to-disk folder on page 395 About using a backup-to-disk folder for GRT-enabled backup operations on page 406 About reclaiming disk space for GRT-enabled backup operations on page 409
Requirements for creating a backup-to-disk folder on page 389
About reclaiming disk space for GRT-enabled backup operations

When a Granular Recovery Technology (GRT)-enabled job creates a backup set, by default Backup Exec erases an IMG media that has an expired protection period. Backup Exec automatically erases the expired media to reclaim disk space for the new media that the backup job creates. Backup Exec erases one IMG media for each backup set in a GRT-enabled job. For example, if a GRT-enabled backup job creates three backup sets, Backup Exec erases three IMG media that have expired overwrite protection. If you want to erase more than one IMG media per backup set, see the following Symantec knowledge base article: http://entsupport.symantec.com/umi/V-269-8 If Backup Exec runs out of disk space during a GRT-enabled backup, it tries to delete expired media and continue the job. If no expired media is available, the job fails and the backup-to-disk device is paused. To restart the job, you must reclaim disk space and unpause the device. The Job Monitor displays information about the GRT-enabled backup jobs that cannot run due to low disk space. The Job Monitor displays Scheduled as the job state and Ready; No idle devices are available as the job status. You can tell if a GRT-enabled backup job is unable to run due to low disk space by looking at the Job Monitor. the job state displays as Scheduled and the job status displays as Ready; No idle devices are available. To correct this status you must reclaim disk space and unpause the device before the job can run. You can reclaim disk space by using any of the following methods.
Table 10-2 Method How to reclaim disk space for GRT backup operations Description
Erase IMG media or backup-to-disk files to Delete any IMG media or backup-to-disk files you no provide adequate disk space longer need. See Erasing backup-to-disk files on page 404. Use Windows Explorer to remove data that is not related to Backup Exec The volume may contain some data that is not related to Backup Exec. You can use Windows Explorer to delete this data. You should never delete Backup Exec data using Windows Explorer.
409
About using a backup-to-disk folder for GRT-enabled backup operations Table 10-2 Method How to reclaim disk space for GRT backup operations Description
Wait for IMG media or backup-to-disk Media set rules include the append and overwrite files to expire according to media set rules protection periods you set for media. You can wait until these rules expire to allow Backup Exec to naturally reclaim disk space. See About media in Backup Exec on page 169. Remove the low disk space threshold setting for the backup-to-disk device for the current operation and take appropriate actions after the job has completed If you set a low disk space threshold for the backup-to-disk device, it may prohibit the job from completing due to low disk space. You can temporarily remove the low disk space threshold to allow Backup Exec access to that reserved space. When the job is complete, you can reinstate the low disk space threshold with a smaller reserve setting. See Configuring advanced options for a backup-to-disk folder on page 395.
After you reclaim disk space, you must pause and unpause the backup-to-disk device to resume the job. See Pausing and resuming a backup-to-disk folder on page 402. Related Topics: About media in Backup Exec on page 169 Configuring advanced options for a backup-to-disk folder on page 395 Erasing backup-to-disk files on page 404 Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407 About using a backup-to-disk folder for GRT-enabled backup operations on page 406
410
Chapter
11
Managing device pools
With Backup Exec, you can maximize your hardware investment by organizing your devices in one or both of the following methods:
Device pools. Devices are grouped so that jobs assigned to the device pool are run on the first available device. See About device pools on page 411. 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. See About cascaded drive pools on page 418.
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.
411
About device pools
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 devices 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. 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 418
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.
412
Adding devices to a device pool
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 2 3 4 On the navigation bar, click Devices. Click Device Pools. Under Device Pool Tasks in the task pane, select New device pool. Select the appropriate options as follows, and then click OK:
Device pool name Description Device type Type the name of the new device pool that you want to create. Type a description of the new device pool. 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. 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 that you want to include in the new device pool.
Device sub-type:
Select the devices to be included in this device pool
Related Topics: About cascaded drive pools on page 418 Creating a cascaded drive pool on page 419

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.
Chapter 11, Managing device pools
413
To add a device to a device pool 1 2 3 4 On the navigation bar, click Devices. Select the device pool. Under Device Pool Tasks in the task pane, select Add device. Select the appropriate options as follows, and then click OK:
Device pool name Description Device type Name of the device pool to which you want to add devices. Description of the device pool. 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. 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 you want to include in the device pool.
Device sub-type:
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.
414
To set device priority in a device pool 1 2 On the navigation bar, click Devices. Under Device Pools, select the device pool containing the device for which you want to set a priority. Select the device. Under General Tasks in the task pane, select Properties. Click General. 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.
3 4 5 6
Related Topics: Viewing a devices configuration properties on page 346
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 2 3 On the navigation bar, click Devices. Under Device Pools, select the device pool from which you want to delete a device. 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 5 Under Device Pool Tasks in the task pane, select Remove device. When prompted to remove the displayed device from the device pool, click Yes.
415
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. To delete a device pool 1 2 3 4 On the navigation bar, click Devices. Under Device Pools, select the device pool or pools that you want to delete. Under General Tasks on the task pane, select Delete. When prompted, click Yes or Yes to All to delete the device pool or pools that are displayed. 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 415 Retargeting a scheduled job from a deleted device pool or media set on page 416
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.
416
In the Destination field, click the <Down arrow> 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. Click Yes or Yes to All to retarget the job or jobs that are displayed to the new destination. 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.
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 pools Properties dialog box. To rename a device pool 1 2 3 4 On the navigation bar, click Devices. Under Device Pools, select the device pool you want to rename. Under General Tasks, select Rename. On the Rename Device Pool 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 417
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 2 3 On the navigation bar, click Devices. Under Device Pools in the tree view, select the device pool. Under General Tasks in the task pane, select Properties.
417
About cascaded drive pools
The Device Pool Properties dialog box provides the following information:
Name Description Creation date Name of the device pool. Rename the device pool by typing a new name in this field. Description of the device pool. You can enter a description or modify the description. Date and time that this device pool was created.

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 411
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 drives property page. See Viewing storage device properties on page 343. 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. To create a cascaded drive pool 1 2 3 4 On the navigation bar, click Devices. Select Cascaded Drive Pools. Under Device Pool Tasks in the task pane, select New device pool. Select the appropriate options as follows, and then click OK:
Device pool name Description Device type Type the name of the new cascaded device pool that you want to create. Description of the cascaded drive pool. 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. 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 devices that you want to include in the new cascaded drive pool. Any devices that you move to a cascaded drive pool are removed from any device pools they are currently in.
Device sub-type:
Select the devices to be included in this device pool.
Related Topics: Deleting drives from a cascaded drive pool on page 420 Deleting a cascaded drive pool on page 421
419
Adding drives to a cascaded drive pool

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. To add a drive to a cascaded drive pool 1 2 3 4 On the navigation bar, click Devices. Select the cascaded drive pool to which you want to add a drive. Under Device Pool Tasks in the task pane, select Add device. Select the appropriate options as follows, and then click OK:
Device pool name Description Device type Device sub-type: Name of the cascaded drive pool to which you want to add drives. Description of the cascaded drive pool. Only stand-alone drives are displayed for selection for a cascaded drive pool. 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 drives you want to include in the drive pool.
Deleting drives from a cascaded drive 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.
420
To delete a drive from a cascaded drive pool 1 2 3 4 5 On the navigation bar, click Devices. Select the cascaded drive pool from which you want to delete a drive. Select the drive you want to delete from the cascaded drive pool. Under Device Pool Tasks in the task pane, select Remove device. When prompted, click Yes to delete the drive that is displayed.
Related Topics: Deleting a cascaded drive pool on page 421 Erasing media on page 370
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 2 3 4 On the navigation bar, click Devices. Under Cascaded Drive Pools, select the drive pool or pools that you want to delete. Under General Tasks, click Delete. When prompted, click Yes or Yes to All to delete the cascaded drive pool or pools that are displayed. 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. 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 416
Chapter 11, Managing device pools 421
Renaming a cascaded drive pool

You can rename a cascaded drive pool using either the Rename option or by typing a new name on the cascaded drive pools Properties dialog box. To rename a cascaded drive pool 1 2 3 4 On the navigation bar, click Devices. Under Cascaded Drive Pools, select the drive pool you want to rename. Under General Tasks in the task pane, select Rename. On the Rename Device Pool 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 2 On the navigation bar, click Devices. Under Cascaded Drive Pools, select the cascaded drive pool for which you want to view properties. Under General Tasks in the task pane, select Properties. The Device Pool Properties dialog box provides the following information:
Name Description Creation date Name of the cascaded drive pool. Rename the drive pool by typing a new name in this field. Description of the cascaded drive pool. You can enter a description or modify the current description. Date and time that this cascaded drive pool was created.
422
Chapter
12
Policies and templates
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 the following:
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. 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. 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. 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.
423
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 645 Backup Set Details by Resource Report on page 623 Policy Protected Resources on page 647 About the synthetic backup feature on page 832 About true image restore on page 846 Resource Backup Policy Performance Report on page 649

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. See About the synthetic backup feature on page 832. See About true image restore on page 846. To create a new policy manually 1 2
424
On the navigation bar, click Job Setup. In the task pane, under Policy Tasks, click New policy.
In the New Policy dialog box, enter the following information:

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. Type a description of this policy.
Policy description

To create a new 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.
To import an existing template:
Click OK to start editing the template that you selected.
To create a policy using the Policy Wizard 1 2 3 On the navigation bar, click Job Setup. In the task pane, under Policy Tasks, click New policy using wizard. Follow the instructions in the wizard to create a policy.
Related Topics: Adding a backup template to a policy on page 430. Adding an export media template to a policy on page 433. Adding a duplicate backup template to a policy on page 444. Importing a template into a policy on page 434 About the synthetic backup feature on page 832 About true image restore on page 846
Chapter 12, Policies and templates
425
Editing a policy
You can change the settings for a policy at any time. To edit a policy

To edit a policy that is not associated with a job: To edit a policy that is associated with a scheduled job:

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.
Related Topics: Editing a template in a policy on page 435
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 2 On the navigation bar, click Job Setup. Select the policy that you want to delete.
426

If selection lists are associated with the policy: Do the following in the order listed:
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.
If no selection lists are associated with the policy:
Under General Tasks on the task pane, click Delete.
Click Yes to confirm that you want to delete this policy.
Using an example 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 2 On the navigation bar, click Job Setup. In the Policies pane, right-click the example policy you want to use, and then click Copy. The Synthetic Backup example policy displays only if you have purchased and installed the Advanced Disk-based Backup Option. See Creating a synthetic backup by copying the example policy on page 839. 3 Do one of the following:
To copy the example policy to this media server: Click Copy to this media server.
427
To copy the example policy to other media servers:

Click Copy to other media servers. Select the media server you want to copy to. If the media server doesnt appear on the list, click Add, and then enter the media server name.
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 448. Backup Exec creates a new policy named "Copy of <example policy>" and places it in the list of policies on the Job Setup view of the media servers that you copied it to.
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. See Adding a backup template to a policy on page 430.
6 7
When finished, click OK. Create jobs using this policy and a selection list. See Creating jobs using policies on page 440.
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.
428
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 the following types of templates:
Backup. Use this template to create backup jobs, such as full, incremental, and differential. See Adding a backup template to a policy on page 430. 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. See About duplicate backup set templates on page 443. 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. See Adding an export media template to a policy on page 433. Synthetic backup. This template is available only with the Backup Exec Advanced Disk-based Backup Option. See About the synthetic backup feature on page 832.
For information about creating a policy for true image restore: See Creating a policy for true image restore on page 850. 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 383 Importing a template into a policy on page 434
429
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. See Creating a new policy on page 424. 2 3 4 On the New Policy dialog box, click New Template. On the Template Selection dialog box, select Backup Template, and then click OK. On the Properties pane, under Destination, click Device and Media. Complete the Device and Media options. See Device and media options for backup jobs and templates on page 272. 5 On the Properties pane, under Settings, click General. Complete the General options for this template. See General options for backup jobs and templates on page 275. 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 840. See Creating a policy for true image restore on page 850. 6 On the Properties pane, under Settings, click Advanced. Complete the Advanced options for this template. See Advanced options for backup jobs on page 280. 7 On the Properties pane, under Settings, click Pre/Post Commands. Complete the Pre/Post Command options. See Pre/post commands for backup or restore jobs on page 283. 8 On the Properties pane, under Settings, click Network and Security.
430
See Encryption keys on page 332. 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. See Enabling managed media servers to use any available network interface card on page 779. 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. See Setting defaults for the Advanced Open File Option for backup jobs on page 816.
If you want to use offhost backup, select Advanced Disk-based Backup and complete the options. See About offhost backup on page 855. 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. See Assigning notification recipients for completed jobs on page 573. If you want to prevent certain files or file types from being included in the backup, select Exclusions. See Including or excluding files for backup on page 241.
10 Set the schedule for the template. See Setting the schedule for a template on page 432. 11 Click OK. The template is complete. You can add another template or combine the policy with a selection list. See Creating jobs using policies on page 440.
431
Setting the schedule for a template

Types of schedules for a template include the following:
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. To set the schedule for a template 1 2 On the Properties pane, under Frequency, select Schedule. Select one of the following options:
Run now and run Select this option to run the job immediately after a selection list according to rules for this is combined with the policy in which this template is contained. If template the template is part of a template rule, the job will also run according to the template rule. 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. Run according to Select this option to configure a schedule for a recurring job, and schedule and run then click Edit Schedule Details to set the schedule. according to rules for this See Scheduling jobs on page 286. template If the template is part of a template rule, the job will also run according to the template rule.
432
Run only according to rules for this template
Select this option to set the job to run based on a template rule. For example, with the After <Template A> completes, start <Template B> template rule, <Template B> will run whenever <Template A> completes. 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 jobs hold status.
Submit job on hold
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. 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 <Template A> completes, start <Template B> to export media template rule to the policy. Backup Exec replaces <Template A> 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 <Template B> with the export media template. To add an export media template to a policy 1 Set up a new policy. See Creating a new policy on page 424. 2 Set up a backup template, which will be the media-producing template that is the source for the export job. On the New Policy dialog box, click New Template.
433
On the Template Selection dialog box, select Export Media Template, and then click OK. The Export Media template displays only if the policy contains a backup template.
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.
On the Properties pane, under Settings, click General. Type a name for this export media template. 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. See Scanning bar code labels to move media on page 203.
If you want to set up notification for this job, on the Properties pane, under Settings, click Notification. See Assigning notification recipients for completed jobs on page 573. The export media job must run according to the template rule, so you do not need to set any schedule options for this job.
Click OK. Backup Exec adds the template rule called After <Template A> completes, start <Template B> to export media. The template is complete. You can add another template or combine the policy with a selection list. See Creating jobs using policies on page 440.
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.
434
To import a template into a policy 1 2 On the navigation bar, click Job Setup. 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 4 5 Click Import Template. Select the templates you want to import. Click OK. Backup Exec copies the templates into the policy and provides the default name of <template name> <number>, where <number> 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.
Editing a template in a policy

You can edit a template at any time. To edit a template in a policy 1 2 On the navigation bar, click Job Setup. In the Policies section, double-click the policy that contains the template you want to edit. Select the template from the list that displays in the Job Templates area. Click Edit Template. Change the template properties as needed.
3 4 5
435
Setting template rules
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 2 3 4 5 On the navigation bar, click Job Setup. In the Policies section, double-click the policy. Select the template from the list that displays in the Job templates area. Click Delete Template. 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 426

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.
436
The following template rules are available:

Table 12-1 Rule If start times conflict, <Template A> supersedes <Template B>. Template Rules Description If two templates in the same policy have the same start time, <Template A> will run first, and <Template B> will run according to the schedule set for it, after the <Template A> 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 <Template A> and the daily backup as <Template B>, 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, <Template A> will start first. After <Template A> completes, <Template B> will start automatically. With this rule, you can run two jobs simultaneously.
If start times conflict, <Template A> will start and upon completion, starts <Template B>. After <Template A> starts, also start <Template B>. After <Template A> completes, start <Template B>. If <Template A> successfully completes, start <Template B>. If <Template A> fails, start <Template B>. <Template A> must complete at least once before any other templates will be allowed to start. Run <Template A> only once.
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 <Template A> 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.
437
Setting template rules Table 12-1 Rule Duplicate all backup sets that were created by <Template A> using <Template B> as scheduled. Template Rules Description 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. 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 <Template A> with the template that you selected as the source for the duplicate backup template, and replaces <Template B> 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 <Template A> using <Template B> 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 <Template A> with the template that you selected as the source for the export media template, and replaces <Template B> with the export media template you created.
After <Template A> completes, start <Template B> to duplicate the backup set.
After <Template A> completes, start <Template B> to export media.
To set a template rule 1 2 On the navigation bar, click Job Setup. 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 4 On the Policy Properties screen, click New Rule. Complete the fields that display as follows:
Template rule Select the template rule that you want to apply.
438
Template A
Select the template that you want to insert into the <Template A> slot in the template rule you selected. Template A is usually the trigger for template B. For example, in the template rule After <Template A> completes, start <Template B>, template A must complete before Backup Exec will start template B. Select the template that you want to insert into the <Template B> 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.
Template B
Click OK.
Changing template rules

You can change the rules for a template at any time. To change a template rule 1 2 3 4 5 On the navigation bar, click Job Setup. In the Policies section, double-click the policy. On the Policy Properties screen, select the rule you want to change and click Edit Rule. Change the template rule as needed. 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 2 On the navigation bar, click Job Setup. In the Policies section, double-click the policy.
439
Creating jobs using policies
On the Policy Properties screen, select the rule you want to delete and then click Delete Rule. The rule is removed from the policy.

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 2 3 4 On the navigation bar, click Job Setup. Select the policy for which you want to create jobs. Under Policy Tasks in the task pane, click New jobs using policy. 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 2 On the navigation bar, click Job Setup. Select the selection list for which you want to create jobs.
440
3 4
Under Selection List Tasks, click New jobs using policy. 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

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 2 On the navigation bar, click Job Setup. Under Policies, right-click the policy for which you want to view selection lists designated for backup. 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 2 On the navigation bar, click Job Setup. Under Backup Selection Lists, right-click the selection list for which you want to view policies. 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 jobs next occurrence. To edit the next occurrence of a scheduled policy-based job 1 2 3 On the navigation bar, click Job Monitor. Click the Job List tab. Right-click the job you want to edit, and then click Edit Next Run.
441
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 2 3 On the navigation bar, click Job Setup. Select the policy or the selection list from which the job was created. 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 5
Check the check box next to the selection list name, and then click OK. 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 2 3 4 On the navigation bar, click Job Setup. Under Jobs, right-click the policy-created job that you want to rename. Click Rename. Type the new name in the Name field, and then click OK.
442
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. You can use the following 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 <Template A> completes, start <Template B> to duplicate the backup set template rule, where <Template A> is the backup template and <Template B> 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 do the following:

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.
443
Backup Exec automatically adds the After <Template A> completes, start <Template B> to duplicate the backup set template rule to the policy.
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 <Template A> using <Template B> as scheduled template rule. To set up duplicate backups using this method, you must set up a policy and then do the following:

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 <Template A> using <Template B> as scheduled template rule.
Adding a duplicate backup template to a policy

To use a multi-stage backup strategy, you must use a duplicate backup template. To add a duplicate backup template 1 Set up a new policy. See Creating a new policy on page 424. 2 3 4 Set up a backup template. On the New Policy dialog box, click New Template. On the Template Selection dialog box, select Duplicate Backup Sets Template, and then click OK. Select the source template, which is the template that will provide the backup data to be copied. In the Properties pane, under Destination, select Device and Media. See Device and media options for backup jobs and templates on page 272. 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.
444
7 8
In the Properties pane, under Settings, select General. Complete the appropriate options as follows:
Template name Backup set description Preferred source device Type the name for this template. Type a description of the information you are backing up. Select the device that was used as the destination device for the original backup job.
In the Properties pane, under Settings, select Advanced.
10 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.
11 On the Properties pane, under Settings, click Network and Security. See Encryption keys on page 332.
Chapter 12, Policies and templates 445
12 If you want to set up notification for this job, on the Properties pane, under Settings, click Notification. See Assigning notification recipients for completed jobs on page 573. 13 Set the schedule for the backup job. See Setting the schedule for a template on page 432. You must set a schedule for the template if you want to use the Use scheduled <Template B> to duplicate all backup sets that were created by <Template A> template rule. 14 Click OK. You can add another template to the policy or combine the policy with a selection list to create jobs.
446
Chapter
13
Administrating Backup Exec

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 See Copying jobs, selection lists, and policies on page 448. Monitor jobs See Monitoring jobs on page 450. Filter jobs See Filtering jobs on page 475. View the Backup Exec System Summary See Viewing the System Summary on page 485. Monitor the Symantec Endpoint Protection Security Summary See Viewing the Symantec Endpoint Protection Security Summary on page 485. Configure error-handling rules See Error-handling rules on page 486. Configure thresholds to recover jobs See Setting thresholds to recover jobs on page 491.
447
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. To copy jobs, selection lists, or polices to other media servers, the Copy Server Configurations feature must be installed. See About Backup Execs standard features on page 68. To copy jobs, selection lists, or policies 1 2 3 4 On the media servers navigation bar, click Job Setup. Select the job, backup selection list, or policy you want to copy. In the task list, under General Tasks, click Copy. Select the appropriate options as follows:
Copy to this media server Copy to other media servers Destination media servers 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 doesnt appear on the list, click Add, and then enter the media server name.
Overwrite jobs with Select this option if you want to overwrite an existing job, selection identical names that list, or policy having the same name. already exist on the destination media server Overwrite logon Select this option if you want to overwrite logon accounts for an accounts used by this job existing job having the same name. This option only appears if you that already exist on the are copying a job to another media server. destination server Add Edit Click this button if you want to add a media server to the Destination media servers list. 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.
448
Remove Import List
Select a media server, and then click this button if you want to remove a media server from the Destination media servers 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.
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 2 3 4 5 6 On the navigation bar, click Alerts. Click Active Alerts or Alert History. Click the Source column heading. Locate an alert with Job as a Source and Copy to Media Server job as a Job Name. Right-click the alert, and then select View Job Log. If a Copy to Media Server alert does not exist, do one of the following:
To enable the alert from the task pane
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. In the Properties pane, under Settings, click Preferences. Check Automatically display new alerts.
To enable the alert from the Tools menu
Chapter 13, Administrating Backup Exec
449
Monitoring jobs
Monitoring jobs
Backup Execs Job Monitor enables you to monitor and perform tasks on the active, scheduled, or completed jobs that have been submitted for processing. The Job Monitor provides the following tabs:
Table 13-1 Tab Job List Job Monitor details Description Displays the active jobs and scheduled jobs in the Current Jobs pane. The Job History pane displays the jobs that are successful, completed with exceptions, failed, and canceled. See Viewing and changing active jobs on page 451. See Viewing and changing scheduled jobs on page 457. See Viewing and changing completed jobs on page 465. Calendar Displays the scheduled, active, and completed jobs in a daily, weekly, or monthly view. See Viewing the job workload for a media server from the Calendar tab on page 483 System Summary Displays the details of media server, job, alert, device, and media activity. See Viewing the System Summary on page 485. Security Summary Displays a summary from Symantec Endpoint Protection of the viruses that were found, and potential threats and risks to the media server. Note This tab appears only if the Symantec Endpoint Protection Manager component is installed. See Viewing the Symantec Endpoint Protection Security Summary on page 485.
Related Topics: About managing custom filters on page 475
450
Monitoring jobs
Viewing and changing active jobs

View properties and change the status of active and scheduled jobs that are submitted for processing in the Job List view in the Job Monitor. To view active job properties 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, click the active job that you want to view. In the task pane, under General Tasks , click Properties. 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 jobs current status. The Job History tab provides a summary of the job as it is processed. See Viewing and changing completed jobs on page 465. The Job Activity tab provides the following information:
Job name Job type Job log The job name entered during job configuration. The type of job submitted for processing. 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. The status of the operation. See Active job statuses on page 456. Current Operation Created On The type of operation currently in progress (Backup, Catalog, Restore, Verify, etc.). 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 Device name The media server processing the job. The name of the storage device processing the job. Only data from the first stream displays for multi-stream jobs. Chapter 13, Administrating Backup Exec 451
Status
Monitoring jobs
Source
The media or share being processed. The icon field to the left of the field name displays either of the following:
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.
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 of the following:

A tape device icon when a backup operation is running, or A disk drive icon when a restore operation is running.
Only data from the first stream displays for multi-stream jobs. Current directory Name of the current directory being processed. The icon field to the left of the field displays either of the following:

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.
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 of the following:

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.
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. See Managing jobs in CASO on page 800.
452
Monitoring jobs
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 <x> is replaced with the name of the managed media server:

Preparing to delegate job to <x> Delegating job to <x> Job has been delegated to <x> Job has been received by <x> Job is actively running on <x> Job has completed on <x> Error in delegating job ... re-submitting job to <x>
See Managing jobs in CASO on page 800. Directories Files Skipped files Corrupt files Files in use Job rate Bytes Start time Elapsed time Percent complete Number of directories processed. Number of files processed. Number of files skipped during the operation. Number of corrupt files encountered during the operation. Number of files in use encountered during the operation. Number of megabytes processed per minute. Number of bytes processed. Time the operation started. Length of time that has elapsed since the operation started. 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. 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. 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.
Estimated total bytes
Estimated time remaining
453
Monitoring 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.
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. 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. Click Find to search for a word in the Job Activity log.
Canceling an active job

You can cancel a job that is in progress. To cancel an active job 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, click the active job that you want to cancel. In the task pane, under Active Job Tasks, click Cancel. To select multiple jobs in the Job List view in the Job Monitor, 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 perform tasks such as Cancel on more than one job at a time, as long as the jobs are of similar type. 4 Confirm the cancellation of the job. If the job is scheduled, it runs again at the next scheduled time. It may take several minutes for a job to cancel. While Backup Exec processes the cancellation of a job, the Cancel Pending status appears in the status column.
454
Monitoring jobs
Placing all scheduled occurrences of an active job on hold

If an active job is scheduled to run again, you can place the scheduled jobs on hold. The active job continues to run when you place the scheduled occurrences of the active job on hold. See Scheduled job statuses on page 458. To place all scheduled occurrences of an active job on hold 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, click the active job that for which you want to hold all scheduled occurrences. In the task pane, under General Tasks, 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. To select multiple jobs in the Current Jobs pane, 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 perform Hold Schedule on more than one job at a time, as long as the state of the jobs are the same. To remove a scheduled occurrence of an active job from a hold 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, click the occurence of the job for which you want to remove from a hold. In the task pane, under General Tasks, clear the Hold Schedule check box by clicking
Hold Schedule.
The active job occurrence is no longer on hold.
455
Monitoring jobs
Active job statuses

Possible statuses for an active job include the following:
Table 13-2 Item Running Queued Cancel Pending Active job statuses Description The operation is underway. The job has been initiated, but Backup Exec is actively looking for a suitable drive or media. 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. The media is being loaded and positioned on the target device. This status can indicate any or all of the following:
Loading Media Pre-processing
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 Device Paused
Backup Exec is processing a snapshot operation. The device that the job was sent to is paused. See Pausing and resuming devices on page 354.
Server Paused
The media server is paused. See Pausing and resuming devices on page 354.
Stalled
The Backup Exec services have become unresponsive. See Setting thresholds to recover jobs on page 491.
Media Request Communication Stalled
You must insert media for the job to continue. Communications between the managed media server and the central administration server have not occurred within the configured time threshold. See Setting communication thresholds and active job status updates on page 773.
456
Monitoring jobs Table 13-2 Item No Communication Active job statuses Description No communication about jobs is being received at the central administration server from the managed media server. The configured time threshold has been reached. See Setting communication thresholds and active job status updates on page 773. Consistency Check Updating Catalogs Backup Exec is running a consistency check of the databases before backup. Backup Exec is updating the catalog information.
Schedule, CPS backup job The Exchange logs are being continuously protected with Continuous running 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.
See About continuous protection for Exchange data on page 1197. Related Topics: Scheduled job statuses on page 458 Completed job statuses on page 471
Viewing and changing scheduled jobs

You can view and change scheduled jobs. You can perform tasks such as Test Run or Delete on more than one job at a time if the jobs are a similar type. To view and change scheduled jobs 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the Filter list, click Scheduled jobs. Single occurrences of scheduled jobs appear in the Current Jobs pane. 3 Do one of the following:
To view or change a specific job Right-click the scheduled job.
457
Monitoring jobs
To view or change multiple jobs
Select a job, and then press the <Ctrl> or <Shift> keys while you select other jobs. Right-click the selected jobs.
From the shortcut menu, select the task that you want to perform.
Related Topics: Running a scheduled job immediately on page 461 Placing a scheduled job or the job queue on hold on page 462 Changing the priority for a scheduled job on page 463 Running a test job for a scheduled job on page 464 Deleting scheduled jobs on page 465
Scheduled job statuses

Possible statuses for scheduled jobs are listed in the following table:
Table 13-3 Scheduled job statuses Description
Scheduled Job Status
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 <Template A> in the policy must run before this scheduled job can run. See Setting template rules on page 436. Invalid Schedule The scheduled job will not run because of one of the following:

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.
See Setting priority and availability windows for selection lists on page 250.
458
Monitoring jobs Table 13-3 Scheduled job statuses (continued) Description 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 jobs time window and the selection lists availability window. See Setting priority and availability windows for selection lists on page 250. On Hold Queued The job has been placed on hold. A temporary state that displays when Backup Exec is applying an error-handling rule that is enabled to retry the job. See Custom error-handling rule for recovered jobs on page 490.
Scheduled Job Status Not in Time Window
459
Monitoring jobs Table 13-3 Scheduled job statuses (continued) Description The job is ready to run, but cannot for one of the following reasons:

Scheduled Job Status Ready
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 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.
460
Monitoring jobs Table 13-3 Scheduled job statuses (continued) Description 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. 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 354. 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, <Template A> supersedes <Template B>. The <Template B> job will run according to the schedule set for it, after the <Template A> job completes. See Setting template rules on page 436. To Be Scheduled A state the scheduled job transitions through as it is being sent for processing.
Scheduled Job Status Scheduled
Server Paused
Related Topics: Active job statuses on page 456 Completed job statuses on page 471
Running a scheduled job immediately

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 2 3 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, select the scheduled job. In the task pane, under Scheduled Job Tasks, 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 463 Running a test job for a scheduled job on page 464
Chapter 13, Administrating Backup Exec 461
Monitoring jobs
Deleting scheduled jobs on page 465
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 2 3 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, select the scheduled job. 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 2 3 On the navigation bar, click Job Monitor. On the Job List tab, in the task pane, under General Tasks, check Hold job queue. 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. To take the job queue off hold 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the task pane, under General Tasks, uncheck Hold job queue. The job queue is no longer on hold. Related Topics: Running a scheduled job immediately on page 461 Running a test job for a scheduled job on page 464
Monitoring jobs
Deleting scheduled jobs on page 465
Changing the priority for a scheduled job

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. The priority of the job is displayed in the Priority column in the Job Monitor on the Job List tab. The priority settings are as follows:

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 <Ctrl> or <Shift> 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 2 3 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, select the scheduled job. In the task pane, under Scheduled Job Tasks, 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 2 On the navigation bar, click Job Setup. Select the job from the Jobs pane.
463
Monitoring jobs
In the task pane, under General Tasks, click Increase Priority or Decrease Priority. The priority is increased or decreased.
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 2 3 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, select the active job. In the task pane, under Scheduled Job Tasks, click Test run. To select multiple jobs in the Job List view in the Job Monitor, 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 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. See Setting test run default options on page 305. 5 In the Properties pane, under Settings, click Notification and enter notification information for the items. See Assigning notification recipients for completed jobs on page 573. 6 In 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 jobs hold status. 7 Click Run Now to submit the test run job.
464
Monitoring jobs
Deleting scheduled jobs

Deleting a scheduled job from the Job List tab in 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. To delete a scheduled job 1 2 3 4 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, right-click the scheduled job. Click Delete. 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 442
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 Technical Support Web site.
465
Monitoring jobs
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. To view completed job properties 1 2 On the navigation bar, click Job Monitor. On the Job list tab, in the Job History pane, select the completed job that you want to view. In the task pane, under General Tasks, 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 Next Job name Job type Job status Job log Server name Selection list name Device Name Target name Media set name All Media Used Byte count Job rate Click this to display the job history of the previous job that was run as part of this recurring job. Click this to display the job history of the next job that was run as part of this recurring job. Job name entered during job configuration. Type of operation that was performed (Archive, Backup, Catalog, Restore, Verify). Status of the operation. File name and location of the job log. Media server that processed the job. Selection list processed in the job. Name of the device that processed the job. Name of the device selected during job configuration. Name of the media set that processed the job. Lists all the media that was used to process the job. Number of bytes processed. Amount of data backed up per minute for the entire job.
466
Monitoring jobs
Files Directories Skipped files Corrupt files Files in use Original start time Job started Job ended Elapsed time Set type Set status Set description Resource name Logon account Encryption key Error
Total number of files processed. Total number of directories processed. Number of files skipped during the operation. Number of corrupt files encountered during the operation. Number of open files encountered during the operation. Time the job was submitted for processing. Time the operation started. The time the operation ended. Length of time the operation took. Type of operation that was performed on the media set (Archive, Backup, Catalog, Restore, Verify). Status of the operation. Job name entered during job configuration. Name of the resource for the job. Name of the logon account that was used for the job. Indicates if an encryption key was used for the job. 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 Technical Support Web site. See Linking from the job log to the Symantec Technical Support Web site on page 470 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 486 for more information.
Agent used
Indicates if the Backup Exec agent was used during the operation.
467
Monitoring jobs
Advanced Open File Option used Start time End time
Indicates if the Advanced Open File Option was used during the operation. Time the operation started. Length of time the operation took.
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 Device and Media Information Utility Job Information Displays the job server, job name, the date and time the job started, the type of job, and the job log name. Displays the drive name, media label, the overwrite protection and append periods, and the media set that this job was targeted to. Displays information about the slot, bar code, media label, status, and device that the utility job was processed on. See About creating utility jobs to help manage devices and media on page 367. 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. See Completed job statuses on page 471. 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 Technical Support Web site. Exceptions Displays a detailed description of the minor errors encountered during job processing. The exceptions section is orange in the job log.
Click Save As to save the job history or job log under a different name or in a different location.
468
Monitoring jobs
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. Click Find to search for a word in the job history. Click Close to close the log.
7 8
Related Topics: Completed job statuses on page 471 Configuring default job log options on page 473
Viewing the history of a job, policy, or selection list

You can view the history of each active job, scheduled job, policy, and selection list. For job histories, you can view details of each recurring job instance. For example, if a job has run 20 times, there are 20 job histories for that job. The View History dialog box for that job lists all 20 job histories for that job. To view the history of a job, policy, or selection list 1 Do one of the following:
To view the history of a policy or selection list On the navigation bar, click Job Setup.
To view the history of an active job, On the navigation bar, click Job Monitor. scheduled job, or job history item
2 3
Right-click the item for which you want to view the history. Do one of the following:

For current jobs, on the shortcut menu, click View History. For job histories, on the shortcut menu, click View Recurring Job Instances.
View the history, and then click OK.
469
Monitoring jobs
Linking from the job log to the Symantec Technical Support Web site
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 Technical Support Web site. From the Web site, you can access technical notes and trouble-shooting tips that are related to a specific message. Unique Message Identifier (UMI) codes establish unique message codes across all Symantec products. Some alerts also contain a UMI. For example, if a Warning alert appears when a job fails, the alert includes a Unique Message Identifier (UMI) code. See Responding to active alerts on page 545. To link from the job log to the Symantec Technical Support Web site 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the Job History pane, select the completed job that you want to view. In the task pane, under General Tasks , click Properties. Click Expand All to view all of the information that is contained in the topics. Click Collapse All to hide the information in the topics. Scroll to the Job Completion Status section. Click the Unique Message Identifier (UMI) code, which appears as a blue hyperlink. A new browser window opens to the Symantec Technical Support Web site. You can create or enable an error-handling rule for this error. These rules let you set options to retry or stop a job when this error occurs. Related Topics: Error-handling rules on page 486
3 4
5 6
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.
470
Monitoring jobs
To delete a completed job 1 2 3 On the navigation bar, click Job Monitor. On the Job List tab, in the Job History pane, select the job that you want to delete. In the task pane, under General Tasks, click Delete. You can select multiple jobs in the Job list view in the Job Monitor by selecting a job, and then pressing the <Ctrl> or <Shift> 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 286
Completed job statuses

Possible job completion statuses for jobs that were processed include the following:
Table 13-4 Status Successful Completed with exceptions Failed over Job completion status Description The job completed without errors. The job completed, but a file in use, skipped, or corrupted was encountered during the operation. 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. The status is the same as the failed over status, however the Apply CheckPoint Restart option was selected. 471
Resumed
Monitoring jobs Table 13-4 Status Canceled Canceled, timed out Job completion status Description The administrator terminated the operation as it was running. 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 286. 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 Technical Support Web site. See Linking from the job log to the Symantec Technical Support Web site on page 470. A job may fail for the following reasons:
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. See Setting communication thresholds and active job status updates on page 773.
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. See Setting the time window for a scheduled job on page 294.
472
Monitoring jobs
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. To configure default job log options 1 2 3 On the Tools menu, click Options. In the Properties pane, under Job Defaults, click Job Logs. Select the appropriate options as follows:
Summary information only Select this option to include the following:

Job name Job type Job log name Media server name Storage device Starting date and time Errors encountered Ending date and time 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. Summary information and directories processed Summary information, directories, and files processed 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.
Summary information, Select this option to include Summary information, processed directories, files and file subdirectories, a list of all the filenames and their attributes. details Selecting this option increases the job log sizes significantly.
473
Monitoring jobs
Prefix for the job log file Enter a prefix to prepend to the job logs that are processed. The name 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. Attach job logs as html Attach job logs as text Job log path Click this to attach the job logs in an html format when an email notification is sent. Click this to attach the job logs in a text format when an email notification is sent. 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 134 Viewing and changing completed jobs on page 465
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"<pathname\job log filename>" 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"
474
Filtering jobs
Filtering jobs
You can select predefined filters to limit the jobs that appear in the Job Setup view, and 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 List tab To filter jobs on the Calendar tab Click Job Setup. Click Job Monitor. Click Job List. Click Job Monitor. Click Calendar.
In the Filter list, click the filter that you want to use.
Related Topics: About managing custom filters on page 475 Viewing and changing active jobs on page 451 Viewing and changing scheduled jobs on page 457 Viewing and changing completed jobs on page 465
About managing custom filters

You can create and edit custom filters for jobs. 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
475
Related Topics: Creating a custom filter for jobs on page 476 Creating a custom filter for current jobs on page 477 Creating a custom filter for jobs in the job history on page 479 Deleting custom filters on page 482 Editing custom filters on page 482
Creating a custom filter for jobs

You can create custom filters to limit the jobs that appear in job lists. To create a custom filter for jobs 1 2 3 4 On the navigation bar, click Job Setup. In the Jobs pane, in the Filter list, click <new custom filter>. Type a unique name and a description for this filter. Do any of the following:
To filter by job type

Under Criteria, click Job Type. 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. 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. 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 backup method
To filter by recurrence
476
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. 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. 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. 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. 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.
To filter by policy
To filter by selection list
To filter by device name
To filter by the server a job was created on
This option appears only if you have the Central Admin Server Option installed.
Click OK.
Creating a custom filter for current jobs

You can create custom filters to limit the current jobs that appear in job lists. To create a custom filter for Current Jobs 1 2 On the navigation bar, click Job Monitor. On the Job List tab, in the Current Jobs pane, in the Filter list, click <new custom
filter>. Chapter 13, Administrating Backup Exec 477
3 4
Type a unique name and a description for this filter. Do any of the following:
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. Under Criteria, click Job Type. 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.
To filter by the job type
This option displays only if you have the Central Admin Server Option installed. To filter by date range

Under Criteria, click Date Range. 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.
To filter by active job status
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. 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.
To filter by media server
This option displays only if you have the Central Admin Server Option installed.
478
To filter by media server pool
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. To filter by scheduled job status

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.
To filter by backup method
Click OK.
Creating a custom filter for jobs in the job history

You can create custom filters to limit the jobs that appear in the job history. To create a custom filter for jobs in the Job History 1 2 3 4 On the navigation bar, click Job Monitor. On the Job List tab, in the Job History pane, in the Filter list, click <new custom filter>. Type a unique name and a description for this filter. Do any of the following:
To filter by job type

Under Criteria, click Job Type. 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.
479
To filter by the job status
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. To filter by media server pool

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. To filter by protected server To filter by job name

Under Criteria, click Protected Server. Type the name of the server on which you want to filter. Under Criteria, click Job Name. Type the name of the job on which you want to filter.
480
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. 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 byte count
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.
Click OK.
481
Deleting custom filters

You can delete custom filters that you no longer need. To delete a custom filter 1 Do one of the following:
To delete a custom filter from the Job Setup view Click Job Setup.
To delete a custom filter Click Job Monitor > Job List. from the Job Monitor view
2 3 4 5 6
In the task pane, under Custom Filter tasks, click Manage custom filters. Highlight the filter that you want to delete. Click Delete. When prompted to delete the custom filter, click Yes. Click Close.
Editing custom filters

You can change options in your custom filters. To edit a custom filter 1 Do one of the following:
To edit a custom filter from the Job Setup view Click Job Setup.
To edit a custom filter Click Job Monitor > Job List. from the Job Monitor view
2 3 4
In the task pane, under Custom Filter tasks, click Manage custom filters. Highlight the filter that you want to edit. Click Edit.
482
Viewing the job workload for a media server from the Calendar tab
5 6 7
Edit the custom filter options. Click OK. Click Close.
Viewing the job workload for a media server from the Calendar tab
You can view a media servers job workload for a month, for a week, or for a day. The month and the week views list the number of jobs and the number of job instances. You can see at a glance what the scheduled work load is for any day. Job details do not appear on these views. The day view provides a graphical view of the scheduled work load, and lists jobs for that day in chronological order. Available tasks for the jobs appear in the task pane. A preview pane provides detailed information for each job, such as final status, and the rate and byte count for job histories. Note Custom filters are not available in the Calendar views. To view the job workload for a media server from the Calendar tab 1 2 On the navigation bar, click Job Monitor. On the Calendar tab, do one of the following:
Click the day icon.
Click the week icon.
Click the month icon.
The number of scheduled, active, and completed jobs appears for each day, as well as the total number of job runs.
483
Viewing jobs for specific days on the calendar
Related Topics: Viewing jobs for specific days on the calendar on page 484 Managing jobs from the Calendar tab on page 484
Viewing jobs for specific days on the calendar

Use the calendar on the task pane to view the number of jobs for a specific day. The day can be any number of days, weeks, or months in the future or in the past. To view jobs for specific days on the calendar 1 2 On the navigation bar, click Job Monitor. On the Calendar tab, in the task pane, click an arrow key to set the calendar forward or backward in monthly increments. To go to the current date, at the bottom of the calendar, click Today.
Related Topics: Viewing the job workload for a media server from the Calendar tab on page 483 Managing jobs from the Calendar tab on page 484
Managing jobs from the Calendar tab

Some common tasks are available on the Calendar tab. You can also right-click a job to access a shortcut menu that contains additional tasks. To manage jobs from the Calendar tab 1 2 On the navigation bar, click Job Monitor. On the Calendar tab, in the task pane, on the calendar, click the day for which you want to view details. Click the day icon. Do one of the following:
To view available tasks in the task pane 484 Select the name of the job.
3 4
Viewing the System Summary
To view available tasks on the right-click menu
Right-click the job.
Click the task that you want to perform.
Related Topics: Viewing the job workload for a media server from the Calendar tab on page 483 Monitoring jobs on page 450
Viewing the System Summary

The System Summary provides detailed summary information about your media server, jobs, alerts, devices, and media. To view the System Summary 1 2 On the navigation bar, click Job Monitor. On the System Summary tab, view summary information.
Related Topics: Monitoring jobs on page 450
Viewing the Symantec Endpoint Protection Security Summary

The Security Summary provides details from the Symantec Endpoint Protection application about viruses, threats, and risks to the media server. Note To enable the Symantec Endpoint Protection features that are integrated into Backup Exec, you must install the Symantec Endpoint Protection Manager component on the media server. See the Administrators Guide for Symantec Endpoint Protection for more information about the Security Summary. You can configure a backup job to start automatically when the Symantec ThreatCon level reaches a specified level.
485
Error-handling rules
To view the Security Summary 1 2 On the navigation bar, click Job Monitor. On the Security Summary tab, view Symantec Endpoint Protection summary information.
Related Topics: About using Backup Exec with Symantec Endpoint Protection on page 324 Creating automatic backup jobs for use with Symantec Endpoint Protection on page 325
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. 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 490. 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.
486
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 491.
Creating a custom error-handling rule

You can create custom rules to set retry options and final job disposition for failed or canceled jobs. 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.
The Error-Handling Rules dialog box appears. 2 Select the appropriate options as described in the following:
Name Type The name of the error-handling rule.
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
Error Category
The category of error codes that this rule applies to.
487
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.
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.
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. The status for the job that will activate the rule. The job status can be viewed, but not modified. Statuses are:

Final Job Status
Error Canceled Failed
488
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 the following:

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. 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.
Available errors
Retry job Maximum retries Retry interval
Select this check box to allow Backup Exec to retry the job. Enter the number of times you want the job retried. The maximum number of times the job can be retried is 99. Enter the number of minutes to wait before the job is retried. The maximum number of minutes is 1440.
Place job on hold until Select this option to place the job on hold until you can manually error condition has been clear the error. After you clear the error, you must remove the hold manually cleared for the job.
489
Reschedule for its next scheduled service Notes
Select this option to run the job at the next scheduled occurrence. Enter any miscellaneous information for the error-handling rule.
Related Topics: Error-handling rules on page 486 Custom error-handling rule for recovered jobs on page 490 Cluster failover error-handling rule on page 491
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.
Table 13-5 Error code 0xE00081D9 E_JOB_ENGINE_DEAD Error codes for recovered jobs custom error-handling rule Description The displayed error message is: The Backup Exec job engine system service is not responding. See Setting thresholds to recover jobs on page 491. 0xE0008820 E_JOB_LOCAL RECOVERNORMAL 0xE000881F E_JOB_REMOTE RECOVERNORMAL 0xE0008821 E_JOB_STARTUP RECOVERY The displayed error message is: The local job has been recovered. is required. The displayed error message is: The remote job has been recovered. No user action is required. The displayed error message is: Job was recovered as a result of Backup Exec RPC service starting. No user action is required. No user action
490
Setting thresholds to recover jobs
Note If the Central Admin Server Option is installed, additional error codes are selected. Related Topics: Error-handling rules on page 486 Cluster failover error-handling rule on page 491
Cluster failover error-handling rule

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 rules setting. Related Topics: Enabling or disabling checkpoint restart on page 700

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 jobs 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.
Chapter 13, Administrating Backup Exec 491
See Custom error-handling rule for recovered jobs on page 490. 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 2 3 On the Tools menu, click Options. In the Properties pane, under Settings, click Job Status and Recovery. 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. 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.
Recovered
Related Topics: Error-handling rules on page 486 Creating a backup job by using the Backup Wizard on page 264 Creating a backup job by setting job properties on page 267 About selection lists on page 243 Duplicating backed up data on page 298 Restoring data by setting job properties on page 498 Using resource discovery to search for new resources on page 255 Configuring DLO on page 987 About managing custom filters on page 475
Chapter
14
Restoring data
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 the following methods for finding the files you need to restore:
Table 14-1 Method Resource view Methods for finding files to restore Description 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. 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. Enables you to specify file and date attributes for the data you want to restore. 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.
Media view
Include/Exclude files feature Search catalogs
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. When creating your restore jobs, you can do the following:
493
Restore jobs and the catalog
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: Selecting data to restore on page 519 Including or excluding files for restore on page 522

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 196 Setting catalog defaults on page 494 Catalog levels on page 496
Setting catalog defaults

Catalog defaults determine how Backup Exec uses the catalog. To set catalog defaults 1 2 On the Tools menu, click Options. On the Properties pane, under Settings, click Catalog.
494

Request all media in the sequence for catalog operations Select this option to catalog media starting with the lowest known tape number in the tape family. For example, if you dont 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. Use storage media-based catalogs 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. Current path Catalog drive Catalog path Type the path where you want catalogs to be located. This path defaults to \Program Files\Symantec\Backup Exec\Catalogs. 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. 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.
Click OK.
495
Chapter 14, Restoring data
Related Topics: Restore jobs and the catalog on page 494 Catalog levels on page 496
Catalog levels
The amount of information that can be viewed through the catalog for media is determined by the medias 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:
Table 14-2 Item Fully cataloged media Media catalog levels Description With fully-cataloged media, you can do the following:
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. There is no catalog information for the media. You must catalog the media to view and select files to restore.
Uncataloged media
Related Topics: Setting catalog defaults on page 494 Restore jobs and the catalog on page 494
496
Restoring data by using the Restore Wizard
Restoring data by using the Restore Wizard

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 2 3 From the navigation bar, click the arrow next to Restore. Click New Restore Job using Wizard. 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 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job using Wizard. Uncheck Always launch the Restore Wizard from the Restore button. Click Next.
To set the Restore Wizard to launch from the Restore button 1 2 3 On the Tools menu, click Wizards > Restore Wizard. Check Always launch the Restore Wizard from the Restore button. Click Next.
497
Restoring data by setting job properties

If you are familiar with Backup Exec, you can restore data by selecting the options you want to use in the restore job. To restore data by setting job properties 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. 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. See Changing and testing resource credentials for restore jobs on page 527. 5 On the Properties pane, under Source, click Device. SeeDevice options for restore jobs on page 502. 6 On the Properties pane, under Settings, click General. SeeGeneral options for restore jobs on page 503.
498
Select any of the following additional configuration options for the restore job:
To redirect this job On the Properties pane, under Destination, do any of the following: to another system Click File Redirection to redirect file sets. other than the one Click Microsoft SQL Redirection to redirect SQL Server sets to from which the another SQL server. data was backed up Click Microsoft Exchange Redirection to redirect Exchange sets to another Exchange server.
Click Microsoft SharePoint Redirection to redirect SharePoint Server sets to another SharePoint server. Click Oracle Redirection to redirect an Oracle instance to another Oracle server or to an alternate path on an alternate server or the original server. Click DB2 Redirection to redirect DB2 instances or containers. Click Enterprise Vault Redirection to redirect the Enterprise Vault or to redirect directory and monitoring databases.
See Redirecting a restore job on page 528.

To set advanced options for the restore job To set commands to run before or after the job To restore other platform types or database agents, such as SQL, Exchange, or NetWare
On the Properties pane, under Settings, click Advanced. See Advanced options for restore jobs on page 505. On the Properties pane, under Settings, click Pre/Post Commands. See Running pre and post commands for restore jobs on page 508.
On the Properties pane, under Settings, select the platform type. Refer to the chapter or appendix for that item for instructions on completing the options.
To specify a local On the Properties pane, click Network and Security, and then enter network to be used the network information. for this restore job See Specifying the restore network on page 533. To have Backup On the Properties pane, under Settings, click Notification, and then select each recipient to be notified when the job completes. Exec notify recipients when See Assigning notification recipients for completed jobs on page 573. this job completes
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.
Chapter 14, Restoring data 499
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 jobs log. 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. See Restore questions on page 680.
Caution When restoring System State, you must reboot your system before performing subsequent restore jobs. Related Topics: Selecting data to restore on page 519 Redirecting a restore job on page 528 Redirecting restores for SQL on page 1354 Requirements for restoring Exchange 2000, 2003, and 2007 on page 1224 Restoring NetWare servers on page 909 Selecting restore options for Lotus Domino databases on page 1306 Filtering jobs on page 475 About restoring file permissions on page 511
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:
Table 14-3 Item Selection list Selections options for restore jobs Description 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. Administrators Guide
500
Restoring data by setting job properties Table 14-3 Item Load selections from existing list Search Catalogs Include/Exclude Selections options for restore jobs (continued) Description Click this button if you want to use a previously created selection list or merge existing selection lists. Click this button to search for files or other items that you want to restore. 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 522. Include subdirectories Show file details Select this option if you want to select the contents of all the subfolders when a directory is selected. 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. 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. Enter the date of the earliest backup set that you want to appear in the selection list. By default, the selection list includes backup sets that were created in the last 30 days. This option appears only when the View by Media and View by Resource tabs are selected. Ending backup date Enter the date of the latest backup set that you want to appear in the selection list. By default, the selection list includes backup sets that were created in the last 30 days. This option appears only when the View by Media and View by Resource tabs are selected. 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. 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. 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.
Preview pane Beginning backup date
View by Media
View Selection Details
501
Device options for restore jobs

To set device options for restore jobs, on the Properties pane, under Source, click Device. The following device options are available:
Table 14-4 Item Device Device options for restore jobs Description Enter the name of the device that contains the media for the data you want to restore. If the media is in another device, Backup Exec ignores this option. 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.
Maximum number of devices to use for resources that support multiple data streams
502
General options for restore jobs

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 the following:
Table 14-5 Item Job name Job priority General settings options for restore job Description 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. 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 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. 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. 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.
Skip if file exists
Overwrite the file on disk only if it is older
Restore all information for files and directories
Select this option to restore all information, including security information, for files and directories.
503
Restoring data by setting job properties Table 14-5 Item Restore only security information for files and directories General settings options for restore job (continued) Description 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.
Restore all information Select this option to restore all information except security except security for files and information for files and directories. This option is valid only for directories 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. 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 498
504
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 the following:

Table 14-6 Item Restore Removable Storage data Advanced options for restore Description 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. Restore Terminal Services database 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. Restore Windows Select this check box to restore the Windows Management Management Instrumentation (WMI) repository. The WMI repository is stored in Instrumentation repository 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 717.
505
Restoring data by setting job properties Table 14-6 Item Force the recovery of the cluster quorum even if other nodes are online and/or disk signatures do not match. Advanced options for restore (continued) Description 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. 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. 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. Merge the existing Select this option if you want to merge the existing hardware and hardware configuration and registry services with the data you selected to be restored. This registry services with the option should only be used for restoring System State. data to be restored Overwrite the existing hardware configuration and registry services with the data to be restored 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.
506
Restoring data by setting job properties Table 14-6 Item Restore junction points, symbolic links, files and directories from backup media Advanced options for restore (continued) Description Select this option to restore the information for the junction points, symbolic links, and the files and directories to which they are linked. If you select this option, existing junction points or symbolic links are overwritten. A junction point or symbolic link must have been backed up with one of the following options selected:

Back up files and directories by following junction points Back up files and directories by following symbolic links
Otherwise, these files and directories are not restored unless the junction point was linked to a mounted drive that did not have an assigned drive letter. See Back up files and directories by following junction points on page 281. Preserve existing junction points and symbolic links and restore files and directories from backup media Select this option to restore files and directories that were backed up from junction points and symbolic links while retaining the destination computer's current junction points and symbolic links. This option prevents current junction points and symbolic links from being overwritten with the junction point and symbolic link information on the backup media. When you select this option and identical junction points, symbolic links, or directory names exist on both the destination computer and the media, the files and directories are restored to the destination computer's junction point, symbolic link, or directory. See Back up files and directories by following junction points on page 281. Allow managed media server to use any network interface to access remote agents 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. 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. 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.
507
Restoring data by setting job properties Table 14-6 Item Path on media server for staging temporary restore data when using Backup Exec Granular Recovery Technology (GRT) to restore individual items from tape Advanced options for restore (continued) Description 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 folder on an NTFS volume on this media server. Restore data and metadata for this job are stored here 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. You can also specify a location that all applicable restore jobs can use. See Setting defaults for restore jobs on page 531.
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.
508
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. To set up commands to run before or after a restore job 1 2 On the Properties pane, under Settings, click Pre/Post Commands. 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. 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 runs. Use local paths, and make sure the paths exist on each server and are correct. Commands that require user interaction, such as prompts, are not supported. Allow pre- and postcommands to be successful only if completed with a return code of zero 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 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.
509
Run job only if pre-command is successful
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.
Run post-command only if pre-command is successful
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.
Run post-command even if job fails
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.
Cancel command if not Select the number of minutes Backup Exec should wait before completed within x minutes canceling a pre- or post-command that did not complete. The default time-out is 30 minutes. On this media server On each server restored to Select this option to run the pre- and post-commands on this media server only. 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.

Setting default pre/post commands on page 314
About restoring file permissions

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. 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 directorys security level of Full. Related Topics: General settings options for restore job on page 503
511
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. 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 <F8> when prompted for Startup Options, and then select the Directory Services Restore Mode option. To open Services, right-click My Computer, and then click Manage. Expand Services and Applications. Click Services. For each Backup Exec service listed, do the following in the order listed:

2 3 4 5
Click Properties on the shortcut menu. Click the Log On tab, click This account, enter a user account with local administrators rights, and then click OK. Right-click the service, and then click Start.
After the Backup Exec services have started, run 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.
512
See Advanced options for restore jobs on page 505. 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. To perform an authoritative restore of the Active Directory, you must run Microsofts 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 498 Advanced options for restore on page 505 About restoring individual Active Directory and ADAM/AD LDS objects on page 879
About restoring Shadow Copy Components

The Backup Exec Shadow Copy Components file system uses Microsofts Volume Shadow Copy Service to protect critical operating system and application service data, and thirdparty application and user data on Windows 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 the following selections:
Table 14-7 Item System State Writers Backup Exec Shadow Copy Components Description
Lets you select System State Writers to restore.
See Restoring System State on page 512.

Service State Writers Lets you select Service State Writers to restore.
See Restoring data by setting job properties on page 498.

User Data Writers Lets you restore user data and the Microsoft Virtual Server.
See Restoring virtual machines and the Virtual Server Host on page 514. Chapter 14, Restoring data 513
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 fails. Related Topics: About restoring individual Active Directory and ADAM/AD LDS objects on page 879 Using redirected restore for Active Directory, Active Directory Application Mode on page 529
Restoring virtual machines and the Virtual Server Host

You can restore individual virtual machines and the Virtual Server Configuration to the Virtual Server Host on which they originally resided. You can also redirect virtual server file sets to an alternate server. See Redirecting a restore job on page 528. If there is a catastrophic failure, you must reinstall the following items:

Virtual Server Host The most recent backup of the virtual machines Virtual Server Configuration
To restore a Virtual Server Host and all settings 1 2 3 4 5 6 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the selection list, navigate to the Virtual Server Host. Expand Shadow Copy Components. Expand User Data. Do one of the following:

Select the set of virtual guest machines you want to restore. Navigate to and select the Virtual Server Configuration.
514
The Virtual Server Configuration may be in a separate backup set. You must select the Virtual Server Configuration to restore the Virtual Server Host. 7 Do one of the following:

To start the Restore job, click Run Now. To select other restore properties, click the appropriate tab.
To restore a virtual machine 1 2 3 4 5 6 7 8 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the selection list, navigate to the Virtual Server Host. Expand Shadow Copy Components. Expand User Data. Expand Microsoft Virtual Server. Select the virtual machine you want to restore. Do one of the following:

To start the Restore job, click Run Now. To select other restore properties, click the appropriate tab.
Related Topics: About the Backup Exec Shadow Copy Components file system on page 258 About restoring Shadow Copy Components on page 513
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:
515
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 516. 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 497 Selecting data to restore on page 519
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. 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 528
516
Manual disaster recovery of Windows computers on page 664
Restoring Distributed File System (Dfs) links

If you want to restore Dfs links, you must know which computer hosts the Dfs root. To restore Distributed file system (Dfs) links 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the selection list, navigate to the computer that hosts the Dfs root. 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. 5 Run the restore job.
Related Topics: Selecting Distributed File System (Dfs) links for backup on page 240
About restoring media created with other backup software

You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 Backup Exec supports restoring NetWare SMS volume backups to non-SMS volumes. For example, the data that is backed up with Backup Exec for NetWare Servers or Novells SBackup can be restored to the Windows media server or another network share.
Restoring data from ARCserve media

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
517
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 2 Inventory all the tapes included in the ARCserve backup. 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. Due to the naming conventions ARCserve uses for some systems, it may be necessary to select a different location for the data using Backup Execs File Redirection. See Redirecting a restore job on page 528. Related Topics: Inventorying media on page 368 Cataloging media while reviewing devices or media on page 196 Restoring data by setting job properties on page 498
Selecting data to restore
Redirecting a restore job on page 528 About restoring media created with other backup software on page 517
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.
View by Media Media label Backup sets
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
519
Creating a restore selection list
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 items 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 494 Cataloging media while reviewing devices or media on page 196 Restoring data by setting job properties on page 498

A restore selection list includes all of the resources that you want to restore. To create a restore selection list 1 2 3
520
On the navigation bar, click Job Setup. On the Task pane, under Selection List Tasks, click New restore selection list. Select the resources that you want to include in the selection list.

Selection list Load selections from existing list Type the name of this selection list or use the name that Backup Exec provides. 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 246. 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. Click Include/Exclude to select files that you want to include in or exclude from this selection list. Select this option if you want to select the contents of all the subfolders when a directory is selected. Select this option to display details about the files available for selecting. 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. 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. 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. 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. 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.
Include/Exclude Include subdirectories Show file details Preview pane Beginning backup date
Ending backup date
View by Resource
View by Media
521
Including or excluding files for restore
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.
(Optional) To change or test a logon account for the resources, on the Properties pane, under Source, click Resource Credentials. See To change and test resource credentials for restore jobs on page 527.
Click OK.

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 do the following:
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 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. Click Include/Exclude. Select the appropriate options as follows:
Media Backup set Path Select the media that contains the files you want to restore. Select the backup set for which you want to specify attributes. Enter any available directory or subdirectory. Enter the full path to the subdirectory.
522
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. Select this option to include the files in the operation. This is the default option. Select this option to exclude files from the job. Select this check box to include or exclude files that were created or modified during the specified time period.
Include Exclude Files dated
Submit the job using the same procedures required for other restore jobs.
Related Topics: Restoring data by using the Restore Wizard on page 497 Redirecting a restore job on page 528
523
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 2 On the Edit menu, click Search Catalogs. Do one of the following:
To search for a file Select the Name and Resource tab, and then complete the appropriate options. by name and resource See Name and resource options for catalog search on page 525. To search for files by date modified
Select the Date Modified tab, and then complete the appropriate options. See Date modified options for catalog search on page 526.
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 files properties. To sort the listings by filename, size, type or date modified, click the appropriate column heading.
4 5
Check the version of the file you want to restore and click Apply. 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 497
524
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 the following:
Table 14-8 Item File/item name Name and resource options Description 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. 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. Select this option to search for directories listed in the Path or File name fields. Select this option to search all subdirectories below the directory listed under the Location field.
Media
Find directories Include subdirectories
525
Date modified options for catalog search

To search for files by date modified, on the Search Catalogs dialog box, select the Date
Modified tab.
Options on this dialog box include the following:

Table 14-9 Item All files/items Find all files/items created or modified Between x/x/x and x/x/x During the previous x month(s) Date Modified options Description Select this option to search for all files or items. Select this option to search only for files or items that have been created or modified in a specified time period. Click this option and enter specific dates by month, day, and year. 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.
Restore jobs and media libraries

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 Execs 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.
526
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 2 3 4 5 6 7 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Select the data you want to restore. On the Properties pane, under Source, click Resource Credentials. Select the resource whose logon account you want to edit. Click Change. 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 498 Redirecting a restore job on page 528
527
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 or share. 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 2 3 4 5 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Select the data to be restored. On the Properties pane, under Destination, click File Redirection. Select the appropriate options as follows:
Redirect file sets Restore to drive Server logon account Click this option to specify target paths or resources other than where the data was originally backed up. Select the destination for the restored data. Click the Browse button (...) to view local and network drives. 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. 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.
Path logon account
528
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 504 Using redirected restore for Active Directory, Active Directory Application Mode on page 529 Redirecting restores for SQL on page 1354 Redirecting SharePoint Portal Server restore jobs on page 1258 Scheduling jobs on page 286
Using redirected restore for Active Directory, Active Directory Application Mode
When you want to install a new Windows 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. To install Active Directory using the Install from Media feature 1 Perform a standard System State backup of an active Windows Server Domain Controller that is in the target domain. Transport the tape to the location of the system that will be installed into the target Domain.
529
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 4 5 Inventory the drive where the tape is loaded. Catalog the tape. 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. Type dcpromo /adv Click OK. Click Next when the Active Directory Installation Wizard appears.
7 8 9
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. 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.
Setting defaults for restore jobs
For more information, refer to your Microsoft documentation. Related Topics: Creating a backup job by setting job properties on page 267 Inventorying media on page 368 Cataloging media while reviewing devices or media on page 196 Redirecting a restore job on page 528

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 2 3 On the Tools menu, select Options. On the Properties pane, under Job Defaults, click Restore. 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. 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. 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.
Skip if file exists
Overwrite the file on disk only if it is older
531
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, symbolic links, files and directories from backup media
When this option is selected, the information for the junction points and symbolic links and the files and directories to which they are linked is restored. If you select this option, existing junction points are overwritten. If a junction point was originally backed up without the Back up files and directories by following junction points check box selected, 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. See Back up files and directories by following junction points on page 281.
Preserve existing junction points and symbolic links and restore files and directories from backup media
Select this option to restore files and directories backed up from junction point links and symbolic links while retaining the system's current junction points. This option prevents 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. If a junction point was originally backed up without the Back up files and directories by following junction points check box selected, 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. See Back up files and directories by following junction points on page 281.
532
Specifying the restore network
Path on media server for staging temporary restore data when using Backup Exec Granular Recovery Technology (GRT) to restore individual items from tape
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 folder on an NTFS volume on this media server. Restore data and metadata for this job are stored here 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. You can also specify a location for an individual job. See Advanced options for restore jobs on page 505.

Backup Exec restores data using the default network information. See Setting default backup network and security options on page 318. 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 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Select the data to be restored. On the Properties pane, under Settings, click Network and Security.
533

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. Protocol The options are as follows:

Subnet Allow use of any available network interface, subnet, or protocol for remote agents not bound to the above network interface, subnet, or protocol
Displays the 32-bit number that determines the subnet to which the network interface card belongs. 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. 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.
Interface details
6 7
Continue selecting options for the restore job. 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 497 Specifying backup networks on page 316 Scheduling jobs on page 286
534
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 2 3 4 5 6 On the navigation bar, click Job Monitor. Click the Job List tab. In the Current Jobs Filter box, click Active jobs. Select the restore job you want to cancel. In the task pane, under Active Job Tasks, click Cancel. Click Yes.
Related Topics: Deleting scheduled jobs on page 465
535
536
Chapter
15
Alerts and notifications
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 one of the following alert types, which helps you distinguish the severity of the alert or whether Backup Exec needs a response from you.
Table 15-1 Item Alert types Description
Attention required
Indicates issues that require a response before the job or operation can continue. Indicates issues that affect job processing or the integrity of your backup. Indicates conditions that may or may not cause jobs to fail. You should monitor the conditions and take actions to resolve them. Provides status messages for the conditions that you might want to know about.
Error
Warning
Information
Most alerts are enabled. However, you choose which alerts to display by editing alert category properties.
537
Viewing alerts
See Configuring alert category properties on page 550. 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 545. 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 553. 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 539. You can double-click alerts in either view to see more detailed information. See Viewing alert properties on page 542. 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 544. 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.
538
Viewing alerts
To view alerts 1 2 On the navigation bar, click Alerts. Click the Active Alerts tab or the Alert History tab.
Related Topics: Responding to active alerts on page 545
Filtering 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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab or the Alert History tab. In the Filter box, click the following options for the alerts that you want to view.
All alerts Lists all alerts.
Attention required alerts Lists alerts that require a response. Error alerts Warning alerts Information alerts System alerts Media alerts Device alerts Job alerts Lists system, job, media, and device error alerts. Lists system, job, media, and device warning alerts. Lists system, job, media, and device information alerts. Lists the alerts that originated from the system. Lists the alerts that originated from media. Lists the alerts that originated from devices. Lists the alerts that originated from a job.
Chapter 15, Alerts and notifications
539
Viewing alerts
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.
Related Topics: Responding to active alerts on page 545 Creating custom filters for alerts on page 540
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 2 On the navigation bar, click Alerts. On the Active Alerts tab or the Alert History tab, click the filter icon next to the Filter menu. Type a unique name and a description for the filter. On the Properties pane, under Criteria, click Alert Type. Check Enable this filter. Uncheck the check boxes for the alert types that you do not want to display. On the Properties pane, under Criteria, click Source. Check Enable this filter. Uncheck the check boxes for the sources that you do not want to filter on.
3 4 5 6 7 8 9
10 Click OK. Related Topics: Editing custom filters for alerts on page 541 Deleting custom filters for alerts on page 541
540
Viewing alerts
Filtering alerts on page 539
Editing custom filters for alerts

You can change custom filters at any time. To edit a custom filter for alerts 1 2 On the navigation bar, click Alerts. Select one of the following tabs:

Active Alerts Alert History
3 4 5 6 7 8
In the task pane, under Custom Filter Tasks, click Manage custom filters. Select the filter that you want to edit. Click Edit. Edit the custom filter options. Click OK. Click Close.
Related Topics: Creating custom filters for alerts on page 540 Filtering alerts on page 539
Deleting custom filters for alerts

You can delete custom filters when you no longer need them. To delete a custom filter for alerts 1 2 On the navigation bar, click Alerts. Select one of the following tabs:

Active Alerts Alert History

541
Viewing alerts
3 4 5 6 7
In the task pane, under Custom Filter Tasks, click Manage custom filters. Select the filter that you want to delete. Click Delete. When you are prompted to delete the custom filter, click Yes. Click Close.
Related Topics: Creating custom filters for alerts on page 540
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 2 3 4 On the navigation bar, click Alerts. Click the Active Alerts or Alert History tab. Select the alert from either the Active Alerts or Alert History pane. Under General Tasks in the task pane, click Properties. The Alert Properties dialog box provides the following items:
Category Type The title of the alert. 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.
542
Viewing alerts
Device Job Name Time alert received Source
The name of the device on which the alert occurred. The name of the job associated with the alert. The date and time the alert occurred. The cause of the alert. Alerts can originate from one of the following sources:

System Job Media Device
SNMP trap Identification Enabled Send notifications Send SNMP notifications Record in event log
The SNMP message from Backup Exec regarding status and error conditions. SNMP must be installed to view this message. The alert is activated or disabled. Notifications are enabled or cleared for the alert. Recipients must be configured in order to use this option. SNMP notifications are enabled or cleared for the alert. SNMP must be installed to use this option. 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 Automatically clear after x days/hours/minutes
The alerts ID in the Windows Event Viewer. 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. This option is available only for the Media Overwrite, Media Remove, Media Insert, Library Insert alert categories. The response Backup Exec automatically sends. 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. The user ID that responded to the alert.
Respond with
Include job log
User who responded
543
Viewing alerts
Response machine Time user responded User response
The name of the computer from which the user responded. The date and time the user responded to the alert. The response the user entered for the alert.
After you view the alert properties, click OK.
Related Topics: Configuring alert category properties on page 550 Configuring recipients on page 557 About SNMP notification on page 575
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts or Alert History tab. Select the alert for which you want to view the job log from either the Active Alerts or Alert History pane. 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.
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.
To print the job log, click Print. You must have a printer attached to your system and configured in order to print the log.
544
Responding to active alerts
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 465

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, and all alerts that require a response. If you have set View Filters, only those alerts that are selected appear, in addition to any alerts that require a response. You can configure automatic responses for alert categories. Some alerts provide a Unique Message Identifier (UMI) code. This code is a hyperlink to the Symantec Technical Support Web site. You can access the technical notes that are related to the alert. See Configuring automatic responses for alert categories on page 547. To respond to an active alert 1 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Select the alert to which you want to respond, and then under Alert Tasks in the task pane, click Respond. 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.
545
Message Click here for more information: V-XXX-XXXXX
Describes the event that caused the alert and provides suggestions for responding to the alert. Appears if a TechNote is associated with an error. Click the Unique Message Identifier (UMI), which starts with the letter V, and appears as a blue hyperlink. A new browser window opens to the Symantec Technical Support Web site. If the computer does not have access to the Internet, you can type the following URL in a browser window on another computer: http://entsupport.symantec.com/umi/<UMI Code>
Server name Device name Job name Time
The name of the computer on which the alert occurred. The name of the device on which the alert occurred. The job associated with the alert. The date and time the alert occurred.
Automatically display new Select this check box to have alerts automatically appear on the alerts Backup Exec console when they are sent. If you do not select this option, you must respond to alerts through the Active Alerts pane. Note Alerts that require a response always appear on the Backup Exec console. See Changing default preferences on page 136. Automatically respond to and clear all alerts in the category To provide automatic responses for this alert select the amount of time to wait before a response is provided and select the response. See Configuring automatic responses for alert categories on page 547.
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 549 Enabling or disabling alerts from the Active Alerts pane on page 552 Viewing alerts on page 538 Linking from the job log to the Symantec Technical Support Web site on page 470
546
Configuring automatic responses for alert categories

Using the Alert Autoresponse Wizard, you can do the following:

Configure the length of time to keep alerts active Specify the response that you want to send for alerts
You can use the Alert Autoresponse Wizard for the following alert categories:
Table 15-2 Alert category Library Insert Media Insert Alert categories for the Alerts Autoresponse Wizard Description The Library Insert alert is a request to insert overwritable media into the robotic library by using the import command. 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. The Media Overwrite alert is displayed when Media Overwrite Protection is configured to prompt before overwriting media. 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.
Media Overwrite Media Remove
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 2 3 On the Tools menu, click Wizards>Alert Autoresponse Wizard. On the Welcome to the Alert Autoresponse Wizard panel, click Next. 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.
547
Do not autorespond
Select this to keep this alert on the Active Alerts tab until media is added to the library.
4 5
Click Next. 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.
Respond with

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.
6 7
Click Next. On the Configure Media Overwrite Category panel, select the appropriate options as follows:
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.
8 9
Click Next. On the Configure Media Remove Category panel, select the appropriate options as follows:
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.
548
Respond with Do not autorespond
This option is not available for the Media Remove alert category. Select this to keep this alert on the Active Alerts tab until you acknowledge the alert by clicking OK.
10 Click Next. 11 Read the Alert Autoresponse Summary panel, and then click Next. 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 550.
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. 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.
549
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 552. 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 2 3 4 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Alert Tasks in the task pane, click Configure alert categories. Under Alert Categories, click the alert for which you want to view or change properties. 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 <Shift>, and then click the last item. To select alert categories that are not consecutive, press and hold down <Ctrl>, and then click each item. Under Category Properties, select the appropriate options as follows:
Category name Enable alerts for this category The title of the alert. This property can be viewed, but not edited. 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. See Enabling or disabling alerts from the Active Alerts pane on page 552.
Tip
550
Send notifications to selected recipients
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. See Configuring recipients on page 557.
Include job log with a Select this check box to send the job log to the recipient notification to an email or configured for notification. The recipient must be configured to printer recipient receive email or printer notifications. Send SNMP Notifications Select this check box to enable SNMP notifications. SNMP must be installed to use this option. See About SNMP notification on page 575. Record event in the Windows Event Log 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. Automatically clear after x Select this check box to enter the number of minutes, hours, or days/hours/minutes 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. See Configuring automatic responses for alert categories on page 547. 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.
Click Apply to apply the properties to the alert and continue configuring additional alerts. Click OK to exit the Configure Alert Categories dialog box.
Related Topics: Assigning recipients to alert categories for notification on page 572
551
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 550. To enable or disable an alert from the active alerts pane 1 2 3 4 On the navigation bar, click Alerts. Click the Active Alerts tab. On the Active Alerts pane, select the alert that you want to enable or disable. 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 2 3 On the navigation bar, click Alerts. Click the Alert History tab. Select the alert you want to delete, and then under Alert History Tasks in the task pane, click Delete. Click Yes to confirm that you want to delete the alert. The alert is removed from the Backup Exec database.
552
Setting up notification for alerts

You can configure Backup Exec to notify recipients when alerts occur. The following notification methods are available:
Table 15-3 Method SMTP email or phone text messaging MAPI email VIM email Pager Notification methods For more information
See Configuring SMTP for email or mobile phone text message notification on page 553. See Configuring MAPI email for notification on page 555. See Configuring VIM email for notification on page 556. See Configuring a pager for alert notification on page 556.
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 2 Configure the method you want to use to notify the recipient. Configure recipients. Recipients are individuals, computer consoles, printers, or groups. 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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure email and pagers.
553
Click the SMTP Configuration tab and select the appropriate options as follows:
Enable SMTP mail server Select this check box to activate the notification method. 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. Defaults to a standard SMTP port. In most cases, the default should not have to be changed. The senders name. Spaces and special characters are allowed here. 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 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 Sender password The login name of the sender on the SMTP mail server. The senders 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.
SMTP port Sender name Sender email address
Click OK.
Related Topics: Configuring recipients on page 557
554
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. 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 2 3 4 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure email and pagers. Click the MAPI Configuration tab and select the appropriate options as follows:
Enable Mail server name Select this check box to activate the notification method. Type the name of the Exchange server. You must use an Exchange server to which the Backup Exec service account has access. See Changing Windows security on page 65. Mailbox name to send email from 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. 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.
Click OK.
555
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 2 3 4 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure email and pagers. Click the VIM Configuration tab and select the appropriate options as follows:
Enable Notes client directory Mail password Confirm mail password Select this check box to activate the notification method. Type the path of the directory in which the Notes client is located. Type the password that enables you to connect to the Notes client. Re-type the password that enables you to connect to the Notes client.
Click OK.
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 2 On the navigation bar, click Alerts. Click the Active Alerts tab.
556
Configuring recipients
Under Notification Tasks in the task pane, click Configure email and pagers. The Notification Configuration Properties dialog box appears.
Click the Pager Configuration tab and select Enable to activate this alert notification method. Select a modem from the Select a modem for sending pages option. Only modems recognized in Windows appear in the list box.
Click OK.
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:
Table 15-4 Item Person Types of recipients Description
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.
Net Send Printer Group
Related Topics: Configuring SMTP for email or mobile phone text message notification on page 553 Assigning recipients to alert categories for notification on page 572 Assigning notification recipients for completed jobs on page 573
557
About selection lists on page 243
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4 5 6 Click New, click Person in the Recipient Type dialog box, and then click OK. In the Name field, type the name of the recipient that you want to configure. Click the SMTP Mail tab and select the appropriate options as follows:
Enable Address Select this check box to activate this notification method for the recipient. 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 Enable Enables you to test the notification configuration for the recipient. Select this check box to activate the option.
558
Notify me a maximum of x Type the total number of notifications you want sent to the times within x minutes 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. Reset the notification limits after x minutes 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. Select this check box to activate the option and configure the length of time the recipient is available for notification. Enables you to select the days and times when notifications can be sent to the recipient. See Scheduling notification for recipients on page 569.
Enable Schedule
Click OK.
Related Topics: Editing recipient notification methods on page 570 Editing recipient notification properties on page 570 Assigning recipients to alert categories for notification on page 572
559
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4 5 6 Click New, click Person in the Recipient Type dialog box, and then click OK. In the Name field, type the name of the recipient that you want to configure. Click the MAPI Mail tab and select the appropriate options as follows:
Enable Mailbox Select this check box to activate this notification method for the recipient. 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. Enables you to test the notification configuration for the recipient. Select this check box to activate the option.
Test Enable (Limit the number of notifications sent)
Notify me a maximum of x Type the total number of notifications you want sent to the times within x minutes 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. Reset the notification limits after x minutes 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.
560
Enable (Limit when notifications can be sent) Schedule
Select this check box to activate the option and configure the length of time the recipient is available for notification. Enables you to select the days and times when notifications can be sent to the recipient. See Scheduling notification for recipients on page 569.
Click OK.
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4 5 6 Click New, click Person in the Recipient Type dialog box, and then click OK. In the Name field, type the name of the recipient that you want to configure. Click the VIM Mail tab and select the appropriate options as follows:
Enable Address Test Select this check box to activate this notification method for the recipient. Type the email address of the recipient to whom the notification message will be sent. For example, JohnSmith@company.com. Enables you to test the notification configuration for the recipient. 561
Enable (Limit the number of notifications sent)
Select this check box to activate the option.
Configuring a pager for a person recipient

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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. 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.
562
5 6
In the Name field, type the name of the recipient that you want to configure. Click the Pager tab and select the appropriate options as follows:
Enable Carrier Phone Select this check box to activate this notification method for the recipient. Type the area code and phone number to access the paging service providers modem. The paging service number may be different from the number you enter to manually enter a page. Enter the country or region name and country code in which the pager is located. 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 pagers phone number. Enables you to configure additional settings for the pager. See step 7 on page 564. Test Enable (Limit the number of notifications sent) Enables you to test the notification configuration for the recipient. Select this check box to activate the option.
Country/region name and code Pager Pin
Advanced
563
Click Advanced to configure the following advanced pager setup options in the Advanced Pager Information dialog box:
Password Message Length Type the password for the pager, if one is required. Type the maximum number of characters you want to use for messages. The number is determined by the paging service provider. Type the number of times you want the paging service provider to retry the page. The number is determined by the paging service provider.
Retrys
Pager type Numeric Alpha-numeric Modem Baud Rate Select this option if you are configuring a pager that accepts only numbers. Select this option if you are configuring a pager that accepts letters and numbers. 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.
Click OK to save the settings in the Advanced Pager Information dialog box, and then click OK to save the pager configuration settings.
564
Configuring a net send recipient

You can configure Net Send to send notification messages to a target computer or user. 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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4 5 Click New, click Net Send in the Recipient Type dialog box, and then click OK. Select the appropriate options as follows from the Net Send Recipient Properties dialog box:
Name Target Computer or User Name Type the recipient for whom you are configuring the notification. 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. If the target computer has Internet pop-up advertisement blocking software installed, the Net Send notification message will not display. All Computers Test Enable (Limit the number of notifications sent) Select the check box to send the notification to all the computers in the network. Enables you to test the notification configuration for the recipient. Select this check box to activate the option.
Notify me a maximum of x Type the total number of notifications you want sent to the times within x minutes 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.
565
Reset the notification limits after x minutes
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. Select this check box to activate the option and configure the length of time the recipient is available for notification. Enables you to select the days and times when notifications can be sent to the recipient. See Scheduling notification for recipients on page 569.
Click OK.
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4 5 Click New, click Printer in the Recipient Type dialog box, and then click OK. Click Printer, and then click OK.
566
Select the appropriate options as follows in the Printer Recipient Properties dialog box:
Name Target Printer Test Enable (Limit the number of notifications sent) Type the recipient for whom you are configuring the notification. You cannot use a fax printer device to receive the notification. Select the name of the printer to which the notification message will be sent. Enables you to test the notification configuration for the recipient. Select this check box to activate the option.
567
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4 5 Click New, click Group in the Recipient Type dialog box, and then 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. 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 570 Editing recipient notification properties on page 570 Assigning recipients to alert categories for notification on page 572
568
Scheduling notification for 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. 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 3 Click Schedule. Clear the Include work days check box to exclude Monday through Friday from 8 A.M. to 6 P.M. Clear the Include weeknights check box to exclude Monday through Friday from 6 P.M. to 8 A.M. Clear the Include weekends check box to exclude Saturday and Sunday, 24 hours a day. 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. After selecting the days and times you want, click OK.
5 6
569
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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. 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 2 3 On the navigation bar, click Alerts. Click the Active Alerts tab. 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.
570
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 553.
MAPI Configuration. See Configuring MAPI email for notification on page 555. VIM Configuration. See Configuring VIM email for notification on page 556. Pager Configuration. Click Enable to activate or clear the notification method, and then select a modem from the Configured Modems list.
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 2 3 4 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Configure recipients. Select the recipient you want to delete, and then click Remove.
571
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 2 3 4 On the navigation bar, click Alerts. Click the Active Alerts tab. Under Notification Tasks in the task pane, click Assign recipients to alert categories. Under Alert Categories, select the alert category to which you want to assign recipients. 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. 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 550 Configuring SMTP for email or mobile phone text message notification on page 553 Configuring recipients on page 557
572
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 jobs 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 3
Select the recipients you want to assign to the job or selection list. If the recipient is using an email or printer notification method, click Include job log with a notification to an email or printer recipient. You can continue selecting other options from the Properties pane.
To configure new recipients or edit recipient properties 1 2 Repeat step 1 on page 573. 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.
Enter or edit recipient properties for the following types of recipients:
Person
SMTP Mail.
573
See Configuring SMTP email or mobile phone text messaging for a person recipient on page 558
MAPI Mail. See Configuring MAPI mail for a person recipient on page 560 VIM Mail. See Configuring VIM mail for a person recipient on page 561 Pager. See Configuring a pager for a person recipient on page 562
Net Send. See Select the appropriate options as follows from the Net Send Recipient Properties dialog box: on page 565
Printer. See Select the appropriate options as follows in the Printer Recipient Properties dialog box: on page 567
Group. Perform the following:
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.
4 5
Click OK. You can edit recipient properties or select other options from the Properties pane.
574
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:
Table 15-5 Trap Type Product Start SNMP Traps Object ID 1302.3.1.1.9.1 String 1 Backup Exec: Application initializing Backup Exec: Application terminating Backup Exec: Job canceled by Operator Backup Exec: Job failed String 2 String 3 String 4
machine name product, version, revision machine name product, version, revision machine name job name local or remote Operator name detail message detail message
Product Stop
1302.3.1.1.9.2
Job Canceled
1302.3.1.2.8.2
Job Failed
1302.3.1.2.8.1
machine name job name
Storage device 1302.3.2.5.3.3 requires human intervention Robotic library requires human intervention 1302.3.2.4.3.3
Backup Exec: machine name job name Storage device requires attention Backup Exec: machine name job name robotic library device requires attention
detail message
575
About SNMP notification Table 15-5 Trap Type Intelligent Disaster Recovery Message Intelligent Disaster Recovery Message Backup Exec system error SNMP Traps Object ID String 1 String 2 String 3 String 4 detail message
1302.3.1.4.2.1. Copy to machine name job name 1 alternate path failed 1302.3.1.4.2.1. Backup 2 complete, update DR disks 1302.3.1.1.9.3 The application has encountered an error Information on normal events The job succeeded machine name job name
detail message
detail message
Backup Exec general information Job Success Job Success with exceptions Job Started
1302.3.1.1.9.4
detail message
1302.3.1.2.8.3 1302.3.1.2.8.4
detail message detail message
The job machine name job name succeeded, but there was a problem The job has started machine name job name
1302.3.1.2.8.5
Job Completed 1302.3.1.2.8.6 with no data
The job machine name job name succeeded, but there was no data The job has a warning machine name job name
Job Warning PVL Device Error
1302.3.1.2.8.7
1302.3.1.5.1.1. The device has machine name job name 1 encountered an error
576
About SNMP notification Table 15-5 Trap Type PVL Device Warning PVL Device Information PVL Device Intervention PVL Media Error PVL Media Warning SNMP Traps Object ID String 1 String 2 String 3 String 4 detail message
1302.3.1.5.1.1. The device has machine name job name 2 encountered a warning 1302.3.1.5.1.1. Normal device machine name job name 3 information 1302.3.1.5.1.1. Device 4 requires attention 1302.3.1.5.2.1. There is an 1 error with the media 1302.3.1.5.2.1. There may be 2 a problem with the media machine name job name
detail message
detail message
PVL Media Information PVL Media Intervention Catalog Error
1302.3.1.5.2.1. Normal media machine name job name 3 information 1302.3.1.5.2.1. Media 4 requires attention 1302.3.1.5.3.1. There is an 1 error with the catalog 1302.3.1.5.4.1. There is a 1 TapeAlert error 1302.3.1.5.4.1. There is a 2 TapeAlert warning 1302.3.1.5.4.1. Normal 3 TapeAlert information machine name job name
detail message
Tape Alert Error Tape Alert Warning Tape Alert Information
detail message
detail message
detail message
577
About SNMP notification Table 15-5 Trap Type Database Maintenance Error Database Maintenance Information Software Update Error Software Update Warning Software Update Information SNMP Traps Object ID String 1 String 2 String 3 String 4 detail message
1302.3.2.5.5.1. There is a 1 database maintenance error 1302.3.2.5.5.1. Normal 2 database maintenance information 1302.3.2.5.6.1. There is a 1 software update error 1302.3.2.5.6.1. There is a 2 software update warning 1302.3.2.5.6.1. Normal 3 software update information
detail message
detail message
detail message
detail message
Install Update 1302.3.2.5.7.1. There is an Warning 1 install warning
detail message
Install Update 1302.3.2.5.7.1. Normal Install machine name job name Information 2 information
detail message
Related Topics: Installing and configuring the SNMP system service on page 579
578
Installing and configuring the SNMP system service

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. Click Add/Remove Windows Components. 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 5 Select Simple Network Management Protocol, and then click OK. 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 550
2 3
579
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 2 Insert the Backup Exec Installation CD. At the command prompt, type the following: mofcomp <CD Drive Letter>:\winnt\wmi\backupexecperfmon.mof To install the WMI SNMP provider 1 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. 2 3 Insert the Backup Exec Installation CD. At the command prompt, type the following: mofcomp <CD Drive Letter>:\winnt\wmi\snmp\eng\bkupexecmib.mof To use the WMI SNMP provider you must set up SNMP notification.
Uninstalling WMI providers

You must uninstall the WMI performance counter provider and the WMI SNMP provider separately. To uninstall the WMI performance counter provider
At the command line, type: mofcomp <CD Drive Letter>:\winnt\wmi\deletebackupexecperfmon.mof
To uninstall the WMI SNMP provider
At the command line, type: Smi2smir /d Backup_Exec_MIB
580
581
582
Chapter
16
Reports in Backup Exec
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 following:
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 584 Running and viewing a new report job on page 587 Scheduling report jobs and setting notification recipients on page 591 Available reports on page 613
583
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 2 3 On the navigation bar, click Reports. In the Reports pane, click All Reports. 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 587 Scheduling report jobs and setting notification recipients on page 591 Available reports on page 613
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 2 On the navigation bar, click Reports. On the Reports pane, select the report you want to run.
584
Running a report
3 4
In the task pane, under Report Tasks, click Run report now. 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 Media server Filters the report based on media set names. Media sets include all the media that is inserted into the storage device. 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. Filters the report based on job status. Filters the report based on specific protected server names. The protected server is the server that is being backed up. Filters the report based on specific vault names. A media vault is a virtual representation of the actual physical location of media. See Media locations and vaults on page 199.
Job status Protected server Vault
Chapter 16, Reports in Backup Exec
585
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 the following:
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. 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.
Click Run Now. The report appears and displays data based on the criteria you set when you ran the report.
To save the report, click Save As. 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.
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.
586
Running and viewing a new report job
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. 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.
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 591 Available reports on page 613

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. To run a new report job 1 2 3 4 On the navigation bar, click Reports. On the Reports pane, select the report for which you want to run a job. Under Report Tasks in the task pane, click New report job. 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.
587
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 Media server Filters the report based on media set names. Media sets include all the media that is inserted into the storage device. 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. Filters the report based on job status. Filters the report based on specific protected server names. The protected server is the server that is being backed up. Filters the report based on specific vault names. A media vault is a virtual representation of the actual physical location of media. See Media locations and vaults on page 199.
Job status Protected server Vault
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 Number of days before day report runs Number of days after day report runs Hours Select this check box to enable the date filter. 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. Select this check box to enable the hours filter.
Number of hours within Type the number of hours either before or after the present hour to time report 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.
588
Event count Maximum number of events to include
Select this check box to enable the event count filter. 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. 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.
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 jobs hold status.
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 2 3 4 On the navigation bar, click Job Monitor. Click the Job List tab. On the Job History pane, select the report you want to view. Under General Tasks in the task pane, click Properties.
589
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 click Report to view the contents of the report. 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.
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 2 3 4 5 On the navigation bar, click Job Monitor. Click the Job List tab. On the Job History pane, right-click the report you want to save. Click Properties. 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 2 3 4 5 On the navigation bar, click Job Monitor. Click the Job List tab. On the Job History pane, select the report you want to delete. Under General Tasks in the task pane, click Delete. Confirm the job deletion. The report and associated job history are deleted. Related Topics: Configuring database maintenance on page 162 Viewing and changing completed jobs on page 465 Available reports on page 613
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. See Running and viewing a new report job on page 587. See Scheduling jobs on page 286. 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.
591
About custom 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 doing the following:

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 the following:

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:
Table 16-1 Filter type Field name Operator Value Filter expression for finding alerts for errors Data Alert type = (Equal) Error
If you want the report to include only alerts for errors that occurred on a specific day, add another filter expression for the date.
592
Creating a custom report
The following filter expression finds alerts on a specific day:

Table 16-2 Filter type Field name Operator Value Filter expression for finding alerts on a specific day Data Date entered =(Equal) 02/03/06
Related Topics: Setting filters for custom reports on page 595 Grouping fields in custom reports on page 600 Sorting fields in custom reports on page 601 Setting graph options in custom reports on page 602

You can create reports that contain information to meet the specific requirements of your organization To create a custom report 1 2 3 4 On the navigation bar, click Reports. On the task pane, click New custom report. On the Custom Report dialog box, type a name and description for the report. 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. On the properties pane, under Report Definition, click Field Selection. 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.
5 6
593
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. Includes fields for information such as the job priority, the job name, the due date, and the policy name. Includes fields for information such as the backup rate, the device used, errors, and 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. Includes fields for information such as the job priority, the policy name and description, the selection list name, and the due date.
Job Job History Media
Policy
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.
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.
To adjust the width of the column for a field, do the following in the order listed:

Click the field name in the Fields selected for the report list. In the Column width box, type the new width. Click Set.
594
10 Do any of the following:

To set filter criteria for the report Do the following in the order listed:

On the properties pane, under Report Definition, click Filters. Complete the appropriate filter options. See Setting filters for custom reports on page 595.
To group fields for the report
On the properties pane, under Report Definition, click Grouping. Complete the appropriate grouping options. See Grouping fields in custom reports on page 600.
To sort fields for the report

On the properties pane, under Report Definition, click Sorting. Complete the appropriate sorting options. See Sorting fields in custom reports on page 601.
To set graph options for the report
On the properties pane, under Report Definition, click Graph Options. Complete the appropriate graphing options. See Setting graph options in custom reports on page 602.
To preview and test the report

On the properties pane, under Preview, click Preview. To test the report, on the Preview dialog box, click Test Report
To finish and close the report
Click OK.
Setting filters for custom reports

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 Operator Chapter 16, Reports in Backup Exec Media Server = (Equal) 595
Value
Test Server
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 2 3 4 5 6 On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report that you want to filter. On the task pane, click Edit. On the properties pane, under Report Definition, click Filters. 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. Select the field on which you want to filter.
Field name
596
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. > (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. <= (Less Than or Equal). The field name must be smaller or equal to the value. $ (Contains). The field name contains the text entered in the Value field. NOT$ (Contains). The field name does not contain the text entered in the Value field. IN LAST. A date or time window that is relative to the time that you create the report. This operator defines dates and times prior to the time when the report is created. This operator is available only for date and time fields. If you enter hours in the Value field you receive more specific results than if you enter days. The Day value is calculated beginning at midnight (00:00) yesterday and ending at the time when the report runs. For example, if you enter 1 day in the Value field and the report runs at 23:59 today, the report includes results for the last 47 hours and 59 minutes. However, if you enter 24 hours, you receive information for exactly 24 hours prior to the time when the report runs.
IN NEXT. A date or time window that is relative to the time that you create the report. This operator defines dates and times after the time when the report is created. For example, to find backup jobs that are scheduled to occur during the next three days, select this operator, and then enter 3 days in the Value field. This is available only for date and time fields.
Value
Type or select the value on which you want to filter. The type of value that you can enter varies depending on the type of field name that you select. For example, if you select Next Due Date in the Field name, Backup Exec displays date and time values.
Click Add.
597
8 9
Repeat step 6 and step 7 to add more filters. To combine sets of filter expressions, do any of the following:
To combine two filter Click AND. expressions so that both For example, to find all backup jobs that failed, add the following expressions must be true expressions: for the result to be true Status = Failed
Type = Backup Click AND to combine the two expressions.
After you set up the expressions, do the following:
The combined expression is: Status = Failed AND Type = Backup To combine two filter Click OR. expressions so that one of For example, to find jobs that either failed or were canceled, add the expressions must be the following expressions: true for the result to be Status = Failed true 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 To combine two filter expressions into a single expression Click ( ) + For example, to find backup jobs and restore jobs that failed, add the following expressions:

Status = Failed Type = Backup Type = Restore 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).
After you set up the expressions, do the following:

The combined expression is: Status = Failed AND (Type = Backup OR Type = Restore)
598
To separate two filter expressions that were combined into a single expression
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.
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 expressions 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 Do the following in the order listed:
On the properties pane, under Report Definition, click Grouping. Complete the appropriate grouping options. See Grouping fields in custom reports on page 600.
To sort fields for the report

599

On the properties pane, under Preview, click Preview. To test the report, on the Preview dialog box, click Test Report.
Click OK.
Grouping fields in custom reports

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 servers 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 2 3 4 5 6 7 On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report that contains the fields you want to group. In the task pane, click Edit. On the properties pane, under Report Definition, click Grouping. In the Group by box, select the name of the field on which you want to group data. Click Ascending to group the information in ascending order or click Descending to group the information in descending order.
600
If you want to group on additional fields, in the Then group by box, repeat step 6 and step 7. Do any of the following:
To sort fields for the report Do the following in the order listed:


Click OK.
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 2 3 4 On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report that contains the fields you want to sort. In the task pane, click Edit.
601
5 6
On the properties pane, under Report Definition, click Sorting. In the Sort on list, select the name of the field on which you want to sort information. Click Ascending to sort the information in ascending order or click Descending to sort the information in descending order. If you want to sort on additional fields, in the Then sort on box repeat step 6 and step 7. Do any of the following:
To set graph options for the report Do the following in the order listed:

Click OK.
Setting graph options in custom reports

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 2 3 4 5
602
On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report for which you want to set graph options. In the task pane, click Edit. On the properties pane, under Report Definition, click Graph Options.
In the Graph type box, select the type of graph that you want to create, either Pie or Bar. In the Graph title box, type the title that you want to display above the graph in the report. Complete the following options for a pie graph:
Category field (pie section Select the field for which you want to display sections in the pie per value) chart. Data field Aggregation function Select the field for which you want to calculate values. Select the way that you want Backup Exec to calculate the values generated for the Data field. Your choices are as follows:
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.
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) 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. Category field (set of series bars per value) Data field Horizontal axis title Select the field that contains the information for which you want to group information along the left side of the graph. Select the field for which you want to calculate values. Type the title that you want to display below the graph.
603
Aggregation function
Select one of the following functions to calculate the values generated for the Data field. Your choices are as follows:

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.
10 Do any of the following:

To preview and test the report Do the following in the order listed:

Click OK.
Example graphs
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.
604
Creating a custom report Example pie graph
The example pie graph, titled Frequency of Alert Types, was created using the following:
Table 16-3 Example pie graph options Fields selected Pie Frequency of Alert Types Event name Event name Count
Graph option name Graph Type Graph title Category field Data field Aggregation function
605
Creating a custom report Example bar graph 1
The example bar graph, titled Average Duration of Job per Device per Selection List, was created using the following:
Table 16-4 Example bar graph 1 options Fields selected Bar Average duration of job per device per selection list Selection list Device name Selection list name Job duration Average Average duration of a job (seconds) Administrators Guide
Graph option name Graph Type Graph title Vertical axis title Series field Category field Data field Aggregation function Horizontal axis title 606
Creating a custom report Example bar graph 2
The example bar graph, titled Total Storage Per Device, was created using the following:
Table 16-5 Example bar graph 2 options Fields selected Bar Total Storage Per Device Resource Device name Resource name Total data size Sum Total Data Stored (MB)
Graph option name Graph Type Graph title Vertical axis title Series field Category field Data field Aggregation function Horizontal axis title
607
Copying custom reports
Previewing custom reports

Use the preview feature to verify that you created a custom report correctly. To preview custom reports 1 2 3 4 5 6 On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report that you want to preview and test. In the task pane, click Edit. On the properties pane, under Preview, click Preview. Click OK.
Copying custom reports

You can create a copy of a custom report, and then modify the copy. To copy custom reports 1 2 3 4 5 6 On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report that you want to copy. In the task pane, click Copy. In the Name of copy box, type a unique name for the copied report. Click OK.
608
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 2 3 4 5 6 On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report that you want to filter. In the task pane, click Edit. Change the report settings as needed. 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 2 On the navigation bar, click Job Monitor. 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 2 3 On the navigation bar, click Reports. In the tree view, click Custom Reports. In the reports list, click the report that you want to filter.
609
Setting default options for reports
4 5
In the task pane, click Delete. Click Yes.
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 do the following:

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 2 3 On the Tools menu, click Options. On the Properties pane, under Settings, click Reports. Complete the following options:
HTML PDF Select this option if you want all reports to display in HTML format. This is the default setting. Select this option if you want all reports to display in Adobe Portable Document Format (PDF).
Use company logo image Check Use company logo image file if you want to use your file companys logo in the header of all custom reports. Image file path Red Green 610 If you checked Use company logo image file, type the path to the logo that you want to use in all custom reports. Type the number that corresponds to the value for red. Type the number that corresponds to the value for green. Administrators Guide
Viewing report properties
Blue Colors Text Include time
Type the number that corresponds to the value for blue. Click Colors to select a basic color or to create a custom color for the banner on custom reports. Type the text that you want to display in the footer of custom reports. Check Include time if you want the footer of custom reports to include the time when the report runs.
Click OK.

Report properties provide detailed information about each report. The properties can be viewed, but not edited. To view report properties 1 2 3 On the navigation bar, click Reports. On the Reports pane, select the report for which you want to view properties. In the task pane, under Report tasks, click Properties. The Report dialog box provides the following information:
Title Description Category The name of the report. Describes the type of data that is included in the report. Classification for the report. Available report categories include the following:

Media Media Vault Jobs Devices Configuration Alerts Template
Author
The creator of the report.
611
Subject File name File size Creation Date
The version of the product for which the report was created. The location of the report. The size of the report. The date the report was installed on the system.
Click OK after you have finished viewing the properties.
Related Topics: Running a report on page 584
612
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:
Table 16-6 Report Name Active Alerts Backup Exec Reports Description Lists all active alerts chronologically, displaying the most recent alerts first. See Active Alerts Report on page 618. 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 618. Alert History Lists all alerts in the alert history chronologically, displaying the most recent alerts first See Alert History Report on page 619. 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 620. Application Event Log Audit Log Lists all Backup Exec application event logs (see Application Event Log Report on page 621). Lists the contents of the audit logs for selected servers for the specified time period. See Audit Log Report on page 621. Backup Job Success Rate Lists the success rate for backup jobs run to protect selected servers. See Backup Job Success Rate Report on page 622. Backup Resource Success Rate 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 623. Backup Set Details by Resource 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 623.
613
Available reports Table 16-6 Report Name Backup Sets by Media Set Backup Exec Reports (continued) Description Lists all backup sets by media set. See Backup Sets by Media Set Report on page 624. 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 625. Configuration Settings Lists the contents of the Backup Exec system configuration parameters table. See Configuration Settings Report on page 626. Current Job Status Details the job queue sorted by status. See Current Job Status Report on page 627. Daily Device Utilization Lists the percentage of the storage devices capacity that the media server uses. See Daily Device Utilization Report on page 628. Device Summary Lists device usage and error summary for each selected media server. See Device Summary Report on page 628. Device Usage by Policy Lists all the policies that are targeted to specific drive selections. See Device Usage by Policy on page 629. Error-Handling Rules Lists all the defined error-handling rules. See Error-Handling Rules Report on page 630. Event Recipients Lists all events registered by each notification recipient. See Event Recipients Report on page 632. Failed Backup Jobs Lists all the failed backup jobs sorted by the resource server and time frame. See Failed Backup Jobs Report on page 632. 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 633.
614
Available reports Table 16-6 Report Name Jobs Summary Backup Exec Reports (continued) Description Lists all the jobs that ran within the last 72 hours in chronological order. See Jobs Summary Report on page 634. Machines Backed Up Lists all the servers that have been protected by Backup Exec. See Machines Backed Up Report on page 634. Managed Media Servers Lists the status and configuration for all media servers managed by Backup Exec. See Managed Media Servers Report on page 635. Media Audit Lists the recent media configuration changes. See Media Audit Report on page 637. Media Errors
Lists the number of errors that occur on all media.

See Media Errors Report on page 637.
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 638.
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 638.
Media Vault Contents
Lists the media located in each media vault. See Media Vault Contents Report on page 639.
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 640. 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 medias append period has expired. See Move Media to Vault Report on page 641. Operations Overview Lists past and future operations data for user-set period. See Operations Overview Report on page 642.
615
Available reports Table 16-6 Report Name Overnight Summary Backup Exec Reports (continued) Description 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 643. 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 644. 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 645. Policy Properties Lists all policies and policy job templates that are defined for the server. See Policy Properties Report on page 647. 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 647. Problem Files Lists all the problem files reported for jobs. The files are grouped by day and resource. See Problem Files Report on page 648. Recently Written Media Lists all media that have been modified in the last 24 hours. See Recently Written Media Report on page 649. Resource Backup Policy Performance Resource Risk Assessment Lists the success rate for policy derived backup jobs. See Resource Backup Policy Performance Report on page 649. 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 650. Resources Protected by Policy Lists the policies, templates, and selection lists being used to protect a resource. See Resources Protected by Policy report on page 651.
616
Available reports Table 16-6 Report Name Restore Set Details by Resource Backup Exec Reports (continued) Description 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 651. Retrieve Media from Vault Lists all reusable media currently in the specified vault. See Retrieve Media from Vault Report on page 652. 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 653. Scheduled Server Workload Lists the estimated scheduled workload for the next 24-hour period by server. See Scheduled Server Workload on page 654. 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 654. Selection Lists Lists a description, policy name, and job name for protected and unprotected selection lists. See Selection Lists Report on page 655. 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 656.
Related Topics: Running a report on page 584 Running and viewing a new report job on page 587
617
Available reports
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.
Table 16-7 Item Time Media Server Job Name Device Name Category Message Active Alerts Report Description Date and time the alert occurred. Name of the media server on which the alert occurred. Name of the job associated with the alert. Name of the device on which the job ran. Title of the alert, such as Service Start or Job Failed. Describes the event that caused the alert.
Active Alerts by Media Server Report

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.
Table 16-8 Item Time Job Name Device Name 618 Active Alerts by Media Server Report Description Date and time the alert occurred. Name of the job associated with the alert. Name of the device on which the job ran. Administrators Guide
Available reports Table 16-8 Item Category Message Active Alerts by Media Server Report (continued) Description Title of the alert, such as Service Start or Job Failed. Describes the event that caused the alert.
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.
Table 16-9 Item Received Responded Responding User Job Name Media Server Category Message Alert History Report Description Date and time the alert occurred. Date and time the user responded to the alert. User that responded to the alert. The name of the job associated with the alert. Name of the media server on which the alert occurred. Title of the alert, such as Service Start or Job Failed. Describes the event that caused the alert.
619
Available reports
Alert History by Media Server Report

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 option. Information displayed in the Alert History by Media Server report is described in the following table.
Table 16-10 Item Media Server Time Received Responded Responding User Job Name Category Message Alert History by Media Server Report Description Name of the media server on which the alert occurred. Date and time the alert occurred. Time the alert occurred. Time the user responded to the alert. User that responded to the alert. Name of the job associated with the alert. Title of the alert, such as Service Start or Job Failed. Describes the event that caused the alert.
620
Available reports
Application Event Log Report

The Application Event Log report lists all Backup Exec application event logs. Information displayed in the Application Event Log report is described in the following table.
Application Event Log Report Item Number Event Date/Time Source Description Description Number assigned to the event in the Windows Event log. Type of event that occurred. Date and time the event occurred. Source from which the event originated. Message displayed for the event.
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.
Table 16-11 Item Media Server Category Date Entered Audit Log Report Description Name of the media server on which the audit logs are located. Category in which the change occurred, such as Logon Account, Alerts, or Job. Time and date the change occurred.
621
Available reports Table 16-11 Item Message User Name Audit Log Report (continued) Description Description of the change made in Backup Exec. User that made the change.
Backup Job Success Rate Report

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.
Table 16-12 Item Server Date Total Jobs Successful Success Rate Backup Success Rate Report Description Name of the server being protected. Date the backup job was processed. Total number of jobs processed by the media server. Total number of jobs successfully performed by the media server. Percentage of successful jobs processed by the media server.
622
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.
Table 16-13 Item Resource Date Backup Sets Successful Success Rate Backup Resource Success Rate Report Description Name of the system being protected. Date the backup job was processed. Total number of backup sets processed by the media server. Total number of jobs successfully performed by the media server. Percentage of successful jobs processed by the media server.
Backup Set Details by Resource Report

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.
Table 16-14 Item Resource Start Time Duration Backup Set Details by Resource Report Description Name of the system being protected. Date and time the operation started. Length of time the operation took to process.
623
Available reports Table 16-14 Item Size (MB) Files Directories MB/Minute Skipped Corrupt FIles Files in Use Status Backup Set Details by Resource Report (continued) Description Number of megabytes processed. Number of files processed. Number of directories processed. Number of megabytes processed per minute. Number of files skipped during the operation. Number of corrupt files encountered during the operation. Number of files in use during the operation. Status of the operation, such as Completed.
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.
Table 16-15 Item Media Set Media Label Set Method Backup Sets by Media Sets Report Description Name of the media set on which the job ran. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Sequential number for backup sets on the media. Specific type of backup. See Choosing a backup strategy on page 222.
624
Available reports Table 16-15 Item Date / Time Backup Sets by Media Sets Report (continued) Description Date and time the data was backed up.
Backup Set Description / Describes the data that was backed up and the location of the data. Source Directories Files MB Number of directories backed up. Number of files backed up. Amount of data backed up in megabytes.
Backup Size By Resource Report

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. See Creating a new policy on page 424. See Creating jobs using policies on page 440. 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.
Table 16-16 Item Server Resource Job Backup Size by Resource Job Report Description Name of the media server where the data for the backup job was located. Name of the resource backed up. Name of the backup job.
625
Available reports Table 16-16 Item Job Date and Time Run Backup Size, MB Trailing Avg, MB Difference % Backup Size by Resource Job Report (continued) Description Date and time the backup job was processed. Amount of data backed up in megabytes. Average amount of data backed up during the seven previous runs. Amount by which the data backed up in the current job differs from the previous backup jobs.
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.
Table 16-17 Item Parameter Name Class Value Configuration Settings Report Description Name of the Backup Exec configuration parameter. Parameters that are associated with the Backup Exec system. Value of the configuration parameter. Note The StoreMaintenanceLastrun and StoreMaintenanceRuntime parameters display the date and time in Greenwich Mean Time (GMT).
626
Available reports
Current Job Status Report

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.
Table 16-18 Item Job Status Job Next Due Date Original Due Date Priority Job Queue Status Report Description Displays the job status. Name of the job. Next date and time the job is scheduled to run. Original date and time the job was scheduled to run. 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 the following:

Highest High Medium Lowest Low
On Hold Type
Displays an X if the job is on hold; otherwise, displays a dash (-). Type of job that was run, such as Backup or Restore.
627
Available reports
Daily 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.
Table 16-19 Item Drive Name Date Jobs Size (MB) Utilization (%) Daily Network Device Utilization Report Description Name of the storage device and the media server where the device is located. Date the storage device was used. Number of jobs processed by the media servers storage device. Number of megabytes processed by the media servers storage device. Percentage of device utilization.
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.
Table 16-20 Item Server Device Name Drive Name Device Summary Report Description Name of the server where the device is located. Name of the device, such as the name of the robotic library. This field is left blank for stand-alone drives. Name of the drive in the robotic library.
628
Available reports Table 16-20 Item Vendor/Product ID SCSI Target State Created Cleaned Hours Errors MB Mounts Hours Errors MB Mounts Device Summary Report (continued) Description Name of the vendor of the drive, the product ID, and firmware from the SCSI Inquiry string. Address of the SCSI Card, SCSI Bus, Target Device ID, and LUN. Device state, such as online. Date media was created. Date last cleaning job was run on the drive. Hours the device has been in use since the last cleaning job. Number of errors occurring since the last cleaning job. Megabytes read and written since the last cleaning job. Number of mounts occurring since the last cleaning job. Total number of hours the device has been in use. Total number of errors occurring on the device. Total number of megabytes read and written to the device. Total number of mounts occurring to the device.
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.
629
Available reports
Information displayed in the Device Usage by Policy report is described in the following table.
Table 16-21 Item Drive Name Method Device Usage by Policy Report Description Name of the storage device and the media server where the device is located. Specific type of backup. See Understanding backup methods and their advantages on page 224. Policy Name Template Name Name of the policy. Name of the job template.
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.
Table 16-22 Item Rule Name Notes Job Status Error Handling Rules Report Description Name of the Error-Handling rule. Information entered in the Notes section when the error-handling rule was created. Final job status that activates the rule. Possible statuses are as follows:

Error Canceled
630
Available reports Table 16-22 Item Error Category Error Handling Rules Report (continued) Description Category of error for which the rule will be applied. Available error categories include the following:

Device Job Media Network Other Resource Security Server System
Enabled Cancel Job
Displays if the rule is enabled or disabled. 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. 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. Displays an X if this option is selected for the error-handling rule. The option enables Backup Exec to retry the job. Number of times the job is to be retried. Number of minutes the job is to wait before being retried.
Pause Job
Retry Job Maximum Retries Retry Interval (minutes)
631
Available reports
Event Recipients Report

The Event Recipient report lists events registered by each notification recipient. Information displayed in the Event Recipient report is described in the following table.
Table 16-23 Item Recipient Type Recipient Name Event Type Event Name Event Recipient Report Description Type of recipient, such as Person, Net Send, Printer, or Group. Name of the recipient. Alert category or ad hoc job. Detail for the alert category or ad hoc job.
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:
Table 16-24 Item Resource Start Time Duration Job Name Category Failed Jobs Report Description Name of the system being protected. Date and time the backup job started. Length of time the operation took to process. Name of job that failed. Category for the failed job that may be generated by a system, job, media, or device error.
632
Available reports Table 16-24 Item Error Code Description Status Device Name Failed Jobs Report (continued) Description Displays the error code that corresponds to the failure. Describes the event that caused the error. Status of the operation, such as Completed. Name of the device on which the job ran.
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 devices 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.
Table 16-25 Item Device Job Date and Time Run Job Job Distribution by Device Report Description Name of the device on which the job ran. Date and time the job was processed. Name of the job that ran on the device.
633
Available reports
Jobs Summary Report

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.
Table 16-26 Item Start Time Job Name Duration Size (MB) Files Directories MB/Minute Skipped Corrupt FIles Files in Use Status Type Jobs Summary Report Description Date and time the operation started. Name of the completed job. Length of time the operation took to process. Number of megabytes processed. Number of files processed. Number of directories processed. Number of megabytes processed per minute. Number of files skipped during the operation. Number of corrupt files encountered during the operation. Number of files in use during the operation. Status of the operation, such as Completed. Specific type of backup. See Understanding backup methods and their advantages on page 224.
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.
Available reports
Information displayed in the Machines Backed Up report is described in the following table.
Table 16-27 Item Server Total Backup Count Last Backup Machines Backed Up Report Description Name of the server that was backed up. Total number of backups performed. Date of the last backup job for this server.
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.
Table 16-28 Item Managed Media Server Status Managed Media Server Report Description Name of the managed media server. Status of the server. Possible status includes the following:

Online - available for use. Stalled - not responding immediately to messages No Comm - communications to the server have been lost for some period of time.
Stalled No Comm
Time limit used for determining Stalled communications status. Time limit used for determining No Comm communications status.
635
Available reports Table 16-28 Item Catalog Location Managed Media Server Report (continued) Description Location where server keeps catalog information. Possible locations are as follows:

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 as follows:

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 as follows:

Status
When status is uploaded from the managed server to the CASO database. Possible upload times are as follows:

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). Maximum time difference tolerance in seconds set for server.
Sec
Available reports
Media Audit Report

The Media Audit report lists the recent configuration changes that you made to your media. You can use filter parameters for the Media Server option to limit the amount of data that appears in the report. You can also enter range parameters for the Days or Event count options. Information displayed in the Media Audit report is described in the following table.
Table 16-29 Item Date Entered Message User Name Media Audit Report Description Time and date the change occurred. Description of the change that was made to the media. User that made the change.
Media Errors Report

The Media Errors report lists the number of errors that occur on all media. You can use filter parameters for the Media Set option to limit the amount of data that appears in the report. You can also enter range parameters for the Event count options. Information displayed in the Media Audit report is described in the following table.
Table 16-30 Item Media Label Total Mounts Total In Use Hours Total Errors Media Errors Report Description Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Total number of times this media has been mounted. Total number of hours that this media has been in use. Total number of system, job, media, and device error alerts.
637
Available reports
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.
Table 16-31 Item Resource Type Media Required for Recovery Report Description Name of the system that was backed up. Specific type of backup. See Understanding backup methods and their advantages on page 224. Date Media Label Date and time the backup job set was created. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label.
Media Set Report

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.
638
Available reports
Information displayed in the Media Set report is described in the following table.
Table 16-32 Item Media Set Media Label Media Type Allocated Modified Location Hours Mounts Soft Errors Hard Errors Write MB Current MB Media Set Report Description Name of the media set. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Type of media cartridge, such as 4mm. Date media was allocated to a media set as a result of an overwrite operation. Date data was last written to the media. Location of the media. Total number of hours that this media has been in use. Total number of times this media has been mounted. Number of recoverable read errors encountered. Number of unrecoverable read errors encountered. Number of bytes that have been written to this media. Estimate of the number of megabytes currently on this media.
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.
639
Available reports
Information displayed in the Media Vault Contents report is described in the following table.
Table 16-33 Item Vault Name Media Label Media Vault Contents Report Description Location of the media. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label.
Overwrite Protection End Date that data on the media may be overwritten. Date Vault Media Rule Move Date Media Set Vault Media Rule Name Date media can be moved to vault. Name of media set to which the media belongs. Name of vault media rule.
Missed Availability Report

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.
Table 16-34 Item Date Attempted Start Time Job Name Selection List 640 Missed Availability Report Description Date and time the job was created. Time Backup Exec attempted to start the job. Name of the job. Name of the selection list for the job. Administrators Guide
Available reports Table 16-34 Item Begin Time End Time Missed Availability Report (continued) Description Date and time for beginning of availability window. Date and time for end of availability window.
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.
Table 16-35 Item Media Server Media Set Media Label Location Append Period End Date Move Media to Vault Report Description Name of the media server where the data for the backup job was located. Name of the media set. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Location of the media. Last date that data may be added to the media.
641
Available reports Table 16-35 Item Move Media to Vault Report (continued) Description
Overwrite Protection End Date that data on the media may be overwritten. Date Vault Media Rule Move Date Vault Name Vault Media Rule Name Date media can be moved to vault. Name of vault to which media is to be moved. Name of vault media rule.
Operations Overview Report

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.
Table 16-36 Item Job summary for jobs completed in the past x Hours Completed (Canceled) Completed (Failed) Completed (Success) Exceptions Media Total Total Size (MB) 642 Operations Overview Description Details Backup Exec job activity for the specified time period.
Total number of canceled jobs. Total number of jobs that failed. Total number of jobs that completed successfully. Total number of jobs that completed successfully, but may contain one or more skipped files, corrupt files, virus infected files or files in use. Total number of media used to back up the completed jobs. Total amount of data backed up. Administrators Guide
Available reports Table 16-36 Item Errors Warnings Information Attention Required Scratch Media Recyclable Allocated Imported Appendable Media Overwrite Protection Level Active Jobs Scheduled Scheduled (On hold) Job Status Operations Overview (continued) Description Total number of system, job, media, and device error alerts. Total number of job, media, and device warning alerts. Total number of system, job, media, and device information alerts. Total number of alerts that require a response from the user. Total number of scratch media available. Total number of recyclable media available. Number of allocated media (media belonging to a user media set). Number of imported media (media created by a product other than this installation of Backup Exec). Total number of appendable media available. Displays level of overwrite protection (Full, Partial, None) assigned to the media. Total number of active jobs. Total number of scheduled jobs. Total number of scheduled jobs on hold. Displays the job status.
Overnight Summary Report

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.
643
Available reports
Information displayed in the Overnight Summary report is described in the following table.
Table 16-37 Item Resource Type Overnight Summary Report Description System being protected. Specific type of backup. See Understanding backup methods and their advantages on page 224. Start time Status Error Category Media Server Device Name Total Tasks Uncorrected Exceptions Service Level Date and time the operation started. Status of the operation. Category for the job that may be generated by a system, job, media, or device error. Name of the media server on which the job ran. Name of the device on which the job ran. Total number of jobs run within the last 24 hours. Number of jobs that failed and were not run again with successful completion. Percentage of jobs that ran successfully.
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.
644
Available reports
Information displayed in the Policy Jobs by Resource Summary report is described in the following table.
Table 16-38 Item Policy Start Time Duration Size (MB) Files Directories MB/Minute Skipped Corrupt FIles Files in Use Status Policy Jobs by Resource Summary Report Description Name of the policy. Date and time the operation started. Length of time the operation took to process. Number of megabytes processed. Number of files processed. Number of directories processed. Number of megabytes processed per minute. Number of files skipped during the operation. Number of corrupt files encountered during the operation. Number of files in use during the operation. Status of the operation, such as Completed.
Policy Jobs Summary Report

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.
645
Available reports
Information displayed in the Policy Jobs Summary report is described in the following table.
Table 16-39 Item Policy Start Time Job Name Duration Size (MB) Files Directories MB/Minute Skipped Corrupt FIles Files in Use Status Type Policy Jobs Summary Report Description Name of the policy. Date and time the operation started. Name of the completed job. Length of time the operation took to process. Number of megabytes processed. Number of files processed. Number of directories processed. Number of megabytes processed per minute. Number of files skipped during the operation. Number of corrupt files encountered during the operation. Number of files in use during the operation. Status of the operation, such as Completed. Specific type of backup. See Understanding backup methods and their advantages on page 224.
646
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.
Table 16-40 Item Template Name Set Description Method Policy Definitions Report Description Name of the job template. Describes the data that was backed up and the location of the data. Specific type of backup. See Understanding backup methods and their advantages on page 224. Type Device Media Set Overwrite/Append Type of job that will run, such as Backup. Name of the device on which the job will run. Name of the media set on which the job will run. The media overwrite protection option configured for the backup job template properties.
Policy Protected Resources

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.
Table 16-41 Item Resource Chapter 16, Reports in Backup Exec Policy Protected Resources Report Description System being protected. 647
Available reports Table 16-41 Item Policy Job Name Next Due Date Policy Protected Resources Report (continued) Description Name of policy. Name of the job. Next date and time the job is scheduled to run.
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.
Table 16-42 Item Date Resource Time Reason File Name Type Media Server Problem Files Report Description Date the problem file was encountered. System on which the problem file is located. Time the problem file was encountered. Error code listed in the job log summary. Name of the problem file. Specific type of file that caused the problem. Name of the server on which the file is located.
648
Available reports
Recently Written Media Report

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.
Table 16-43 Item Media Label Location Set Date and Time Modified Recently Written Media Description Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Location of the media, such as the storage vault name or drive name. Name of backup set. Date and time media was last modified.
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.
Table 16-44 Item Policy Resource Date Backup Sets Resource Backup Policy Performance Description Name of policy. Name of system being protected. Date job completed. Total number of backup sets processed by the media server.
649
Available reports Table 16-44 Item Successful Success Rate Resource Backup Policy Performance Description Total number of jobs successfully performed by the media server. Percentage of successful jobs processed by the media server.
Resource Risk Assessment Report

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.
Table 16-45 Item Resource Error Text Start Time Job Error Category Media Server Device Name Resource Risk Assessment Report Description System on which the job ran. Describes the event that caused the job to fail. Time the operation started. Name of the job that failed. The category for the failed job that may be generated by a system, job, media, or device error. Name of the media server on which the job ran. Name of the device on which the job ran.
650
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:
Table 16-46 Item Policy Resource Template Name Selection List Job Next Due Date Resources Protected by Policy Report Description Name of the policy. The resource that is being protected. The name of the job template contained in the policy that is applied to the resource being protected. The list of resources selected for protection Name of the job. Next date and time that the job is scheduled to run.
Restore Set Details by Resource Report

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.
Table 16-47 Item Resource Start Time Duration Size (MB) Files Backup Set Details by Resource Report Description Name of the system being protected. Date and time the operation started. Length of time the operation took to process. Number of megabytes processed. Number of files processed.
651
Available reports Table 16-47 Item Directories MB/Minute Skipped Corrupt FIles Files in Use Status Backup Set Details by Resource Report (continued) Description Number of directories processed. Number of megabytes processed per minute. Number of files skipped during the operation. Number of corrupt files encountered during the operation. Number of files in use during the operation. Status of the operation, such as Completed.
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.
Table 16-48 Item Vault Name Media Label Retrieve Media from Vault Report Description Name of the vault where the media is located. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label.
Overwrite Protection End Date that data on the media may be overwritten. Date Move Date Media Set Vault Media Rule Name Date media can be moved to vault. Name of the media set. Name of vault media rule.
652
Available reports
Robotic Library Inventory Report

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.
Table 16-49 Item Server Device Name Slot Media Label State Modified Write MB Full Hours Mounts Append Robotic Library Inventory Report Description Name of the server where the robotic library is located. Name of the robotic library. Sequential number of the slot in the robotic library. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. State of operation of the slot: paused, disabled, enabled, offline, or online. Date the media in the slot was last accessed. Number of bytes that have been written to this media. Space available on a media; 1 indicates that media is full and 0 indicates that there is space available on the media. Total number of hours this media has been in use. Total number of times this media has been mounted. The time remaining in the medias append period.
Chapter 16, Reports in Backup Exec 653
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 use filter parameters for the Media Server option to limit the amount of data that appears in the report. You can also enter range parameters for the Hours option. Information displayed in the Scheduled Server Workload report is described in the following table.
Table 16-50 Item Media Server Job Next Due Date Backup Size, MB Total Size (MB) Total Size (MB) Scheduled Server Workload Report Description Name of the media server that will process the scheduled jobs. Name of the job scheduled to run. Time and day the next job is scheduled to run. Estimated amount of data in megabytes to be processed during the next 24 hours. Total amount of data to be processed on the server during the next 24 hours. Total amount of data to be processed on all media servers.
Scratch Media Availability Report

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.
654
Available reports
Information displayed in the Scratch Media Availability report is described in the following table.
Table 16-51 Item Category Media Label Size (GB) Scratch Media Availability Report Description The media set period configured in media set properties. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. 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 Media Total Total number and capacity of scratch media available to the system. Total number of scratch media available.
Selection Lists Report

The Selection Lists report lists information about protected and unprotected selection lists. Information displayed in the Resources Protected by Policy report is described in the following table.
Table 16-52 Item Selection List Name Selection List Description Policy Name Job Name Selection Lists Report Description Name of the selection list. Description of the protected selection list. Name of the policy. An unprotected selection list does not have a job associated with it. Name of the job. An unprotected selection list does not have a job associated with it.
655
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.
Table 16-53 Item Media Server Job Date and Time Run Job Name Media Type Device Name Max Needed Online Media Total Online Media Total Credential Check Backup Size, MB Test Run Results Description Name of the media server on which the job ran. Date and time the backup job was processed. Name of the test run job. Type of media used, such as 4mm. Name of the device, such as the name of the robotic library. Amount of space needed on the media to run the job. Capacity of media available in the device to which data can be appended. Total amount of appendable media available to the system. Capacity of media available in the device to which data can be written. Total amount of overwritable media available to the system. Indicates if the Backup Exec logon account was verified as correct for the resources being backed up. Size in megabytes of the backup.
Available reports
657
Available reports
658
Chapter
17
Disaster preparation and recovery

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. The following basic methods are available for disaster recovery:
Manual recovery. This section provides procedures for manually recovering both local and remote Windows computers. Automated recovery. Backup Execs Intelligent Disaster Recovery (IDR) option automates the disaster recovery process for Windows computers. IDR is an option you must purchase separately.
Related Topics: Getting started with IDR on page 1503 Returning to the last known good configuration on page 661 Manual disaster recovery of Windows computers on page 664
659
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, consider the following elements when creating a comprehensive DPP.
Table 17-1 Element Key elements of a DPP 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 Make sure that proper precautions are taken by everyone to implement plans for network interruptions. For example, the phones in the sales department wont 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 organizations 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.
A sound backup strategy. Off-site storage of backups.
Effective DPP management
660
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 231

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 operating systems. 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 2 3 Restart the system. Press <F8> during startup. 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. This option allows you to return to a previous saved configuration.
Last Known Good Configuration
Related Topics: Creating a hardware profile copy on page 662 Creating an emergency repair disk on page 663
Chapter 17, Disaster preparation and recovery
661
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 2 3 4 5 6 7 Right-click the My Computer icon. Click Properties to display the System Properties dialog box. Click Hardware. Click Hardware Profiles. Select the current hardware profile, and then click Copy. Type the name for the new configuration in the To field, and then click OK. 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. 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. Click OK. The new configuration is saved, and the startup options are set. Related Topics: Returning to the last known good configuration on page 661 Creating an emergency repair disk on page 663
662
Creating an emergency repair disk
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 2 3 Click Start> Programs> Accessories> System Tools> Backup. Click Tools> Create an Emergency Repair Disk. 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 661 Creating a hardware profile copy on page 662 Creating an emergency repair disk on page 663
Chapter 17, Disaster preparation and recovery 663
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 664

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 1499 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 computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) on page 665.
Remote Windows computer See Disaster recovery of a remote Windows computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) on page 669.
These procedures will restore your computers 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:
664
The Windows operating system has become corrupted and cannot be restored using the Emergency Repair Disks. The hard drive containing the Windows operating system has encountered an unrecoverable error that requires reformatting the disk. The hard drive that contains the Windows operating system needs to be replaced.
Manual disaster recovery of a local Windows computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller)
This procedure will restore your computers 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 1499. 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 the following items:
A current full backup of the computer to be recovered and any subsequent incremental/differential backups. The Windows installation media. The Backup Exec for Windows Servers installation media.
Note If you recover a computer that runs Windows 2008, you may need to turn on the Windows BitLocker Drive Encryption option.
665
To manually recover a local Windows computer 1 Install the original version of Windows. 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. 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, as follows:
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.
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.
Using the Device Configuration Wizard, install the appropriate device driver for the attached media drive. See Using the Getting Started with Backup Exec page on page 127.
4 5 6
Start Backup Exec for Windows Servers. From the navigation bar, click Devices. Inventory the media containing the latest full backup of the computer to be recovered. See Inventorying media on page 368.
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 196.
From the navigation bar, click Restore.
666
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
11 On the Properties pane, under Settings, click Advanced, and then select the appropriate options. See Advanced options for restore on page 505. 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 computers 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 go to step 15.
If you are not performing the recovery is complete. an authoritative restore
15 Do the following to 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.
667

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. 17 Press <F8> during startup. A menu appears that allows you to diagnose and fix system startup problems. 18 Select Directory Services Restore Mode. 19 Launch Backup Exec. 20 From the navigation bar, click Restore. 21 Select System State (Windows 2000/XP) or Shadow Copy (Windows 2003/2008) 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. Open a command prompt. Type NTDSUTIL and press Enter. Type Authoritative Restore and press Enter. Type Restore Subtree "ou=<OU Name>.dc=<domain name>,dc=<xxx> (without the quotation marks), and then press Enter, where <OU Name> is the name of the organizational unit you want to restore, <domain name> is the domain name the OU resides in, and <xxx> 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.
Restore specific objects from the Active Directory by performing the following:

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 498 Disaster recovery of a remote Windows computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) on page 669 Manual disaster recovery of Windows computers on page 664
Disaster recovery of a remote Windows 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 computers 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 53 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 1499 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 the following:
A current full backup of the computer to be recovered and any subsequent incremental/differential backups. The Windows installation media.
Always log on to Windows using the Administrator account or its equivalent during this procedure. Note If you recover a computer that runs Windows 2008, you may need to turn on the Windows BitLocker Drive Encryption option. To manually recover a remote Windows computer At the remote computer: 1 Install the original version of Windows.
669
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, as follows:
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: 2 Install the Backup Exec Remote Agent to the remote computer. See Installing the Remote Agent for Windows Systems on page 88. 3 4 Start Backup Exec for Windows Servers. 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 368. 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 196. 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. On the Properties pane, under Settings, click General, and then select the following options:

Restore over existing files Restore security Preserve tree
670
On the Properties pane, under Settings, click Advanced, and then select the appropriate options. See Advanced options for restore on page 505. 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.
Click Run Now.
10 After the job completes, restart the remote computer. Your computers operating system is now restored to its pre-disaster state. Your data files have been restored, except those protected by Backup Exec database agents. 11 Continue with one of the following:
If you are performing an authoritative restore go to step 12.
If you are not performing the recovery is complete. an authoritative restore
12 At the remote server, press <F8> 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/XP) or Shadow Copy (Windows 2003/2008 or Windows Vista) 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.
Chapter 17, Disaster preparation and recovery 671
21 Run the Restore job. At the remote server: 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. Open a command prompt. Type NTDSUTIL and press Enter. Type Authoritative Restore and press Enter. Type Restore Subtree "ou=<OU Name>.dc=<domain name>,dc=<xxx> (without the quotation marks), and then press Enter, where <OU Name> is the name of the organizational unit you want to restore, <domain name> is the domain name the OU resides in, and <xxx> 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.
Restore specific objects from the Active Directory by performing the following:

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 498 Manual disaster recovery of Windows computers on page 664
672
Chapter
18
Troubleshooting
This section provides information on troubleshooting Backup Exec. Note For more information, the Symantec Technical Support web site (entsupport.symantec.com) provides information on error messages, how to troubleshooting information and software downloads. 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:
Table 18-1 Troubleshooting categories
For problems with Do this this Storage hardware See Hardware-related questions on page 674.
Error messages in See Error messages on page 677 Backup Exec Performance issues Issues relating to backing up data Issues relating to restoring data See Improving Backup Exec performance on page 680. See Backup questions on page 678. See Restore questions on page 680.
673
Hardware-related questions
If you have tried everything you can to solve a problem, but still need a resolution, you can contact Technical Support.
See Contacting Technical Support on page 685.
If you have trouble with your hardware, review the following questions. My drive is not listed in Backup Execs 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. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2. If your device is listed on the Hardware Compatibility List, try running Backup Execs Device Configuration wizard and installing Symantec device drivers. See Configuring storage devices by using the Device Configuration Wizard on page 340. 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 in the following situations:

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. 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.
Other storage devices may go offline in the following situations:

674

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. 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 place the device online, try the following:
To restart the Backup Exec services
From the Tools menu, select Backup Exec Services and then click the Restart all services button.
If the drives firmware is updated or changed
If the drives 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 dont seem to be working. Why? After setting up bar code rules, you must perform the following two steps in order for the bar code rules to work.
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 librarys properties. 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.
See Bar code rules in mixed media libraries on page 193. How do I get the latest device drivers for my hardware? You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2
Chapter 18, Troubleshooting
675
Backup Exec doesnt detect my robotic library. What could be wrong? Be sure that Windows operating system properly recognizes the device. This can be verified by checking the Windows Device Manager. See Configuring multi-drive robotic libraries on page 1538. Im 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:
Contaminated read/write heads of the tape device. Check with the hardware manufacturer for proper cleaning techniques. Bad media. Replace the media. Try a new tape that is certified by the hardware manufacturer. Tape driver. Load the appropriate Backup Exec tape driver. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2. 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. 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. 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. 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. 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. General SCSI problems. Isolate the tape drive on its own controller card or try a different SCSI card.
676
Error messages
Why does my DLT tape drive pause 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. 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 340 Error messages on page 677 Improving Backup Exec performance on page 680
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 a condition. You can get more information on Backup Exec alert and error messages in the following ways:
On the alert dialog box, click the link for the Unique Message Identifier (UMI) code, or look in the job log and click the UMI link. This code is a hyperlink to the Symantec Technical Support Web site. You can access the technical notes that are related to the alert. See Linking from the job log to the Symantec Technical Support Web site on page 470.
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.
677
Backup questions
Related Topics: Error-handling rules on page 486 Hardware-related questions on page 674.
Backup questions
If you have problems with backing up data, review the following 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 Execs Advanced Open File Option (sold separately) provides uninterrupted data protection for network environments. Why do Backup Execs 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
678
Backup questions
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. 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.
Table 18-2 NTFS Partition Cluster Sizes Cluster Size 512 1024 2048 4096
Partition Size (MB) <= 255 256 - 511 512 - 1023 1024 - 2047
The following tables display the cluster sizes for FAT partitions.
Table 18-3 FAT Partition Cluster Sizes Cluster Size (K) 2 4 8 16 32
Partition Size (MB) <= 127 128 - 255 256 - 511 512 - 1023 512 - 1023
679
Restore questions
Restore questions
If you have problems with restoring data, review the following questions. Sometimes the byte counts for data that I restore dont 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 by setting job properties on page 498 Hardware-related questions on page 674.
Improving Backup Exec performance

Many variables can affect throughput performance. These include:
Table 18-4 Item Hardware Variables that affect throughput performance Description 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 ensure the following:
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.
680
Improving Backup Exec performance Table 18-4 Item System Variables that affect throughput performance Description 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. See System requirements on page 69. 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.
681
Improving Backup Exec performance Table 18-4 Item System Variables that affect throughput performance Description 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. See System requirements on page 69. 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.
682
Improving Backup Exec performance Table 18-4 Item Block Size Variables that affect throughput performance Description 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. 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 or larger. If you use a device that supports larger block sizes, you can change the devices block size in the Device Configuration tab. However, if the option to change the block size is unavailable, you must configure the device to use a larger size. See the device manufacturers documentation for help to configure the device. 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 following:

The make/model of network cards. The network card driver. 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.
683
Improving Backup Exec performance Table 18-4 Item Hardware Variables that affect throughput performance Description 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 ensure the following:
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.
684
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 or via the Internet with Symantec DirectAssist. See Before calling Technical Support on page 685.
Before calling Technical Support

To expedite the Technical Support process, do the following:
Know your Backup Exec version and revision number. See Finding version and revision information for your Backup Exec installation on page 685.
Use one of the diagnostic utilities included with Backup Exec to collect information that technical support can use to diagnose your issue. See Backup Exec diagnostic utilities on page 685.
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 the following 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. See Generating a diagnostic file for troubleshooting on page 686. 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
685
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 688.
Generating a diagnostic file for troubleshooting

Backup Exec includes a diagnostic application (Bediag.exe) that gathers information about a Windows computer for troubleshooting purposes. You can run it from the media server, or from a remote computer. 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 the following:

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.
To create a bediag.txt from within Backup Exec 1 2 Start Backup Exec. On the Tools menu, select Backup Exec Diagnostics. 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.
Click Run Diagnostics. The bediag.txt file will appear.
From a command line prompt on the media server 1 2 Launch the command prompt. 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). The file Bediag.txtis in the directory that contains Bediag.exe (by default Program Files\Symantec\Backup Exec).
686
The following switches can be used with the command line option (bediag [switches] servername):
/a /b:[server] /c /app /sys /bex /err /recs:n Dump Agent List Specify a Backup Exec server to poll for service account information Dump Backup Exec software configuration from the registry Dump Application Event log Dump System Event log Dump only Backup Exec entries in the Application Event log Dump only error events from any event log 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 /l /n /p /q /s /u /v /w /x /? Dump SCSI hardware subkey from registry Dump Lotus Notes information Dump Windows Socket Network Protocols Dump user privileges Dump Microsoft SQL Server information Dump information on Services Dump Microsoft update information. Dump Server Information Dump Windows version information Dump Microsoft Exchange Server Information Display usage information
687
Running Bediag on a remote computer You can run diagnostics on a remote media server provided:

Backup Exec is installed on the remote server. Backup Exec services are running.
To run Backup Exec diagnostics on a remote media server 1 2 On the Tools menu, click Backup Exec Diagnostics. Click Select Server and select the remote media server on which you want to run the diagnostic utility. Enter the logon credentials for this remote system. Click Run Diagnostics. Diagnostic information appears in a .txt file.
3 4
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. Check all of the boxes in the Data to gather (if available) field. Use the default Output root directory (required) or specify an alternate one.
If you want to use the Go to step 4. default directory.
2 3
688
If you know the name Type the name of the directory. of the directory. If you do not know the name of the directory. Click Browse to browse to the correct directory.
4 5
Enter your case number with the dashes (example 123-456-789). If there are additional files you want added to the compressed file enter them now.
If you know the name Type the file name in the Files text box, of the file. and then click Add. If you do not know the file name.
Click Browse to browse to the correct file. Select the file and then click Open. Click Add.
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 that contains the log files.
689
690
Chapter
19
Using Symantec Backup Exec with Server Clusters

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 694 Configurations for Backup Exec and Microsoft Cluster Servers on page 704 Backing up Microsoft Cluster Servers on page 714 About restoring data to a Microsoft cluster on page 717 Requirements for installing Backup Exec on a Microsoft Cluster Server on page 693 Disaster recovery of a cluster on page 731 Installing Backup Exec with the CASO option on a Veritas Cluster Server on page 723
691
How Backup Exec works in a Microsoft Cluster Server
About backing up Veritas Cluster Servers on page 726 About restoring data to Veritas Cluster Servers on page 730
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 704 Installing Backup Exec on a Microsoft Cluster Server on page 694
692
Requirements for installing Backup Exec on a Microsoft Cluster Server
Requirements for installing Backup Exec on a Microsoft Cluster Server

The following items are required to install Backup Exec on a Microsoft Cluster Server:
Two-node clusters are supported with Backup Exec for Windows Servers on Microsoft Windows 2000 Advanced Server/DataCenter, Windows Server 2003 Enterprise/DataCenter, and Windows Server 2008 Enterprise/DataCenter. Four-node clusters are supported with Backup Exec for Windows Servers on Microsoft Windows 2000 DataCenter, Windows Server 2003 Enterprise/DataCenter, and Windows Server 2008 Enterprise/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 Windows Server 2003/2008 majority node configurations. 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),
693
Chapter 19, Using Symantec Backup Exec with Server Clusters
Installing Backup Exec on a Microsoft Cluster Server
then you cannot log on to the locally installed Backup Exec media server. You can 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 694 Configurations for Backup Exec and Microsoft Cluster Servers on page 704

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. See Specifying a new drive letter for the cluster quorum disk on page 721. 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. From the node that you want to be the active node, start Backup Exec. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. Follow the instructions on the screen. 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.
2 3 4
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. See Creating device pools for Microsoft Cluster Servers on page 698.
Repeat step 5 for all nodes.
Related Topics: Enabling or disabling checkpoint restart on page 700 Configurations for Backup Exec and Microsoft Cluster Servers on page 704 Specifying a different failover node on page 701
Upgrading Backup Exec on a Microsoft cluster

You can upgrade Backup Exec on the nodes in a cluster without taking the nodes out of the cluster. You can upgrade to Backup Exec 12 on nodes in a cluster that use the Desktop and Laptop Option. However, you must ensure that each node had been an active host before you begin the upgrade. To upgrade Backup Exec on a cluster 1 2 3 Select a node to upgrade and make that node the active Backup Exec cluster node. Run the Backup Exec installation program on the active node. 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. Repeat step 3 for each node in the cluster.
Related Topics: Upgrading from previous versions of Backup Exec on page 123
695
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. Install the additional options. See Installing Backup Exec options to the local computer on page 75. 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. See Installation and configuration requirements for the Oracle Agent on page 1376. SeeAbout installing the SAP Agent on page 1421.
Uninstalling Backup Exec from a Microsoft cluster

You use the Cluster Configuration Wizard to remove Backup Exec. To uninstall Backup Exec from a cluster 1 2 From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. 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 4
Uninstall Backup Exec from all the nodes. 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. On any node, click Start, point to Settings, and then click Control Panel to uninstall Backup Exec. 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
697
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 (<Node Name>) for each node in the cluster. If a node has storage devices, those storage devices are automatically assigned to All Devices (<Node Name>), 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 2 From the controlling node, open Backup Exec. Create a new device pool. See Creating device pools on page 412. 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. See Adding devices to a device pool on page 413. 4 Using the cluster administrator, move the Backup Exec resource group to the next appropriate node. 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. Repeat step 4 and step 5 for each node in the cluster.
698
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 Exchange mailboxes and public folders Exchange 2000/2003 IS with multiple storage groups SQL database non-snapshot backups System State Lotus Domino Exchange 5.5 IS and DS Exchange 2000/2003 IS with one storage group 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) The Advanced Open File Option. Microsoft Windows Vista/Server 2008. 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.
The following types of files cannot use checkpoint restart:

Checkpoint restart is not supported by the following:

Jobs that are restarted from the point of failover display a status of Resumed in the Job Monitor.
699
Enabling or disabling checkpoint restart
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.
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 486.
Specifying a different failover node
To enable or disable checkpoint restart 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Settings, click Clusters. 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. Select the Cluster Failover rule, and then click Edit. Verify that the Enabled field is selected.
6 7
Specifying a different failover node

You can do the following:

Change the order in which the nodes fail over. Add a failover node to the cluster. Remove a failover node from the cluster. 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 change the order in which nodes fail over
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.
Chapter 19, Using Symantec Backup Exec with Server Clusters 701
Designating a new SAN SSO primary server and central administration server in a Microsoft Cluster Server
If you are removing a node, do not run the cluster configuration wizard from the node you want to remove. 1 2 3 4 On the controlling node, on the Tools menu, point to Wizards. Click Cluster Configuration Wizard. Follow the instructions on the screen to add or remove a node. 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. See Uninstalling Backup Exec from a Microsoft cluster on page 696. Related Topics: Creating device pools for Microsoft Cluster Servers on page 698 Specifying a different failover node on page 701 Configurations for Backup Exec and Microsoft Cluster Servers on page 704
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.
702
Using the cluster administrator, shut down the Backup Exec cluster services. Be sure to keep the Disk resource online.
Move the catalog files from the Backup Exec cluster installation path to the respective installation paths on the new database server. Use BEUtility.exe to connect all Backup Exec servers to the new database server and to start all Backup Exec services. Stop and restart the Backup Exec Services on the new database server. Using the Cluster Administrator, move the Backup Exec resource group to the failover node and make sure services start on that node. 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.
5 6
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. 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 central administration server. Use BEUtility.exe to connect all Backup Exec servers to the new central administration server and to start all Backup Exec services. Stop and restart the Backup Exec Services on the central administration server. Using the Cluster Administrator, move the Backup Exec resource group to the failover node and make sure services start on that node. 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.
5 6
Related Topics: Multi-node clusters on a fibre channel SAN with the SAN SSO on page 709
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. 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. See Adding devices by using the Hot-swappable Device Wizard on page 341. See the following for examples of various cluster configurations:

Two-node cluster with locally attached storage devices on page 704 Two-node cluster with tape devices on a shared SCSI bus on page 706 Multi-node clusters on a fibre channel SAN with the SAN SSO on page 709
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 nodes locally attached storage devices are automatically assigned to the All Devices (<Node Name>) 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.
See Creating device pools for Microsoft Cluster Servers on page 698. To restore data in this configuration, move media to the failover nodes 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 Locally attached storage devices
Failover node Shared SCSI Bus for disks Heartbeat LAN Locally attached storage devices
705
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. See Creating device pools for Microsoft Cluster Servers on page 698. 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. See Configuring a shared SCSI bus for tape devices on page 707.
Two-node Cluster with Tape Devices on a Shared SCSI Bus
Backup Exec Virtual Server Controlling node Shared SCSI Bus for Disks Shared SCSI Bus for Tape Devices Failover node
Heartbeat LAN
706
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 706, 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 707, and the tape device has internal termination, you can use the devices internal termination to terminate the bus.
Example of a shared bus with tape devices at the end of the bus Backup Exec Virtual Server Controlling node Shared SCSI bus for disks Shared SCSI bus for tape devices Heartbeat LAN Failover node
Following are methods you can use to terminate a bus:
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.
707
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. To ensure termination if a power supply failure occurs, turn off the on-board terminators on the SCSI controller (using the host adapter manufacturers 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.
Tip
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 manufacturers documentation for details. 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 706
708
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. See Creating device pools for Microsoft Cluster Servers on page 698. 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:
709
Configurations for Backup Exec and Microsoft Cluster Servers Two 2-node Clusters on a Fibre Channel SAN with the SAN SSO
Fibre Channel SAN Secondary Storage Devices
Secondary server
Backup Exec Virtual Server A Controlling node Shared SCSI Busfor disks Failover Heartbeat node
Backup Exec Virtual Server B Shared SCSI Bus for disks Controlling node Heartbeat
Failover node
LAN
710
Configurations for Backup Exec and Microsoft Cluster Servers Four-node Cluster on Fibre Channel SAN with the SAN SSO Secondary server Fibre Channel SAN Shared Drives Secondary Storage Devices Backup Exec Virtual Server Controlling node
Failover nodes
Heartbeat
LAN
See Installing the SAN Shared Storage Option on page 1548. Related Topics: Designating a new SAN SSO primary server and central administration server in a Microsoft Cluster Server on page 702
711
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. From the node that you want to designate as the active node, start Backup Exec. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. Follow the instructions on the screen. 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.
2 3 4 5
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. From the node that you want to designate as the active node, start Backup Exec. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. Follow the instructions on the screen.
2 3 4
712
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 3 4 From the node that you want to designate as the active node, start Backup Exec. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. 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 3 4 From the node that you want to designate as the active node, start Backup Exec. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. Follow the instructions on the screen.
713
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, Shadow Copy Components, 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. See Backing up local disks in a Microsoft cluster on page 715. All shared disks, including the data in the Microsoft Cluster Server folder on the Quorum disk. See Backing up shared disks in a Microsoft cluster on page 715. 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. See Backing up database files in a Microsoft cluster on page 716.
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 715 Backing up shared disks in a Microsoft cluster on page 715 Backing up database files in a Microsoft cluster on page 716 About backing up Windows 2000 and Windows Server 2003/2008 features in a Veritas cluster on page 727 Creating a backup job by using the Backup Wizard on page 264
714
Backing up local disks in a Microsoft cluster

Select local disks for backup from the physical node to which they are attached. To back up local disks in a Microsoft cluster 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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. See Selecting data to back up on page 231. 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. Configure the remainder of the settings for the backup job. Run the backup job now or schedule it to run later.
5 6
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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. Select the drive letters that represent the shared disks. 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.
715
4 5
6 7
Configure the remainder of the settings for the backup job. Run the backup job now or schedule it to run later. 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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the backup selections pane, expand the domain that contains the cluster, then expand the virtual server that contains the database files. Check the database files. Set database-specific defaults. Refer to the specific Backup Exec database agent documentation for details on how to set backup defaults for the database. 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. Configure the remainder of the settings for the backup job. Run the backup job now or schedule it to run later.
4 5
7 8
716
About restoring data to a Microsoft cluster

For all file restore operations, including redirecting restores, use the normal restore procedures. See Restoring data by setting job properties on page 498. 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/2008 computers to a Microsoft cluster on page 718 Restoring the cluster quorum to a Windows 2000 and Windows Server 2003/2008 node running Active Directory to a Microsoft cluster on page 719 Specifying a new drive letter for the cluster quorum disk on page 721
About restoring Windows 2000 and Windows Server 2003/2008 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.
717
Restoring the cluster quorum for Windows 2000 and Windows Server 2003/2008 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. See Restoring the cluster quorum to a Windows 2000 and Windows Server 2003/2008 node running Active Directory to a Microsoft cluster on page 719. 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 721. 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. See step 5. To restore the cluster quorum 1 2 3 4 5 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Settings, click Advanced. Select Restore Cluster Quorum. 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.
Select any additional options as needed for this restore job.
718
See Restoring data by setting job properties on page 498. 7 When the restore operation is complete, use the cluster administrator software to restart the cluster service on nodes on which it was stopped.
Restoring the cluster quorum to a Windows 2000 and Windows Server 2003/2008 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. 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. See step 9. To restore the cluster quorum to a node running Active Directory without using Backup Exec Cluster 1 To restore System State, start the computer in safe (repair) mode (restart the computer and then press <F8> 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. See Starting and stopping Backup Exec services on page 114.
719
2 3 4 5 6 7
On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the Restore Selections pane, click System State. On the Properties pane, under Settings, click Advanced. Clear the Restore cluster quorum option. This option must not be selected. 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 9
When the restore has completed, reboot the target node. 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.
720
[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.
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 2 3 4 5 6 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the Restore Selections pane, click System State. On the Properties pane, under Settings, click Advanced. Clear the Restore cluster quorum option. This option must not be selected. Start the restore operation. During the restore, the cluster quorum files are copied to the default location %SystemRoot%\cluster\BackupExec. 7 8 When the restore has completed, reboot the target node. 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
Using Backup Exec with Veritas Cluster Server
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. 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: Installing Backup Exec with the CASO option on a Veritas Cluster Server on page 723 Installing Backup Exec on a Microsoft Cluster Server on page 694 Clustering Backup Exec using Veritas Cluster Server on page 725
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 694
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. 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.
723
Requirements for clustering Backup Exec using Veritas Cluster Server
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. 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: About installing the Remote Agent for Windows Systems on page 889
Requirements for clustering Backup Exec using Veritas Cluster Server

Review the following items before you cluster 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.
724
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 Storage Foundation for Windows Servers High Availability Edition Administrators Guide. Install Backup Exec to the local drive on each machine that will be part of the Backup Exec service group. 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 Storage Foundation for Windows Servers High Availability Edition Administrators Guide. 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. On the Tools menu, click Wizards>Cluster Configuration Wizard. At the Cluster Configuration Wizard welcome screen click Next. 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. Click Next.
5 6 7
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.
About backing up Veritas Cluster Servers
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.

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.
See Creating a backup job by using the Backup Wizard on page 264. 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 728 Backing up shared disks in a Veritas cluster on page 728 Backing up database files in a Veritas cluster on page 729 About backing up Windows 2000 and Windows Server 2003/2008 features in a Veritas cluster on page 727
726
About backing up Windows 2000 and Windows Server 2003/2008 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 730
727
Backing up local disks in a Veritas cluster

Select local disks for backup from the physical node to which they are attached. 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. To back up local disks in a Veritas cluster 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the backup selection pane, expand the domain that contains the nodes, and then select the local disks on each node. See Selecting data to back up on page 231. 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. Configure the remainder of the settings for the backup job. Run the backup job now or schedule it to run later.
5 6
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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. Select the drive letters that represent the shared disks.
4
728
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. Configure the remainder of the settings for the backup job. Run the backup job now or schedule it to run later.
6 7
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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. Set database-specific defaults. Refer to the specific Backup Exec database agent documentation for details on how to set backup defaults for the database. 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. Configure the remainder of the settings for the backup job. Run the backup job now or schedule it to run later.
6 7
729
About restoring data to Veritas Cluster Servers
About restoring data to Veritas Cluster Servers

For all file restore operations, including redirecting restores, use the normal restore procedures. See Restoring data by using the Restore Wizard on page 497. 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.
730
Disaster recovery of a cluster

Prepare for recovery by creating a disaster preparation plan. See Key elements of a disaster preparation plan (DPP) on page 660. 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 Group name Preferred nodes Failover/failback policies 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)
Cluster Groups

Cluster Resources

731
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. See Preparing computers for IDR on page 1502. 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 Execs 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.
732
Note After Windows has been installed, you cannot change the system drives letter. You must restore the system to the same drive letter from which it was backed up. 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 Restore the nodes. See About recovering a computer and using the Disaster Recovery Wizard on page 1522. 3 4 Reconnect the shared drives and bring the nodes online. 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 1369 Disaster recovery for Exchange Server 5.5 on page 1248 Disaster recovery of a Lotus Domino server on page 1309 About restoring and recovering Oracle resources on page 1399
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 2 Replace all shared disks, if necessary. 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. Reboot the server.
733
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

As part of the manual recovery process, you must reinstall Windows, including the last service pack applied before the failure. 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. See Manual disaster recovery of Windows computers on page 664. 2 On the other nodes you want to recover, reinstall Windows, including the last service pack applied before the failure. Reinstall the cluster services and bring the cluster online. Do the following:
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. 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.
If you are recovering a Veritas Cluster Server, re-install Backup Exec. SeeInstalling Backup Exec with the CASO option on a Veritas Cluster Server on page 723.
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.
734
See Installing Backup Exec on a Microsoft Cluster Server on page 694. 5 6 7 Catalog the media in the cluster. On the Backup Exec navigation bar on the active node, click Restore. In the Restore selections pane, select the last full backup sets made of the active node, and then select System State. 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).
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 1369 Disaster recovery for Exchange Server 5.5 on page 1248 Disaster recovery of a Lotus Domino server on page 1309 About restoring and recovering Oracle resources on page 1399
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.
735
To restore the cluster data files 1 2 3 4 5 6 7 8 9 Shut down the secondary nodes. Start the primary node. On the Computer Management menu, select System Tools. Then select Device Manager. Right-click the cluster disk driver, and then select Disable. Click OK. Reboot the primary node. On the Backup Exec navigation bar, click the arrow next to Restore. Click New Restore Job. 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.
Recovering all shared disks in a Microsoft 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 2 3 Disable the cluster disk driver on all nodes in order to gain access to the new disk. On the Computer Management menu, select System Tools. Then select Device Manager. Right-click the cluster disk driver, and then select Disable.
736
4 5 6 7 8 9
Replace and then repartition the shared disk. Use Disk Manager to verify that all nodes have access to the same shared disk. Run Dumpcfg or Clusterrecovery to replace the disk signature for the Quorum disk. Using a remote Backup Exec server, restore the cluster files to the Quorum disk via the node that has access to the disk. Enable the cluster disk driver on all nodes. On the Computer Management menu, select System Tools. Then select Device Manager. Right-click the cluster disk driver, and then select Enable.
10 Reboot all cluster nodes. To recover all shared disks without using Dumpcfg 1 2 3 4 Uninstall all cluster applications and the cluster software from both nodes. Replace and then use Disk Manager to repartition the shared disk to the previously saved configuration. Reinstall the cluster software. Reinstall the cluster-aware version of Backup Exec for Windows Servers on the cluster. See Installing Backup Exec to a local computer on page 71. 5 6 Reinstall additional cluster-aware software applications on the shared disk. Use Backup Exec to restore any data from the catalogs.
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 2 Use Volume Manger to recreate all shared volumes and disk groups. 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.
737
Troubleshooting clusters
From the directory in which Veritas Cluster Server was installed, use a text editor such as Notepad to open the Main.cf. 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.
Restore the shared information using the virtual server backup.
Recovering Backup Exec in a Microsoft cluster

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. Reinstall the cluster-aware version of Backup Exec for Windows Servers on the cluster using the same information used in the original installation. See Installing Backup Exec to a local computer on page 71. 3 Use Backup Exec to restore any data from the catalogs.
If you experience problems with using Backup Exec in a cluster environment, review the questions and answers in this section. After I recovered my cluster and all shared disks, the cluster service will not start. Why wont 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
738
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. Open the Cluster Administrator and right-click the cluster, and then select Properties. Select the Quorum tab. In the Quorum resource field, select a different disk. Click OK. 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.
3 4 5 6
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.
739
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 2 3 The snapped volumes are split from the original volumes. The previously split snapped volumes are placed into a new cluster disk group. 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. 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. The new cluster disk group joins the original cluster disk group if it is located in the same node. 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. Rejoin the new cluster disk group with the original cluster disk group. Snap back the snapped volumes with their original volumes. Ensure that the option to synchronize using the original volume is selected.
2 3
740
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 wont 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.
741
742
Appendix
Symantec Backup Exec Central Admin Server Option

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.
743
How CASO works CASO-configured Backup Exec environment - LAN 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.
744
How CASO works CASO-configured Backup Exec environment - WAN WAN Data center Central administration server Managed media servers
Jobs
Remote office
Jobs Jobs
Protected servers
Jobs
Remote office Managed media servers

Jobs
Managed media servers
Remote office
Managed media servers
Protected servers
The following graphic shows CASO installed in a Backup Exec SAN Shared Storage Network environment.
Appendix A, Symantec Backup Exec Central Admin Server Option
745
How CASO works CASO-configured Backup Exec environment - SAN Shared Storage Network Managed media servers not attached to the SAN LAN Managed media servers attached to the SAN Fibre-to-SCSI bridges SCSI tape libraries
Primary database server/central administration server
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. CASO includes the following additional functionality:
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.
746
Requirements for installing CASO
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. 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.
Related Topics: Choosing the location for device and media data on page 749 Installing the central administration server on page 750 Upgrading an existing CASO installation on page 760

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 69

Appendix A, Symantec Backup Exec Central Admin Server Option 747
Installing the central administration server on page 750
748
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 servers 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 servers device and media data:
Table A-1 Task Comparison of CASO tasks Device and media data Device and media data on the central on the managed media administration server 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 791. 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 769. 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 769. Send job status updates, job logs, and job Yes histories to the central administration server if the option to monitor jobs is enabled on the managed media server See Configuring CASO on page 769. Yes Yes Yes Yes No
Delegate jobs from the central administration server to the managed media server See About job delegation in CASO on page 783.
Yes
Yes
749
Installing the central administration server Table A-1 Task Comparison of CASO tasks Device and media data Device and media data on the central on the managed media administration server 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.
Centralize, distribute, or replicate the catalog See Changing the catalog location on page 781. Run centralized restore See How centralized restore works on page 792.
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 760 Setting defaults for managed media servers on page 770 Running the Backup Exec Utility on page 767
Installing the central administration server

Before you start the installation, review the information about the location of device and media data. See Choosing the location for device and media data on page 749. During the installation of the Managed Media Server feature, you are prompted to keep the managed media servers 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.
750
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. See Installing Backup Exec to a local computer on page 71. 2 3 Enter the CASO license key when the prompt appears. 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. 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. On the task pane, under Media Server Installation Tasks, click Configure managed media server defaults. On the Managed Media Servers Defaults dialog box, choose the settings that you want applied to each new managed media server that you install. See Setting defaults for managed media servers on page 770. 7 Install a managed media server. See Installing a managed media server from the central administration server on page 751.

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 servers 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 749.
751
To push-install a managed media server from the central administration server 1 2 On the central administration servers navigation bar, click Media Servers. In the task pane, under Media Server Tasks, click Install additional managed media servers. When the Welcome screen displays, click Next to begin the installation wizard. 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 Do the following in the order listed:

3 4
Click Add Remote Computer. Browse the list to select all of the remote computers that you want to install an option to. Click Next.
To add a remote computer Do the following in the order listed: manually Click Add Remote Computer Manually.

Type the Domain and Computer Name. Click OK.
On the Remote Computer Logon Credentials panel, complete the fields as follows:
User Name Password Domain Use this user name and password when attempting to connect to additional computers during the installation Type the user name for an account that has administrative rights on the remote computer. Type the password for an account that has administrative rights on the remote computer. Select the domain in which the remote computer is located. 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.
On the Remote Installation Types dialog box, select Remote install with licensed options, and then click Next.
752

If you have serial numbers 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.
Go to step 8.
Select one of the following methods to enter license keys:.

To enter license keys Do the following in the order listed: manually 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 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. See About Backup Execs standard features on page 68. 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 <computer names> hard drive. If the feature icon is shaded, the option is not available for change.
753

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. 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 64 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 configure a managed media server as a secondary server in the SAN SSO, make the primary server the central administration server. The primary server must be the same server as the central administration server. 16 Select where to keep the device and media data for this managed media server:
On the central administration server Click this if you want to do the following:

Delegate jobs to this managed media server. Manage all of the storage devices and media from the central administration server.
754
On the managed media server
Use this in the following situations:
There is 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 749. If you select the SAN SSO option and the Managed Media Server option during installation, all Backup Exec catalog and database functions are centralized by default.
17 Click Next. 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. See About Microsoft SQL Server 2005 Express Edition components installed with Backup Exec on page 66. 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. 21 After the computer has restarted, right-click the computer name and select the Retry Install option. Verify the credentials when prompted.
755
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) 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 340. 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 servers 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 757. Related Topics: Installing Backup Exec to remote computers on page 77
756
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 servers 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. After you change the configuration of the port from dynamic to static, you must add the static port to the Windows Firewall Exceptions list. See your Windows operating system documentation. You must change the port that you use for the SQL instance to a static port and assign it an alias. Do one of the following:
Table A-2 For this
SQL ports Do this See Changing the dynamic port on a SQL Express instance to a static port on page 757. See Opening a SQL port for a SQL 2000 or 2005 instance on page 759.
A SQL Express instance A SQL 2000 or 2005 instance
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.
757
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. Expand SQL Server 2005 Network Configuration. Click Protocols for BKUPEXEC, and then in the right pane, double-click TPC/IP. On the TCP/IP Properties dialog box, click the IP Addresses tab. Under IPAll, in TCP Dynamic Ports, remove the value and leave the field blank. Under IPAll, type in a port number for TCP Port. The port number can be between 1025 and 65535 and must not be in use by another application. See Restore questions on page 680. 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. Under that same heading, in TCP Dynamic Ports, remove the value of 0, and type the same port number you entered for TCP Port. Click Apply.
2 3 4 5 6
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 758. To create an alias when a SQL Express instance is used 1 2 3 On the managed media server, click Start > SQL Server Configuration Manager. Expand SQL Native Client Configuration. Click Aliases, and then double-click the alias name that contains the central administration server name and the Backup Exec SQL instance name.
758
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. Type the port number of the remote Backup Exec SQL Server instance that you noted in the previous procedure. Select TCP/IP. Type the name of the central administration server and the Backup Exec SQL instance name using the format server name\instance name.
Port No Protocol Server
5 6
Click Apply, and then click OK. 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. On the General tab, select the Backup Exec SQL instance. Under Enabled Protocols, select TCP/IP, and then click Properties. Note the port number that is displayed. 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 760.
2 3 4 5
759
Upgrading an existing CASO installation
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. On the Alias tab, click Add. In the Server alias field, type: server name\instance name 4 5 Under Network libraries, select TCP/IP. In the Server name field, type: server name\instance name 6 7 Uncheck Dynamically determine port. In the Port number field, type the port number of the remote Backup Exec SQL Server instance.
2 3
Related Topics: Using Backup Exec with firewalls on page 326

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

760
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. Related Topics: About catalog locations on page 780 Changing the catalog location on page 781 Upgrading an existing central administration server on page 761 Upgrading an existing managed media server on page 763
Upgrading an existing central administration server

The central administration server must be upgraded before any managed media servers are upgraded. See Upgrading an existing CASO installation on page 760. 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. See Configuring database maintenance on page 162. Note Symantec recommends that you stop all Backup Exec services on each managed media server before you upgrade the central administration server. To upgrade an existing central administration server 1 2 Verify that the latest service pack for Backup Exec 10d is installed. Place all scheduled jobs on hold on the central administration server and the managed media servers. See Placing all scheduled occurrences of an active job on hold on page 455. 3 4 Allow all active jobs to complete. From the installation CD browser, select the option to install Symantec Backup Exec.
761
5 6 7 8 9
On the Welcome panel, click Next. Select I accept the terms of the license agreement, and then click Next. Check Local Install, and then click Install Backup Exec software and options. Click Next. Do one of the following:
If you have serial Do the following in the order listed: numbers for Backup Exec Go to https://licensing.symantec.com to activate the product. and its options 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.
Go to step 10.
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.
762
13 Release all jobs from hold. See Placing all scheduled occurrences of an active job on hold on page 455. 14 Upgrade some or all of the managed media servers.
Upgrading an existing managed media server

The central administration server must be upgraded before any managed media servers are upgraded. See Upgrading an existing CASO installation on page 760. 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. See Configuring database maintenance on page 162. To upgrade an existing managed media server 1 2 Verify that the latest service pack for Backup Exec 10d is installed. 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 802. 3 On the managed media server that you want to upgrade, do one of the following:
To choose where to keep See Installing a managed media server from the central the device and media data administration server on page 751. To keep the managed media servers device and media data centralized on the central administration server See Changing a media server to a managed media server on page 766. 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.
763
Changing a Backup Exec media server to a central administration server
Resume the managed media server. See Pausing and resuming a managed media server on page 802.
Related Topics: Running the Backup Exec Utility on page 767

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. On the Tools menu, click Install Options and License Keys on this Media Server. On the Welcome screen, click Next. Check Local Install, and then click Next. Do one of the following:
If you have serial Do the following in the order listed: numbers for Backup Exec Go to https://licensing.symantec.com to activate the product. and its options 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.
2 3 4 5
Go to step 6.
764
Select one of the following methods to enter license keys:.

To enter license keys Do the following in the order listed: manually 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.


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. See About Backup Execs standard features on page 68 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 <computer names> hard drive. If the feature icon is gray, the option is not available for change. 9 Do one of the following:
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.
765
10 Click Next. 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.
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 2 3 4 Verify that the central administration server is running. Start Backup Exec at the stand-alone media server. From the Tools menu, click Set Central Administration Server. 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 6 7 8 Click OK. Click Close. Restart the Backup Exec media server. On the central administration servers 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 757.
Changing a managed media server to a stand-alone media server
Related Topics: Installing a managed media server from the central administration server on page 751 Running the Backup Exec Utility on page 767
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 managed media server to a stand-alone media server 1 2 3 On the central administration server, from the navigation bar, click Media Servers. Select the managed media server that you want to delete. On the task pane, under General Tasks, click Delete.
Related Topics: Changing a media server to a managed media server on page 766
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. Refer to the help for information about performing tasks. On the Backup Exec Utility menu bar, click Help.
767
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 2 3 4 On the central administration servers navigation bar, click Media Servers. Select a managed media server. On the task pane, under General Tasks, click Delete. Repeat these steps for each managed media server that is displayed in the Media Servers view. After deleting all managed media servers, uninstall Backup Exec on the central administration server. See Uninstalling Backup Exec on page 115.
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 2 3 4 On the central administration server, from the navigation bar, click Media Servers. Select the managed media server that you want to delete. On the task pane, under General Tasks, click Delete. 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 115.
768
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 Set defaults for a managed media server 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 job log settings and job history information to remain on managed media servers. The information also can be copied and moved automatically to the central administration server. Change the location of the device and media data Do this See Setting defaults for managed media servers on page 770. See About reducing network traffic in CASO on page 770. See Setting communication thresholds and active job status updates on page 773.
See Copying logs and histories to the central administration server on page 776.
See Running the Backup Exec Utility on page 767.
Delegate jobs from the central administration See Creating device pools on page 412. server to any available devices Perform operations on a group of managed media servers View alerts that are generated on a managed media server Configure notification when alerts occur 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 See Grouping managed media servers in pools on page 783. See Configuring alerts in CASO on page 778. See Configuring notification in CASO on page 779. See Recovering failed jobs in CASO on page 800. See Enabling managed media servers to use any available network interface card on page 779.
769
Configuring CASO
About reducing network traffic in CASO

To accommodate a low bandwidth network connection or to reduce network traffic, you can do the following:
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 servers 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 770 Copying logs and histories to the central administration server on page 776 Setting communication thresholds and active job status updates on page 773 Changing the catalog location on page 781
Setting defaults for managed media servers

Backup Exec sets communication defaults automatically. However, you can change the default settings. See About reducing network traffic in CASO on page 770.
770
Configuring CASO
To set defaults for managed media servers 1 2 On the central administration servers navigation bar, click Media Servers. Do one of the following:
To set defaults to apply to Do the following in the order listed: a managed media server On the task pane, under Media Server Installation Tasks, click when it is installed Configure managed media server defaults.
Proceed with step 3.
To set defaults for an existing managed media server
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.
To set defaults for a group Do the following in the order listed: of managed media servers Select or create the media server pool that contains the in a pool 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.
On the Settings tab, select the appropriate options as follows.

Fast 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.
Slow connection with the central administration server
771
Configuring CASO
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 773. See Copying logs and histories to the central administration server on page 776.
Edit Custom Settings
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 773. See Copying logs and histories to the central administration server on page 776.
Monitor jobs that are created on the local managed media server in addition to the jobs that are delegated from the central administration server
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. Jobs that are created by policies on the managed media server cannot be deleted from the central administration server.
772
Configuring CASO
Display alert when the difference in seconds between the clocks on the managed media server and the central administration server is more than
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. 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.
Click OK.
Related Topics: Setting communication thresholds and active job status updates on page 773 Managing jobs in CASO on page 800
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. See What happens when communication thresholds are reached on page 775. 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.
773
Configuring CASO
To set communication thresholds and the frequency of active job status updates 1 2 On the central administration servers navigation bar, click Media Servers. Do one of the following:
To set defaults to apply to Do the following in the order listed: a managed media server On the task pane, under Media Server Installation Tasks, click when it is installed Configure managed media server defaults.
Proceed with step 3.
To set defaults for an existing managed media server
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.

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 4
On the Settings tab, click Custom settings, and then click Edit Custom Settings. On the Configuration tab, change the defaults as appropriate:
Communication Stalled (no more jobs are queued to the managed media server) Type the amount of time before the managed media servers 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.
774
Configuring CASO
No Communication (jobs are recovered from the managed media server)
Type the amount of time before the managed media servers 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.
Send active job status updates in seconds to the central administration server
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.
Click OK.
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 servers communication status changes from Enabled to Stalled. The jobs waiting to be processed by the managed media server are held in the managed media servers job queue until the communications are restored. You can set the amount of time that Backup Exec waits before changing the managed media servers status if it becomes unresponsive. The configuration settings use time thresholds that when exceeded, change the managed media server statuses that are
Configuring CASO
reported to the central administration server. These statuses include Stalled and No Communication. When a managed media servers 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 servers 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. See Setting communication thresholds and active job status updates on page 773.
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. To copy logs and histories to the central administration server 1 2 On the central administration servers navigation bar, click Media Servers. Do one of the following:
To set defaults to apply to On the task pane, under Media Server Installation Tasks, click a managed media server Configure managed media server defaults. when it is installed To set defaults for an existing managed media server Do the following in the order listed:
Right-click the managed media server for which you want to configure settings, and then click Properties. Click the Settings tab.
776
Configuring CASO

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 4
On the Settings tab, click Custom settings, and then click Edit Custom Settings. On the Job Logs and Histories tab, select the appropriate options as follows.
Never Every day at On job completion Click this option to keep the job log on the managed media server where the job ran. Click this option to send a copy of the job log to the central administration server every day at the time you specify. 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. Only when required Click this option to send a copy of the job history to the central by job type 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 On job completion Click this option to send a copy of the job history to the central administration server every day at a specified time. 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.
Click OK.
777
Configuring CASO
Configuring alerts in CASO

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. To configure specific alerts on the central administration server 1 2 3 Start Backup Exec on the central administration server. From the Tools menu, click Alert Categories. Scroll through the list of alert categories until you find the category you want to configure. From Category Properties, select the check box Enable alerts for this category. Click OK.
4 5
To copy specific alerts to managed media servers. 1 2 3 4 From the Tools menu, select Copy Settings to Media Servers. Under Select Settings to Copy, select the check box for Alert Configuration. Click Add. Enter the name of a managed media server to which the configuration will be copied.
778
Configuring CASO
5 6
Click OK. On the Copy Settings dialog box, click OK. An alert on the central administration server will confirm that the copy succeeded.
Click OK to clear the active alert.
Related Topics: Alerts and notifications on page 537 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. Related Topics: Alerts and notifications on page 537
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 2 On the central administration servers navigation bar, click the arrow next to Backup. Click New Backup Job.
779
Configuring CASO
3 4 5
In the task pane, under Settings, click Network and Security. Check Allow managed media server to use any network interface to access remote agents. Click OK.
Related Topics: Specifying backup networks on page 316
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. Related Topics: Distributed catalog on page 780 Centralized catalog on page 781 Replicated catalog on page 781 Changing the catalog location on page 781
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
780
Configuring CASO
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.
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.
781
Configuring CASO
See About catalog locations on page 780. To change the catalog location 1 2 On the central administration server, click the Media Servers tab. Right-click the managed media server for which you want to change the catalogs, and then click Properties. On the media server properties dialog box, click the Advanced tab. Choose one of the following options
Managed media server (distributed) 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. Central administration server (centralized) 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.
3 4
Related Topics: Restoring data by setting job properties on page 498 Setting catalog defaults on page 494.
782
Grouping managed media servers in pools
How centralized restore works on page 792 How CASO restores data that resides on multiple devices on page 793
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 servers 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 769 Grouping managed media servers in pools on page 783

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. 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 Central administration server
Media server pool
Use a media server pool to do any of the following:

Table A-3 To 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 Advantages of a media server pool Do this See Applying settings to all managed media servers in a pool on page 790. See Restricting the backup of a selection list to specific devices on page 785. See Viewing active job and alert statistics for a media server pool on page 789.
Copy configuration settings and logon See Copying configuration settings on page 156. information from a media server to all media servers in a pool
784
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. See Creating a backup job by setting job properties on page 267. Create a backup selection list. See Creating selection lists on page 244.
2 3
On the Properties pane, under Destination, click Device and Media. Check Restrict backup of the selection list to devices on the following media server or
media servers in a pool.
4 5
Select a media server or media server pool. Continue setting job properties for the job.
Related Topics: Creating a media server pool on page 785 About job delegation in CASO on page 783 Grouping managed media servers in pools on page 783
Creating a media server pool

You can group, or pool, media servers. To create a media server pool 1 2 On the central administration servers navigation bar, click Media Servers. On the task pane, under Media Server Pool Tasks, click New media server pool.
785
3 4 5
Enter a media server pool name and description. Select the media servers you want to add to the pool. Click OK.
Related Topics: Grouping managed media servers in pools on page 783 Adding managed media servers to a media server pool on page 786 Removing a managed media server from a media server pool on page 788 Renaming a media server pool on page 787 Deleting a media server pool on page 787
Adding managed media servers to a media server pool

You can add managed media servers to existing media server pools. To add managed media servers to a media server pool 1 2 3 4 5 On the central administration servers navigation bar, click Media Servers. Select a media server pool to which you want to add managed media servers. On the task pane, under Media Server Pool Tasks, click Add Media Server. Select the media servers you want to add to the pool. Click OK. The managed media server appears in the media server pool. Related Topics: Renaming a media server pool on page 787 Creating a media server pool on page 785 Deleting a media server pool on page 787 Removing a managed media server from a media server pool on page 788
786
Renaming a media server pool

You can rename a media server pool at any time. To rename a media server pool 1 2 3 4 On the central administration servers navigation bar, click Media Servers. Right-click the media server pool that you want to rename, and then click Rename. When prompted, enter a new name for the media server pool. Click OK. The media server pool is renamed. Related Topics: Adding managed media servers to a media server pool on page 786 Creating a media server pool on page 785 Removing a managed media server from a media server pool on page 788
Deleting a media server pool

You can delete a media server pool at any time. To delete a media server pool 1 2 3 On the central administration servers navigation bar, click Media Servers. Right-click the media server pool that you want to delete, and then click Delete. 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 786 Creating a media server pool on page 785 Removing a managed media server from a media server pool on page 788
787
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 2 3 4 5 On the central administration servers navigation bar, click Media Servers. Select a media server pool from which you want to remove a managed media server. On the right pane, select the managed media server that you want to remove. On the task pane, under Media Server Pool Tasks, click Remove Media Server. 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 786 Creating a media server pool on page 785 Deleting a media server pool on page 787
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 2 3 On the central administration servers navigation bar, click Media Servers. Right-click the media server pool, and then click Properties. Click the General tab. The Media Server Pool Properties General tab provides the following information:
Name Description Creation date 788 The name of the media server pool. The description of the media server pool. The date and time that this media server pool was created. Administrators Guide
Click OK.
Related Topics: Adding managed media servers to a media server pool on page 786 Creating a media server pool on page 785 Deleting a media server pool on page 787
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 2 3 On the central administration servers navigation bar, click Media Servers. Right-click the media server pool, and then click Properties. 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 jobs currently in progress in this media server pool. 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 warning alerts Number of active error alerts for this media server. Number of active warning alerts for this media server.
Number of active jobs View jobs...
789
Number of informational alerts View alerts...
Number of active information alerts for this media server. 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.
Click OK.
Applying settings to all managed media servers in a pool

You can apply the same settings to all of the managed media servers that are in a media server pool. To apply settings to all managed media servers in a pool 1 2 On the central administration servers navigation bar, click Media Servers. Select or create a media server pool that contains the managed media servers to which you want to apply the settings. Right-click the media server pool, and then click Properties. Click the Settings tab, and then check Apply these settings to all of the managed media servers in the pool. 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 See Setting defaults for managed media servers on page 770.
3 4
For thresholds for See Setting communication thresholds and active job status unresponsive managed updates on page 773. media servers, or for how often active job status updates are sent by the managed media server
790
Copying jobs instead of delegating jobs
For setting when job log See Copying logs and histories to the central administration and job history details are server on page 776. sent to the central administration server
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 servers 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 448 Setting defaults for managed media servers on page 770
791
Requirements for duplicate backup data and synthetic backup jobs in CASO
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. 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: Creating jobs using policies on page 440 Adding a duplicate backup template to a policy on page 444 Creating a synthetic backup by copying the example policy on page 839
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. When you use centralized restore 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. When you use centralized restore 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 do the following:

Submit the restore job on hold as a scheduled job 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: About media in Backup Exec on page 169
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.
793
How centralized restore works 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. For data stored on a single storage device 1. Data selections for restore are made at the central administration server.
2. For data that resides on one storage device....
3. CASO creates one restore job, which is delegated for processing at the managed media server where the data resides.
4. The job is delegated and processing begins.
794
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...
4.Jobs are delegated and processing begins.
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 796
795
Restoring from the central administration server

Before you create a restore job, review the best practices for centralized restore. See Best practices for centralized restore on page 795. To restore from the central administration server 1 Create a restore selection list. See Creating a restore selection list on page 520. 2 On the Restore Job Properties dialog box, in the task pane, under Source, click Device and Media. Enter or change the following information as appropriate:
Media or Resource Media Location Displays a list of media that is required for the restore, or the name of the resource that you selected for restore. 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 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.
Set other restore job properties from the Properties pane. See Restoring data by setting job properties on page 498.
796
Administering managed media servers
Click Run Now to start the restore operation.
Related Topics: How centralized restore works on page 792

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.
Table A-4 Item Name Media Servers view Description 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 797. Description Displays a user-defined description of the managed media server or the central administration server.
797
Administering managed media servers Table A-4 Item Communication Status Media Servers view Description Displays the status of communications between the managed media server and the central administration server. Statuses include the following:
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 775.
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 800. N/A - This status appears when the computer displayed in the Name column is a central administration server.
Media Server Status
Displays the present status of a managed media server. Valid statuses include the following:
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 Execs description of the media server. It can be either a managed media server or a central administration server.
798
Administering managed media servers Table A-4 Item Monitor Jobs Created Locally Media Servers view Description 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 770. Catalog Location Displays the location of the catalog. See Changing the catalog location on page 781. Version Operating System Operating System Build Displays the version of Backup Exec for Windows Servers that is installed and running on the media server. Displays the type of operating system that is installed and running on the media server. Displays the build number of the operating system that is installed on the media server.
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:
Table A-5 Icon CASO icons Description 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.
799
Administering managed media servers Table A-5 Icon CASO icons (continued) Description 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.
Managing jobs in CASO

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 442 Copying jobs instead of delegating jobs on page 791 Setting defaults for managed media servers on page 770
Recovering failed jobs in CASO

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.
800
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:
Table A-6 Error code 0xE000881B JOBDISPATCH 0xE000881D JOB_CASO_QUEUE FAILURE Error codes for Recovered Jobs custom error-handling rule Description The displayed message is: Job failed while being dispatched. The job will be recovered. 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.
0xE000881E The displayed message is: The job failed to start on the JOB_CASO_REMOTEMM destination managed media server, possibly because a S_STARTFAILURE database error occurred. The job will be recovered.
Related Topics: Error-handling rules on page 486 Custom error-handling rule for recovered jobs on page 490 Setting communication thresholds and active job status updates on page 773
801
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 servers 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 1 2 3 On the central administration server, from the navigation bar, click Media Servers. Select the managed media server you want to pause or resume. 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. 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 773 Administering managed media servers on page 797
802
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 797
Disabling and enabling communications

You can disable and enable managed media server communications from the central administration server. To disable and enable communications 1 2 3 On the central administration server, from the navigation bar, click Media Servers. Select the managed media server that you want to disable or enable. Do one of the following:
To disable communications, from the task pane, under Media Server Tasks, click Communication Enabled. Communications are disabled between the managed media server and the central administration server. The managed media servers 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.
803
The managed media servers 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 797 Setting communication thresholds and active job status updates on page 773
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 2 3 4 On the central administration server, from the navigation bar, click Media Servers. Select the managed media server on which you want to start or stop services. From the task pane, under Media Server Tasks, click Backup Exec Services. 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. Click this to start all Backup Exec services for the selected server. Click this to stop all Backup Exec services for the selected server. Click this to stop all Backup Exec services and then restart the services for the selected server. Click this to change service account information or to change startup options. Click this to refresh this dialog box. Click this to remove a selected server or servers from the server list.
Start all services Stop all services Restart all services Services credentials Refresh Remove Server(s)
804
Connecting to a remote managed media server

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 2 3 4 5 Start Backup Exec on the central administration server. From the navigation bar, click Media Servers. Select the managed media server to which you want to connect. From the task pane, under Media Server Tasks, click Connect to media server. If the managed media server name does not appear, enter the computer name in the Server field. Enter administrator or administrator equivalent logon information for the managed media server. In the Domain field, enter the computer name of the managed media server. 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. 9 To return to the central administration server console, close the managed media server console and restart Backup Exec on the central administration server.
7 8
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 2 Start Backup Exec on the central administration server. From the navigation bar, click Media Servers.
805
Disaster Recovery in CASO
3 4
Select the managed media server for which you want to view properties. On the task pane, under General Tasks, click Properties. For information on data displayed on the property tabs, see the following table:
General System Statistics License Information Settings Advanced See Viewing media server properties on page 139. See Viewing a media servers general properties on page 140. See Viewing a media servers system properties on page 141. See Viewing license information on page 120. See Setting defaults for managed media servers on page 770. See Changing the catalog location on page 781.

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. See About using IDR with the Central Admin Server Option on page 1535. 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.
806
These options include the following:
Yes, create the bootable tape image now. See Creating a bootable tape image on page 1512. No, connect to a central administration server - If a bootable tape drive is not detected on a managed media server, only this option appears.
You must locally back up and restore a central administration server.
807
808
Appendix
Symantec Backup Exec Advanced Open File Option

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. AOFO 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 809 Supported snapshot technologies on page 812 Best practices for using the Symantec Volume Snapshot Provider on page 822
About the Advanced Open File Option

When a job is submitted for backup with the Advanced Open File Option (AOFO) 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. 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.
809
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 822.
Advanced Open File Option with Symantec Snapshot Provider Backup Exec media server
3 2
Volume C: Snapshot C:
Original Word file (open) Start of backup job Data Block During the backup, data is changed A B 1 2 B i D End of backup job Data Block A 1 D 2 C 3 iii Changed file C 3 B ii Cache file for original data
The illustration represents the following: 1 - A backup begins for volume C on a Windows server using AOFO. 2 - A snapshot is taken of volume C, that provides a point-in-time record of the data.
810
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. AOFO 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. When the snapshot comes to a changed block, it replaces the changed block with the original data from the cache file. The snapshot sends the point-in-time data to Backup Exec. The data is then written to tape or disk. 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. When you select AOFO for a volume-level backup of Microsoft SQL or Exchange servers but do not use the database agents, the SQL or Exchange databases are excluded from the backup. When you select AOFO for backup of an Oracle server, databases are backed up automatically. To avoid duplicate backups of the database files, manually exclude the database files from the backup job. You can use AOFO on the same volume as a database to provide open file support for other applications. AOFO provides generic protection for flat files when Backup Exec agents are not used, and provides protection for Microsoft Outlook PST files. AOFO is not available for use with Extensible Firmware Interface (EFI) system partition backups. Related Topics: About the Backup Exec Exchange Agent on page 1179 Setting backup options for SQL on page 1326 About the Backup Exec Oracle Agent on page 1375 Setting defaults for the Advanced Open File Option for backup jobs on page 816
Appendix B, Symantec Backup Exec Advanced Open File Option 811
Best practices for using the Symantec Volume Snapshot Provider on page 822
Supported snapshot technologies

To use snapshot technologies with Backup Exec, you must install the Advanced Open File Option (AOFO). After making backup selections and selecting AOFO, you can configure Backup Exec to use the snapshot technologies installed on your computers. Backup Exec supports the following snapshot technologies:
Table B-1 Supported snapshot technologies Snapshot Technology
Operating System On Windows 2000/2003 only
Symantec Volume Snapshot Provider (VSP) Symantec Volume Snapshot Provider (VSP) is installed when you install AOFO.
Veritas Storage Foundation by Symantec, formerly known as Veritas Volume Manager (VM), FlashSnap Option Microsoft Volume Shadow Copy Service (VSS) 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 computers 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.
On Windows 2003 and later
Note If you turn off Active Directory, Microsoft Volume Shadow Copy Service (VSS) is not available. Jobs that require VSS fail.
Related Topics: Setting defaults for the Advanced Open File Option for backup jobs on page 816 Changing the default settings for the Symantec Volume Snapshot Provider on page 824 Using Snap Start on a Veritas Storage Foundation volume on page 821 Best practices for using the Symantec Volume Snapshot Provider on page 822 Symantec Volume Snapshot Provider cache file location on page 822
812
Requirements for using Advanced Open File Option

The computer for which you want to use the Advanced Open File Option (AOFO) requires the following:

AOFO must be installed. There must be enough free disk space on at least one volume to cache the data that changes during the backup job. See Adjusting the Symantec Volume Snapshot Provider cache file size on page 824. The file system must be NTFS, FAT32, or FAT. To use Microsoft Volume Shadow Copy Service (VSS), at least one NTFS partition is required. To protect remote and local computers, the Backup Exec Remote Agent for Windows Systems must be installed. The Remote Agent is installed by default on the media server when Backup Exec is installed. When you install AOFO on remote computers, it automatically installs the Remote Agent.
Note AOFO cannot be used on CD-ROM, floppy diskettes, or removable media. Additionally, the Checkpoint Restart option is not supported by AOFO. See Enabling or disabling checkpoint restart on page 700. When backing up encrypted files with AOFO on Windows 2000 computers, a drive letter for the snapshot appears 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. Related Topics: About the Advanced Open File Option on page 809 Installing the Remote Agent to an x64-based operating system on page 95 Setting defaults for the Advanced Open File Option for backup jobs on page 816 Changing the default settings for the Symantec Volume Snapshot Provider on page 824 Using Snap Start on a Veritas Storage Foundation volume on page 821 Best practices for using the Symantec Volume Snapshot Provider on page 822 Symantec Volume Snapshot Provider cache file location on page 822
Appendix B, Symantec Backup Exec Advanced Open File Option
813
Installing the Advanced Open File Option
Installing the Advanced Open File Option

The Advanced Open File Option (AOFO) is enabled from the media server when you enter the AOFO license key. 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 AOFO is also available, and can be installed with the 64-bit Remote Agent for Windows Systems. Caution Backup Exec for Windows Servers cannot use versions of AOFO that are previous to version 9.0. It is recommended that you uninstall versions previous to version 9.0. You must upgrade AOFO by purchasing and re-installing it on the local media server and on all remote computers on which it currently resides. You can install AOFO in the following ways:
Table B-2 To: AOFO installation methods Do the following:
Install AOFO on a See Installing Backup Exec options to the local computer on page 75. local media server Install AOFO on a remote media server See Installing Backup Exec options to remote computers on page 82.
Install the Remote See Installing the Remote Agent to an x64-based operating system on Agent and AOFO page 95. to an x64-based operating system Use a command See Using a command script to install the Remote Agent and AOFO on script to install page 97. the Remote Agent and AOFO to an x64-based operating system
814
Installing the Advanced Open File Option Table B-2 To: AOFO installation methods Do the following:
Use the Windows See Installing and uninstalling the Advanced Open File Option to remote command line to windows computers using the command line on page 815 Install and uninstall AOFO on remote servers
Related Topics: Upgrading Backup Exec options on remote computers on page 124
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 AOFO on a remote computer 1 2 Move to a remote server. Map a drive letter to the Backup Exec 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 4 Open a command prompt and enter the drive letter you mapped in step 2. 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: <media server name 1> <media server name 2> The -s parameter is used to run the install operation in silent mode, without the benefit of a user interface.
815
Setting defaults for the Advanced Open File Option for backup jobs
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. 5 The AOFO files are installed on the remote computer in the following directory: \Program Files\Symantec\Backup Exec\RAWS The AOFO installation log file is created in the following directory: \Documents and Settings\All Users\Application Data\Symantec\Backup Exec\Logs\bkupinst.log On Windows Vista/Server 2008, the AOFO installation log file is created in the following directory: \ProgramData\Symantec\Backup Exec\Logs\bkupinst.log 6 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 231
You can set the Advanced Open File Option (AOFO) defaults for each backup job, or you can set defaults that are used for every backup job. After a job is completed, check the section Backup Set Detail Information in the job log to make sure that AOFO was used during the backup.
816
To set AOFO defaults for backup jobs 1 Do one of the following:

To set AOFO backup options for a single backup job To set AOFO backup options for all 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 the appropriate options from the following:

Use Advanced Open File Select this check box to enable AOFO for backup jobs. Option If you do not select this option, jobs saved before you installed the Advanced Open File Option will continue to use the previous settings for backing up open files. Automatically select open file technology 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 AOFO, then the open file backup options apply (Never; If closed within 30 seconds; With a lock; Without a lock). See Advanced options for backup jobs on page 280. If you select AOFO and the Microsoft VSS provider, then Backup Exes uses the first available hardware, software, or system provider to perform the snapshot. For computers that run Windows Server 2003 or later, Backup Exec uses snapshot methods as follows:
If you select Shadow Copy Components, or Microsoft SQL or Exchange databases, Backup Exec uses Microsoft Volume Shadow Copy Service (VSS). In all other cases, Backup Exec uses Symantec Volume Snapshot Provider (VSP). If VSP is not installed, Backup Exec uses VSS.
Symantec Volume Snapshot Provider (Windows 2000 and 2003 only)
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. See Best practices for using the Symantec Volume Snapshot Provider on page 822.
817
Veritas Storage Foundation for Windows FlashSnap Option (Windows 2000 and 2003 only)
Veritas Storage Foundation for Windows FlashSnap Option was formerly known as Volume Manager (VM). Before you can use this option to back up volumes, you must use Veritas Enterprise Administrator (VEA) to snap-start the volumes. You must purchase VEA separately. See Using Snap Start on a Veritas Storage Foundation volume on page 821. 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.
Microsoft Volume Shadow Copy Service (Windows 2003 and later)
Microsoft Volume Shadow Copy Service (VSS) technology enables third-party hardware and software vendors to create snapshot add-ins for use with Microsofts 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 computers 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. Note If you turn off Active Directory, Microsoft Volume Shadow Copy Service (VSS) is not available. Jobs that require VSS fail.
818
Snapshot provider
Select one of the following options:
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 the following information applies:
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.
819
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. On computers that run Windows Server 2003, snapshots for volumes are created using VSP in the following conditions:
The selection list for a backup job contains volumes as well as Shadow Copy Components (SCC) The options Automatically select open file technology and Process logical volumes for backup one at a time are selected.
The Shadow Copy Components snapshots are created using VSS. This is reported in the job log and job history.
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.
If you are configuring the Advanced Open File Option as the default for all backup jobs, click OK. 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 231 About selection lists on page 243
Creating a backup job by setting job properties on page 267 About the Advanced Open File Option on page 809 Best practices for using the Symantec Volume Snapshot Provider on page 822 Changing the default settings for the Symantec Volume Snapshot Provider on page 824 Checking the job log when using AOFO on page 828
Using Snap Start on a Veritas Storage Foundation volume

You can use Snap Start to start a 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. To Snap Start a volume 1 2 3 Start Veritas Enterprise Administrator. In the left pane, expand the Localhost object. Under the Localhost object, expand the Volumes object, and then right-click the volume to Snap Start. On the short cut menu, select Snap, and then select Snap Start. 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.
4 5
Related Topics: Selecting data to back up on page 231 Backup strategies for SQL on page 1319 About the Backup Exec Exchange Agent on page 1179
821
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. To prevent the VSP cache file from excessively large growth on a disk during a backup operation, avoid the following:

Processes that write excessive data to the disk. Operations that copy large amounts of data to the disk.
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 809 Requirements for using Advanced Open File Option on page 813 Setting defaults for the Advanced Open File Option for backup jobs on page 816 Changing the default settings for the Symantec Volume Snapshot Provider on page 824 Adjusting the Symantec Volume Snapshot Provider cache file size on page 824 Checking the job log when using AOFO on page 828.
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.
Backup Exec locates the Symantec Volume Snapshot Provider (VSP) cache files based on the following:
Table B-3 Item How Backup Exec locates VSP cache files Description Notes 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 used the AOFO The location that you specified is wizard to specify a location used if it is not write-protected, and for the cache files if it is not part of the resources that are being snapped.
If you have not specified a location for the cache file
Backup Exec will attempt to locate These volumes must meet the cache file on volumes other than the following requirements: the source volumes. The volumes must be If the criteria for the non-source fixed drives. volumes are not met, the cache file is The volumes must use a created on the source volume. 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 must meet the following requirements:
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 809 Supported snapshot technologies on page 812 Setting defaults for the Advanced Open File Option for backup jobs on page 816 Checking the job log when using AOFO on page 828
Appendix B, Symantec Backup Exec Advanced Open File Option 823
Changing the default settings for the Symantec Volume Snapshot Provider
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. 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. See Changing the default settings for the Symantec Volume Snapshot Provider on page 824 Related Topics: Setting defaults for the Advanced Open File Option for backup jobs on page 816 Symantec Volume Snapshot Provider cache file location on page 822
To change the default settings for the configuration options for the Symantec Volume Snapshot Provider (VSP), use the Advanced Open File Option wizard. This wizard helps you configure VSP for use with AOFO on each Windows 2000/2003 server that AOFO is installed on.
824
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. 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 3 Click Next to continue past the Welcome page. 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 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. To specify alternate locations for the cache files To change or delete existing cache file locations 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.
825
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 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. See Symantec Volume Snapshot Provider cache file location on page 822. Initial size of the cache file Sets the initial size of the cache file. (1 - 100 percent): 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 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.
826
Maximum size that the cache file can grow to:
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.
Number of seconds during which there can be no disk activity before the snapshot is created
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 820.
827
Checking the job log when using AOFO
Number of seconds that the application tries to obtain the minimum quiet time, after which the job fails
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.
Review the summary screen. If the configuration is satisfactory, click Finish. To make more changes, click Back. 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 809 Setting defaults for the Advanced Open File Option for backup jobs on page 816 Best practices for using the Symantec Volume Snapshot Provider on page 822 Symantec Volume Snapshot Provider cache file location on page 822

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 AOFO fails on initialization, the backup still runs but the job is logged as Completed with Exceptions in the job log. If AOFO fails during the backup of a device, that backup set is terminated and is reported as an error. Note If a job that uses the Symantec Volume Snapshot Provider fails, an active image may remain on the computer. The active image may cause subsequent jobs to fail with an unknown error. If this occurs, restart the computer to clear the active image. Related Topics: Setting defaults for the Advanced Open File Option for backup jobs on page 816
828
Best practices for using the Symantec Volume Snapshot Provider on page 822 Symantec Volume Snapshot Provider cache file location on page 822
829
830
Appendix
Symantec Backup Exec Advanced Disk-based Backup Option

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 the following:
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.
831
Installing the Advanced Disk-based Backup Option
Related Topics: About the synthetic backup feature on page 832 About true image restore on page 846 About offhost backup on page 855
Installing the Advanced Disk-based Backup Option

ADBO is enabled on the media server when you enter the ADBO license key. See Installing Backup Exec options to the local computer on page 75.
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 as follows:
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.
832
About the synthetic backup feature Baseline backup is run from the synthetic backup policy Network Backup Exec media server Resource selected for backup from the media server
Tape library Storage device
Baseline backup (can be backed up to disk or tape)
Incremental backups are run from the synthetic backup policy Network Backup Exec media server Incremental backups
Resource selected for backup from the media server Baseline backup (can be backed up to disk or tape)
Tape library Storage device
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option
833
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 Incremental backups Synthetic backup Storage device
Resource selected for backup from the media server Baseline backup (can be backed up to disk or tape)
Tape library
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. SeeAbout duplicate backup set templates on page 443. Related Topics: Best practices for synthetic backup on page 836 Creating a synthetic backup on page 838 Collecting additional information for synthetic backup and true image restore on page 837
What you can back up with synthetic backup

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.
834
Requirements for synthetic backup
Related Topics: Requirements for synthetic backup on page 835 Creating a synthetic backup on page 838

Before you create a synthetic backup, review the following information:

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. See Creating a synthetic backup by copying the example policy on page 839. 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. See Creating a synthetic backup by adding templates to a policy on page 840. This option also enables true image restore for backup sets. See About true image restore on page 846. 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). Only file system resources are supported for synthetic backup. See What you can back up with synthetic backup on page 834.
Following are limitations when running synthetic backup:
835
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. See Requirements for duplicate backup data and synthetic backup jobs in CASO on page 792.
The option Checkpoint Restart is not supported when the option Collect additional information for synthetic backup and for true image restore is selected. See Using checkpoint restart on Microsoft Cluster Server failover on page 699.
Related Topics: Collecting additional information for synthetic backup and true image restore on page 837 Creating a synthetic backup by copying the example policy on page 839 Creating a synthetic backup by adding templates to a policy
Best practices for synthetic backup

The following best practices are recommended:
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. See Setting template rules on page 436. 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 832 Creating a synthetic backup by copying the example policy on page 839
836
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 832 Creating a synthetic backup on page 838 Adding a backup template to a policy on page 430 About true image restore on page 846
837
Creating a synthetic backup

A synthetic backup can only be created in a policy. You can use the following methods 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 838. 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 839. 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 840.
Before creating a synthetic backup, review the requirements for synthetic backups. See Requirements for synthetic backup on page 835. Related Topics: About the synthetic backup feature on page 832 Best practices for synthetic backup on page 836
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 the following:

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 2 3 On the navigation bar, click Job Setup. In the task pane, under Policy Tasks, click New policy using wizard. On the Welcome page, click Next to continue, and follow the instructions in the wizard to complete the policy.
838
All of the necessary job templates for synthetic backup will be created in the new policy. Related Topics: About the synthetic backup feature on page 832 What you can back up with synthetic backup on page 834 Requirements for synthetic backup on page 835 Best practices for synthetic backup on page 836 Creating a synthetic backup by copying the example policy on page 839 Creating a synthetic backup by adding templates to a policy on page 840
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. See Using an example policy on page 427. Note In order for the example policy for a synthetic backup to be displayed, you must configure a backup-to-disk folder, and then re-create the 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. You can view the synthetic backup policy example in the Job Setup view. 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.
839
In the example policy, a full backup template is included to act as the baseline. This template should be the first template to run, and it only needs to run once. The template that runs first is called Template A. The following rules were added:
<Template A> must complete at least once before any other templates will be allowed to start. Baseline Backup is selected as <Template A>. If start times conflict, <Template A> will start and upon completion, starts <Template B>. Incremental Backup is selected as <Template A> and Synthetic Backup is selected as <Template B>. Run <Template A> only once. Baseline Backup is selected as <Template A>.
Related Topics: What you can back up with synthetic backup on page 834 Requirements for synthetic backup on page 835 Setting template rules on page 436 About the synthetic backup feature on page 832 Best practices for synthetic backup on page 836
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 the requirements and the list of items you can back up with synthetic backup. See Requirements for synthetic backup on page 835. See What you can back up with synthetic backup on page 834. To create a synthetic backup by adding templates to a policy 1 2 3 On the navigation bar, click Job Setup. On the task pane, under Policy Tasks, click New policy. Type a policy name and description for this synthetic backup policy, and then click New template.
840
The Template Selection dialog box appears. 4 5 Select Backup Template, and then click OK. 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.
Select the Collect additional information for synthetic backup and for true image restore option. (Optional) Select the Use the Microsoft Change Journal if available option. See Using the Windows NTFS Change Journal to determine changed files on page 230. 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.
On the Properties pane, under Settings, click Network and Security. 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. See About encryption on page 330. 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. See Enabling managed media servers to use any available network interface card on page 779.
Under Frequency, click Schedule and set the scheduling options you want to use. See Setting the schedule for a template on page 432. 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.
841
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. 10 Select other options as appropriate, and then click OK. See Adding a backup template to a policy on page 430. 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 842 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. See Using the Windows NTFS Change Journal to determine changed files on page 230. 16 Under Frequency, click Schedule and set the scheduling options you want to use. See Setting the schedule for a template on page 432. 17 Select other options as appropriate, and then click OK. See Adding a backup template to a policy on page 430. 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.
842
19 On the Properties pane, under Destination, select Device and Media, and complete the appropriate options. See Device and media options for backup jobs and templates on page 272. 20 On the Properties pane, under Settings, click General, and complete the appropriate options as follows:
Template name Backup set description Preferred source device Type the name for this job template. Type a description of the information you are backing up. 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.
843
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 573. 23 Do one or both of the following:
To set scheduling options Under Frequency, click Schedule. See Setting the schedule for a template on page 432.
To create template See (Recommended) Create template rules to run job templates for rules synthetic backup on page 844.
(Recommended) Create template rules to run job templates for synthetic backup 1 Review the documentation about template rules. See Setting template rules on page 436 before creating template rules. 2 3 On the New Policy dialog box, under Template rules, click New Rule. 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 <Template A> only once. Click the Template A is: 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 5.
4 5
Click New Rule again to add another rule. On the Template Rule Properties dialog box, click the template rules drop down list, and then select <Template A> must complete at least once before any other templates will be allowed to start. Click the Template A is: drop down list, select the template name of the baseline backup, and then click OK. Click New Rule again to add another rule. On the Template Rule Properties dialog box, click the template rules drop down list, and then select If start times conflict, <Template A> will start and upon completion, starts <Template B>.
7 8
844
Click the Template A is: list, and then select the template name of the incremental backup.
10 Click the Template B is: list, and then select the template name of the synthetic backup, and then click OK. 11 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. See Creating jobs using policies on page 440. Related Topics: About the synthetic backup feature on page 832 What you can back up with synthetic backup on page 834 Requirements for synthetic backup on page 835 Best practices for synthetic backup on page 836
845
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.
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:
846
Note 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.
Table C-1 Day Example table of files backed up because true image restore is enabled Type of Backup Files Backed Up in C:\user\doc file1 file2 file2 file2 file2 dirA\fileA dirA\fileA dirA\fileA dirB\fileB file3
December 1, Full 2006
December 2, Incremental file1 2006 December 3, Incremental file1 2006 December 4, Incremental file1 2006
---------------- ------------------------------- ----------------
---------------- ---------------- ---------------- file4 -
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. For example, the following files and directories are included:

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.
847
The following list include the files and directories that existed.

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 837 Best practices for true image restore on page 849 True image catalogs on page 851 Creating a policy for true image restore on page 850 Restoring a backup set enabled for true image restore on page 852 Troubleshooting tips for true image restore on page 853
848
Requirements for running true image restore

Refer to the following list for the requirements for running true image restore:

Backup Exec must be installed on the media server. The Backup Exec Remote Agent 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. 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. Windows and Unix file system backups. Windows system state backups.
True image restore supports the following resource types:

Related Topics: Collecting additional information for synthetic backup and true image restore on page 837 True image catalogs on page 851 Restoring a backup set enabled for true image restore on page 852 Troubleshooting tips for true image restore on page 853
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 846 Troubleshooting tips for true image restore on page 853
849
Creating a policy for true image restore
Creating a policy for true image restore

Before you can perform a true image restore, you must do the following:
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.
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. See Best practices for true image restore on page 849. See Creating a new policy on page 424. 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 851. 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 837 About true image restore on page 846 Requirements for running true image restore on page 849 Restoring a backup set enabled for true image restore on page 852 Troubleshooting tips for true image restore on page 853
850
Creating a policy for true image restore by using the Policy Wizard
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. See To create a policy using the Policy Wizard on page 425. Before you create templates, review the best practices for true image restore. See Best practices for true image restore on page 849. Related Topics: About true image restore on page 846 Requirements for running true image restore on page 849 Restoring a backup set enabled for true image restore on page 852 Troubleshooting tips for true image restore on page 853
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 837 About true image restore on page 846 Troubleshooting tips for true image restore on page 853
851
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. 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 or later 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.
852
Restoring a backup set enabled for true image restore True image restore icons
True image icon for backup sets
Icon indicates that the file is in a prior image
Related Topics: About true image restore on page 846 Requirements for running true image restore on page 849 Creating a policy for true image restore on page 850 True image catalogs on page 851 About duplicate backup set templates on page 443
Troubleshooting tips for true image restore

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. The following tables lists troubleshooting tips:
Table C-2 Problem The job fails with the error Error retrieving catalog information. Troubleshooting tips for true image restore operations Explanation 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.
You cannot expand the View by If any prior catalogs are missing, the restore view cannot Resource restore selections to display be expanded. the true image restore selections.
853
Related Topics: About true image restore on page 846 Requirements for running true image restore on page 849 True image catalogs on page 851
854
About offhost backup

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.
Offhost Backup
Remote computer Backup Exec media server
Attached SAN device
1 3
Tape library
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.
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.
855
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. SQL Agent backups for Microsoft SQL Server 2000 databases. Exchange Agent backups for Microsoft Exchange Server 2003 (Service Pack 1)/ 2007 instances that run on Windows Server 2003. Support for the option to use Backup Exec Granular Recovery Technology for Exchange Agent backups is included. The option Checkpoint Restart. Volumes that run Windows BitLocker Drive Encryption. The option Use the Microsoft Change Journal if available for differential and incremental backups, unless you select the modified time method. Exchange Agent backup jobs that are configured to use Symantec Continuous Protection Server (CPS).
ADBO offhost backup does not support the following:

Related Topics: Requirements for offhost backup when using the Veritas Storage Foundation for Windows Provider on page 858 Setting offhost backup options for a backup job on page 861 Troubleshooting the offhost backup on page 867 Browsing remote computers for installed snapshot providers on page 860 Restoring offhost backup data on page 866 Setting default backup and restore options for Exchange data on page 1207 About using GRT-enabled backups to restore individual items from the Information Store on page 1190 Using the ADBO with the SQL Agent on page 1325
856
Requirements for offhost backup

The following are requirements for offhost backup:
Table C-3 Item Media server Offhost backup requirements Description The following must be installed on the media server:

Backup Exec for Windows Servers Backup Exec Advanced Disk-based Backup Option
Remote computer Media server and the remote computer
The Backup Exec Remote Agent for Windows Systems must be installed on the remote computer. The following must be installed on both the media server and on the remote computer:
Microsoft Windows Server 2003 with Service Pack 1 and the most recent Volume Shadow Copy Services (VSS) patches or Windows Server 2008. The Microsoft VSS hardware or software snapshot provider that you want to use. Otherwise, the snapshots of the volumes cannot be deported to the media server. Ability to access the disks that are shared between the media server and the remote computer.
GRT-enabled offhost backup of Exchange Server resources
The following requirements must be met:
Microsoft Exchange Server 2003 (Service Pack 1) or Exchange Server 2007 instances that run on Windows Server 2003 must be installed on the Exchange Server. Requirements for using the Exchange Agent on page 1180 About using GRT-enabled backups to restore individual items from the Information Store on page 1190 If the destination device is tape or a backup-to-disk folder on a network share, Backup Exec must store data temporarily during the backup job. Specify a path to an NTFS volume on the local media server for the temporary storage location. See Setting default backup options on page 307.
Related Topics: Using checkpoint restart on Microsoft Cluster Server failover on page 699
Appendix C, Symantec Backup Exec Advanced Disk-based Backup Option 857
About offhost backup on page 855 Best practices for using offhost backup on page 859 Troubleshooting the offhost backup on page 867 Browsing remote computers for installed snapshot providers on page 860
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. See Using Snap Start on a Veritas Storage Foundation volume on page 821. 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. 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 867 Browsing remote computers for installed snapshot providers on page 860
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. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2 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. 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 783. 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
859
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 691. Related Topics: About offhost backup on page 855 Requirements for offhost backup on page 857 Requirements for offhost backup when using the Veritas Storage Foundation for Windows Provider on page 858 Setting offhost backup options for a backup job on page 861 Browsing remote computers for installed snapshot providers on page 860 Troubleshooting the offhost backup on page 867
Browsing remote computers for installed snapshot providers

You can view the snapshot providers that are installed on a remote computer before you run an offhost backup for selected resources. 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. To browse remote computers for installed snapshot providers 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Properties pane, under Source, click Selections.
860
In the backup selections pane, do the following in the order listed:

Right-click the remote computer that contains the volumes you want to back up. Click List Snapshot Providers.
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 858 Requirements for offhost backup on page 857 Best practices for using offhost backup on page 859 Setting offhost backup options for a backup job on page 861
Setting offhost backup options for a backup job

You can set offhost backup options for each backup job. For Exchange Server resources, you can create a GRT-enabled offhost backup job. See Configuring a GRT-enabled offhost backup for Exchange resources on page 865. Note If the Central Admin Server Option (CASO) is installed, do not let the central administration server delegate the job. It can delegate the job to a media server that does not have offhost capability. You must manually select the destination device for the CASO jobs that use the offhost backup method. See Grouping managed media servers in pools on page 783 To set offhost backup options for a backup job 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Properties pane, under Settings, click Advanced Disk-based Option.
861

Use offhost backup to move backup processing from remote computer to media server 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. See About offhost backup on page 855. Snapshot provider Select one of the following options:
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:

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.
If any of the selected Select one of the following options: resources do not support Continue the backup job (offhost backup is not used): Select this offhost backup 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.
862
Process logical volumes Enables the backup of multiple volumes in one job, while creating a for offhost backup one snapshot of only one logical volume at a time. To ensure database at a time 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 855 Requirements for offhost backup on page 857 Setting default offhost backup options on page 863 Requirements for offhost backup when using the Veritas Storage Foundation for Windows Provider on page 858 Best practices for using offhost backup on page 859 Troubleshooting the offhost backup on page 867
Setting default offhost backup options

You can set the defaults that are used for every backup job. Note If the Central Admin Server Option (CASO) is installed, do not let the central administration server delegate the job. It can delegate the job to a media server that does not have offhost capability. You must manually select the destination device for the CASO jobs that use the offhost backup method. See Grouping managed media servers in pools on page 783. To set default offhost backup options 1 2 On the Tools menu, click Options. In the Properties pane, under Job Defaults, click Advanced Disk-based Backup Option.
863

Use offhost backup to Select this check box to use the offhost backup method for volumes move backup processing in all backup jobs. All requirements for offhost backup must be met. from remote computer See About offhost backup on page 855. to media server Snapshot provider Select one of the following options:
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:

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.
If any of the selected Select one of the following options: resources do not support Continue the backup job (offhost backup is not used): Select this offhost backup 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.
864
Configuring a GRT-enabled offhost backup for Exchange resources
Process logical volumes Enables the backup of multiple volumes in one job, while creating a for offhost backup one snapshot of only one logical volume at a time. To ensure database at a time 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: Setting offhost backup options for a backup job on page 861 Configuring a GRT-enabled offhost backup for Exchange resources on page 865

You can enable the Backup Exec Granular Recovery Technology (GRT) option for offhost backups of Exchange resources. When you select the GRT option for a backup, Backup Exec collects additional information for the catalog. This information lets you restore individual mailboxes, mail messages, and public folders from Information Store backups. Offhost backup does not support the Exchange Server backup jobs that are configured to use Symantec Continuous Protection Server (CPS). You should perform consistency checks before you run an offhost backup. See Perform consistency check before backup when using Microsoft Volume Shadow Copy Service (VSS) snapshot provider on page 1215. To configure a GRT-enabled offhost backup for Exchange resources 1 Create an Exchange backup job. See Backing up Exchange on page 1211. 2 Check Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of
individual mailboxes, mail messages, and public folders from Information Store backups.
Specify a path to an NTFS volume on the local media server if you send the job to one of the following devices:
865

A tape A backup-to-disk folder that is on a network share
See Setting default backup options on page 307. 4 Set the offhost backup options. See Setting offhost backup options for a backup job on page 861. 5 Select Automatic - Use hardware if available; otherwise use software. The options for job disposition are not available. 6 If you include resources that are not supported for offhost backup, check the following check box: Process logical volumes for offhost backup one at a time. This allows the job to complete with errors. Schedule or start the backup job.
Related Topics: Requirements for offhost backup on page 857 Snapshot and offhost backups with the Exchange Agent on page 1191 Troubleshooting Exchange Agent snapshot and offhost jobs on page 1193 Setting default offhost backup options on page 863 About using GRT-enabled backups to restore individual items from the Information Store on page 1190 Requirements for using backup-to-disk folders with GRT-enabled backup operations on page 407
Restoring offhost backup data

Use a standard restore job to restore data that is backed up with the offhost backup method. Data is restored directly from the backup media to the original volumes on the remote computer. Additional requirements must be met to restore Exchange data from a GRT-enabled offhost backup that is on tape. See About restoring individual items from Information Store backups on page 1229. Related Topics: Restoring data by setting job properties on page 498
866
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. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2 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 as follows:

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. See Requirements for offhost backup on page 857. See Requirements for offhost backup when using the Veritas Storage Foundation for Windows Provider on page 858.
Other factors to consider are as follows:
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 the following setup issues that are common to all providers may cause offhost backup to fail:
Volumes are not shared
867
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 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 783. Clusters
868
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 How Backup Exec works in a Microsoft Cluster Server on page 692. 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, ensure that the RM Shadow Copy Provider for Volume Snapshot Service is present and running. 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 821. 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.
869
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.
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 that can occur when using Hitachi hardware include the following:
870
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 857 Requirements for offhost backup when using the Veritas Storage Foundation for Windows Provider on page 858 Best practices for synthetic backup on page 836
871
872
Appendix
Symantec Backup Exec Active Directory Recovery Agent

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. With ADRA you can use Granular Recovery Technology (GRT) to restore individual Active Directory objects and attributes without performing an authoritative or non-authoritative full restore. You can also restore individual Active Directory Application Mode (ADAM) and Active Directory Lightweight Directory Services (AD LDS) objects and attributes. Related Topics: Requirements for the Active Directory Recovery Agent on page 873 Installing the Active Directory Recovery Agent on page 875 About the Active Directory Recovery Agent on page 875 About restoring individual Active Directory and ADAM/AD LDS objects on page 879
Requirements for the Active Directory Recovery Agent

Review the following requirements before you use Granular Recovery Technology (GRT) to restore individual objects and attributes using the Active Directory Recovery Agent:
To use a backup-to-disk folder as the destination device for a full mode backup, the backup-to-disk folder must reside on a local NTFS volume. SeeRequirements for using backup-to-disk folders with GRT-enabled backup operations on page 407.
You must have a full mode backup of the ADAM/AD LDS or the Windows System State (where Active Directory is installed).
873
Requirements for the Active Directory Recovery Agent
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 reanimation of objects from the Active Directory Deleted Objects container on a Windows 2000 domain controller. Symantec recommends that you use the Remote Agent on a Windows 2003 domain controller to run GRT restore jobs of deleted objects. Deleted objects can only be restored using an agent on a Windows 2000 domain controller if the Recreate deleted object check box is checked. This check box is located on the Restore Job Properties dialog box after you select the Microsoft Active Directory node under Settings.
Windows Server 2003 with Service Pack 1 or later Windows Server 2003 R2 Windows Server 2008
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 run the Backup Exec Remote Agent for Windows Systems version 12 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. Make sure you select the option Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual objects from Active Directory backups. Individual attributes and properties cannot be restored from full Active Directory and ADAM/AD LDS backups if you do not select this option during backup. Note You cannot restore individual objects and attributes from Active Directory backups for a Read-Only Domain Controller (RODC). You should do GRT backups and restores of the Active Directory to a writable centralized datacenter domain controller.
Related Topics: Installing the Active Directory Recovery Agent on page 875
Installing the Active Directory Recovery Agent
About the Active Directory Recovery Agent on page 875 About restoring individual Active Directory and ADAM/AD LDS objects on page 879
Installing the Active Directory Recovery Agent

ADRA is installed locally as a separate, add-on component of Backup Exec for Windows Servers. See Installing Backup Exec options to the local computer on page 75.
About the Active Directory Recovery Agent

ADRA works with backups of the Windows System State (where Active Directory is installed) and ADAM/AD LDS. 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. You can also use ADRA to restore individual ADAM/AD LDS objects and attributes. If multiple ADAM/AD LDS instances are backed up, each instance appears under the Active Directory Application Mode node.
View by Resource view - ADAM/AD LDS and Active Directory ADAM/AD LDS
Active Directory
Individual Active Directory objects
ADRA also lets you restore tombstoned objects from the Active Directory Deleted Objects container in the following situations:
Their tombstone lifetimes have not passed.
Appendix D, Symantec Backup Exec Active Directory Recovery Agent
875
Setting default backup and restore options for the Active Directory Recovery Agent

They have not been purged from the Deleted Objects container. You are restoring to a Windows Server 2003/2008/XP/X64 system.
Symantec recommends that Active directory and ADAM/AD LDS backups be backed up to a backup-to-disk folder before you back them up to tape. This strategy provides you with shorter backup windows. It also lets you administer Active Directory or ADAM/AD LDS without requiring the individual cataloging of the backed up objects and properties. When you back up any Windows Active Directory or ADAM/AD LDS application database directly to tape, objects and properties that are 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/AD LDS database and the cataloging of the individual Active Directory or ADAM/AD LDS objects occurs after the snapshot is performed. Since the catalog operation catalogs objects and properties from the live Active Directory or ADAM/AD LDS database, object and property changes can occur after the snapshot was taken. Related Topics: About restoring individual Active Directory and ADAM/AD LDS objects on page 879 About recreating purged Active Directory and ADAM/AD LDS objects on page 883
You can set default job options for all Active Directory and ADAM/AD LDS backup and restore jobs. You also can override these defaults when you set up Active Directory and ADAM/AD LDS backup and restore jobs. To set backup and restore job defaults for the Active Directory Recovery Agent 1 2 On the Tools menu, click Options. In the Properties pane, under Job Defaults, click Microsoft Active Directory.
876

Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual objects from Active Directory backups Check this option to enable the restore of individual items from full backups of the Active Directory or ADAM/ AD LDS. You should select a backup-to-disk folder on an NTFS volume on the local media server as the destination device. See Device and media options for backup jobs and templates on page 272. See Requirements for using backup-to-disk folders with GRT-enabled backup operations on page 407. Perform consistency check before backup when using Microsoft Volume Shadow Copy Service (VSS) snapshot provider Select this option to check snapshots for data corruption. This option applies only to snapshots that are performed by the Microsoft Volume Shadow Copy Services (VSS). If corrupt data is found and this option is not selected, the job fails. Continue with backup if consistency check fails 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 a backup of the database in its current state is better than no backup at all. Or you may want the job to continue if you back up a large database that may have only a small problem.
Recreate deleted objects that Select this option to try to recreate deleted objects if cannot be restored from the Active both of the following event occurred: Directory Deleted Objects container The objects tombstone lifetimes have passed.
The objects were purged from the Active Directory Deleted Objects container.
Note You must use this option to restore deleted objects on a computer that runs Windows 2000. See About recreating purged Active Directory and ADAM/AD LDS objects on page 883.
Click OK.
Related Topics: About restoring individual Active Directory and ADAM/AD LDS objects on page 879 About recreating purged Active Directory and ADAM/AD LDS objects on page 883
877
Backing up Active Directory or ADAM/ AD LDS
Backing up Active Directory or ADAM/ AD LDS

Use the following steps to back up Active Directory or ADAM/AD LDS. To back up Active Directory or ADAM/AD LDS 1 2 3 On the navigation bar, click the down arrow next to Backup. Click New Backup Job. Do one of the following:
To back up Active Directory
On the View by Resources tab, under All Resources, expand the name of the computer that contains the Active Directory that you want to back up. Click System State. In the Properties pane, under Settings, click Microsoft Active Directory. In the View by Resources tab, expand Favorite Resources. Expand Windows Systems. Expand the name of the computer where ADAM/AD LDS is installed. Select ADAM/AD LDS.
To back up ADAM/AD LDS

Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual objects from Active Directory backups Check this option to enable the restore of individual items from full backups of the Active Directory or ADAM/ AD LDS. You should select a backup-to-disk folder on an NTFS volume on the local media server as the destination device. See Device and media options for backup jobs and templates on page 272. See Requirements for using backup-to-disk folders with GRT-enabled backup operations on page 407. Perform consistency check before backup when using Microsoft Volume Shadow Copy Service (VSS) snapshot provider Select this option to check snapshots for data corruption. This option applies only to snapshots that are performed by the Microsoft Volume Shadow Copy Services (VSS). If corrupt data is found and this option is not selected, the job fails.
878
About restoring individual Active Directory and ADAM/AD LDS objects
Continue with backup if consistency check fails
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 a backup of the database in its current state is better than no backup at all. Or you may want the job to continue if you back up a large database that may have only a small problem.

To run the job now To schedule the job to run later Click Run Now. Do the following in the order listed:

In the Properties pane, under Frequency, click Schedule. Set the scheduling options. Click Submit.

Before starting the restore job, you should review information on finding and viewing specific data to restore, as well as on details on restore options and restore jobs. See Restoring data on page 493. When you restore Active Directory and ADAM/AD LDS 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/AD LDS restore job by entering a path in the Advanced node found under Settings on the Restore Job Properties pane. System volumes should not be used as a staging location because of the potentially large file sizes that are created on the disk specified in the staging location path. 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.
Appendix D, Symantec Backup Exec Active Directory Recovery Agent 879
By default, ADRA restores deleted Active Directory or ADAM/AD LDS 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/AD LDS 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/AD LDS databases. Following are requirements for backup and restore operations when an Active Directory or ADAM/AD LDS backup is enabled for the restore of individual items:
Table D-1 Task If the destination device for the backup job is a backup-to-disk folder If you create full backups Requirements for backup and restore operations for Active Directory or ADAM/AD LDS Requirements See About using a backup-to-disk folder for GRT-enabled backup operations on page 406. The full 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 Active Directory or ADAM/AD LDS, the full job template does not have to be in a policy. See Creating a new policy on page 424. If you restore individual items from an Active Directory or ADAM/AD LDS backup set that is on a device other than a backup-to-disk folder 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.
When restoring Active Directory user objects, you must reset the objects user password and then re-enable the objects user account. For ADAM/AD LDS user objects, you must reset the objects user password and then re-enable the objects user account. For Active Directory user objects, use the Microsoft Active Directory Users and Computers application. For ADAM/AD LDS user objects, use ADSI Edit. For Active Directory computer objects, you must reset the objects account. See Resetting the Active Directory computer object account on page 886. ADRA does not support reanimation 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. Note Some objects in the Active Directory Configuration Partition node cannot be reanimated from the Active Directory Deleted Objects container. However, recreated objects may not be recognized by some applications. For more information, see your Microsoft Active Directory documentation. Related Topics: Inventorying media on page 368 Cataloging media while reviewing devices or media on page 196 Restoring individual objects from an Active Directory backup on page 881 Path on media server for staging temporary restore data when using Backup Exec Granular Recovery Technology (GRT) to restore individual items from tape on page 508 Restoring individual objects from an ADAM/AD LDS backup on page 882 About recreating purged Active Directory and ADAM/AD LDS objects on page 883 Resetting the Active Directory computer object account on page 886
Restoring individual objects from an Active Directory backup

Use ADRA to restore individual objects from Active Directory. To restore individual objects from an Active Directory backup 1 2 3 On the navigation bar, click the down arrow next to Restore. Click New Restore Job. 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 5 6 Double-click System State. Double-click the most recent System State snapshot. Double-click Active Directory.
881
7 8
In the Results pane, select the appropriate object or objects. If you are restoring from tape, do the following:

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 tape.
Click Run Now to start the restore job or select other restore options from the Properties pane. Any Active Directory or ADAM/AD LDS 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 objects user password and re-enable the objects user account. If you restored a computer object, you must reset the account for it. Related Topics: Resetting the Active Directory computer object account on page 886 Restoring individual objects from an ADAM/AD LDS backup on page 882 About recreating purged Active Directory and ADAM/AD LDS objects on page 883
Restoring individual objects from an ADAM/AD LDS backup

Use ADRA to restore individual objects from ADAM/AD LDS. To restore individual objects from an ADAM/AD LDS backup 1 2 3 4 5 6
882
On the navigation bar, click the down arrow next to Restore. Click New Restore Job. In the View by Resource pane, double-click Active Directory Application Mode. Double-click the appropriate ADAM/AD LDS instance. Double-click the appropriate backup set. In the Results pane, select the appropriate object or objects.
About recreating purged Active Directory and ADAM/AD LDS objects
If you are restoring from tape, do the following:

Click Run Now to start the restore job or select other restore options from the Properties pane. Any Active Directory or ADAM/AD LDS 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.
If you restored a deleted user object, use the ADSI Edit application to reset the objects user password and re-enable the objects user account.
Related Topics: Restoring individual objects from an Active Directory backup on page 881 About recreating purged Active Directory and ADAM/AD LDS objects on page 883

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, you should be aware of the following:
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 884 Recreating purged ADAM/AD LDS objects on page 885 About restoring individual Active Directory and ADAM/AD LDS objects on page 879
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 2 3 On the navigation bar, click the down arrow next to Restore. Click New Restore Job. 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 5 6 7 8 9 Double-click System State. Double-click the most recent System State snapshot. Double-click Active Directory. In the Results pane, select the appropriate objects. On the Properties pane, under Settings, click Microsoft Active Directory. Check Recreate deleted objects that cannot be restored from the Active Directory Deleted Objects container.
10 If you are restoring from tape, do the following:

11 Click Run Now to start the restore job or select other restore options from the Properties pane. Any Active Directory or ADAM/AD LDS 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.
884
12 Use the Microsoft Active Directory Users and Computers application to reset the objects user password and re-enable the objects user account. Related Topics: Recreating purged ADAM/AD LDS objects on page 885 About restoring individual Active Directory and ADAM/AD LDS objects on page 879 Resetting the Active Directory computer object account on page 886
Recreating purged ADAM/AD LDS objects

You can attempt to recreate deleted ADAM/AD LDS objects after they have been purged from the Active Directory Deleted Objects container by restoring the object from a prior ADAM/AD LDS backup. To recreate purged ADAM/AD LDS objects 1 2 3 4 5 6 7 8 On the navigation bar, click the down arrow next to Restore. Click New Restore Job. In the View by Resource pane, double-click Active Directory Application Mode. Double-click the appropriate ADAM/AD LDS instance. Double-click the appropriate backup set. In the Results pane, select the appropriate objects. On the Properties pane, under Settings, click Microsoft Active Directory. Check Recreate deleted objects that cannot be restored from the Active Directory Deleted Objects container. If you are restoring from tape, do the following:

10 Click Run Now to start the restore job or select other restore options from the Properties pane.
Any Active Directory or ADAM/AD LDS 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 objects user password and re-enable the objects user account. Related Topics: Recreating purged Active Directory objects on page 884 Resetting the Active Directory computer object account on page 886
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. To reset a computer objects account 1 2 Remove the computer from the domain. 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/AD LDS objects on page 885
886
Appendix
Symantec Backup Exec Remote Agent for Windows 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. This section details how to protect remote Windows resources. For specific information on protecting remote NetWare resources: See About backing up NetWare servers on page 904. 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 do the following:

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. 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.
887
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 888 Installing the Remote Agent for Windows Systems on page 88 Setting default backup network and security options on page 318 Using Backup Exec with firewalls on page 326 About the Backup Exec Shadow Copy Components file system on page 258 The Remote Agent Utility for Windows Systems on page 889
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. To protect the Workstation versions of the supported Windows platforms, you must install the Remote Agent on each platform; however a license is not required for computers running Windows workstation operating systems. You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1
888
About installing the Remote Agent for Windows Systems
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. Related Topics: Installing the Remote Agent for Windows Systems on page 88
About installing the Remote Agent for Windows Systems

You can install the Remote Agent for Windows Systems using many methods, depending on your environment. See Installing the Remote Agent for Windows Systems on page 88.
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 2 On a Windows computer, right-click My Computer, and then click Manage. On the Computer Management dialog box, double-click Services and Applications and then click Services. 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.
The Remote Agent Utility for Windows Systems

The Remote Agent Utility is installed when the Remote Agent is installed on a remote Windows computer.
Appendix E, Symantec Backup Exec Remote Agent for Windows Systems
889
The following table lists the tasks that you can perform with the Remote Agent Utility:
Table E-1 To: Features in the Remote Agent Utility Do the following:
Start the Remote Agent Utility, or See Starting the Remote Agent Utility on page 891. 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 See Viewing activity on the remote computer on page 891. See Publishing the remote Windows computer to media servers on page 892.
See Configuring the Oracle Agent on Windows computers on page 1377. See Configuring the DB2 Agent on Windows computers on page 1443.
890
Starting the Remote Agent Utility

You access the Remote Agent Utility from the Windows taskbar. To start the Remote Agent Utility 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.
Related Topics: Viewing activity on the remote computer on page 891 Publishing the remote Windows computer to media servers on page 892
Viewing activity on the remote computer

You can view the status of a remote Windows 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 3 Click the Status tab. Complete the appropriate options as follows:
Start the Remote Agent Check Start the Remote Agent Utility every time you log on to Utility every time you display the Remote Agent Utility when you log on to this computer. log on
891
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. Name of the media server that is processing the current operation. Media or share that is being processed. Name of the current directory, folder, or database (depending on the specific agent) that is being processed. Name of the current file that is being processed.
Media server Source Current folder Current file
4 5
Click OK. To display an activity status on the remote computer, position the cursor over the Remote Agent icon in the system tray. Possible statuses are as follows:

A backup job is running A restore job is running A backup and a restore job are running Snapshot in progress The Backup Exec client service, Beremote.exe, is not running on the computer Idle
Related Topics: Viewing activity on the remote computer on page 891 Publishing the remote Windows computer to media servers on page 892
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 computers IP addresses. Because the remote computers 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.
892
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. See Specifying backup networks on page 316. 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. 2 3 Click the Publishing tab. 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. Click Add to add the media server name or IP address to the Media server list. Select a name or address in the list, and then click Edit to make changes.
Add Edit
893
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 servers Favorite Resources node.
Published names for this Displays the names that this remote computer is published as agent under a media servers Favorite Resources node. These names can include the following:

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 servers backup selection list under the Oracle RAC node.
Click OK.
Related Topics: Installing the Remote Agent and the Advanced Open File Option to a remote computer in the backup selections list on page 89 Viewing activity on the remote computer on page 891 About the Favorite Resources node on page 234 Adding a Windows system to the Favorite Resources node on page 235 Deleting a Windows system from the Favorite Resources node on page 236
894
About the Remote Agent Utility Command Line Applet
About the Remote Agent Utility Command Line Applet

You can use the Remote Agent Utility Command Line Applet from any Windows operating system command prompt to access the Remote Agent Utility. The Remote Agent Utility Command Line Applet is installed when you install the Remote Agent. If you run the command line utility on a Windows Vista or Windows Server 2008 computer, you must run it in elevated command prompt. Note You must use the Remote Agent Utility Command Line Applet on a computer that runs the Server Core installation option of Microsoft Windows Server 2008 and the Remote Agent. You can run the following Remote Agent Utility functions with the Remote Agent Utility Command Line Applet:

Set the publishing interval (in minutes). List the published name for the agent. List the media server names to which the agent is publishing. Add a media server to the publishing list. Remove a media server from the publishing list. View the following status information:

Activity status Current source Current folder Current file Currently attached media server
The following table explains the switches that you can use with the Remote Agent Utility Command Line Applet.
Table E-2 Switch status:[n] Remote Agent Utility Command Line Applet switches Description Status output is repeated every <n> seconds, with a range of 1 - 86400. Press Q to stop the output from running. ramcmd /status:[n] When you use the /status switch without a time value, the Remote Agent status appears in the command window and then the applet exits.
895
About the Remote Agent Utility Command Line Applet Table E-2 Switch /publish:[on | off | add | remove | interval] [/ms:<media server>] [/t:<x>] Remote Agent Utility Command Line Applet switches Description Use the following parameters with the /publish switch:
No parameter specified- Displays the publishing status and then exits. [on] - Turns publishing on. Lets the Remote Agent send information about itself, such as its version and IP address. [off] - Turns publishing off. [add], [remove] - Used with /ms. You can use this parameter to add or remove media servers from the Remote Agents publish list. [interval] - Used with /t. Specifies the time interval that the Remote Agent sends information about itself to the media server. You can set the time interval in minutes using the /t:[<x>] parameter.
Note The [interval] switch must be used with the /t: switch. Using [interval] alone on the command line is not supported. ramcmd /publish:[on|off|add|remove|interval] [/ms<media server>][/t:<x>] /oracle: [new | edit | Use the following parameters with the /oracle switch: delete] No parameter specified- Displays the existing Oracle instances and /in:[<instance name>] then exits. /ms:[<media server | [new], [edit], [delete] - Used with switch /in. address>] /in:[<instance name>] - Used to add, edit, and delete Oracle instance /jt:[<job template>] names from the Oracle instance list. /user:[<username>] /password:[<password /ms:[<media server name | address>] - Sets the media server name or >|*] its IP address. /rc: [yes | no] /jt:[<job template>] - Sets a Backup Exec job template. /tns:[<TNS name>]

/user:[<username>] - Sets a username. /password:[<password> | *] - Sets a password to be used with /user:[<username>]. If you omit the password, or you use an asterisk [*], you do not need to enter the password on the command line. After the command runs, a prompt appears asking you for a password. /rc:[yes | no] - Turns the Use recover catalog setting on or off. If /rc appears without a parameter, then the current status for that instance is displayed. /tns:[TNS name] - Sets the TNS name alias of an available Oracle database and the server it resides on in the Oracle TNSNAMES file. ramcmd.exe /oracle:edit /in:<instance name> /rc:[yes|no][/tns:<TNS name>][/user:<username>][/password:password|*]
896
About the Remote Agent Utility Command Line Applet Table E-2 Switch Remote Agent Utility Command Line Applet switches Description
/db2: [new | edit | Use the following parameters with the /db2 switch: delete] No parameter specified- Displays the existing DB2 instances and then /in:[<instance name>] exits. /ms:[<media server | [new], [edit], [delete] - Used with switch /in. address>] /in:[<instance name>] - Used to add, edit, and delete DB2 instance /jt:[<job template>] names from the DB2 instance list. /user:[<username>] /password:[<password /ms:[<media server name | address>] - Sets the media server name or >|*] its IP address. /al:<archive log /jt:[<job template>] - Sets a Backup Exec job template. template> /user:[<username>] - Sets a username. /tns:[<TNS name>]
/password:[<password> | *] - Sets a password to be used with /user:[<username>]. If you omit the password, or you use an asterisk [*], you do not need to enter the password on the command line. After the command runs, a prompt appears asking you for a password. /al:<archive log template>- Sets the archive log template name to <archive log template>. /tns:[TNS name] - Sets the TNS name alias of an available Oracle database and the server it resides on in the Oracle TNSNAMES file. ramcmd .exe /db2:new /in:<instance name> /ms:<media server|address> [/jt:<job template>] [/al:<archive log template>] /user:<username> [/password:<password>|*]
/auth:[on | off] Enables or disables media server authentication for Oracle and DB2 [/user:<username>] operations. [/password:<password /auth:on - Turns the state on. Requires /user parameter. > | *] /auth:off - Turns the state off. Requires /user parameter.

/user:<user> - Sets a username. /password:<password> - Sets a password to be used with /user:<username>. If you enter an asterisk for the password or omit the password, you are prompted for the password.
897
About the Remote Agent Utility Command Line Applet Table E-2 Switch /full: [on | off] [/ms:<name | address>] Remote Agent Utility Command Line Applet switches Description Turns on or off the use of the full computer name or the IP address for operations between the remote computer and the media server. (Oracle and DB2 operations only)

/full - Displays the current settings. /full:on - Turns the state on. Requires /ms:<name | address> parameter. /full:off - Turns the state off. Requires /ms:<name | address> parameter. /ms:<media server | address> - Sets the media server name or IP address to <media server> or <address>.
/port:[<port>]
Displays or sets a custom port that is used to connect to the media server during Oracle and DB2 operations.
/port - Displays the current port number. If the port is the default port, displays (default). /port:<port> - Sets the port number to <port>. To change the port to the default port number, type [/port:0].
/log_path:[<log path>] Displays or sets a custom path for debug logs.

/log_path - Displays the log directory path and then exits. /log_path:<logs path> - Creates the directory <logs path>. If the path has a space in the name, enclose the path in quotes. For example, C:\Program files\LogsFolder.
See Using the Remote Agent Utility Command Line Applet on page 898
Using the Remote Agent Utility Command Line Applet

Use the following steps to use the Remote Agent Utility Command Line Applet. To use the Remote Agent Utility Command Line Applet: 1 2 Open a command prompt. Type ramcmd.exe followed by a series of command switches.
898
Appendix
Symantec Backup Exec Remote Agent for NetWare Systems

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. The Remote Agent allows network administrators for Windows servers to perform backup and restore operations on NetWare servers that are connected to their network. You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 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 Novells 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 900
899
Requirements for installing the Remote Agent for NetWare Systems on a NetWare server
About installing the Remote Agent for NetWare Systems on a NetWare server on page 901 About backing up NetWare servers on page 904 Setting default options for the Remote Agent for NetWare Systems on page 910 About backing up the NetWare Directory Services (NDS) on page 905
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 904 About installing the Remote Agent for NetWare Systems on a NetWare server on page 901 About backing up NetWare servers on page 904 Setting default options for the Remote Agent for NetWare Systems on page 910 About backing up the NetWare Directory Services (NDS) on page 905
900
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.
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 82. 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. See Setting default options for the Remote Agent for NetWare Systems on page 910. Related Topics: Installing Backup Exec options to remote computers on page 82 Adding BESTART to the Autoexec.ncf file on the NetWare server on page 903
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. When the Remote Agent is installed with Backup Exec for NetWare Servers, the Advrtms.dat file in sys:bkupexec is not included. The Remote Agent cannot publish information to a media server. You must create the Advrtms.dat file in the sys:bkupexec directory on the NetWare server. Ensure that this file contains all names or IP addresses of the Backup Exec media servers that you want to back up the NetWare server.
Appendix F, Symantec Backup Exec Remote Agent for NetWare Systems
901
Running BESTART at the NetWare server automatically loads Novells 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 Execs 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 Execs server list. See Setting default options for the Remote Agent for NetWare Systems on page 910. 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.
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. With a text editor, open the Advrtms.dat file. Add the NetWare servers IP address. Save the Advrtms.dat file.
2 3 4
Related Topics: Adding BESTART to the Autoexec.ncf file on the NetWare server on page 903
902
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 servers 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. 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 903
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 servers console prompt, type: bestop 2 Press ENTER. All NLMs associated with the Agent will be unloaded. Related Topics: About backing up NetWare servers on page 904
903
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:
Table F-1 To do this: Backup Necessary rights for NFS backup You need these rights: 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
904
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:
Table F-2 To do this: Backup/ Restore Necessary rights for NDS backup You need these rights: 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 907 Setting default options for the Remote Agent for NetWare Systems on page 910
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.
905
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 Novells 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 904 Backing up NetWare servers on page 907
Setting default options for the Remote Agent for NetWare Systems on page 910
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. The Remote Agent does not support encrypted backups. 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 2 On the navigation bar, click the arrow next to Backup. Click New Backup Job.
Backup selections
3 4 5
Double-click Favorite Resources. Doubleclick NetWare Agents. Double-click the NetWare computer icon for the NetWare server you want to back up.
907
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 objects 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
If you want to change the backup default, on the Properties pane, under Settings, click NetWare SMS. 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. Continue creating the job. See Creating a backup job by setting job properties on page 267.
Related Topics: About restoring NetWare servers on page 909 Restoring NetWare servers on page 909
About restoring NetWare servers
About restoring NetWare servers

Before restoring your NetWare server, you may want to read about restore operations in general. See Restoring data by setting job properties on page 498. 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 909
Restoring NetWare servers

To restore NetWare servers 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Select the data you want to restore. See Selecting data to restore on page 519. 4 If you want to change the Restore option default, on the Properties pane, under Settings, click NetWare SMS. 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. (Optional) If you want to redirect the restore to another server, under Destination, click File Redirection and complete the options.
909
Setting default options for the Remote Agent for NetWare Systems
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. 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.
Complete the restore job. See Restoring data by setting job properties on page 498. 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 910 Saving configuration information for the NetWare server on page 912
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.
910
To specify TCP dynamic port ranges on the media server 1 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Network and Security. Specify a TCP dynamic port range by clicking Enable remote agent TCP dynamic port
range and enter the port ranges.
4 5
Click OK. Restart Backup Exec.
To change backup and restore defaults for the NetWare server 1 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click NetWare SMS. Select the appropriate options as follows:
Display the following servers 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 networks 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 servers 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. Back up compressed files Click this to decompress, or expand, compressed files as they are in decompressed form 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.
911
Saving configuration information for the NetWare server
Restore volume restrictions
Click this to restore NetWare volume restrictions. Restoring volume restrictions is not recommended unless you are performing a disaster recovery job.

To manually add a server to the server list

Click Add. Type the name of the server you want to add, and then click OK. Select the server you want to delete. Click Delete.
To delete a server from the server list
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 912 Disaster recovery of NetWare servers on page 913
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.
912
Disaster recovery of NetWare servers
The information in this file includes the following:

The contents of your Config.sys and Autoexec.bat files. Contents of the Startup.ncf file. 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.
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 913

To manually recover NetWare servers if a disaster occurs, you must do the following:

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 Administrators Guide.
Related Topics: About backing up NetWare servers on page 904 About restoring NetWare servers on page 909
913
914
Appendix
Symantec Backup Exec Remote Agent for Linux or UNIX Servers

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 the following backup types:

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 916 Installing Remote Agent for Linux or UNIX Servers using the SSH (Secure Shell) protocol on page 920 About protecting Novell Open Enterprise Server components on SUSE Linux Enterprise Server on page 927
915
Requirements for the Remote Agent for Linux or UNIX Servers
Creating a Linux or UNIX logon account on page 924
Requirements for the Remote Agent for Linux or UNIX Servers

You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 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. TCP/IP, which is used for communication with the UNIX host computers, is required on the media server.
Related Topics: Installing the Remote Agent for Linux or UNIX Servers on page 917 Installing Remote Agent for Linux or UNIX Servers using the SSH (Secure Shell) protocol on page 920 Creating a Linux or UNIX logon account on page 924 Backing up Linux and UNIX servers on page 925 Requirements for Novell Open Enterprise Server on page 928 Backing up OES components on page 928 Restoring Novell OES components on page 929 Restoring Novell OES components on page 929 Manually uninstalling the Remote Agent for Linux or UNIX Servers on page 931
916
Installing the Remote Agent for Linux or UNIX Servers
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:
Table G-1 To do this Install the Remote Agent from the Backup Exec for Windows Servers CD Install the Remote Agent using the SSH protocol Manually uninstall the Remote Agent Manually start the Remote Agent daemon How to Do the following See Installing Remote Agent for Linux or UNIX Servers by using the installation script on page 918. See Installing Remote Agent for Linux or UNIX Servers using the SSH (Secure Shell) protocol on page 920. See Manually uninstalling the Remote Agent for Linux or UNIX Servers on page 931. See Manually starting the Remote Agent for Linux or UNIX Servers on page 932.
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 domains 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:

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 hosts that are members of a NIS domain, refer to the NIS documentation for information on adding groups to a NIS domain. For more information on creating groups, see your Linux and UNIX system documentation.
Appendix G, Symantec Backup Exec Remote Agent for Linux or UNIX Servers 917
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 922 About editing the ralus.cfg file on page 922 About ralus.cfg format components on page 922 Creating a Linux or UNIX logon account on page 924
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). 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. 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. Logon to the target computer with root privileges. Navigate to Remote Agent for Linux or UNIX Servers installer on the Backup Exec CD using the following path: <device_name>/ At the command prompt, type the following command:
./installralus.
2 3
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. After the installer successfully checks for a valid Linux or UNIX host operating system during the initial system check, press Enter. After reviewing the package installation summary, press Enter.
918
8 9
Press Enter to start the Remote Agent installation requirements precheck. 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<summary file number>/installralus.log
Related Topics: Publishing Linux and UNIX hosts to a media server on page 922 About editing the ralus.cfg file on page 922
Appendix G, Symantec Backup Exec Remote Agent for Linux or UNIX Servers
919
About ralus.cfg format components on page 922 Creating a Linux or UNIX logon account on page 924
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 set up the trust relationship, you must locate the roots home directory on each computer where you want to install the Remote Agent. Following are the default locations of the roots home directory for each operating system:
Table G-2 Location of the roots home directory Location of the roots home directory
/root / / / /var/root
Operating system
Linux HP/UX AIX Solaris Macintosh OS X
To install the Remote Agent using the SSH protocol 1 Ensure that SSH is installed and enabled on each computer where you want to install the Remote Agent. On the SSH client computer from where you want to install the Remote Agent, log on as root. On the SSH client computer from where the Remote Agent agent is being installed, run the following command:
ssh-keygen -b 1042 -t dsa
Accept the defaults, including no passphrase. An ssh key for the computer is created in the file /.ssh/id_dsa.pub
920
On each remote computer where you want to install the Remote Agent agent, check to see if a /.ssh/authorized_keys2 file exists in the roots home directory. 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.
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.
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.
To test the trust relationship on all operating systems 1 On the SSH client computer from where you installed the Remote Agent, log on as root. To test the trust relationship, type the following command: ssh root@<target name or IP address> 3 At the prompt, type Yes.
To remove the trust relationship after you install the Remote Agent
Remove the key from the authorized_keys2 file on the computers where you installed the Remote Agent.
Related Topics: About creating the beoper group on page 917 Publishing Linux and UNIX hosts to a media server on page 922
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 922 About ralus.cfg format components on page 922 About file and directory exclusions in ralus.cfg on page 923
About editing the ralus.cfg file

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 922 About file and directory exclusions in ralus.cfg on page 923
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 922 About file and directory exclusions in ralus.cfg on page 923
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.
923
Creating a Linux or UNIX logon account File and directory exclusions in the ralus.cfg file
Related Topics: Creating a Linux or UNIX logon account on page 924 Backing up Linux and UNIX servers on page 925
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. To add logon credentials 1 2 In Backup Job Properties pane under Favorite Resources, expand Linux/UNIX Servers. 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 4 On the Logon Account Selection screen, click New. Add the following account credentials for the host and then click OK.
924
Backing up Linux and UNIX servers
Credentials supplied for the Linux or UNIX host must have root privileges that can be authenticated by the host.
User name Password Confirm password Account name Notes The user name required to access the Linux or UNIX host. This name must have root privileges, which can be authenticated by the host. The password used to access the host. The same password entered in the Password field, which is used to confirm the password was entered correctly in the Password field. A label you enter to name the logon account. Pertinent notes about the account.
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 925

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. 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.
925
The following options appear:

Preserve change time Use this option to prevent the Remote Agent from changing an objects (files and directories) attributes when a backup occurs. Normally, during a backup, Backup Exec preserves an objects 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 objects ctime. An objects ctime is the time when an objects attributes (permissions, timestamps, etc.) have been modified. If the attributes are not changed by the Remote Agent after a backup, the objects 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 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. When you use this option, the following limitations apply:
Follow local mount points Follow remote mount points
The data that is mounted must reside on a computer that is compatible with Backup Exec, and where you can install a Backup Exec remote agent. You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1
If the mount point leads to an operating system that Backup Exec does not support, you must work with the operating systems vendor to resolve any problems related to backups or restores.
Back up contents of soft-linked directories
Use this option to back up the contents of directories that are linked using soft links. You must also select the directory that contains the soft links. If you select only the soft link, the link is backed up. However, the data to which the link points is not backed up. 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. For more information on soft-linked directories, see your Linux or UNIX documentation.
926
About protecting Novell Open Enterprise Server components on SUSE Linux Enterprise Server
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).
Backup method for Select a backup method for backing up eDirectory data. Selections eDirectory (Linux only) include Full Backup and Incremental - since last full or incremental.
2 3 4
Make the appropriate selections or use the default selections provided. Click General in the Properties pane of the Backup Job Properties screen. 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 927 Restoring Novell OES components on page 929
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)
Related Topics: Requirements for Novell Open Enterprise Server on page 928 Backing up OES components on page 928 Backing up Linux and UNIX servers on page 925
927
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 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 928 Backing up Linux and UNIX servers on page 925
Backing up OES components

To back up OES components, you must be able to access the Linux or UNIX host. To back up OES components 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the backup selections list, under Favorite resources, expand Linux/UNIX Servers. 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 6 7 8 Select a logon account to access the host, and then click OK. Select the appropriate data to back up. On the Properties pane, under Settings, click Linux, UNIX, and Macintosh. Select the appropriate backup options. See Backing up Linux and UNIX servers on page 925. 9 If you are backing up eDirectory data, select a backup method under the heading Novell OES.
928
Restoring Novell OES components
10 Click Run Now. Related Topics: Backing up Linux and UNIX servers on page 925 Setting Linux/UNIX properties for Remote Agent restore jobs on page 929
Restoring Novell OES components

Backup Exec includes restore job properties for restoring Linux and UNIX servers. To restore Novell OES components 1 2 3 4 5 6 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. In the restore selections list, select the appropriate data to restore. On the Properties pane, under Settings, click Linux, UNIX, and Macintosh. Select the appropriate Linux/UNIX restore options. See Setting Linux/UNIX properties for Remote Agent restore jobs on page 929. 7 Click Run Now.
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. See Restoring data by setting job properties on page 498. 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.
929
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). Check the check box to activate the restore of the Novell Directory Services database.
Restore DIB set
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 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
Roll forward log directory 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.
Related Topics: Restoring Novell OES components on page 929
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 2 3 At a UNIX host, place the Backup Exec for Windows Servers CD in a CD-ROM drive. Logon to the target computer with root privileges. Navigate to Remote Agent for Linux or UNIX Servers uninstaller on the Backup Exec CD using the following path: <device_name>/uninstallralus
Manually uninstalling the Remote Agent for Linux or UNIX Servers
At the command prompt, type the following command:

uninstallralus
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. Press Enter after the Remote Agent package check completes successfully. Press Enter when prompted, Are you sure you want to uninstall RALUS packages? [y,n,q] <y>. 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.
6 7
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 file number>.summary
Uninstallralus log:
/opt/VRTS/install/logs/uninstallralus<summary file number>.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 931
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. To manually uninstall the Remote Agent for Linux or UNIX Servers 1 2 Connect to the target UNIX host as the root user using a terminal session. Stop the Remote Agent daemon.
931
Manually starting the Remote Agent for Linux or UNIX Servers
3 4
Change to the /opt/VRTSralus/bin directory. 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.
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 933
Manually starting the Remote Agent for Linux or UNIX Servers

Use a command to start the Remote Agent daemon. To manually start the Remote Agent for Linux or UNIX Servers daemon 1 2 Connect to the target UNIX host as the root user using a terminal session. 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 933
932
Manually stopping the Remote Agent for Linux or UNIX Server daemon
Manually stopping the Remote Agent for Linux or UNIX Server daemon
Use the following steps to manually stop the Remote Agent daemon. To manually stop the Remote Agent for Linux or UNIX Servers daemon 1 2 Connect to the target UNIX host as the root user using a terminal session. Type the following stop command:
/etc/init.d/VRTSralus.init stop
Related Topics: Troubleshooting the Remote Agent for Linux or UNIX Servers on page 933
Troubleshooting the Remote Agent for Linux or UNIX Servers

If you experience problems while using the Remote Agent, read the questions and answers in this section. 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. Im 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.
Troubleshooting the Remote Agent for Linux or UNIX Servers
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 <id>
A user attention icon appears Related Topics: Symantec Backup Exec Remote Agent for Linux or UNIX Servers on page 915
934
Appendix
Symantec Backup Exec Remote Agent for Macintosh Systems

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 the following backup types:

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. See Requirements for the Remote Agent for Macintosh Systems on page 936. See Installing the Remote Agent for Macintosh Systems by using the SSH (Secure Shell) protocol on page 938. See Backing up Macintosh computers on page 943.
935
Requirements for the Remote Agent for Macintosh Systems
Requirements for the Remote Agent for Macintosh Systems

The following platforms and file systems are supported:.
Table H-1 Platform Macintosh OS X Macintosh OS X Server Supported Macintosh platforms and file systems Version 10.3, 10.4 (PowerPC) 10.3, 10.4 (PowerPC) File System Native 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.
See Installing the Remote Agent for Macintosh Systems on page 936. See Installing the Remote Agent for Macintosh Systems by using the SSH (Secure Shell) protocol on page 938.
Installing the Remote Agent for Macintosh Systems

See the following topics when installing the Remote Agent for Macintosh Systems on a Macintosh computer.
Table H-2 Item Installation topics Description
To install the Remote Agent from See Installing the Remote Agent for Macintosh Systems using the installation script on page 937. the Backup Exec for Windows Servers CD 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 938.
936
Installing the Remote Agent for Macintosh Systems Table H-2 Item To manually start the Remote Agent daemon To manually stop the Remote Agent daemon Installation topics Description
See Manually starting the Remote Agent for Macintosh Systems daemon on page 946. See Manually stopping the Remote Agent for Macintosh Systems daemon on page 947.
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. 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 3 4 5 6 Open a Finder window and then browse to Applications>Utilities. Open Terminal. In Terminal, type sudo ./installrams. Enter a password, which should be the password of the currently logged in user. 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. After the installer successfully checks for a valid Macintosh computer operating system during the initial system check, press Enter.
937
Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems
8 9
After reviewing the package installation summary, press Enter. Press Enter to start the Remote Agent installation requirements precheck.
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. 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<summary file number>/installrams.log
Related Topics: Publishing Macintosh computers to a media server on page 940 About editing the ralus.cfg file on page 940 Backing up Macintosh computers on page 943
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:
938
To establish a trust relationship and enable SSH 1 2 3 4 To enable SSH, open System Preferences. Click Sharing. Check the name of the check box for Remote Login. On the SSH client computer from where you are installing the Remote Agent, log in as root. Run the following command: ssh-keygen -b 1042 -t dsa 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, and then do one of the following.
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. 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.
If the file does exist
To test the trust relationship 1 On the SSH client computer from where the Remote Agent is being installed, log in as root. Run the following command:
ssh root@<client name or IP address>
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.
939
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 940 About editing the ralus.cfg file on page 940 Backing up Macintosh computers on page 943
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 940 About ralus.cfg format components on page 941 Backing up Macintosh computers on page 943
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
940
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 940 About ralus.cfg format components on page 941 Backing up Macintosh computers on page 943
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
Editing a ralus.cfg file can be done using any UNIX text editor. Related Topics: About editing the ralus.cfg file on page 940 About file and directory exclusions in ralus.cfg on page 942
Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems 941
Creating a Macintosh logon account
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.
File and Directory Exclusions in the ralus.cfg File
Related Topics: Backing up Macintosh computers on page 943
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 2 In Backup Job Properties pane under Favorite Resources, expand Macintosh Systems. 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.
Backing up Macintosh computers
3 4
On the Logon Account Selection screen, click New. Add account credentials for the Macintosh computer and then click OK. Credentials supplied for the Macintosh computer must have Admin privileges that can be authenticated by the Macintosh computer. Credentials include the following information:
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. The password used to access the Macintosh computer. The same password entered in the Password field, which is used to confirm the password was entered correctly in the Password field. A label you enter to name the logon account. Pertinent notes about the account.
Password Confirm password
Account name Notes
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 943

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.
943
The following options appear:

Preserve change time Use this option to prevent the Remote Agent from changing an objects (files and directories) attributes when a backup occurs. Normally, during a backup, Backup Exec preserves an objects 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 objects ctime. An objects ctime is the time when an objects attributes (permissions, timestamps, etc.) have been modified. If the attributes are not changed by the Remote Agent after a backup, the objects 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. 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).
Follow local mount points Follow remote mount points Back up contents of soft-linked directories
2 3
Make the appropriate selections or use the default selections provided. Click General in the Properties pane of the Backup Job Properties screen.
944
Uninstalling the Remote Agent for Macintosh Systems
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: Troubleshooting the Remote Agent for Macintosh Systems on page 947

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. Logon to the target computer with Admin privileges. Navigate to Remote Agent for Macintosh Systems uninstaller on the Backup Exec CD using the following path: <device_name>/RAMS/<device_name>/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. Press Enter after the Remote Agent package check completes successfully. Press Enter when prompted, Are you sure that you want to uninstall RALUS packages from <computer name>? [y,n,q] <y>. 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:
Appendix H, Symantec Backup Exec Remote Agent for Macintosh Systems 945
2 3
6 7
Uninstallation summary:
/opt/VRTS/install/logs/uninstallrams<summary file number>.summary
Uninstallrams log:
/opt/VRTS/install/logs/uninstallrams<summary file number>.log
After the log files are saved, the Remote Agent uninstall is complete. Related Topics: Manually starting the Remote Agent for Macintosh Systems daemon on page 946 Manually stopping the Remote Agent for Macintosh Systems daemon on page 947
Manually starting the Remote Agent for Macintosh Systems daemon

To manually start the Remote Agent for Macintosh Systems daemon 1 2 Connect to the target Macintosh computer as the root user using a terminal session. From the root prompt, issue the following start commands: cd /Library/Startupitems/VRTSrams ./VRTSrams start Related Topics: Manually stopping the Remote Agent for Macintosh Systems daemon on page 947 Uninstalling the Remote Agent for Macintosh Systems on page 945
946
Troubleshooting the Remote Agent for Macintosh Systems
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 2 Connect to the target Macintosh computer as the root user using a terminal session From the root prompt, issue the following stop commands: cd /Library/Startupitems/VRTSrams ./VRTSrams stop Related Topics: Manually starting the Remote Agent for Macintosh Systems daemon on page 946 Uninstalling the Remote Agent for Macintosh Systems on page 945

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. Im 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
947
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 <id>
948
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.
949
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 users 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 users 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 987 About DLO Profiles on page 988 About Backup Selections on page 1001 About DLO Storage Locations on page 1021 About Automated User Assignments on page 1027
950
How the Desktop and Laptop Option Works Relationship Between Backup Exec and the Desktop and Laptop Option Components
- Backup Exec Administration Console
Administration Console on the media server or a remote server
- 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.
Storage Locations If you use Backup Exec to protect the file servers that host the Network User Data Folders remotely, the Remote Agent for Windows Servers is required.
DLO File Server
DLO File Server
- Desktop Agent - Desktop User Data Folder
Desktops and Laptops
- Desktop Agent - Desktop User Data Folder
951
Before you install
Before you install

Before you install DLO, you should consider the following:
Table I-1 Item Domains and Active Directory Pre-installation considerations Description 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. 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 users 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 965 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.
Server loading
952
Before you install Table I-1 Item Database Selection Pre-installation considerations Description By default DLO installs its own instance of SQL Express 2005. You can also manually configure DLO to use an existing local or remote instance of the following:

SQL Express 2005 SQL Server 2000 SQL Server 2005 MSDE 2000
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. 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.
Cons
SQL Server Pros

Allows reasonable scalability beyond 1000 Desktop Agents. Database tools are included with SQL Server. Cost, however you do not need to purchase a SQL Server client license for each Desktop Agent.
Cons
MSDE

Free Unless you back up more than 1000 Desktop Agents per media server, MSDE should be sufficient for most needs. 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. 953
Cons
Before you install Table I-1 Item Time Synchronization Pre-installation considerations Description 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. 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.
Firewalls
MDAC Support for the DLO Administration Console
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
MDAC Support for the Desktop Agent
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
954
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.
Table I-2 Item Operating System Minimum System Requirements Description

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 Microsoft Windows Vista Microsoft Windows Server 2008
Note You cannot install DLO on computers that run the Windows Server Core option. Internet Browser Processor Memory Internet Explorer 5.01 or later; however, version 5.5 is recommended Pentium system Required: 256 MB RAM Recommended: 512 MB or more for better performance Disk Space Other Hardware 150 MB hard disk space required after Microsoft Windows is installed (typical installation)

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.
955
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 71. If you prefer to install DLO from the Command Line (Silent Mode), see Installing Backup Exec using the command line (silent mode) on page 101 and Command line switches for Backup Exec silent mode installation on page 102. 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. See Configuring DLO on page 987. See Installing the Desktop Agent on page 1122. 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 952. This section discusses a number of topics that should be considered before installing DLO.
956
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.
Table I-3 Desktop Agent Deployment Methods Description The Desktop Agent can be push installed using the Backup Exec installer (see Installing Backup Exec options to remote computers on page 82). 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 Web page Logon scripts Send a hypertext link to the install files or include the install files as an attachment. Place the install files on your companys intranet. 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. 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. 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.
Deployment Methods Push Install
Microsoft Systems Management Server (SMS) CD-ROM
Related Topics: Installing the Desktop Agent on page 1122
957
Desktop Agent Installation Options

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 2 In the Desktop Agent setup directory, open the SETUP.INI file for editing. Modify the value that begins CmdLine= /qf as shown below:
Desktop Agent CmdLine Installation Options Original command Desktop Agent installation interface Options 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. Set the Default Media Server Launch the Desktop Agent 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 Specify the Required MDAC Version DLO uses MDAC 2.8 by default. Force the use of MDAC 2.7 by adding the following: REQUIREDMDACVERSION=2.7 Suppress Reboot To suppress a reboot, even if one is required, add the following: REBOOT=ReallySuppress 958 Administrators Guide
Installing the Backup Exec Desktop and Laptop Option Desktop Agent CmdLine Installation Options Original command Logging Options 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/.
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
959
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 \\<servername>\DLOAgent directory the following files are required:

*.mst *.cab DLOBuildInfo.ini *.msi
Run the msiexec command using, as a base, the value in setup.ini from the cmdline key: /qf DEFAULTMEDIASERVER="<From setup.INI File>" DLODBINSTANCENAME="<FromSetup.INI File>" LAUNCHCLIENT="1" REQUIREDMDACVERSION="2.8" TRANSFORMS="1033.mst" /l*v "%TEMP%\DLOAgentInstall.log" The default values are as follows:
Default Values
Item
Default 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. Specifies the SQL instance name. It is recommended that you do not modify this value. 1
DEFAULTMEDIASERVER
DLODBINSTANCENAME
LAUNCHCLIENT REQUIREDMDACVERSION TRANSFORMS 3
"2.8" "1033.mst"
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.
960
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. 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)
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. MSI 3 . 1 is required on the target systems. The MSI 3.1 installer is included in: \\<servername>\DLOAgent\WindowsInstaller-KB893803-v2-x86.exe
961
Post Installation Tasks

Setting a Recovery Password
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 962 -SetRecoveryPwd Command on page 1116 -EmergencyRestore Command on page 1115
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 2 From the Tools menu, select Wizards and then Data Integrity Scanner. Click Next.
962
If you would like to set advanced options, click Advanced Options. Select the appropriate options and then click OK.
Data Integrity Scanner Advanced Options
Item Permanently remove previously quarantined data
Description Select this check box to cause all previously quarantined data to be deleted.
Quarantine data Select this check box to quarantine all files with outdated encrypted with outdated keys. If this option is not checked, data is scanned without keys being quarantined. After data is quarantined, the Desktop Agent backs up a new version of the file with the correct encryption key. Include computers that have already been validated Verbose output Select this check box to force all data to be rescanned, even if it has previously been validated. Select this check box to receive detailed information from the scan.
4 5
Click Start. 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 7
Click Next. Click Finish.
Related Topics: Setting a Recovery Password on page 962 -SetRecoveryPwd Command on page 1116 -EmergencyRestore Command on page 1115
963
Changing DLO Service Credentials

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 2 3 On the Tools menu, select Manage Service Credentials. Select Change DLO Service Account Information. Enter account credentials as follows:
Service Account Information Item Change DLO service account information User name Domain name Password Confirm password Description Select this check box to change the DLO service account information. Type the user name for the account to be used. Enter the domain for this account. Type the password for this account. Type the password again to confirm.
964
About Administrator Accounts

The DLO Administration Console can be managed by any user who has full administrator rights on the media server. The users 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 966 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 users data, whereas the limited administrator group only supplies list access, thus protecting the users data from unauthorized access.
965
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 967 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 users 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 965. Alternatively, DLO can be configured to use domain groups for permissions management. See Using Domain Groups to Manage DLO Permissions on page 967 for additional information. To configure DLO to use a list of individual accounts for permissions management: 1 2 3 On the DLO Administration Console Network menu, select Administrator Accounts. Click Permissions. 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
966
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 5 Click OK. 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.
Define the administrator account as follows:

Add Administrator Account Options
Item User Name Description Notes Grant administrator full restore privileges
Description Type the name of the user you want to give administrative rights to. Use the format DomainName\UserName Type a description for this administrator account. Type any relevant notes regarding the administrator account. 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.
Click OK twice.
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 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 965.
967
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 966 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. Click Permissions. Check or verify checked the Use domain groups to manage access to network user data
folders checkbox.
2 3
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 For DLO administrators with full restore privileges, use the domain group Description To grant DLO administrators in a specified domain group full restore privileges including the ability to restore a desktop users files to an alternate location, enter or browse to a fully qualified domain group. Example: Enterprise\DLOFullAdmins For DLO administrators with limited restore privileges, use the domain group To grant DLO administrators in a specified domain group limited restore privileges that do not include the ability to restore a desktop users files to an alternate location, enter or browse to a fully qualified domain group. Example: Enterprise\DLOLimitedAdmins
Click OK twice.
968
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 2 3 4 5 6 On the DLO navigation bar, click Setup. On the task pane, under Tool Tasks, click Options. In the properties pane, under New Profile Defaults, click General. Set the options as explained in General Profile Properties on page 988. In the properties pane, under New Profile Defaults, click User Settings. Set the profile user settings options as explained in Profile User Settings Dialog Box on page 992. In the properties pane, under New Profile Defaults, click Schedule. Set the profile schedule options as explained in Profile Schedule Dialog Box on page 995. In the properties pane, under New Profile Defaults, click Options.
7 8
10 Set the profile options as explained in Additional Profile Options on page 997.
969
Changing Default Backup Selection Settings

The default DLO backup selection settings can be modified as described below. To change default backup selection settings 1 2 3 On the DLO navigation bar, click Setup. On the task pane, under Tool Tasks, select Options. 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 1009. In the Properties pane under New Backup Selection Defaults, click Options. Set the backup selection options as explained in Backup Selection Options on page 1011.
4 5
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 2 3 4 On the DLO navigation bar, click Setup. On the task pane under Tool Tasks, select Options. In the Properties pane under Global Settings, click Options. Set global options as follows:
Global Settings Options Item Disable All Desktop Agents Checking this box will prevent all Desktop Agents from backing up. Description
970
Post Installation Tasks Global Settings Options Item Incremental backups of Outlook PST files Description 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 1139 for additional information. Incremental backups of Lotus Notes email files 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 1141 for additional information. Reports Generate reports in PDF format Generate reports in HTML format Other Time to delay Desktop Check this option and enter the number of seconds to delay the Agent startup after user start of the Desktop Agent after the user logs in. The Desktop logs in Agent start is only delayed if this option is checked and the Desktop Agent is started from the startup menu. Desktop Agent low disk error threshold Desktop Agent low disk warning threshold 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. 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.
Desktop Agent low quota Enter a percentage of the desktop user data folder storage limit. If warning threshold 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.
In the Properties pane under Global Settings, click Desktop Agent Intervals.
971
Set the Desktop Agent Interval defaults as follows:

Desktop Agent Interval Options
Item How long to wait before retrying the backup of a previously busy file
Description 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. 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.
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
Minimum time between closing a job log and starting a new one
972
Post Installation Tasks Desktop Agent Interval Options Item Minimum time between maintenance cycles Description 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.
Minimum time between checking for changes to Lotus Notes email files
Time during which Desktop Agents randomly respond to restart requests
7 8
In the Properties pane under Global Settings, click User Activity Settings. Set the User Activity Settings defaults as follows:
User Activity Settings
Item Enable user activity restrictions Limit network bandwidth usage to
Description 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.
Restrictions will be Enter the number of seconds of user inactivity after which DLO removed when there has will no longer restrict jobs. been no user activity for x seconds
973
Post Installation Tasks User Activity Settings Item Description
Maximum scanner items Scanner items per second limits the number of items processed per second 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.
In the Properties pane under Global Settings, click LiveUpdate.
10 Set the LiveUpdate defaults as follows:

LiveUpdate Options Item Enable Desktop Agent scheduled automatic updates When checking for updates Description 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.
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.
974
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. 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. 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. 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
975
Updating DLO
machine, or using the push-install mechanism in the CPS Administration Console. See the Symantec Backup Exec Continuous Protection Server Administrators 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 1163.
Updating DLO
Updates to 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 956. 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 962. 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 962 for additional information.
976
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: \\<media server>\DLOAgent\update_12.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 2 Update the media server as directed in the update documentation. 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..\agents\dlo\update_12.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= 12.0 Update
977
Updating DLO
Description=Updates Backup Exec DLO Desktop Agent from 9.1 to 12.0 Version=3.0 Build=3.XX.XX srcPath=\\MediaServerName\DLOAgent\update_12.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 1113. Related Topics: DLO Command Line Interface Management Tools on page 1103
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. Set PromptUser=0. Save and Close the file.
2 3
978
Updating DLO
Run the upgrade using one of the methods described in Updating the Desktop Agent on page 977.
About upgrading to Windows Vista

DLO includes the following changes to support Windows Vista:
The Documents folder no longer includes subfolders for Music, Pictures, or Videos. Therefore, if you select the Documents folder and the Include subfolders option, the data in the Music, Pictures, and Videos folders is not backed up. You must select each folder that you want to back up. All backed-up data is stored in the AppData folder. File revisions and delta file copies begin anew. Previous data remains in the user data folders according to the settings in the deleted file retention policy. You can synchronize data between two computers that run Windows Vista. You cannot synchronize data between a computer that runs Windows Vista and a computer that runs an earlier operating system, such as Windows XP.
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.
979
Updating DLO
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=<MSIPropertiesAppend>TRANSFORMS=%%%%LANG_FILE%%%% REBOOT=ReallySuppress LAUNCHCLIENT=0 REQUIREDMDACVERSION=2.7 </MSIPropertiesAppend><MSIPropertiesFile>setup.ini</MSIPropertiesFile> To upgrade from NetBackup Professional to 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. 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 both the leave and remove NBUP options available for selection in various profiles. 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. Copy the entire contents of the DLOAgent share on the media server into the DLOAgent folder on the NBUP server. Launch the NBUP Console. 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. Repeat step 1 through step 6 for each NBUP Profile you want to upgrade to DLO.
5 6
980
Updating DLO
Follow the standard procedure for upgrading NBUP (Check for upgrade now in the console or refresh the client). See the NetBackup Professional Administrators 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.
981
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.
982
To access the DLO Administration Console from Backup Exec 1 2 On the navigation bar, click Job Setup. In the task pane under Backup Strategy Tasks, click Configure desktop and laptop backups.
Related Topics: Configuring DLO on page 987 About DLO Storage Locations on page 1021 About DLO Profiles on page 988 About Automated User Assignments on page 1027 Managing Desktop Agent Users on page 1041
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 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
983
The System Summary overview provides the DLO administrator with a brief summary of the current state of desktop backups, server status, and alerts. To access the Getting Started view 1 2 On the DLO navigation bar, click Overview. Click the Getting Started tab.
To access the DLO System Summary 1 2 On the DLO navigation bar, click Overview. Click the System Summary tab.
The following information is available in the System Summary overview:

Table I-4 Item System Summary 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.
984
Connecting to DLO on a different Backup Exec Media Server Table I-4 Item 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. System Summary (continued) Description
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.
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 2 On the DLO Administration Console Network menu, click Connect to Media Server. Select the appropriate options as follows:
Connect to media server dialog box options Item Server Login information User name Password Type the user name for an account with administrator access to the media server. Type the password for this account. Description Enter the name of the media server you want to connect to, or select a media server from the drop-down menu.
985
Connecting to DLO on a different Backup Exec Media Server Connect to media server dialog box options (continued) Item Domain Description Enter the domain for this account.
Click OK.
Related Topics About Administrator Accounts on page 965
986
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 988. 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 1021 and Managing Desktop Agent Users on page 1041. 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 1027. 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 2 3 On the DLO navigation bar, click Setup. On the task pane under Getting Started, select DLO Configuration using wizard. 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 988 About DLO Storage Locations on page 1021 About Automated User Assignments on page 1027 Managing Desktop Agent Users on page 1041
987
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 users 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 2 3 4 5 On the DLO navigation bar, click Setup. In the Settings pane, click Profiles. In the task pane under Settings Tasks, click New Profile. Click the General tab in the New Profile dialog box. Select the appropriate options as follows.
General Profile Properties Item Profile Name Description Type the name of the new profile that you want to create. The profile name cannot contain any of the following characters: \@#$%^&*()=+|/{}[]
988
About DLO Profiles General Profile Properties (continued) Item Description Enable Profile Description Type a description for the profile. Clear this check box to disable the profile. Profiles are enabled by default.
User Bandwidth Settings Limit bandwidth (KB/sec) 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. Yield bandwidth Enables DLO to reduce data transfer over the network when other to other programs 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.
989
About DLO Profiles General Profile Properties (continued) Item Storage Limits Limit network Limits the disk space available on the network to store DLO backup files user data folder to and type the amount of space you want to use for storage. (MB) Enable desktop user data folder 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:
Description
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. 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.
Advantages to disabling the desktop user data folder:
990
About DLO Profiles General Profile Properties (continued) Item Description
Limit desktop Limits the disk space available to store DLO backup files. user data folder to 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. Override the default desktop user data folder path If you do not want the desktop user data folder to reside in the default location, check Override the default desktop user data folder path. Then, type the path to the folder that you want all new Desktop Agent users that are assigned to this profile to use. The folder must already exist on the desktop before the new user logs on for the first time after being assigned to this profile. The Desktop Agent does not create the folder. If the folder does not exist before the user logs on for the first time, DLO uses the default folder for backups. The default folder is located at the following path on the computers that run Windows XP and earlier operating systems: \\Documents and Settings\<user_name>\Local Settings\Application Data\Symantec The default folder is located at the following path on the computers that run Windows Vista: \\Users\<user_name>\AppData\Symantec
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 1001.
991
About DLO Profiles
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 Desktop Agent display settings Description Select one of the following options to determine the desktop users 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.
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. When selected, users in this profile can restore their backed up files. For more information, see Restoring Files Using the Desktop Agent on page 1159.
Restore data
992
About DLO Profiles Profile User Settings Dialog Box (continued) Item Description
Add user-defined backup Enables users in this profile to create and modify backup selections 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 1001, Modifying Backup Selections in the Standard View on page 1132 or Modifying Backup Selections in the Advanced View on page 1138. Modify profile backup selections 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 1001 or Modifying Backup Selections in the Advanced View on page 1138. 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 1136.
Customize backup selection revision policy settings
Change backup selection Enables users in this profile to turn encryption of backup files on encryption settings or off. For more information, see Backup Selection Options on page 1137. Change backup selection Enables users in this profile to turn compression of backup files compression settings on or off. For more information, see Backup Selection Options on page 1137. Customize profile logging settings Enables users in this profile to customize profile logging settings. For more information, see Setting Customized Options on page 1146. Enables users in this profile to customize mail settings in the profile. For more information, see Setting Customized Options on page 1146. 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 1148.
Customize profile email settings Move local user data folder
993
About DLO Profiles Profile User Settings Dialog Box (continued) Item Change groom policy settings Description Enables users in this profile to customize grooming settings. For more information, see Setting Customized Options on page 1146.
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 1151.
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 1146.
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 1143.
Customize connection policies
Enables users in this profile to customize connected based policies. For more information, seeCustomizing Connection Policies on page 1149.
Cancel scheduled or manual jobs
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 1156.
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 1156. 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. Enables users in this profile to set the Desktop Agent to work offline. See Changing Your Connection Status on page 1127 for additional information.
Disable Desktop Agent
Work Offline
994
About DLO Profiles Profile User Settings Dialog Box (continued) Item Save encrypted passwords used by DLO Description 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.
Suppress errors and warnings When user goes offline, automatically go back online after
When user suspends a Enter the time after which a job will be resumed or the Desktop job or disables the Agent enabled after the user suspends a job or disables the Desktop Agent, Desktop Agent. automatically resume or enable after
8 9
Click the Schedule tab. Select the appropriate options as follows:

Profile Schedule Dialog Box
Item Run backups
Description
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.
995
About DLO Profiles Profile Schedule Dialog Box (continued) Item When initiated by the user Description Select this option to enable desktop users to determine when to back up their files.
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.
996
About DLO Profiles
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 Run on these days Frequency Run once at Run every From Until Select this option to run a single backup on the days you selected at the time specified. Select this option to run backups at the specified time interval on the days you selected. If you selected Run every, select the beginning of the time interval over which you want backups to begin. 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. Description Select the days on which you want to back up files.
11 Click the Options tab. 12 Select the appropriate options as follows: 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 1071.
Additional Profile Options Item Log file maintenance Description
997
About DLO Profiles Additional Profile Options (continued) Item Keep log files for a minimum of (days) Description 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. After minimum number Enter the maximum combined size of all log files to be retained of days, delete oldest log before the oldest log files are deleted. files when combined Note You may have more than the specified number of MB of log size exceeds (MB) files stored if none of the log files is as old as specified in the Keep log files for a minimum of (days) setting. Logging options Log groom messages Log information messages for backup Log warning messages Mail options Enable message level incremental backups of Outlook PST 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 1139. Ignore PST files which have not been configured in Outlook Select this option to exclude PST files that are not registered with the Microsoft Outlook client on a Desktop Agent computer. Select this check box to create logs for grooming operations. Select this check box to create logs for all backup operations. Select this check box to create logs for all operations that generate warnings.
998
About DLO Profiles Additional Profile Options (continued) Item Enable message level incremental backups of Lotus Notes email files Description 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 1141. 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.
13 Click the Connection Policies tab to disable or limit backups for specific connection types. 14 Click Add. 15 Create a new connection policy and configure it as follows:
Add/Edit Connection Policy Item Connection Type Dialup IP address range Select Dialup from the drop-down menu to limit or disable backups when using a dialup connection. 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 1149 for details on configuring connection policy settings for Active Directory. Description
Desktop Agent Behavior
999
About DLO Profiles Add/Edit Connection Policy Item Disable network backup Description 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. 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.
Disable network backup for files greater than Limit network bandwidth usage to
Enforce policy according Check the Enforce policy according to scheduled window to cause to scheduled window 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.
16 Click OK. Related Topics: About Backup Selections on page 1001 Monitoring Alerts on the DLO Administration Console on page 1071 Modifying Desktop Agent Settings on page 1142
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 2 3 On the DLO navigation bar, click Setup. In the Settings pane, click Profiles. Right click on the profile you want to copy.
1000
About Backup Selections
4 5 6 7
Click Copy. Type a name for the new profile. Type a description of the new profile. Click OK.
Modifying a Profile
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 2 3 4 5 6 On the DLO navigation bar, click Setup. In the Settings pane, click Profiles. In the Results pane, select the profile you want to modify. In the task pane, under General Tasks, click Properties. Modify the profile properties as needed. Click OK.
Related Topics Creating a New Profile on page 988

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.

1001

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. 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 1002 Removing Default Backup Selections From a Profile on page 1003 Adding a Backup Selection on page 1004 Defining General Backup Selection Properties on page 1005 Including and Excluding Files or Folders from a Backup Selection on page 1006 Revision Control on page 1008 Setting Options for a Backup Selection on page 1010 Using DLO Macros in Backup Selections on page 1012 Modifying a Backup Selection on page 1014 Deleting Backup Selections on page 1015
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 My Documents My Favorites 1002 Description All files in My Documents (Documents in Windows Vista) Internet Explorer Favorites Administrators Guide
About Backup Selections Default Backup Selections Backup Selection Outlook PST Files My Desktop Notes Files (Multi-user) Notes Archive (Multi-user) Notes Files (Single-user) Notes Archive (Single-user) My Music My Pictures My Videos Description PST files in the default location All files on the Desktop Lotus Notes data for multiple user install Lotus Notes archive for multiple user install Lotus Notes data for single user install Lotus Notes archive for single user install All files in My Music (Music in Windows Vista) All files in My Pictures (Pictures in Windows Vista) All files in My Videos (Videos in Windows Vista)
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 1014 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 2 3 4 5 6 On the DLO navigation bar, click Setup. In the Settings pane, click Profiles. In the Results pane, select the profile you want to modify. In the task pane, under General Tasks, click Properties. Click the Backup Selections tab. Uncheck those backup selections you do not want to use.
1003
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. To add a backup selection: 1 2 3 4 5 6 On the DLO navigation bar, click Setup. In the Settings pane, click Profiles. In the Results pane, select the profile for which you want to add a backup selection. In the task pane, under General Tasks, click Properties. Click the Backup Selections tab in the Profile Properties dialog box. 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 8 Read the message that displays, and then click OK. 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 1005. To include or exclude specific files from this backup selection, see Including and Excluding Files or Folders from a Backup Selection on page 1006. To set revision control for this backup selection, see Setting Revision Control for a Backup Selection on page 1009. To set Delta File Transfer, encryption and compression options for this backup selection, see Setting Options for a Backup Selection on page 1010.
Click OK twice.
1004
Defining General Backup Selection Properties

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 1004 Modifying a Backup Selection on page 1014
From the General tab in the Backup Selection dialog box, select the appropriate options as follows:
Backup Selection General Dialog Box
Item Name Description
Description Type a descriptive name for the backup selection. 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 1012 for information on using macros to define the folders backed up by a backup selection. Select a pre-defined folder Select this option to choose a pre-defined folder from the list provided. Note See Using DLO Macros in Backup Selections on page 1012 for information on the macros used to define the pre-defined folders.
1005
About Backup Selections Backup Selection General Dialog Box (continued) Item Include subfolders Description Check this option to also back up all subfolders in the specified directory. This option is selected by default. On computers that run Microsoft Windows Vista, this option does not include the Music, Pictures, or Videos folders in the backup selection. On computers that run previous versions of Microsoft Windows, this option does include My Music, My Pictures, and My Videos folders in the backup selections.
Click OK.
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 969 Configuring Global Exclude Filters on page 1032 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:

From the Include/Exclude tab in the Backup Selection dialog box, select the appropriate options as follows:
Backup Selection Include/Exclude Dialog Box
Item Include all file types
Description Select this option to include all file types in this backup selection.
1006
About Backup Selections Backup Selection Include/Exclude Dialog Box (continued) Item Description
Include and exclude only Select this option to include or exclude only specific files or file the items listed below types. When this option is selected, a wildcard include is added to back up all files not specifically excluded.
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. 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. Select the appropriate options as follows:
Add Include Filter or Add Exclude Filter Dialog Box Options
Item Filter
Description 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. If you select Files and Folders in the Apply to option, you must use wildcards. If you do not use wildcards, the filter works for folders, but does not work for files. For example, to include or exclude files and folders that are titled Test, use the following filter: Test.* To include or exclude files and folders that include Test anywhere in the name, use the following filter: *Test*.* Click Extensions to select a predefined filter to either include or exclude all files with a given file extension.
Description Apply to
Type a description of this include or exclude filter. 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.
1007
Click OK.
Revision Control
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. 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 have 10 MB disk space consistent retaining three revisions of each file and of data to back up, approximately 30 MB of are required if file sizes remain 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 1009 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.
1008
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:

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 Number of revisions
Description
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.
1009
About Backup Selections Backup Selection Revision Control (continued) Item Limit to Description Check this option to limit the number of revisions retained in a given amount of time, and specify the following:

Note The oldest revision is deleted when a new revision is created that exceeds one of these limits. 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 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.
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:

1010
From the Options tab in the Backup Selection dialog box, select the appropriate options as follows:
Backup Selection Options
Item Delta File Transfer
Description 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. SeeAdding a new Maintenance Server on page 1017 for additional information. 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.
Compression
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 Indicate the number of days after which DLO will delete all file after versions from the desktop user data folder after the source file has been deleted from the desktop. network user data folder Indicate the number of days after which DLO will delete all file after versions from the network user data folder after the source file has been deleted from the desktop.
Click OK to save the backup selection.
1011
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 1005. The following macros are supported:
Table I-5 Folder Macros for use with Backup Selections Folders backed up 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 (for Windows XP) or the C:\Users\current user profile directory (for Windows Vista). The My Documents directory for the user who is logged on. The Favorites directory for the user who is logged on. The Printers directory for the user who is logged on. The Network Locations directory for the user who is logged on. The Desktop directory for the user who is logged on. The Recent Files directory for the user who is logged on. The Windows Program Files directory. Example:
Backup Selection Macro %LOCALFIXEDDRIVES%
%CURRENTUSERMYDOCS% %CURRENTUSERFAVORITES% %CURRENTUSERPRINTHOOD% %CURRENTUSERNETHOOD% %CURRENTUSERDESKTOP% %CURRENTUSERRECENT% %PROGRAMFILES%
%PROGRAMFILES%\lotus\notes\data\archives
1012
About Backup Selections Table I-5 Folder Macros for use with Backup Selections (continued) Folders backed up The Windows local application data directory:
Backup Selection Macro %LOCALAPPDATA%
On Windows XP:
Documents and Settings\<user_name>\Local Settings\Application Data
On Windows Vista:
Users\<user_name>\AppData\Local The following additional pre-defined folder macros are available for selection in the backup selection dialog box:
Table I-6 Folder Name My Documents My Music My Pictures My Videos Desktop Favorites PrintHood NetHood Recent All local fixed drives Macros for Pre-defined Folders in the Backup Selection dialog Pre-Defined Folder Macro %CURRENTUSERMYDOCS% %CURRENTUSERMYMUSIC% %CURRENTUSERMYPICTURES% %CURRENTUSERMYVIDEO% %CURRENTUSERDESKTOP% %CURRENTUSERFAVORITES% %CURRENTUSERPRINTHOOD% %CURRENTUSERNETHOOD% %CURRENTUSERRECENT% %LOCALFIXEDDRIVES% Folders Backed Up The My Documents directory for the user who is logged on. The My Music folder for the user who is logged on. The My Pictures folder for the user who is logged on. The My Videos folder for the user who is logged on. The Desktop directory for the user who is logged on. The Favorites directory for the user who is logged on. The Printers directory for the user who is logged on. The Network Locations directory for the user who is logged on. The Recent Files directory for the user who is logged on. All local fixed drives.
1013
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.
Modifying a Backup Selection

Profile backup selections can be modified from the DLO Administration Console. To modify a backup selection: 1 2 3 4 5 6 On the DLO navigation bar, click Setup. In the Settings pane, click Profiles. In the results pane, click the profile you want to modify. In the task pane, under General Tasks, click Properties. Click the Backup Selections tab. 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. Change the backup selection as described in the following topics: Defining General Backup Selection Properties on page 1005 Including and Excluding Files or Folders from a Backup Selection on page 1006 Setting Revision Control for a Backup Selection on page 1009 Setting Options for a Backup Selection on page 1010 9
1014
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. To delete a backup selection: 1 2 3 On the DLO navigation bar, click Setup. In the Settings pane, Click Profiles. In the results pane, click the profile that contains the backup selection you want to delete. In the task pane, under General Tasks, click Properties. From the Backup Selections tab, select the backup selection you want to delete. Click Delete. Click Yes.
4 5 6 7
Related Topics: Backup Selection Options on page 1011
1015
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 1032. 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.
1016
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 1018 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 1011. 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 1018. 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 969 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 1020. 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. 2 3 From the DLO Console, on the DLO navigation bar, click Setup. In the task pane, under Manage Tasks, click Maintenance servers.
1017
4 5 6 7
Click Add. Navigate to the computer where the maintenance server is installed. Select this computer. 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 users 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
Confirm that the desktop user account is configured for delegation. See Confirm that the Desktop Users Account is Configured for Delegation on page 1018. Confirm that the server process account is trusted for delegation.Confirm that the Server Process Account is Trusted for Delegation on page 1019.
Confirm that the Desktop Users Account is Configured for Delegation This process verifies that the desktop agent users account can be delegated.
1018
To confirm that the desktop users account is configured for delegation 1 2 Log on to the domain controller using a domain administrator account. On the taskbar, click the Start button, point to Programs and then Administrative Tools and click Active Directory Users and Computers. Under the domain, click the Users folder. Right-click the user account to be delegated and click Properties. Click the Account tab. In the Account options list, verify that the Account is sensitive and cannot be delegated is not selected. Click OK.
3 4 5 6
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 2 Log on to the domain controller using a domain administrator account. On the taskbar, click the Start button, point to Programs and then Administrative Tools and click Active Directory Users and Computers. Right-click the Computers folder and click Properties. Right-click the computer on which the maintenance server runs and then click Properties. On the General page, click Trust computer for delegation. Click OK.
3 4
5 6
1019
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 2 3 From the DLO Console, on the DLO navigation bar, click Setup. In the task pane, under Manage Tasks, click Maintenance servers. In the Maintenance Servers list, check the box for the maintenance server you want to set as the default. 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 2 3 4 5 6 7 8 9
1020
Verify that the new maintenance server has been installed and configured. On the DLO navigation bar, click Setup. In the task pane under Manage Tasks, click Maintenance servers. Select the maintenance server currently manages the file server. Click Edit. Select the file server you want to reassign. Click Reassign. Select the new maintenance server from the drop-down menu. Click OK three times.
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 users 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 1022 for additional information.
Supported Storage Location Configurations

The following table summarizes supported configurations for DLO Storage Locations:
Table I-7 Description All media server platforms Windows 2000 NAS/SAK NAS devices Local media server direct-attached storage SAN 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 NetWare 3.1x, 4.x, or E-Directory Storage Locations Storage Location Configuration Support Supported X X X X X X Not Supported
1021
About DLO Storage Locations Table I-7 Description UNIX file systems or SAMBA shares on UNIX systems Storage Location Configuration Support (continued) Supported Not Supported 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 Everyone Allow Full Control, Change, Read Allow Full Control, Change, Read
Security Permissions on NTFS Volumes Administrator Everyone Full control Allow Read & Execute Allow List Folder Contents Allow Read Special security permissions or advanced settings Allow Traverse Folder/Execute File Allow List Folder/Read Data Allow Read Attributes Allow Read Extended Attributes Allow Read Permissions Advanced Security Permissions on NTFS Volumes Administrator Allow Full Control
1022
About DLO Storage Locations Permission Settings for Hidden Shares (continued) Drive Type User or Group Everyone Permissions 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 Owner Full Admin Group Allow Full Control, Change, Read Allow Full Control, Change, Read Allow Full Control, Change, Read
Limited Admin Group Allow Read
Creating 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 will 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. Users 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 1046. 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
1023
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 2 3 4 On the DLO navigation bar, click Setup. In the selection pane, click File Servers. In the task pane, under Settings Tasks, click New Storage Location. Select the appropriate options as follows.
New Storage Location Dialog Box Item Computer name Path Description Type a computer name or browse to a computer on which to create the Storage Location. 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 servers domain. Storage Location name Summary Type a name for the new Storage Location. The name cannot contain any of the following characters: \@#$%^&*()=+|/{}[] 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 users 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.
1024
Click OK.
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 To create Storage Locations when the DLO administration service is a full administrator on the remote system 1 2 Validate that DLO 5.1 MP1 or later is installed. Ensure that the account credentials used for DLO services have full administrator rights to the remote storage location or NAS device. 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. 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.
1025
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 965. 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. 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. Create a folder on the remote storage location using an administrator, or administrator equivalent user. Share the new folder. Ensure that 'Everyone' has full-access to the share. 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. 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 8 Once the required fields are completed, click OK 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 b c Move or delete all users in the Storage Location. Manually remove the Storage Location share and folder from the server. Delete the Storage Location from the DLO Admin Console.
4 5
1026
About Automated User Assignments
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 2 On the DLO navigation bar, click Setup. In the selection pane, expand the file servers list by clicking the + next to File Servers. In the selection pane, Click the File Server on which the Storage Location resides. In the results pane, click the storage location you want to delete. In the task pane, under General Tasks, click Delete. Click Yes.
3 4 5 6
Related Topics: Managing Desktop Agent Users on page 1041 Modifying Automated User Assignments on page 1030 Deleting Automated User Assignments on page 1032

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.
1027
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 1041. 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 users 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. For information on modifying Automated User Assignment priorities, see Changing the Priority of Automated User Assignments on page 1031.
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 2 3 4 On the DLO navigation bar, click Setup. In the selection pane, click Automated User Assignments. In the task pane under Settings Tasks, click New user assignment. Select the appropriate options as follows:
New Automated User Assignment Dialog Box Options Item User Assignment User assignment name Type a name for the Automated User Assignment. The Automated User Assignment name cannot contain the following characters: \@#$%^&*()=+|/{}[] Description
1028
About Automated User Assignments New Automated User Assignment Dialog Box Options (continued) Item Assign using Domain and Group Domain Group Assign Using Active Directory Configure Description Select this option to match Desktop Agent users to Automated User Assignments based on their domain and group. Select the domain to which this Automated User Assignment will apply. Select the group to which this Automated User Assignment will apply. Select this option to match Desktop Agent users to Automated User Assignments based on Active Directory settings. 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 Profile Select a Storage Location to be assigned to the users in the selected domain and group. Select a profile to be assigned to the users in the selected domain and group.
1029
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 Object In LDAP Directory
Description For Automated User Assignments, the only option is User. 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 Select this option to apply the connection policy only to that match the criteria below those objects in the specified directory that match the criteria entered. Attributes Condition Value Select an attribute from the drop-down menu or type a custom attribute. Select the appropriate condition. Available options include =, <, <>, and >. Type a value to complete the criteria that will be used to determine matches. Wildcards can be used to specify the value.
Click OK.
Modifying Automated User Assignments

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 1044.
1030
To modify an Automated User Assignment: 1 2 3 4 5 On the DLO navigation bar, click Setup. In the selection pane, click Automated User Assignments. In the results pane, select the Automated User Assignment you want to modify. In the task pane, under General Tasks, select Properties. 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 2 3 On the DLO navigation bar, click Setup. In the selection pane, click Automated User Assignments. In the results pane, select the Automated User Assignment for which you want to change the priority. 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 2 3 4 On the DLO navigation bar, click Setup. In the selection pane, click Automated User Assignments. In the results pane, select an Automated User Assignment. In the task pane, under General Tasks, select Properties.
1031
Configuring Global Exclude Filters
Deleting Automated User Assignments

You can delete Automated User Assignments when you no longer need them. To delete an Automated User Assignment: 1 2 3 4 5 On the DLO navigation bar, click Setup. In the selection pane, click Automated User Assignments. Click the Automated User Assignment to be deleted. In the task pane, under General Tasks, click Delete. Click Yes.
Related Topics: About Automated User Assignments on page 1027 New Automated User Assignment Dialog Box Options on page 1028 Modifying Automated User Assignments on page 1030 Changing the Priority of Automated User Assignments on page 1031 Moving Desktop Agent Users to a new Network User Data Folder on page 1046 Modifying Desktop Agent User Properties on page 1044

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. When you add a global exclude, all previous backups that match the global exclude are deleted when their retention period expires. You set the retention period when you set up backup selections.
1032
See Adding Backup Selections in the Advanced View on page 1134. In the following circumstances, the backups are deleted immediately during the next maintenance cycle:

The retention period is set to 1 day. The default value for the time between maintenance cycles is used. The default value is 24 hours. If you change this value, it affects file rentention for all files. See Changing Default Global Settings on page 970.
To configure global excludes, see the following procedures: Specifying Files and Folders to Exclude from all Backups on page 1033 Specifying Email to Exclude from All Backups on page 1034 Specifying Files and Folders to Exclude from Compression on page 1036 Specifying Files and Folders to Exclude from Encryption: on page 1037 Specifying Files and Folders to Exclude from Delta File Transfer on page 1038 Using DLO Macros to Define Global Excludes on page 1040
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 2 3 From the Tools menu in the DLO Administration Console, select Global Excludes. Select the Files/Folders tab. Default Files/Folders global excludes are listed. To exclude all files greater than a specific size, check the Exclude all files greater than check box and enter a size in KB. To Exclude all files modified before a specified date, check the Exclude all files modified before check box and enter a date.
1033
To add a new Files/Folders global exclude, click Add and configure as follows:
Add Global Exclude Filter Dialog
Item Filter
Description 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.
Type a description of the global exclude. Indicate whether this global exclude should apply to files, folders, or both files and folders.
6 7
Click OK. To edit a global exclude filter, click Edit and configure as described in the step 5 above. 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. 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.
1034
To specify email attachments to exclude from all backups: 1 2 3 From the Tools menu in the DLO Administration Console, select Global Excludes. Select the Email tab. To exclude from all backup attachments greater than a specific size, check the Exclude all attachments greater than check box and enter a size in KB. This feature does not apply to Lotus Notes emails. To Exclude from all backup messages received before a specified date, check the Exclude all messages received before check box and enter a date. To Add a new email global exclude, click Add and configure as follows:
Add Global Email Exclude Filter Dialog Item Attachment file type Description 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 Description Type the name of the mail folder you would like to exclude from backup. Type a description of the global exclude.
6 7
Click OK. 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. 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.
1035
Click OK.
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 2 From the Tools menu in the DLO Administration Console, select Global Excludes. To exclude files or folders from compression, select the Compressed Files tab. Default compressed files global excludes are listed. To exclude all files greater than a specific size from compression, check the Exclude all files greater than check box and enter a size in KB. To Add a new compressed file global exclude, click Add and configure as follows:
Add Global Compression Exclude Filter Dialog Item Filter Description 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 Apply to Type a description of the global exclude. Indicate whether this global exclude should apply to files, folders, or both files and folders.
Click OK.
1036
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. 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. 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 2 From the Tools menu in the DLO Administration Console, select Global Excludes. To exclude files or folders from encryption, select the Encrypted Files tab. Default encrypted files global excludes are listed. To exclude files greater than a specific size from encryption, check the Exclude all files greater than check box and enter a size in KB. To Add a new encrypted file global exclude, click Add and configure as follows:
Add Global Encryption Exclude Filter Dialog Item Filter Description 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.
1037
Configuring Global Exclude Filters Add Global Encryption Exclude Filter Dialog (continued) Item Apply to Description Indicate whether this global exclude should apply to files, folders, or both files and folders.
5 6
Click OK. 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. 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.
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 2 From the Tools menu in the DLO Administration Console, select Global Excludes. 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 Exclude all files greater than check box and enter a size in KB. To exclude files smaller than a specific size from Delta File Transfer, check the Exclude all files less than check box and enter a size in KB.
1038
To Add a new Delta File Transfer global exclude, click Add and configure as follows:
Add Global Delta File Transfer Exclude Filter Dialog
Item Filter
Description 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.
Type a description of the global exclude. Indicate whether this global exclude should apply to files, folders, or both files and folders.
6 7
Click OK. 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. 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. Click OK.
Related Topics: Using Delta File Transfer on page 1016
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.
C:\Windows\System32\Config
1039
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 1001 Configuring Global Exclude Filters on page 1032
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.
Table I-8 Macro %TEMP% %WINDIR% Global Exclude Macros Folder The temp directory for the user who is logged on. The Windows directory. Example: C:\Windows or C:\Winnt %WEBTEMP% %RECYCLED% %SYSTEM% The web cache for the user who is logged on. Recycle bins The Windows system directory. Example: C:\Windows\system or C:\Winnt\system
1040
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 1027 Adding a Single Desktop User to DLO on page 1042 Importing Multiple Desktop Users Who Have Existing Network Storage on page 1043 Viewing a List of Desktop Agent Users on page 1048 Modifying Desktop Agent User Properties on page 1044 Enabling or Disabling DLO Access For a Desktop User on page 1044 Deleting a User from DLO on page 1045 Moving Desktop Agent Users to a new Network User Data Folder on page 1046
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 2 3 4 5 6 7 Create or locate a network share on the computer where backup files will be stored. Right-click the share you created in step 1, and then select Properties. Click the Sharing tab. Verify that Share this folder is selected. Click Permissions. Select the following permissions for user Everyone: Full Control, Change, Read Click OK.
1041
8 9
Click the Security tab. Click Advanced.
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 1027). 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 2
1042
On the DLO navigation bar, click Setup. In the selection pane, Click Users.
3 4
In the task pane, under User Tasks, click New user. Complete the appropriate options as follows:
New User Properties
Item Enable User User Profile User data folder
Description Select this option to enable this user to use the Desktop Agent, or clear it to prevent the user from using the Desktop Agent. Browse to the username or type it in the form DomainName\UserName. Select the profile that you want to assign to this user. 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 users backup files will be stored. This must be an existing folder, and the security attributes must be set for the folder according to your organizations 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
1043
To import multiple desktop users from a file: 1 2 3 4 On the DLO navigation bar, click Setup. In the selection pane, click Users. In the task pane, under User Tasks, click Import users using wizard. Follow the wizard prompts.
Modifying Desktop Agent User Properties

1 2 On the DLO navigation bar, click Setup. In the selection pane, click Users. Users are listed in the results pane. 3 4 5 Select the user you want to modify. In the task pane, under General Tasks, select Properties. Select the appropriate options as follows:
User Properties Item Enable User User Profile Description Select this option to enable this user to use the Desktop Agent, or clear it to prevent the user from using the Desktop Agent. The name of the user. This field cannot be edited. Select a profile to apply to this user.
network user data folder This is the location where the users 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 1046.
Enabling or Disabling DLO Access For a Desktop User

This option allows to you either allow or prevent a user from using the Desktop Agent.
1044
To enable or disable DLO access for a desktop user: 1 2 3 4 5 On the DLO navigation bar, click Setup. In the selection pane, click Users. Users are listed in the results pane. Select the user you want to modify. In the task pane, under General Tasks, select Properties. 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 users entry from DLO. Before deleting the user from the DLO Administration Console database, you should uninstall the Desktop Agent from the users 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 users computer, disable the user (see Enabling or Disabling DLO Access For a Desktop User on page 1044). To delete a user from the DLO database: 1 2 3 4 5 6 Uninstall the Desktop Agent from the users computer. On the DLO navigation bar, click Setup. In the selection pane, click Users. Click the user or users you want to delete. In the task pane, under General Tasks, click Delete. To delete the data stored in the user data folder, check Delete data stored in the user data folder.
1045
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 users 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 1041. 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 2 3 4 On the DLO navigation bar, click Setup. In the selection pane, click Users. Select one or more user to be moved. In the task pane, under User Tasks, click Move network user data folder.
1046

Move User
Item User From Destination Move the user data folder to an existing Storage Location
Description Lists the domain and user name of the selected user or users. Lists the current network user data folder location.
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.
Move the contents of the Select this option to specify a new Storage Location. Type the user data folder to an path in the box provided, or click Browse and navigate to the alternative location new location. A new network user data folder will be created in the new Storage Location for each user who is moved.
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 users 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 1 Restore the user data as described in Restoring Files and Folders from the DLO Administration Console on page 1055 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.
1047
Managing Desktop Computers
Viewing a List of Desktop Agent Users

1 2 On the DLO navigation bar, click Setup. In the selection pane, click Users to list users in the results pane.

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 2 3 On the DLO navigation bar, click Setup. In the selection pane, click Computers. Right-click the computer for which you want to modify properties, and click
Properties.
4 5
To modify the backup schedule for the computer, click the Schedule tab. Configure the schedule as follows:
Profile Schedule Dialog Box
Item Use Profile schedule
Description 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.
1048
Managing Desktop Computers Profile Schedule Dialog Box (continued) Item Use customized 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 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. Select this option to require that the DLO Administrator or desktop user initiate backups manually. Description Select this option in the drop-down menu to specify a customized schedule that differs from the profile schedule.
To modify computer options, click the Options tab and configure the computer options as follows:
Additional Profile Options
Item Use Profile options
Description 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.
1049
Managing Desktop Computers Additional Profile Options (continued) Item Limit disk space usage on my computer to Description 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. Log file maintenance Keep log files for a minimum of (days) 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. After minimum number Type the maximum combined size of all log files to be retained of days, delete oldest log before the oldest log files are deleted. files when combined Note You may have more than the specified number of MB of log size exceeds (MB) files stored if none of the log files are as old as specified in the keep log files for a minimum of (days) setting. Logging options Log groom messages Log information messages for backup Log warning messages Mail options Select this check box to create logs for grooming operations. Select this check box to create logs for all backup operations. Select this check box to create logs for all operations that generate warnings.
1050
Managing Desktop Computers Additional Profile Options (continued) Item Enable incremental backups of Outlook PST files Description 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 1162. Note Synchronized files cannot be backed up incrementally. For additional information, see Backing up Outlook PST files Incrementally on page 1139. Enable incremental backups of Lotus Notes email files 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 1141. 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 8
To view the computer backup folders, click the Backup Folders tab. To modify the computer backup selections, click the Backup Selections tab. See Adding a Backup Selection on page 1004. Profile backup selections are not listed, and can only be modified directly in the profile as described in Modifying a Backup Selection on page 1014.
To view synchronized selections for a computer schedule, click the Synchronized

Selections tab.
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 1151. 10 To view and modify connection policies, click the Connection Policies tab.
1051
Profile defined connection policies can only be modified in the profile. See Customizing Connection Policies on page 1149.
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 2 3 4 On the DLO navigation bar, click Setup. In the selection pane, click Computers. In the results pane, select one or more computers to be enabled or disabled. 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 2 3 4 5 On the DLO navigation bar, click Setup. In the selection pane, click Computers. In the results pane, select one or more computers to be deleted. In the task pane, under General Tasks, click Delete. When asked if you want to delete each selected computer and all backup files, click Yes.
1052
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 2 3 On the DLO navigation bar, click Setup. In the selection pane, click Computers. In the results pane, select one or more computers on which to run an immediate backup. 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 2 3 On the DLO navigation bar, click Setup. In the task pane, under Tool Tasks, click Blackout windows. From the File Server list, select a network resource for which you want to configure a blackout window. Do one of the following:

To edit an existing schedule, select it from the drop-down menu. To create a new schedule click New.
1053
Configure the schedule as follows:

Blackout Window Schedule Description Select this check box to activate this schedule. Select the frequency of occurrence. Selections include on a specific date and weekly. 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.
Table I-9 Item Enable Schedule Occurs Starts at
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.
Click OK.
Deleting a Blackout Window Schedule

To delete a blackout window schedule: 1 2 3 4 5 On the DLO navigation bar, click Setup. In the task pane, under Tool Tasks, click Blackout windows. Under Schedules, select the schedule to be deleted. Click Delete. Click OK.
1054
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. DLO does not restore a file to its original location if the file is in use by another application. If DLO encounters a file that is in use, you can do one of the following tasks to restore the file:
Schedule a time to restore the file. The file is restored after the computer restarts. You are not notified when the file is restored. Log on to the desktop computer with an administrative account. After you log on with an administrative account, run a restore job to overwrite the locked file and restore it. Close the file in the other application. Restore the file to an alternate location.
To restore files and folders from the DLO Administration Console: 1 2 On the DLO navigation bar, click Restore. In the Computer pane, click the desktop from which the data to be restored originated. In the Backup Folder pane tree view, select the folder containing the files you want to restore. To restore the entire folder, check the folder in the Backup Folder pane. To restore specific files, check the files in the File Version pane. 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 1008 for additional information.
4 5 6
1055
7 8
In the task pane, under Restore Tasks, click Restore files to open the Restore dialog. Select the appropriate options as follows, and then click OK:
Restore Dialog Box
Item Restore destination Restore to original computer
Description
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 Redirect the restore to an alternate folder
Select this option to restore the file or folder to its original location. 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. Note You can browse only if the Windows Firewall is turned off.
Restore to an alternate computer
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.
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 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 1047 for additional information.
1056
Restoring Files and Folders from the DLO Administration Console Restore Dialog Box (continued) Item Preserve folder structure Description 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 Select Preserve security attributes on restored files to restored files 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.
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.
1057
Searching for Files and Folders to Restore

To search for desktop files and folders to restore: 1 2 On the DLO navigation bar, click Restore. In the Computer pane, click the desktop on which you would like to search for files to restore. In the task pane, under Restore Tasks, click Search for files to restore. Select the appropriate options as follows:
Search Dialog Box Options Item Search for file names with this text in the file name Modified Description Type all or part of the name of the file or folder you want to find. Wildcard entries are accepted, for example *proj.doc. Select this option to search for files that were modified during a specific time frame, and then select the time frame. Select this option to search for files modified on the current calendar day. Select this option to search for files modified in the last calendar week. Select this option to search for files modified during a range of days. Select this check box to select a file type from the list provided. Select this check box and then enter information as follows:
3 4
Today Within the past week Between Of the following type Of the following size
Select from equal to, at least, or at most in the first drop-down menu. Type a file size. Select KB, MB, or GB.
5 6
1058
Click Search. 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 8 Click Restore. Select the appropriate options as outlined in Restoring Files and Folders from the DLO Administration Console on page 1055. Click OK.
1059
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 1061 Recovering Data for a Single User without Using DLO Emergency Restore on page 1062 Recovering a Damaged or Corrupt media server on page 1063 Recovering a damaged or corrupt File Server on page 1063
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.
1060
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 1060 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. Use the DLO Command Line Interface to restore the data to DLO. dlocommandu -emergencyrestore <usersharepath> -w <RecoveryPassword> -ap <destination-path>
1061
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 2 Take both the File Server and media server offline 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. 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. Restore the configuration database to the media server. The default database path is C:\Program Files\Symantec\Backup Exec\Data. Restart the media server. Use the DLO Console to restore the user's data. Select Restore to an alternate computer and restore the data to a temporary location. Restore both the File Server and media server back to the most recent state.
5 6
1062
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 2 3 Fix or replace the failed disk Restore the entire disk from the backup copy 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. Install DLO on the new media server. Be sure to use the same version of DLO as was installed on the failed media server. 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. 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 2 3 Fix or replace the failed disk Restore the entire disk from the backup copy Restart the computer
1063
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. 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. Restore the DLO file data.
1064
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:
Table I-10 Item User Computer
Computer History pane Description The user name of the user who is logged on to the desktop that generated the message. The name of the desktop that generated this message. 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 984.
Last Backup Result
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 988
Backup Mode
The backup mode specified in the profile. Backup modes include:

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.
1065
Monitoring DLO Job Histories Table I-10 Item Desktop Data Folder Size Network Data Folder Size Network Data Folder Path Computer History pane (continued) Description 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.
The Job History pane displays the following information:

Table I-11 Item Start Time End Time Operation Status Files Protected (Desktop) Size Protected (Desktop) Files Protected (Network) Size Protected (Network) Errors Job History pane Description The time the job was started. The time the job ended. The operation performed in this job, such as backup or restore. The current status of the job, such as active, completed, completed with errors, completed with warnings, canceled, or failed. The number of files copied to the desktop user data folder during the job. The total bytes of data copied to the desktop user data folder during the job. The number of files copied to the network user data folder during the job. The total bytes of data copied to the network user data folder during the job. The number of errors, if any, that were generated during the job.
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.
1066
To set job history view filters: 1 2 3 On the DLO navigation bar, click History. Click the desktop for which you want to view the history. On the task pane, under Job History View Filters, click one of the following:
Type of Jobs Viewed in the History View Item List all jobs Description Lists history logs for all jobs that have run on the selected desktop. These may include backup, synchronization, restore, or move user jobs. Lists history logs only for backup jobs that have run on the selected desktop. Lists history logs only for restore jobs that have run on the selected desktop.
List backup jobs only List restore jobs only
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 Show successful jobs
Description 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 Show canceled jobs Lists history logs for all jobs that generated errors on the selected desktop. Lists history logs for all jobs that were cancelled on the selected desktop.
Select a time frame for filters to be displayed by selecting one of the following:
Time Frame for Job Histories viewed
Item Show last 24 hours
Description Lists history logs that have been generated in the last 24 hours, and that meet all other filtering criteria.
1067
Monitoring DLO Job Histories Time Frame for Job Histories viewed (continued) Item Show last 7 days Show all Description Lists history logs that have been generated in the last 7 days, and that meet all other filtering criteria. 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 2 3 4 On the DLO navigation bar, click History. In the History pane, select the computer for which you want to view a history log. In the Job History pane, click the log you want to view. 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. To filter the results, select the appropriate options as follows:
Log File Viewer Filtering Options Item Search for log entries in All log files Current log file With timestamp Select this option to show all log entries in the log file viewer. Select this option to search only those log entries in the current log file. 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. Description
1068
Monitoring DLO Job Histories Log File Viewer Filtering Options Item Of the following type Description 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
6 7 8
Click Search. Double click on a log entry to view additional details. Click Close.
Searching History Logs

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.
1069
To search for log files using the DLO Administration Console: 1 2 On the DLO navigation bar, click History. In the task pane, under General Tasks, click Search log files to display the log file viewer. Set filtering options as discussed in step 5 on page 1068. Click Search. Double click on a log entry to view additional details. Click Close.
3 4 5 6
1070
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 1076 for additional information. Following are descriptions of the types of alerts:
Table I-12 Alert Type Informational Alert Categories Description Notifies you that an expected action has occurred, such as the successful completion of a backup or restore job.
1071
Monitoring Alerts on the DLO Administration Console Table I-12 Alert Type Warning Alert Categories (continued) Description 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. 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.
Error
Possible alerts are listed in the following table:

Table I-13 Type Errors 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 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. A backup job has completed, but errors were generated. A restore job has completed, but errors were generated. Name DLO Alerts Description
Desktop user data folder storage limit has been reached
Filename, directory name, Indicates either a storage system problem that requires or volume label syntax is attention, or a file name denied by SRM software. If the incorrect. latter, these files should be added to DLOs global exclude list. See Configuring Global Exclude Filters on page 1032 for additional information. Network user data folder disk space full The volume containing the network user data folder is full. There is insufficient free disk space to back up the current file.
1072
Monitoring Alerts on the DLO Administration Console Table I-13 Type Name Network user data folder storage limit has been reached Unable to configure the Desktop Agent Warnings A backup job has A backup job has completed, but warnings were generated. completed with warnings A restore job has A restore job has completed, but warnings were generated. 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 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. DLO Alerts (continued) Description 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.
Desktop user data folder The amount of stored backup data in a users desktop user approaching storage limit data folder is approaching the specified size limit. Desktop user data folder disk space low Evaluation period daily reminder Evaluation period has expired 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.
Network user data folder The amount of stored backup data in a users network user approaching storage limit data folder is approaching the specified size limit. Network user data folder disk space low No backups in 14 days The volume containing the network user data folder is running low. A desktop computer has not performed a backup for 14 days.
1073
Monitoring Alerts on the DLO Administration Console Table I-13 Type Name No backups in 28 days No backups in 7 days No matching automated user assignment 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 User was configured 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. A new user connected and was successfully configured. DLO Alerts (continued) Description A desktop computer has not performed a backup for 28 days. A desktop computer has not performed a backup for 7 days. A new user connected, but no matching Automated User Assignment was found.
Configuring Alerts
To configure alerts: 1 2 3 On the DLO navigation bar, click Alerts. In the task pane, under Alert Tasks, click Configure alerts. Check the alerts you want to receive, and clear the check boxes for the alerts you do not want to receive. To send notification to recipients when the selected alerts are generated, do the following:
1074
Note Alerts must be configured for notification before selecting recipients. See Configuring Alerts for Notification on page 1076 and Configuring Recipients for Notification on page 1081 for additional information.
Select one or more alerts from the list. To select multiple alerts, click one item and press <Ctrl> or <Shift> 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.
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. To view DLO alerts: 1 2 On the DLO navigation bar, click Alerts. 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 Show errors Show warnings Show information Description Lists error alerts for the selected view. Lists warning alerts for the selected view. Lists informational alerts for the selected view.
1075
Configuring Alerts for Notification
To view the properties of an alert, right-click the alert in the Active Alerts or Alert History list and select properties. 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. 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 2 3 4 On the DLO navigation bar, click Alerts. If needed, filter the Alerts view as described in To view DLO alerts: on page 1075. From the alert list, select one or more alerts that you want to clear. 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.

DLO has several methods to notify you of alerts:

SMTP MAPI Lotus Notes email Pagers Printers Net Send Configure the methods you want to use to notify the recipient. Printer and Net Send notification methods do not require pre-configuration.
To use notifications you must perform the following:
1076
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 1077. MAPI email Notification. See Configuring MAPI email for Notification on page 1078. VIM (Lotus Notes) email Notification. See Configuring VIM email for Notification on page 1079. Pager Notification. See Configuring a Pager for Alert Notification on page 1080.
Configuring SMTP Email 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 2 3 From the Tools menu, click Email and Pager Notification. Click the SMTP Configuration tab. Select the appropriate options as follows:
SMTP Configuration dialog box Item Enable SMTP mail server Description Select this check box to activate the notification method. 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. Defaults to a standard SMTP port. In most cases, the default should not have to be changed.
SMTP port
1077
Configuring Alerts for Notification SMTP Configuration dialog box (continued) Item Sender Name Description 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 SMTP server login sender password confirm password
Select this check box to enable SMTP authentication Type the SMTP server login credentials Type the password for this login. Re-type the password again to confirm.
Click OK.
Related Topics: Configuring Recipients for Notification on page 1081
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 2 From the Tools menu, click Email and Pager Notification. Click the MAPI Configuration tab.
1078

MAPI Configuration dialog box
Item Enable Mail server name Mailbox name of sender
Description Select this check box to activate the notification method. Type the name of the Exchange server. You must use an Exchange server to which the DLO service account has access. 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.
Click OK.
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 2 3 From the Tools menu, click Email and Pager Notification. Click the VIM Configuration tab. Select the appropriate options as follows:
VIM Configuration dialog box Item Enable Notes client directory Description Select this check box to activate the notification method. Type the path of the directory in which the Notes client is located.
1079
Configuring Alerts for Notification VIM Configuration dialog box (continued) Item Mail password Confirm mail password Description Type the password that enables you to connect to the Notes client. Re-type the password that enables you to connect to the Notes client.
Click OK.
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 2 3 From the Tools menu, click Email and Pager Notification. Click the Pager Configuration tab. Select the appropriate options as follows:
Table I-14 Item Enable Select a modem for sending pages Description Check Enable to activate this alert notification method. Select a modem from the list. Only modems that are recognized in Windows appear in the list.
Click OK.
1080
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 1076
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. To configure SMTP mail for a person recipient: 1 2 3 4 5 6 From the Tools menu, click Recipients. Click New. Click Person. Click OK. In the Name field, type the name of the recipient that you want to configure. Click the SMTP Mail tab.
1081

SMTP Mail dialog box
Item Enable Address Test
Description Select this check box to activate this notification method for the recipient. Type the email address of the person to whom the notification message will be sent. For example, john.smith@company.com. 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 Type the total number of notifications that can be sent to the times within x minutes 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. Reset the notification limits after x minutes 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.
Limit when notifications can be sent Enable Schedule Select this check box to activate the option and configure the length of time the recipient is available for notification. 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 1093.
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.
1082
To configure MAPI mail for a person recipient: 1 2 3 4 5 6 7 From the Tools menu, click Recipients. Click New. Click Person. Click OK. In the Name field, type the name of the recipient that you want to configure. Click the MAPI Mail tab. Select the appropriate options as follows:
MAPI Mail dialog box Item Enable Mailbox Description Select this check box to activate this notification method for the recipient. 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. Enables you to test the notification configuration for the recipient.
Test
Notify me a maximum of x Type the maximum number of notifications sent to the recipient times within x minutes 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. Reset the notification limits after x minutes 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.
Limit when notifications can be sent
1083
Configuring Recipients for Notification MAPI Mail dialog box (continued) Item Enable Schedule Description Select this check box to activate the option and configure the length of time the recipient is available for notification. 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 1093.
Click OK.
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 2 3 4 5 6 7 From the Tools menu, click Recipients. Click New. Click Person. Click OK. In the Name field, type the name of the recipient that you want to configure. Click the VIM Mail tab. Select the appropriate options as follows:
VIM Mail dialog box Item Enable Address Test Description Select this check box to activate this notification method for the recipient. Type the email address of the recipient to whom the notification message will be sent. For example, JohnSmith@company.com. Enables you to test the notification configuration for the recipient. Administrators Guide
1084
Configuring Recipients for Notification VIM Mail dialog box (continued) Item Description
Notify me a maximum of x Type the total number of notifications sent to the recipient for times within x minutes 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. Reset the notification limits after x minutes 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.
Configuring a Pager for a Person Recipient

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 2 3 4 5 From the Tools menu, click Recipients. Click New, and then click Person. Click OK. In the Name field, type the name of the recipient that you want to configure. Click the Pager tab.
1085

Pager dialog box
Item Enable Carrier Phone
Description Select this check box to activate this notification method for the recipient. Type the area code and phone number to access the paging service providers modem. The paging service number may be different from the number you enter to manually send a page. Enter the country or region name and country code in which the pager is located. 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 pagers phone number.
Country/region name and code Pager Pin
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 1087. Enables you to test the notification configuration for the recipient.
Test
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. Administrators Guide
1086
Configuring Recipients for Notification Pager dialog box (continued) Item Schedule Description 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 1093.
Click Advanced to configure advanced pager setup options and select the appropriate options as follows:
Advanced Pager Information dialog box
Item Pager Configuration Password Message Length
Description
Type the password for the pager, if one is required. Type the maximum number of characters you want to use for messages. The number is determined by the paging service provider. Type the number of times you want the paging service provider to retry the page. The number is determined by the paging service provider.
Retrys
Pager type Numeric Alpha-numeric 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. Select the communication protocol. In most cases, you should use the Windows default. Select this option if you are configuring a pager that accepts only numbers. Select this option if you are configuring a pager that accepts letters and numbers.
Data bits, Parity, Stop bit
Click OK to save the settings in the Advanced Pager Information dialog box, and then click OK to save the pager configuration settings.
1087
Configuring a SNMP Trap Recipient

To configure a SNMP Trap as a recipient: 1 2 3 4 5 From the Tools menu, click Recipients. Click New. Click SNMP Trap. Click OK. Select the appropriate options as follows:
SMTP Mail dialog box Item Name Host Port Description Type a name for the SNMP Trap recipient. Type the name of the SNMP host computer. Enter the SNMP port number. The default SNMP port is 162.
Limit when notifications can be sent Enable Schedule Select this check box to activate the option and configure the length of time the recipient is available for notification. 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 1093. Administrators Guide
1088
6 7
Click OK. Click Close.
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 2 3 4 From the Tools menu, click Recipients. Click New and then click Net Send. Click OK. Select the appropriate options as follows:
Net Send Recipient Properties dialog box Item Name Target Computer or User Name Description Type the name of the recipient for whom you are configuring the notification. 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 Test Select All Computers to send the notification to all the computers in the network. Enables you to test the notification configuration for the recipient.
1089
Configuring Recipients for Notification Net Send Recipient Properties dialog box (continued) Item Description
Click OK.
1090
Configuring a Printer Recipient

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 2 3 4 From the Tools menu, click Recipients. Click New and then click Printer. Click OK. Select the appropriate options as follows:
Printer Recipient Properties dialog box Item Name Description Type the recipient for whom you are configuring the notification. You cannot use a fax printer device to receive the notification. Select the name of the printer to which the notification message will be sent. Enables you to test the notification configuration for the recipient.
Target Printer Test
Limit when notifications can be sent
1091
Configuring Recipients for Notification Printer Recipient Properties dialog box (continued) Item Enable Schedule Description Select this check box to activate the option and configure the length of time the recipient is available for notification. 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 1093.
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 2 3 4 From the Tools menu, click Recipients. Click New and then click Group. Click OK. In the Group Name field, type the name of the group for whom you are configuring the notification. Do one of the following:
Table I-15 Item To add members to the group Description
Select recipients from the All Recipients list, and then click Add to move them to the Group Members list.
To remove members from Select recipients from the Group Members list, and then the group click Remove to move them to the All Recipients list.
Click OK. The new group can be added to other groups.
1092
Scheduling Notification for 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. See Configuring Recipients for Notification on page 1081 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 3 Click Schedule. Do any of the following:
Scheduling Notification Item Include work days Include weeknights Include weekends Description Clear the Include work days check box to exclude Monday through Friday from 8 A.M. to 6 P.M. Clear the Include weeknights check box to exclude Monday through Friday from 6 P.M. to 8 A.M. Clear the Include weekends check box to exclude Saturday and Sunday, 24 hours a day.
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.
1093
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 2 3 4 From the Tools menu, click Recipients. Select the recipient you want to edit. Click Properties. 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.
1094
Editing Recipient Notification Methods

You can configure new notification methods or edit existing notification methods after you configure recipients. To edit notification methods: 1 2 3 From the Tools menu, click Recipients. Select the recipient to be edited and click Properties. Edit notification properties for the following types of notification methods:

SMTP Configuration. See SMTP Configuration dialog box on page 1077. MAPI Configuration. See MAPI Configuration dialog box on page 1079. VIM Configuration. See VIM Configuration dialog box on page 1079. Pager Configuration. Click Enable to activate or clear the notification method, and then select a modem from the Configured Modems list.
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 2 From the Tools menu, click Recipients. Select the recipient you want to delete, and then click Remove.
1095
DLO Reports
3 4
Click OK. You can start the job after configuring the new recipients or edit recipient properties or select other options from the Properties pane.
DLO Reports
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 Active Alerts Active Alerts by Computer Active Alerts by User Alert History Alert History by Computer Alert History by User Failed Backups
Description A list of all currently active alerts arranged chronologically. A list of all currently active alerts sorted by computer name. A list of all currently active alerts from all computers sorted alphabetically by Desktop Agent user name. A chronological list of alerts that have been sent by all computers in the past. A list of alerts that have been sent by all computers in the past, sorted by computer name. A list of alerts that have been sent by all computers in the past, sorted by Desktop Agent user name. A chronological list of computers that have a failed status for the last backup.
1096
DLO Reports DLO Reports (continued) Report Name Description
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 Last Backup Status by Computer A chronological list of the last backup status for all Desktop Agent computers. 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.
Related Topics: Viewing Report Properties on page 1098 Running a Report on page 1097
Running a Report
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 2 3 On the navigation bar, click Reports. On the Reports pane, select the report you want to run. In the task pane, under Reports Tasks, click Run report now.
1097
DLO Reports
Select the appropriate parameters for the data you want to include in the report from the following available parameters:
Report Filters
Item Computer User Days
Description Select this option to create a report for a specific computer, and then enter a desktop computer name. Select this check box to create a report for a specific desktop user, and then enter the users name. Select this option to create a report for a specific number of days, and then enter the number of days.
5 6
Click OK to run the report. The report can be printed or saved before it is closed. 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 2 3 On the navigation bar, click Reports. On the Reports pane, select the report for which you want to view properties. In the task pane, under General tasks, click Properties. The Report dialog box provides the following information:
Report Properties Item Title Description Description The name of the report.
The type of data that is included in the report.
1098
DLO Reports Report Properties (continued) Item Category Description
Classification for the report. Available report categories include:

Alerts Last Backup Status Failed Jobs
Author Subject Keywords File name File size Creation Date
The creator of the report.
The version of the product for which the report was created.
The primary information used to categorize the report.
The file name of the report template. The size of the report template. The date the report was installed on the system.
Click OK.
1099
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 767.
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 12 and the Desktop and Laptop Option to an existing cluster: 1 Install Backup Exec 12 on the active cluster node. Be sure to include the Desktop and Laptop Option during the Backup Exec installation. Install Backup Exec 12 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.
1100
To upgrade an existing Backup Exec 9.x or 10.x cluster that includes DLO: 1 Install Backup Exec 12 on the active Backup Exec cluster node. Be sure to include the Desktop and Laptop Option during the Backup Exec installation. Install Backup Exec 12 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 12 on the active Backup Exec cluster node. Do not select the DLO option. Install Backup Exec 12 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. Install DLO on all cluster nodes. All nodes must have DLO before you can recluster them. 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. Add all cluster nodes that were upgraded. The DLO services are added to the Cluster Administrator.
1101
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. In the text file, type the name of the new DLO server on the first line and save the file. 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. 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. 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 722 Uninstalling Backup Exec from a Microsoft cluster on page 696 Installing the Backup Exec Desktop and Laptop Option on page 956 Installing Backup Exec on a Microsoft Cluster Server on page 694
1102
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 1103 Commands in Detail on page 1104
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:
Table I-16 Option C <computer> N <user> W <password> Remote Server Options Description Remote computer name, default to local computer Fully qualified user name, e.g. Enterprise\GFord. The default is the current user User password if n is specified
1103
Commands in Detail
See the following topics for detailed information on available commands:

-AssignSL Command on page 1104 -EnableUser Command on page 1106 -ChangeServer Command on page 1107 -KeyTest Command on page 1108 -ListProfile Command on page 1109 -ListSL Command on page 1110 -ListUser Command on page 1111 -LogFile Command on page 1112 -Update Command on page 1113 -EmergencyRestore Command on page 1115 -SetRecoveryPwd Command on page 1116 -NotifyClients Command on page 1116 -InactiveAccounts Command on page 1116 -RenameDomain Command on page 1117 -RenameMS Command on page 1117 -LimitAdminTo Command on page 1118 -IOProfile Command on page 1119
-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 1046 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.
1104
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 ] 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 NI <newSLID> A F <file server> P <profile name> PI <profile id> S <SL name> SI <SL id> U <user> Description The -NI option is used to specify the name of the new storage location. Assigns a new storage location to all users. Assigns a new storage location to users with storage locations on the named file server. Assigns a new storage location to users with named profile. Assigns a new storage location to users with given profile id. Assigns a new storage location to users with named storage location. Assigns a new storage location to users with the given storage location ID. Assigns a new storage location to named user account only.
Examples: DLOCommandu assignsl NI DLO_SL02 A DLOCommandu assignsl NI DLO_SL03 U mmouse
1105
-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. 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 A E | D F <file server> P <profile name> PI <profile id> S <SL name> SI <SL id> U <user> Description Enables or disables all users on the media server. Enables or disables a user account. The default value is to enable a user (i.e. E). Enables or disables users with storage locations on the named file server. Enables or disables users with the specified profile name. Enables or disables users that are assigned to the specified profile. Enables or disables users assigned to the specified storage location. Enables or disables users in the specified storage location. Enables or disables only the user with the specified user name.
Examples: DLOCommandu enableuser E A

DLOCommandu enableuser D U mmouse
-ChangeServer Command
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 users current profile settings and existing backup files are not moved. They remain on the original file server. Syntax: DLOCommandu ChangeServer M <media server> [ A | F <file server> | P <profile name> | PI <profile id> | S <SL name> | SI <SL id> | SP <SL path> | U <user> ] 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.
1107
Command Options:
ChangeServer Command Options Option A F <file server> M <media server> P <profile name> PI <profile id> S <SL name> SI <SL id> SP <SL path> U <user> Description Switches all users (default). Switches users with storage locations on the named file server. The new media server name. Switches users based on profile name. Switches users based on profile id. Switches users based on storage location name. Switches users based on storage location id. Switches users based on storage location path. 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\EnterpriseMNoel
-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
1108
Command Options: The following options can be used independently or in combination.

KeyTest Command Options Option -f -quar Description The -f option forces a full scan for all users even if the data has already been validated. 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 users network user data folder. If this option is not specified the data will be scanned and reported but will not be quarantined. The -purge option deletes any previously quarantined data.
-purge
Examples:
Check for unrestorable data that has not DLOCommandu keytest 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. DLOCommandu keytest -f -quar
-ListProfile Command
The -ListProfile command is used to list profiles of Desktop Agent users. Syntax: DLOCommandu listprofile [ A | P ] 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.
1109
Command Options:
ListProfile Command Options Option A P <profile name> Description Lists settings for all profiles (default). 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.
Command Options:
ListSL Command Options Option A F <file server> S <SL name> Description Lists all storage locations (default) Lists storage locations for the named server Lists only the named storage location
Examples: DLOCommandu listsl A DLOCommandu listsl F yourserver

DLOCommandu listsl S yourSL
-ListUser Command
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.
Command Options:
ListUser Command Options Option A F <file server> P <profile name> PI <profile id> S <SL name> SI <SL id> U <user> Description Lists settings for all users (default) Lists settings for users with storage locations on the named file server Lists settings for users by profile name Lists settings for users by profile id Lists settings for users by storage location name Lists settings for users by storage location id Lists settings for users by user name
Examples: DLOCommandu listuser A DLOCommandu listuser P yourprofile DLOCommandu listuser U mmouse DLOCommandu listuser U m*
1111
-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\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\DLO\Logs Syntax: LogFile <path\file> 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 <path> <file> 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
1112
-Update Command
The -Update command is used to list, add, remove, and publish Desktop Agent updates. See Updating DLO on page 976 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 1114 for a description of the available options for each command.
Update SubCommands SubCommand List [-A|UI <update id>] Add F <file name> Description Lists settings for previously used updates. 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. Removes a file or files from the update list. 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
Remove [-UI <update id>|A] Publish [-R] UI <update id> [P <profile name>|PI <profile id>|U <user>]
1113
Command Options:
Update Command and Sub-Command Options Option A F <file name> U <user name> P <profile name> PI <profile id> R UI <update id> Description Updates all Specifies a text file that contains update records Specifies a fully qualified user name, such as Enterprise\JFord Specifies a profile name Specifies a profile record id Designates to unpublish 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.
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 <updateID>
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
1114
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 <updateID> -P <profile name> DLOCommandu -update -publish -UI 63 -P yourprofile To publish an update for a specific user: DLOCommandu -update -list -UI <updateID> -U <username> To publish an update for all users: DLOCommandu -update -list -UI <updateID> -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
-EmergencyRestore Command
The -Emergency Restore command uses the DLO administrators 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 962 for more information. Syntax: DLOCommandu EmergencyRestore <usersharepath> -W <recovery password> -AP <destination path>
1115
Command Options:
EmergencyRestore Command Options Option <usersharepath> -W <recovery password> -AP <destination path> Description Specifies the full path to the user share directory Specifies the recovery password 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 962 for more information. Syntax: DLOCommandu SetRecoveryPwd <password>
-NotifyClients Command
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.
1116
To list inactive accounts: dlocommandu -inactiveaccounts -list -days <#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 <domain\user name> -M <computer name> -days <#days> dlocommandu inactiveaccounts -delete UI <userID> -MI <computer ID> -days <#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 <#days>
-RenameDomain Command
The -RenameDomain command is used after a Windows domain has been renamed. Running the RenameDomain command changes each Desktop Agent users 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 <OldDomainName> <NewDomainName>
-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.
1117
Before you can use the -RenameMS command, you must do the following steps in the order listed:
Use the Windows control panel to rename the media server. See the Microsoft Windows documentation. Use Backup Exec Utility to update the configuration for the new media server name. See the Backup Exec Utility online help.
After you rename the media server and use Backup Exec Utility to update the configuration, you can use the -RenameMS command. Syntax: DLOCommandu RenameMS <OldServerName> <NewServerName>
-LimitAdminTo Command
The -LimitAdminTo command limits administration of DLO to the specified group or user. Syntax: DLOCommandu LimitAdminTo -NAU <domain\NewAdminName> DLOCommandu LimitAdminTo -NAU <domain\NewAdminGroup>
1118
Command Options
-LimitAdminTo Command Option Option -NAU Description The -NAU option is used to add a new DLO administrator or to add a group that can be used of DLO administrators. The -DAU option is used to delete a DLO administrator or a DLO administration group. The -L option lists all of the current DLO administrators and groups.
-DAU
-L
-IOProfile Command
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 <master server name> -IOProfile -DBF <export file name> -E <profile name> 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 <export file name> 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:
1119
DLOCommandu C < server name> -IOProfile -DBF <export file name> -IPRGCS
To import the global settings in addition to the profile, use the IPRGS option as follows: DLOCommandu C < server name> -IOProfile -DBF <export file name> -IPRGS
1120
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 desktops 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 desktops 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.
1121
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.
Table I-17 Item Operating System Minimum System Requirements Description Microsoft Windows 2000 Microsoft Windows XP Service Pack 1 (SP1) or later Microsoft Windows XP Professional x64 Edition Microsoft Windows Vista 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 Memory Pentium system Required: 256 MB RAM Recommended: 512 MB (or more for better performance). Internet Browser Disk Space Internet Explorer 5.01 or later; however, version 5.5 is recommended. 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. Network interface card or a virtual network adapter card.
Other Hardware
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.
1122
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 \\<Backup Exec media server name>\DLOAgent. If you are unsure of the location, contact the administrator. Double-click the file setup.exe. On the Welcome screen, click Next. Read the license agreement, and then click I accept the terms in the license agreement. Click Next. Do one of the following: a To change the location on the desktops local drive where the Desktop Agent will be installed, click Change and enter the alternate location, then click OK. To install the Desktop Agent in the default location, continue with step 7. The default installation location is C:\Program Files\Symantec\Backup Exec\DLO. 7 8 9 Click Next. Click Install. Click Finish to install the Desktop Agent.
2 3 4 5 6
1123
Configuring the Desktop Agent

The following topics are useful for reference when configuring the Desktop Agent:

Connecting to the media server on page 1124 Using local accounts on desktop computers on page 1124 Using Alternate Credentials for the Desktop Agent on page 1125 Resetting Dialog Boxes and Account Information on page 1127 Changing Your Connection Status on page 1127 Disabling the Desktop Agent on page 1128 Enabling the Desktop Agent on page 1128
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 server using 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:
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 1126 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.
1125
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 1127. 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. Specify Desktop Agent logging options as outlined below:
Alternate Credentials Item Use this account Username Password Domain Save my password Description Select this option to enable the Desktop Agent to run when you are using the account under which you are currently logged on. Enter the user name for an account that is authorized for Desktop Agent operation. Enter the password for the account to be used for Desktop Agent operation. Type the domain for the account to be used for Desktop Agent operation. 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 enabled 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.
Click OK.
1126
Resetting Dialog Boxes and Account Information

While using DLO, you can suppress dialogs by checking the Dont 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 2 From the Tools menu, click Options. If you want to reset any information dialogs suppressed by the Dont show me this message again check box, click Reset dialogs. Click Yes when prompted to reset the dialogs. If you want to clear any passwords and account information that the Desktop Agent has stored, click Reset accounts. Click Yes when prompted to clear the accounts. Click OK.
3 4
5 6
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 2 Click the connection status on the lower right corner of the Desktop Agent. 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.
1127
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 2 From the Windows system tray, right-click the Desktop Agent icon. 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 2 From the Windows system tray, right-click the Desktop Agent icon. Click Enable. This option will be grayed out if you do not have permission to take this action.
1128
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. The Desktop Agent Console has the following components:
Table I-18 Item Menu bar Desktop Agent Console Features Description 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. 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. The Views menu appears in the Tasks bar and enables you to navigate to the following views: Provides job status, lists pending jobs, and summarizes recent backup activity. See Viewing the Desktop Agent Status on page 1155 for additional information. Enables you to define what data is protected by the Desktop Agent. See Using the Desktop Agent to Back Up Your Data on page 1130 for additional information. Enables you to configure the Desktop Agent to maintain a users 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 1151 for additional information. 1129
Tasks bar
Views menu Status
Backup Selections Synchronized Selections
Using the Desktop Agent to Back Up Your Data Table I-18 Item Restore Desktop Agent Console Features (continued) Description Enables the user to restore backed up data and search for backed up files. See Restoring Files Using the Desktop Agent on page 1159 for additional information. Displays Desktop Agent error, warning, and informational messages. Actions are initiated from the tasks menu. These actions vary with the selected view.
History Tasks menu Tools menu Options
Enables you to do the following:
Reset dialogs that have been suppressed by the Dont 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 1127 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 desktops 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 1139 and Restoring Microsoft Outlook Personal Folder Files on page 1162.
1130
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.
1131
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 1132 Adding Backup Selections in the Advanced View on page 1134 Backing up Outlook PST files Incrementally on page 1139 Restoring Microsoft Outlook Personal Folder Files on page 1162 Restoring Files with Alternate Stream Data on page 1163
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.
1132
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 1138 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. To modify backup selections in the Backup Selections Standard view: 1 2 3 Under Views in the Desktop Agent Tasks Bar, click Backup Selections. Click Standard view. Select the folders and files you want to back up. 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.
1133
Adding Backup Selections in the Advanced View

To add a backup selection in the Backup Selections advanced view: 1 2 3 4 Under Views in the Desktop Agent Tasks Bar, click Backup Selections. Click Advanced view. Click Add. From the General tab in the Backup Selection dialog box, select the appropriate options as follows:
Backup Selection General Dialog Box Item Name Description Description Type a descriptive name for the backup selection. 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 Once a backup selection is created, the folder cannot be modified. Select a pre-defined folder Include subfolders Select this option to choose a pre-defined folder from the list provided. Check this option to also back up all subfolders in the specified directory. This option is selected by default. On computers that run Microsoft Windows Vista, this option does not include the Music, Pictures, or Videos folders in the backup selection. On computers that run previous versions of Microsoft Windows, this option does include My Music, My Pictures, and My Videos folders in the backup selections.
1134
From the Include/Exclude tab, select the appropriate options as follows:

Backup Selection Include/Exclude Dialog Box
Item Include all file types
Description Select this option to include all file types in this backup selection.
Include and exclude only Select this option to include or exclude only specific files or file the items listed below types.
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. 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. Select the appropriate options as follows and then click OK.
Add Include Filter or Add Exclude Filter Dialog Box Options
Item Filter
Description 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.
Type a description of this include or exclude filter. 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.
1135
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 Number of Revisions
Description
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:

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:

Note The oldest revision is deleted when a new revision is created that exceeds one of these limits. Revision Age Discard all revisions in the desktop 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.
1136
Using the Desktop Agent to Back Up Your Data Backup Selection Revision Control Dialog Box (continued) Item Discard all revisions in the network user data folder older than Description 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 Delta File Transfer Description 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. 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. When source files are deleted, delete the backed up files from the: desktop user data folder Indicate the number of days after which DLO will delete all file after versions from the desktop user data folder after the source file has been deleted from the desktop. The default setting is 60 days. This option also determines the amount of time that DLO waits before it deletes existing backup sets that match new global excludes.
Compression
1137
Using the Desktop Agent to Back Up Your Data Backup Selection Options (continued) Item Description
network user data folder Indicate the number of days after which DLO will delete all file after versions from the network user data folder after the source file has been deleted from the desktop. The default setting is 60 days. This option also determines the amount of time that DLO waits before it deletes existing backup sets that match new global excludes.
11 Click OK to save your changes.
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 2 3 4 Under Views in the Desktop Agent Tasks Bar, click Backup Selections. Click Advanced view. Select the backup selection you want to change, and then click Modify. 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. 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 1134. Click OK.
1138
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 1137. To delete a backup selection: 1 2 3 Under Views in the Desktop Agent Tasks Bar, click Backup Selections. Click Advanced view. Select the backup selection you want to delete. You cannot delete profile backup selections. 4 5 Click Remove. Click Yes to verify that you want to delete this backup selection, or click No to cancel.
Backing up Outlook PST files Incrementally

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 1146

1139
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 2 3 4 Open Internet Explorer. On the Tools menu, click Internet Options. Select the Programs tab. 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. 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 1162
1140
Backing Up Lotus Notes NSF Files Incrementally

The following types of Lotus Notes NSF Files can be backed up incrementally:
Table I-19 File Name BOOKMARK.NSF NAMES.NSF NSF Files That Can Be Backed Up Incrementally Location Notes\Data directory Notes\Data directory Description Contains saved bookmarks and Welcome Page information. This file contains contacts, connections, locations and Personal Address Book information. 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.
A_<name>.NSF
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. Verify that emails to be backed up have been archived in Lotus Notes.
1141
Modifying Desktop Agent Settings
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 1130 for additional information on backup selections. Under Tools in the Desktop Agent Tasks Bar, click Options. Select the Options tab. Check Enable message level incremental backups of Lotus Notes email files. Click OK.
4 5 6 7
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: <time_date_stamp> Created new log files as C:\Documents and Settings\<user_name>\Local Settings\Application Data\Lotus\Notes\Data\log.nsf. <time_date_stamp> 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.

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
1142

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 1143 and Setting Customized Options on page 1146. 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 2 3 In the tasks bar, under Tools, click Settings. Click the Schedule tab. Select the appropriate options as follows, and then click OK:
Job Schedule Options Item Use Profile schedule Description 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.
1143
Modifying Desktop Agent Settings Job Schedule Options (continued) Item 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. 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. Description
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.
1144
Modifying Desktop Agent Settings Job Schedule Options (continued) Item 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. 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. Description
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.
1145
Modifying Desktop Agent Settings Job Schedule Options (continued) Item Run job as scheduled Description 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.
Setting Customized Options

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 2 3 4 On the tasks bar, under Tools, and then click Options. Click the Options tab. Select Use custom options from the drop-down menu. Select the appropriate options as follows, and then click OK:
Options Dialog Box Item Use Profile options Description 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.
1146
Modifying Desktop Agent Settings Options Dialog Box (continued) Item Use customized options Description 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: Select Limit disk space usage on my computer 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. Log file maintenance Keep log files for a minimum of (days) 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. After minimum number of days, delete oldest log files when combined size exceeds 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.
Logging options Log groom messages Log information messages for backup Log warning messages Select Log groom messages to create logs for grooming operations. Select Log information messages for backup to create logs for all backup operations. Select Log warning messages to create logs for all operations that generate warnings.
1147
Modifying Desktop Agent Settings Options Dialog Box (continued) Item Description
Enable message level Select Enable incremental backups of Outlook PST files to enable incremental backups of incremental backups of Microsoft Outlook Personal Folder (PST) Outlook PST files 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 1139. Enable message level Check Enable incremental backups of Lotus Notes email files to incremental backups of enable the configuration of DLO for incremental backup of certain Lotus Notes email files 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 1141 for additional information. Unchecking this box will prevent the incremental backup of Lotus Notes files.
Moving the Desktop User Data Folder

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 2 3 4 In the tasks bar, under Tools, click Settings. Click the Backup Folders tab. Click Move. In the Browse for folder dialog box, choose a new location for the desktop user data folder. Click OK. When prompted to continue, click Yes. Click OK.
5 6 7
1148
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. Select the appropriate options as follows, and then click OK
Add/Edit Connection Policy Item Connection Type Dialup Select Dialup from the drop-down menu to limit or disable backups when using a dialup connection. Description
1149
Modifying Desktop Agent Settings Add/Edit Connection Policy Item IP address range Description 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 1151 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. 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.
Disable network backup for files greater than Limit network bandwidth usage to
Enforce policy according Check the Enforce policy according to scheduled window to cause to scheduled window 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.
1150
Synchronizing Desktop User Data
If you selected Active Directory in step 2 above, configure the Active Directory settings as follows and click OK:
Active Directory Object Dialog
Item Object
Description Select the Active Directory Object you want to use to configure the connection policy. You can select either Computer or User. Type or browse to the LDAP directory. Select this option to apply the connection policy to all objects in this directory.
In LDAP Directory All objects in this directory
Only the objects in this directory Select this option to apply the connection policy only to that match the criteria below those objects in the directory that match the specified criteria. Attributes Condition Value Select an attribute from the drop-down menu or type in a custom attribute. Select the appropriate condition. Available options include =, <, <>, and >. Type a value to complete the criteria that will be used to determine matches. Wildcards can be used to specify the value.
4 5
Click OK to close the Add/Edit Connection Policy dialog. Click OK to close the Settings dialog.

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, 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.
1151
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. Note If you customize NTFS permissions or folder attributes for compression or encryption, you must reapply these settings after restoration or synchronization.
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 1032 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 users computers must be synchronized. In addition, the computers that run the Desktop Agent must use the same version of the Windows operating system. For example, you can synchronize data between two computers that both run Microsoft Windows Vista. You cannot synchronize data between a computer that runs Windows Vista and a computer that runs Windows XP. To synchronize a folder across multiple desktops: 1 2 Under Views in the Desktop Agent Tasks Bar, click Synchronized Selections. Click Standard view. 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 4 Select the folders that you want to synchronize. When the Choose Local Folder dialog box appears, type or browse to the location where the synchronized files are to be stored. Click OK. Click Save changes to save the selections or Undo changes to return to the last saved settings.
5 6
1153
To view or change a synchronized folder: 1 2 3 4 Under Views in the Desktop Agent Tasks Bar, click Synchronized Selections. Select the Advanced view radio button. Click the folder to be viewed or modified. 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 1135. 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 2 3 4 5 Under Views in the Desktop Agent Tasks Bar, click Synchronized Selections. Click the Advanced View radio button. Click the synchronization selection to be deleted. Click Remove. 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 3 4 5 6 Click the Conflicts have been found link to open the Resolve Conflicts wizard. Review the information on synchronization conflicts and click Next. Select the file you wish to resolve. Click the Open Folder button. 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.
Viewing the Desktop Agent Status

The Desktop Agent Status view provides a summary of Desktop Agent operations, including:
Table I-20 Item Status Details Desktop Agent Operations Description Displays the current state of Desktop Agent jobs, displays when backups will run, and summarizes the results of the last backup. 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 Local Usage Displays the total amount of data stored in the network user data folder for this computer. Displays the total amount of data stored in the desktop user data folder on this computer.
1155
Synchronizing Desktop User Data Table I-20 Item Details Desktop Agent Operations (continued) Description 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 1157.
Starting a Pending Job in the Status View

To run a pending job from the Status view: 1 2 Under Views in the Desktop Agent Tasks Bar, click Status. 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. .
Options for Suspending Jobs Type of Job Running Continuous Manual Options
Suspend the job and resume after a specified number of minutes. Suspend the job and resume after a specified number of minutes. Cancel the job until it is started again manually. Suspend the job and resume after a specified number of minutes. Cancel the job until it is scheduled to run again.
Scheduled
1156
Viewing Usage Details

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 2 Under Views in the Desktop Agent Tasks Bar, click Status. Under Usage Summary in the Status pane, click Details to open the Usage Details dialog. Review the usage information and take the appropriate actions as described below:
Usage Details Item Usage Description
1157
Synchronizing Desktop User Data Usage Details (continued) Item Local Description 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 1142. 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.
1158
Restoring Files Using the Desktop Agent Usage Details (continued) Item Remove deleted files Description 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. 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. Additional information Click here to view last job log 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 1164.
Restoring Files Using the Desktop Agent

If the DLO administrator has set your profile to include Restore 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 users 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 1139 and Restoring Microsoft Outlook Personal Folder Files on page 1162. 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. DLO does not restore a file to its original location if the file is in use by another application.
1159
If DLO encounters a file that is in use, you can do one of the following tasks to restore the file:
Schedule a time to restore the file. The file is restored after the computer restarts. You are not notified when the file is restored. Log on to the desktop computer with an administrative account. Then, run a restore job to overwrite the locked file and restore it. Close the file in the other application. Restore the file to an alternate location.
To restore data: 1 2 Under Views in the Desktop Agent Tasks Bar, click Restore. In Show, select one of the following revision display options:
Restore File Version Display Options Item All revisions Latest revision Revisions modified on or after Description All file revisions will be displayed and available as restore selections. Only the latest file revision will be displayed and available as a restore selection. If selected, enter a date and time after which revisions will be displayed and available as restore selections, then click OK.
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 1132 for additional information.
Click Restore.
1160

Restore Dialog Box Options
Item
Description
Restore to the original Select this option to restore files and folders to their original folders on this computer location. Redirect the restore to an alternate folder on this computer Preserve folder structure Options If file already exists Select one of the following:

Select this option to restore files and folders to an alternate folder on the same computer. 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.
Do not overwrite Prompt Overwrite
Restore deleted files Preserve security attributes on restored files
Select this option if you want to restore files even though the source file has been deleted. 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.
Searching for Desktop Files to Restore

To search for desktop files and folders to restore: 1 2 Under Views in the Desktop Agent Tasks Bar, click Restore. Click Search for files to restore under Tasks in the Desktop Agent Tasks Bar to open the Search dialog box.
1161

Search Dialog Box Options
Item Search for file names with this text in the file name Modified
Description Type all or part of the file name or folder you want to find. Select this option to search for files that were modified during a specific time frame. Then specify the time frame. Select this option to search for files modified on the current calendar day. Select this option to search for files modified in the last calendar week. Select this option to search between calendar dates. Select this check box to select a file type from the list provided. Select this check box and then enter information as follows:
Today Within the past week Between Of the following type Of the following size
Select from equal to, at least or at most in the first drop-down menu Type a file size. Select KB, MB, or GB.
Restoring Microsoft Outlook Personal Folder Files

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. 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. If you use a password for your PST file, you must reset the password after restoring your PST file.
1162
Related Topics: Backing up Outlook PST files Incrementally on page 1139
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 1161 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
1163
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 Administrators Guide For information on configuring Backup Exec Retrieve, see Using Backup Exec Retrieve With DLO on page 975.

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.
Table I-21 Item Started Ended Status Files Transferred (Local) Size Transferred (Local) Files Transferred (Network) Job History View Information Description The date and time the operation started The date and time the operation ended The status of the job, such as Active, Completed, Cancelled or Failed. The total number of files transferred to the desktop user data folder during the listed job. The total number of bytes of data transferred to the desktop user data folder during the listed job. 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.
1164
Viewing Log Files

To view history logs: 1 2 Under Views in the Desktop Agent Tasks Bar, click History. To view backup logs, select the Backup tab, or to view restore logs, select the Restore tab. Select the appropriate History view filter from the Show drop-down menu as follows:
History View Filtering Options Item All logs All logs with errors Logs filtered by date Description All history logs are displayed History logs for all jobs that generated errors are displayed. 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 5 6 7
Click the job history entry for which you want to view the history log. Click View log to open the log file viewer. If required, click Save As to save the log file as a text file. 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 2 Under Views in the Desktop Agent Tasks Bar, click History. Click the Search link, which is located under the History pane, to open the Log File Viewer.
1165
Enter filtering parameters as described below:

Log File Viewer Filtering Options
Item Search for log entries in All log files Current log file With timestamp of
Description
Select this option to show all log entries in the log file viewer. Select this option to search only those log entries in the current log file. 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
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.
Filter Informational entries only Error and warning entries only Error entries only Select Informational entries only to display only informational entries. Select Error and warning entries only to display both error and warning entries. Select Error entries only to display only error entries.
1166
Troubleshooting Log File Viewer Filtering Options (continued) Item Warning entries only Description Select Warning entries only to display only entries for warnings.
4 5
Click Search. To view detailed information for a log file entry, expand the tree view for the entry by clicking on the + check box. If required, click Save As to save the log file as a text file. Click Close when finished.
6 7
Log file grooming

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 1146.
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.
1167
Troubleshooting
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. 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 isnt 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 users 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.
Troubleshooting
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 1044 Managing Desktop Agent Users on page 1041 About Automated User Assignments on page 1027 About DLO Profiles on page 988 Moving Desktop Agent Users to a new Network User Data Folder on page 1046 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 users 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 1027 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.
1169
Troubleshooting
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 987 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 964. 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 2 3 4 5 On the navigation bar, click Setup. In the Settings pane, click Users. Select the user you do not want to be able to perform backups. Under General Tasks in the Task pane, select Properties. Clear the Enable user check box. 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.
1170
Troubleshooting
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. I just tried to restore a file, but it doesnt 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:
1171
Troubleshooting
Excluding Files that are Always Open on page 1039 The History view in the DLO Administration Console doesnt 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.
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. The Desktop Agent installation program is located in a share where you installed DLO. This share will have a name in the following format: \\<Server>\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.
1172
Troubleshooting
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. 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.
1173
Accessibility and DLO
Accessibility and DLO

The following table lists keyboard navigation within tabbed dialog boxes:
Table I-22 Keyboard input CTRL+PAGE DOWN or CTRL+TAB CTRL+ PAGE UP Keyboard Navigation within Tabbed Dialog Boxes Result Switches to the next tab and displays the page.
Switches to the previous tab and displays the page.
RIGHT ARROW When the focus is on a tab selector, chooses the next or previous tab in the or LEFT current row and displays the page. ARROW
The following table lists keyboard shortcuts for the Administration Console:
Table I-23 Keyboard Shortcuts Unique to Backup Exec Desktop and Laptop Option Administration Console Mnemonic F E Result The File menu expands. From the File menu, you can create new profiles and Storage Locations, and add users. The Edit menu expands. From the Edit menu, you can restore files, search for files to restore, manage alerts, and delete items. The View menu expands. From the View menu, you can change the information that displays on the screen. The Network menu expands. Use the Network menu to work with administrator accounts, connect to the DLO Administration Servers on the network, or to reconnect to a local DLO Administration Server. The Tools menu expands. Use the Tools menu to set global excludes, access all DLO wizards, and manage service credentials. The Window menu expands. Use the Window menu to move to a new window or view.
Accelerator ALT ALT
ALT ALT
V N
ALT
ALT
1174
Accessibility and DLO Table I-23 Keyboard Shortcuts Unique to Backup Exec Desktop and Laptop Option Administration Console (continued) Mnemonic H Result The Help menu expands. Use the Help menu to access documentation and various Symantec web sites.
Accelerator ALT
The following table lists keyboard shortcuts for the Desktop Agent:
Table I-24 Accelerator ALT ALT ALT ALT ALT Keyboard Shortcuts Unique to Desktop and Laptop Option Desktop Agent Mnemonic F V K O H Result The File menu expands. From the File menu, you can
minimize or exit the Desktop Agent.

The View menu expands. From the View menu, you can change the information that displays on the screen. The Tasks menu expands. Use the Tasks menu to run a job
or refresh the view.
The Tools menu expands. Use the Tools menu to reset
dialog boxes and accounts.
The Help menu expands. Use the Help menu to access the online help for the Desktop Agent.
1175
Glossary of Terms for DLO

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 users 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 administrators interface with Backup Exec. Compression A method of reducing data to expedite transmission time or storage volume. DLO Administration Console The administrators 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.
1176
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 DLO settings configured by the administrator and that apply to users or groups of users. Revision 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.
1177
Task An accessible program function that varies with the view selected in the DLO administration console or Desktop Agent console. User 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.
1178
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

The Exchange Agent lets you integrate backups of Microsoft Exchange Server databases with network backups without separate administration or dedicated hardware. The Exchange Agent provides the following features:
Increased performance of backup and restore through Granular Recovery Technology (GRT) for the mail messages and folders that are backed up with the Information Store. GRT lets you restore individual mailboxes, mail messages, and public 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 Exchange backup job provides complete recovery to any point in time of the Information Store, including the latest complete transaction log. When you enable recovery points to run at intervals between the full backups, you can restore individual items at a point in time when the recovery point was created. Even without recovery points, you can restore individual items 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.
1179
Requirements for using the Exchange Agent
The ability to restore individual databases or storage groups from non-snapshot backups by using the Recovery Storage Group feature of Exchange Server 2003. For Exchange Server 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. Offhost backup with Granular Recovery Technology (GRT) for Exchange Server 2003/2007
Related Topics: Installing the Exchange Agent on page 1183 Backup strategies for Exchange on page 1186 Recommended configurations for Exchange on page 1183 About offhost backup on page 855 About the Advanced Open File Option on page 809

The media server must meet the following requirements:
Table J-1 Media server requirements for the Backup Exec Exchange Agent Description
Media server requirements To support the Exchange Agent
Symantec Backup Exec for Windows Servers Microsoft Exchange Server Agent (Exchange Agent) must be licensed and installed. The media server must have access to the Exchange Server. Symantec recommends that you use a Backup Exec services account that has domain and local administrator rights on the Exchange Server.
1180
Requirements for using the Exchange Agent Table J-1 Media server requirements for the Backup Exec Exchange Agent Description To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on the media server. The Tools on the media server must be the same version or later as the Tools that are on the Exchange Server 2007. You can install the management tools when you do a custom install of Microsoft Exchange Server 2007. A Backup Exec media server that runs on Windows 2000 cannot back up Exchange Server 2007. To support the Backup Exec Resource Microsoft Exchange System Manager utility must be Discovery feature, which allows installed. detection of new backup resources within a Windows domain To back up Exchange data from any node of a Veritas Cluster Server To support Granular Recovery Technology (GRT) for the restore of individual items from Information Store backups Microsoft Exchange System Manager utility must be installed on all nodes. One of the following versions of a Microsoft Windows operating system that supports minifilter drivers must be installed:
Media server requirements To back up Exchange Server 2007
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
To support Backup Exec Continuous Protection Server
See Requirements for installing components for CPS Exchange backup jobs on page 1198.
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server
1181
The following are requirements for the Exchange Server with the Backup Exec Exchange Agent:
Table J-2 Exchange Server requirements Description Download the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package and install it on Exchange Server 2007. This package provides support for the following:
Exchange Server requirements To support Exchange Server 2007
The restore of individual mailboxes, mail messages, and public folders from an Information Store backup. The collection of catalog information for a backup for which the Granular Recovery Technology option is enabled and the destination device is tape.
You can find this package on the Microsoft Web site. For operations on all Exchange resources To support the Granular Recovery Technology option for Exchange Server 2007 To support snapshot backups Use the appropriate Exchange Server management utility to grant the Exchange Administrator role to the user account at the Administrative Group level. Use the appropriate Exchange Server management utility to grant the role of the Exchange Organization Administrators to the user account at the Administrative Group level. Use Microsoft Exchange Server 2003/2007 that run 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 See Requirements for installing components for CPS Exchange backup jobs on page 1198.
Note Backup Exec does not support configurations of Exchange Server where any version of Outlook or another MAPI email client is also installed. If you back up an Exchange Server on which Outlook or another MAPI email client is installed, backup and restore failures may occur. See the Microsoft Knowledge Base for information about using Outlook and Exchange together. Related Topics: Using resource discovery to search for new resources on page 255 About selecting individual mailboxes for backup on page 1217
Installing the Exchange Agent
About continuous protection for Exchange data on page 1197
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. See Installing Backup Exec options to the local computer on page 75.
Recommended configurations for Exchange

Before starting backups for Exchange, read the following recommendations for configuring Exchange to make it easier to restore from backups:
Table J-3 Recommendations for configuring Exchange for better restore Description
Recommendation
Put transaction log files on a separate This is the single most important configuration affecting physical disk from the database. the performance of Exchange. This configuration also has recovery implications, since transaction logs provide an additional recovery resource. Make Write Cache unavailable on the SCSI controller. 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.
1183
Recommended configurations for Exchange Table J-3 Recommendations for configuring Exchange for better restore Description 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. Avoid making the Exchange Server a domain controller. Install Exchange into a domain that has at least two domain controllers. For disaster recovery purposes, it is much easier to restore Exchange if you dont 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.
Recommendation Make circular logging unavailable if possible.
Related Topics: Reviewing the circular logging setting for Exchange on page 1189 Exchange mailbox access requirements on page 1185
1184
Exchange mailbox access requirements
Exchange mailbox access requirements

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 do the following:
Back up individual mailboxes separately from the Information Store (also called the legacy mailbox backup method). Configure a backup job that has all of the following settings:

A device other than a backup-to-disk folder is the destination device. The Granular Recovery Technology option is enabled. A backup method other than a snapshot method.
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. 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
1185
Backup strategies for Exchange
Related Topics: About using GRT-enabled backups to restore individual items from the Information Store on page 1190 Creating a Backup Exec logon account on page 149

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. 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.
1186
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 follows:

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.
In addition to backing up Exchange storage groups, you should also back up the following on a regular basis:
Table J-4 Backup selections for Exchange configuration data Description
Recommended backup selections for configuration data 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 System State and/or Shadow Copy Components
Back up the registry by running a full backup. Select System State and run a full backup to back up the following:

The Internet Information Service (IIS) metabase The Windows registry
See Selecting data to back up on page 231. 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.
1187
Backup strategies for Exchange Table J-4 Backup selections for Exchange configuration data (continued) Description
Recommended backup selections for configuration data
Key Management Service Back up the Key Management Service database by selecting the KMS (KMS) database 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. Site Replication Services If Exchange 2000 or 2003 is running in an Exchange Server 5.5 (SRS) database 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. 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 Configure an Information Store backup for which the Granular Recovery Technology (GRT) option is enabled to restore individual mailboxes, mail messages, and public folders. Backing up individual Exchange mailboxes separately from the Information Store uses legacy backup methods, and is no longer required for individual mailbox recovery. Related Topics: About using GRT-enabled backups to restore individual items from the Information Store on page 1190 Backing up Exchange on page 1211 Preparing for disaster recovery of Exchange Server on page 1245
1188
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. 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 the following occurs:

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 1186
1189
About using GRT-enabled backups to restore individual items from the Information Store
About using GRT-enabled backups to restore individual items from the Information Store
Backup Exec Granular Recovery Technology (GRT) lets you restore individual mailboxes, mail messages, and public folders from an Information Store backup. You can also enable GRT when you create an offhost backup for the Information Store. Offhost backup lets Backup Exec move the backup process from the host computer to the Backup Exec media server. The host computer is the remote computer that contains the volumes that you selected for backup. To run a GRT-enabled offhost backup, you must install the Backup Exec Advanced Disk-based Option on the media server. See Configuring a GRT-enabled offhost backup for Exchange resources on page 865. Following are requirements for backup and restore operations when GRT is enabled for an Information Store backup:
Table J-5 Requirements for Information Store backups with the Granular Recovery Technology (GRT) option Requirements See Requirements for using backup-to-disk folders with GRT-enabled backup operations on page 407.
Task If the destination device for the backup job is a backup-to-disk folder
If the destination device for the backup job is to Backup Exec must have access to a uniquely a device other than a backup-to-disk folder named mailbox within the Exchange organization for backup and restore of the Information Store. See Exchange mailbox access requirements on page 1185. If the destination device is tape, and if you must restore from the tape, note the following:
Backup Exec must temporarily stage the entire database to a path on an NTFS volume on the media server to extract individual items. You can specify a path, or use the default path of \temp. See Advanced options for restore jobs on page 505. See About restoring individual items from Information Store backups on page 1229.
You cannot restore individual mailboxes and messages from any incremental Exchange backup sets that are on tape.
1190
Snapshot and offhost backups with the Exchange Agent Table J-5 Requirements for Information Store backups with the Granular Recovery Technology (GRT) option Requirements You must configure the backups with the following:
Task If you create full backups and incremental backups
The full and the incremental job templates must be in a policy, A backup-to-disk folder must be the destination device. In the job templates for the full backup and the incremental backup, specify backup-to-disk folders that are on the same volume for both backups. To restore individual items from the incremental backup, the backup sets from the full and the incremental jobs must be on the same volume.
Note 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 424.
Note In previous versions of Backup Exec, individual Exchange mailboxes were backed up separately from the Information Store so that individual mailboxes could be restored. These legacy backup options are enabled by default only if you upgrade from a previous Backup Exec version and jobs for mailbox backups already exist. See About selecting individual mailboxes for backup on page 1217. Related Topics: Snapshot and offhost backups with the Exchange Agent on page 1191 Configuring a GRT-enabled offhost backup for Exchange resources on page 865 Installing the Advanced Disk-based Backup Option on page 832
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.
Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server 1191
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. If the Advanced Disk-based Backup Option (ADBO) is installed on the media server, you can use the Backup Exec Granular Recovery Technology (GRT) option when you create an offhost backup for the Information Store. See Configuring a GRT-enabled offhost backup for Exchange resources on page 865. The Exchange Agent snapshot does not support the following:

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 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.
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:
Table J-6 Available Backup Exec options when using a snapshot method with the Exchange Agent Available feature The following options are available:

Backup Exec option Backup Exec Advanced Open File Option (AOFO)
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. Backup Exec Advanced Disk-based Option (ADBO) Process logical volumes for offhost backup one at a time
1192
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:
Table J-7 Available backup methods for Exchange snapshot versions Available backup methods The following backup methods are available:

Exchange version Exchange Server 2003
Full Copy
Exchange Server 2003 with Service Pack 1 or later Exchange Server 2007
The following backup methods are available:

Full Copy Differential Incremental storage group level snapshot backup Individual database restore
Exchange Server 2007
LCR/CCR - Back up from the passive copy or the active copy. Note You cannot back up the passive copy of the Standby Continuous Replication (SCR) database with Exchange Server 2007. The SCR is not available for backup selection.
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 or later on Windows Server 2003 or later. 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:
1193
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 circular logging is enabled, and incremental or differential backup methods are selected.
1194
Configuring a snapshot backup for Exchange resources

Symantec recommends that you perform consistency checks before running a snapshot backup. See Perform consistency check before backup when using Microsoft Volume Shadow Copy Service (VSS) snapshot provider on page 1215. To configure a snapshot backup for Exchange resources 1 Create an Exchange backup job. See Backing up Exchange on page 1211. 2 Set default options for the Advanced Open File Option. For Exchange Server 2007 resources, Backup Exec automatically performs snapshot backups. You do not need to select options for the Advanced Open File Option. See Setting defaults for the Advanced Open File Option for backup jobs on page 816. 3 Ensure that either the Microsoft Volume Shadow Copy Service option or the Automatically select open file technology option is selected. 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. Schedule or start the backup job.
Related Topics: Creating a backup job by setting job properties on page 267 Snapshot and offhost backups with the Exchange Agent on page 1191 Troubleshooting Exchange Agent snapshot and offhost jobs on page 1193 About restoring Exchange data from snapshot backups on page 1227
1195
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 1215. If the Advanced Disk-based Backup Option (ADBO) is installed on the media server, you can use the Backup Exec Granular Recovery Technology (GRT) option when you create an offhost backup for the Information Store. You can restore individual mailboxes, mail messages, and public folders from Information Store backups for which GRT is enabled. See Configuring a GRT-enabled offhost backup for Exchange resources on page 865. To configure an offhost backup with the Exchange Agent 1. Follow the instructions in Backing up Exchange on page 1211. 2. Follow the instructions in Setting offhost backup options for a backup job on page 861. 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: Snapshot and offhost backups with the Exchange Agent on page 1191 Troubleshooting Exchange Agent snapshot and offhost jobs on page 1193
1196
About 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. When you enable continuous protection, Backup Exec protects the Information Store with a recurring full backup, which is called a CPS Exchange job. The CPS Exchange job is sent to a backup-to-disk folder on a local NTFS volume. You can also enable recovery points that run in 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 recovery to any point in time of the Information Store, including the latest complete transaction log. The recovery points let you 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 continuous protection feature does not support the following:
The Microsoft Volume Shadow Copy Service (VSS) snapshot provider. Snapshot options that you select on the Advanced Open File Option backup job properties are ignored for CPS Exchange backup jobs. CPS Exchange backup jobs for Exchange Server 2007 are always run as snapshot backups. Note CPS Exchange backup jobs for Exchange 2000/2003 are always run as traditional streaming backups.
For Exchange Server 2000/2003 resources, the delegation of continuous protection-related jobs to managed media servers in a Central Admin Server Option (CASO) environment. Job delegation is supported for Exchange Server 2007 resources. Circular logging, if recovery points are used. Recovery points fail if circular logging is enabled. Exchange Server 5.5. Clusters.
Related Topics: Media server requirements for the Backup Exec Exchange Agent on page 1180 Exchange Server requirements on page 1182
1197
Requirements for installing components for CPS Exchange backup jobs

To use Backup Exec Continuous Protection Server (CPS) for continuous protection of Exchange data, you must install CPS components. For information on how to install the Continuous Protection Server components, see the Symantec Backup Exec Continuous Protection Server Administrators Guide. The following table lists requirements for installing the necessary components to create CPS Exchange backup jobs:
Table J-8 Component Requirements for installing components for CPS Exchange backup jobs Requirements
If you install the Do the following when you install CPS: Continuous Management Ensure that the path for the journal files is on a different drive Service (CMS) on the than the CPS Exchange backup-to-disk folder. same server that hosts When you select the path for the journal files, review the current the Backup Exec media disk space availability on the server. Select a drive with enough server space for the journal files. For information about required space for journal files, see the Symantec Backup Exec Continuous Protection Server Administrators Guide. Note When you install CPS, you must restart the server.
On the Push Install CPS Components Wizard panel, ensure that the Exchange Protection Agent is selected. If the Exchange Protection Agent is not available on the Push Install CPS Components Wizard panel, then check for DNS errors.
Do the following after you install CPS:
Use Symantec LiveUpdate to update the server. For information on how to use LiveUpdate with CPS, see the Symantec Backup Exec Continuous Protection Server Administrators Guide.
View the services to ensure that the CPS Exchange Agent is installed. If the Backup Exec Continuous Protection Broker Service is present, the CPS Exchange Agent is installed. Push-install the CPS Continuous Protection Agent to the Exchange Server.
1198
About continuous protection for Exchange data Table J-8 Component Exchange Server Requirements for installing components for CPS Exchange backup jobs Requirements The following are required for the Exchange Server:
It must be on a different server than the media server and the server on which CMS is installed. It must be in the same domain as the media server unless the domains are trusted. It must have the Backup Exec Remote Agent for Windows Systems installed. You can install the Remote Agent from either the media server or from the server on which CMS is installed.
If you install the Do the following: Continuous Management You must push-install the CPS Continuous Protection Agent to the Service (CMS) on a server Backup Exec media server and to the Exchange Server. that does not host the Optionally, to view the CPS console from the media server, you can Backup Exec media push-install the CPS Administration Console to the Backup Exec server media server. Backup Exec media server 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 Server 2008 Minimum of 1 GB RAM A processor with a minimum of 2 GHz
The media server must have the following:

Backup Exec service account
The Continuous Protection Agent and the Exchange Protection Agent must use the Backup Exec service account. Ensure that the Backup Exec service account has the following:

Domain and local administrator rights. Ability to query the location of the transaction logs on the local active Exchange server.
Related Topics: Best practices for continuous protection of Exchange on page 1202 About managing the CPS Exchange backup job for Exchange data on page 1203
1199
Requirements for configuring continuous protection for Exchange data

To configure continuous protection jobs for the Exchange Information Store, the following are required:
Table J-9 Requirement Requirements for configuring continuous protection for Exchange Description
Install the Backup Exec See Requirements for installing components for CPS Exchange Continuous Protection Server backup jobs on page 1198. (CPS) components. Specify a recurring schedule for the full backup of the Information Store as part of the CPS job. Recovery points are dependent on the last full backup. If the full backup is not run often enough, or if it is not available, then the subsequent recovery points are not usable. If there is not enough disk space to maintain the full backup and subsequent recovery points, then consider one or both of the following actions:

Schedule the full backup more often. Schedule the recovery points less often.
You must balance the frequency of the full backup and the frequency of the recovery points to achieve efficient use of the available disk space. See Scheduling jobs on page 286. See Results of changing the default interval for recovery points on page 1206. Ensure that the full backup job for the Information Store is not in a policy. See Creating a backup job by setting job properties on page 267.
Ensure that the Exchange If the Exchange mailbox store is backed up by a CPS Exchange backup job, do not include it in other backup selection lists. mailbox stores are not included in any other backup job.
1200
About continuous protection for Exchange data Table J-9 Requirement Requirements for configuring continuous protection for Exchange Description
Select a backup-to-disk folder Configure the backup-to-disk folder as follows: as the destination device for It must reside on a local NTFS volume. the CPS Exchange backup job. 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 396.
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 fails. See About backup-to-disk folders and files on page 387. Use the backup-to-disk folder exclusively for the CPS Exchange backup job. Do not back up other resources to the backup-to-disk folder that is the destination device for the CPS Exchange backup job. See Review disk space availability for CPS Exchange backup jobs on page 1204. Make circular logging unavailable. If circular logging is enabled, the recurring full backup of the Information Store completes without errors, but recovery points fail. See Reviewing the circular logging setting for Exchange on page 1189. Select the Exchange Server name in the backup selections list. You cannot select an IP address for an Exchange server in the backup selections list on the media server.
Related Topics: Review disk space availability for CPS Exchange backup jobs on page 1204 Best practices for continuous protection of Exchange on page 1202
1201
Best practices for continuous protection of Exchange

When you use continuous protection as part of your backup strategy, note the following best practices:
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 off-site storage, 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 necessary, you can create a copy job to run before the full backup. This copies all of the transaction logs, as well as the full backup sets, to tape.
If you duplicate Information Store backup sets to tape, and then back to disk, specify the same volume for the full and the incremental backups. The backup sets must be on the same volume to restore individual items from the incremental backup. You can create a custom filter to limit the display of recovery points in the Job History view. After you create and run a CPS Exchange backup job, do not change the backup-to-disk folder that it was run to. If you must change backup-to-disk folders, then create a new CPS Exchange backup job with a new backup-to-disk folder as the destination device. Delete the previous job.
Related Topics: Creating selection lists on page 244 Adding a duplicate backup template to a policy on page 444 About managing custom filters on page 475 Backing up Exchange on page 1211 Review disk space availability for CPS Exchange backup jobs on page 1204 Troubleshooting CPS Exchange backup jobs on page 1207
1202
About managing the CPS Exchange backup job for Exchange data
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. 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 statuses for the different operations are listed in the following table:
Table J-10 Continuous protection job statuses Status on the Job Monitor in the Current Jobs view 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
Continuous protection operation 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, the recovery point appears in the Job History view. The recovery point appears as the name of the full job, with the description Exchange Recovery Point appended to it. If you enable error-handling rules, they apply to recovery points that fail. If you place a CPS Exchange backup job on hold, the transaction log replication is stopped in CPS until you take the job off hold. Related Topics: Review disk space availability for CPS Exchange backup jobs on page 1204 Temporarily stopping CPS Exchange backup jobs on page 1204 Viewing the CPS console from Backup Exec on page 1205 Troubleshooting CPS Exchange backup jobs on page 1207
1203
Review disk space availability for CPS Exchange backup jobs

Hard links are a feature of the Microsoft operating systems, and are used when CPS Exchange backup jobs are processed. When you review disk space availability for CPS Exchange backup jobs, hard links affect the amount of reported available disk space. The scheduled CPS Exchange full backup creates a media with a name such as IMG000060. The recovery points create VDB subfolders under the IMG media with names such as vdb_2007_03_08_1735_08. The Exchange transaction log files are put into the IMG media during backup. The logs in the VDB subfolders are hard links to the Exchange transaction log files. As VDB subfolders are created, they contain all of the hard links from the previous recovery points until the next full backup runs. For example: VDB1 contains hard links to log files 1-5. VDB2 contains hard links to log files 1-10. VDB3 contains hard links to log files 1-15. In this example, log files 1-5 are reported as having three times more space than they actually use. A result of using hard links is that disk space usage appears to be greater than it is. For example, if 300 MB of disk space on a drive is used, it may appear that 500 MB of disk space is used. Be aware of this limitation when you review disk space availability for CPS Exchange backup jobs. Related Topics: About using a backup-to-disk folder for GRT-enabled backup operations on page 406 Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407
Temporarily stopping CPS Exchange backup jobs

Stop the CPS Exchange backup jobs temporarily to perform any maintenance tasks that can affect the media server or the Exchange Server. To temporarily stop CPS Exchange backup jobs 1 On the media server, put all of the scheduled occurrences of the active CPS Exchange backup job on hold. See Placing all scheduled occurrences of an active job on hold on page 455.
1204
Stop the CPS service on the media server and on the Exchange Server, and then change the startup type to Manual. Stop the Backup Exec service on the media server, and then change the startup type to Manual. Perform the necessary maintenance on the media server or on the Exchange Server. After maintenance is complete, start the Backup Exec service on the media server, and then change the startup type to Automatic. Start the CPS service on the media server, and then change the startup type to Automatic. Start the CPS service on the Exchange Server, and then change the startup type to Automatic. Remove the scheduled occurrences of the active CPS Exchange backup job from hold. See Placing all scheduled occurrences of an active job on hold on page 455.
4 5
Related Topics: Viewing the CPS console from Backup Exec on page 1205 About using recovery points to restore individual items to a point in time on page 1206 Best practices for continuous protection of Exchange on page 1202 Error-handling rules on page 486
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.
1205
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. 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:
Table J-11 Results of changing the default interval for recovery points Results
Making recovery points
If recovery points are set to occur The following may occur: more frequently than the default rate The Job Monitor view and the restore selections list of every 8 hours 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.
If recovery points are set to occur less Transaction logs are also deleted less frequently and frequently than the default rate of therefore use more disk space. every 8 hours
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 1202
Setting default backup and restore options for Exchange data
Backing up Exchange on page 1211 About continuous protection for Exchange data on page 1197
Troubleshooting CPS Exchange backup jobs

Use a log file named Trace_RBS_##########.txt on the Exchange Server to find out if transaction logs are replicated to the media server. The Backup Exec Continuous Protection Broker Service generates this log. Entries that show that the transaction log was successfully replicated from the Exchange Server to the media server appear similar to the following example: Example CRepServiceBroker::CheckLogReplica::CheckLocalLogRepl ica(target:MEDIA SERVER, EXCHANGE SERVER, First Storage Group, E00000F4.log, replicated:true) ... hr(0x0) MEDIA SERVER is the media server name, and EXCHANGE SERVER is the Exchange Server name. The text E00000F4.log, replicated:true means that the Exchange transaction log E00000F4.log was replicated.

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 2 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Microsoft Exchange.
1207

Information Store backup method 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. See Available backup methods for Exchange snapshot versions on page 1193. If circular logging is enabled, incremental, differential, and continuous protection backups cannot be performed.
Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual mailboxes, mail messages, and public folders from Information Store backups (Exchange 2000 and later only; incremental backups supported with policy-based jobs only)
Check this option to enable the restore of individual items from Information Store backups. See Requirements for Information Store backups with the Granular Recovery Technology (GRT) option on page 1190. The GRT option is automatically enabled when you check the option Continuously back up transaction logs with Backup Exec Continuous Protection Server. The combined options let you restore individual items from a CPS Exchange backup.
1208
Enable legacy mailbox Check Enable legacy mailbox support to select individual support (not supported for mailboxes for backup with the Information Store. Exchange Server 2007) See Backing up individual Exchange mailboxes on page 1219. This option is not Note that a separate job to back up mailboxes is not necessary. recommended; use GRT See About using GRT-enabled backups to restore individual instead. items from the Information Store on page 1190. 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. No loss restore (do not Select this to preserve the existing transaction logs on Exchange delete existing transaction Server 5.5. Transaction logs on the storage media are then logs) 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. Restore public folder Select this to restore only Exchange 5.5 Information Stores public database (PUB.EDB). Although this database cannot be backed up separately from the Information Stores private database (PRIV.EDB), it can be restored separately. Select this to restore only Exchange 5.5 Information Stores private database. Although this database cannot be backed up separately from the Information Stores 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.
Restore private mailboxes
1209
Temporary location for log Type a location where the associated log and patch files are to be and patch files 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 1223. 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. Automatically recreate user accounts and mailboxes 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. Note To restore any mailboxes that were backed up with the legacy backup method, the option Back up the information used to automatically recreate user accounts and mailboxes must have been selected for the backup job. See Backing up individual Exchange mailboxes on page 1219. When you check Automatically recreate user accounts and mailboxes, you are prompted for a password for accounts that are recreated. 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.
1210
Backing up Exchange
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. See About using GRT-enabled backups to restore individual items from the Information Store on page 1190. See About using recovery points to restore individual items to a point in time on page 1206.
Related Topics: Backup strategies for Exchange on page 1186 Snapshot and offhost backups with the Exchange Agent on page 1191 About restoring Exchange data on page 1223
Backing up Exchange
To back up Exchange data, you can select the following:

Multiple storage groups Individual storage groups 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.
1211
Backing up Exchange
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 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Source, click Selections. View the Exchange data that you want to back up by doing one or both of the following:
To display Exchange data Do the following in the order listed: on local or remote Click the domain name icon or icons that contain the Exchange computers: installations
Expand the actual Windows computer icon that contains the Exchange installation.
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. To display Exchange data Do the following in the order listed: from a server cluster: 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 Expand the Microsoft Information Store icon, and then select groups individual storage groups.
If prompted, select a logon account that you can use to connect to the Exchange Server. On the Properties pane, under Settings, click Microsoft Exchange.
7
1212
Backing up Exchange

Backup method
Select one of the following backup methods:
(Information Store backups)
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. The option to enable the restore of individual mail messages and folders is not available if you select the differential backup method. 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. See Available backup methods for Exchange snapshot versions on page 1193.
If circular logging is enabled, incremental, differential, continuous protection backups cannot be performed. Continuously back up transaction logs with Backup Exec Continuous Protection Server 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. Before you check this check box, do the following: See Requirements for configuring continuous protection for Exchange on page 1200. See Best practices for continuous protection of Exchange on page 1202. Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server 1213
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. See About using recovery points to restore individual items to a point in time on page 1206.
Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual mailboxes, mail messages, and public folders from Information Store backups (Exchange 2000 and later only; incremental backups supported with policy-based jobs only) Guide Me
Check this option to enable the restore of individual items from Information Store backups. See Requirements for Information Store backups with the Granular Recovery Technology (GRT) option on page 1190. The GRT option is automatically enabled when you check the option Continuously back up transaction logs with Backup Exec Continuous Protection Server. The combined options let you restore individual items from a CPS Exchange backup.
Click Guide Me to start a wizard that helps you choose backup job properties for backing up Exchange data.
1214
Backing up Exchange
Perform consistency check before backup when using Microsoft Volume Shadow Copy Service (VSS) snapshot provider
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. 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 1191.
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.
1215
Backing up Exchange
If Exchange 2007 backup source is LCR or CCR
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.
Note You cannot back up the passive copy of the Standby Continuous Replication (SCR) database with Exchange Server 2007. The SCR is not available for backup selection.
Related Topics: About using GRT-enabled backups to restore individual items from the Information Store on page 1190 Reviewing the circular logging setting for Exchange on page 1189 About backup-to-disk folders and files on page 387
1216
Backing up Exchange
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:
Table J-12 When using legacy backup methods for mailboxes Description
Recommendation
Use full and incremental Consider running full backups of mailboxes or public folders on a backups 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 items from Information Store backups on page 1229. See Restoring individual Exchange public folder messages from tape by duplicating backup sets to disk on page 1231. Continue to back up the Information Store 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. Consider using the Exchange System Manager utility to adjust the deletion settings in each Stores 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.
Recover deleted items rather than restoring them
1217
Backing up Exchange Table J-12 When using legacy backup methods for mailboxes Description 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 241. 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\* Enable single-instance backup for message attachments 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. Do not back up special system mailboxes created by Exchange Although these special system mailboxes can be backed up, it is not necessary or useful. The following are common examples of special system mailboxes:

Recommendation Exclude unwanted or unnecessary folders from the backup
System Attendant Any mailbox name starting with SMTP or System Mailbox
There may be others depending on the Exchange server configuration and environment. 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.
1218
Backing up Exchange Table J-12 When using legacy backup methods for mailboxes Description 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.
Recommendation Select public folders from only one Exchange server
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.
Backing up individual Exchange mailboxes

If you have only a few mailboxes, and if you can only back up to tape, you may prefer to use this legacy mailbox backup method. Note Exchange 2007 does not support individual mailbox backup. See About selecting individual mailboxes for backup on page 1217. To back up individual Exchange mailboxes 1 2 3 On the Tools menu, click Options. On the properties pane, under Job Defaults, click Microsoft Exchange. Check Enable legacy mailbox support (not recommended - use Information Store instead).
1219
Backing up Exchange
If you want to recreate user accounts and mailboxes during a restore, check Back up the information used to automatically recreate user accounts and mailboxes. This option is not checked by default.
5 6 7 8 9
Click OK. On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Source, click Selections. 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.
10 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. 11 If prompted, select a logon account that allows you to connect to the Exchange mailboxes or public folders. See Exchange mailbox access requirements on page 1185. 12 On the Properties pane, under Settings, click Microsoft Exchange. 13 Select a backup method for the Information Store.
1220
Backing up Exchange
14 Select the following options as appropriate:

Mailbox backup method The following backup methods are available:
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.
1221
Backing up Exchange
Enable single instance backup for message attachments (for mailbox and public folder backups only)
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. 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.
15 If necessary, select other backup options from the Properties pane that you want to apply to these selections. 16 Schedule or start the backup job. Related Topics: Exchange mailbox access requirements on page 1185 When using legacy backup methods for mailboxes on page 1217 Creating a backup job by setting job properties on page 267
1222
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:
Table J-13 Restoring Exchange data Do this See Requirements for restoring Exchange 2000, 2003, and 2007 on page 1224.
For information about Required configuration and tasks before restoring Exchange data
Using the recovery storage group to recover See About restoring Exchange 2003 and data from an older backup copy of the store Exchange 2007 data using the recovery storage without disturbing client access to current data group on page 1225. Restoring Exchange data from snapshot backups Restoring the Exchange database from continuous protection backup sets and restoring individual mail messages and folders See About restoring Exchange data from snapshot backups on page 1227. See Restoring Exchange data from continuous protection backups on page 1228.
Restoring individual mail messages and folders See About restoring individual items from from Information Store backups for which the Information Store backups on page 1229. option to restore individual items was enabled Restoring Exchange mailboxes and folders from See About restoring Exchange mailboxes and a backup that is separate from the Information public folders from mailbox backups on Store backup page 1230. Restoring individual Exchange public folder messages from tape Configuring a restore job for Exchange data See Restoring individual Exchange public folder messages from tape by duplicating backup sets to disk on page 1231. See Restoring Exchange data on page 1232.
Restoring Exchange data to a server other than See About redirecting Exchange restore data the one from which it was backed up on page 1238.
1223
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:

Table J-14 Task Required tasks before restoring Exchange data Description
Configure the target databases so that they can To configure the databases, do the following in be overwritten 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.
Requirements for restoring Exchange Server 5.5

Review the following before restoring an Exchange Server 5.5:
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.
1224
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, you should review the requirements for redirecting the restore of Exchange storage groups. See About redirecting Exchange storage group and database restores on page 1238. 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.
1225
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.
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 1232 About redirecting Exchange storage group and database restores on page 1238
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. On the navigation bar, click the arrow next to Restore. Click New Restore Job.
2 3
1226
4 5 6
On the Restore Job Properties pane, under Source, click Selections. Select an Exchange 2007 database to restore. On the Restore Job Properties pane, under Destination, click Microsoft Exchange
Redirection.
7 8 9
Click Redirect Exchange sets. In the Restore to server field, type the name of the destination Exchange 2007 server. 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 1232 About redirecting Exchange storage group and database restores on page 1238
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
1227

Path on Exchange Server for temporary storage of log and patch files Commit after restore completes
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 1225.
Related Topics: About selecting individual mailboxes for backup on page 1217 Restoring Exchange data on page 1232
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 you restore a storage group or mailbox store from a CPS Exchange backup, you must restart the CPS Exchange backup job. Otherwise, the continuous protection job and any associated recovery points do not restart. 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. 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 2 Select backup sets from the last full backup or recovery point. On the Microsoft Exchange Restore Job Properties dialog box, click Restore all transaction logs; do not delete existing transaction logs (no loss restore).
1228
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. On the Microsoft Exchange Restore Job Properties dialog box, click For continuous
protection jobs only, restore all transaction logs until point in time; skip transaction logs after this time.
Specify the point in time.
Related Topics: Restoring Exchange data on page 1232 About continuous protection for Exchange data on page 1197 About redirecting Exchange restore data on page 1238
About restoring individual items from Information Store backups

If you enabled the Backup Exec Granular Recovery Technology (GRT) option for the Information Store backups, you can restore individual mailboxes, mail messages, and public folders from that backup. The GRT option is automatically enabled when you select the option Continuously back up transaction logs with Backup Exec Continuous Protection Server. This lets you restore individual items from a CPS backup. Note Individual items cannot be restored from incremental Exchange backup sets that are on tape. 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. The default location is \temp. See Advanced options for restore jobs on page 505. Backup Exec must also have access to a uniquely named mailbox in the Exchange organization. See Exchange mailbox access requirements on page 1185. Related Topics: Restoring Exchange data on page 1232
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 the following legacy methods:
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 redirect the restore. See About redirecting restores of mailboxes or public folders that were backed up separately from the Information Store on page 1240.
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. See General settings options for restore job on page 503. 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) Microsoft Schedule + Free/Busy Connector (Exchange Server 5.5) Directory Service (Exchange Server 5.5)
1230
Related Topics: Requirements for restoring Exchange 2000, 2003, and 2007 on page 1224 Restoring Exchange data on page 1232 About redirecting restores of mailboxes or public folders that were backed up separately from the Information Store on page 1240 About using GRT-enabled backups to restore individual items from the Information Store on page 1190
Restoring individual Exchange public folder messages from tape by duplicating backup sets to disk
To restore individual public folder messages from tape, you must first duplicate the backup sets that contain the messages to a backup-to-disk folder. You can then restore the data from that folder. The backup that you want to restore from must be a full backup or a copy backup. If there is an incremental backup that is subsequent to the full backup, then you can restore individual items from the incremental backup. The backup sets for the full backup and the incremental backup must be on the same volume. You cannot restore individual public folder messages from tape if the original backup is an incremental backup. To restore individual Exchange public folder messages from tape by duplicating backup sets to disk 1 2 3 4 5 6 7 8 Insert the tape containing the required Exchange backup sets into a tape drive. On the menu bar, click File, and then click New > Duplicate Backup Sets Job. Click Duplicate existing backup sets. Click OK. Select the Exchange backup sets that you want to duplicate. On the Properties pane, under Destination, click Device and Media. In the Device list box, select a backup-to-disk folder. Click Run Now.
1231
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 1232
Restoring Exchange data

This procedure details how to select restore job properties for Exchange, and provides definitions for restore options specific to Exchange. 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. See Requirements for restoring Exchange 2000, 2003, and 2007 on page 1224. Note After you restore a storage group or mailbox store from a CPS Exchange backup, you must restart the CPS Exchange backup job. Otherwise, the continuous protection job and any associated recovery points do not restart. To restore Exchange data 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. 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. See About restoring Exchange data on page 1223. 5 On the Properties pane, under Settings, click Microsoft Exchange.
1232

Automatically recreate user accounts and mailboxes 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. Note To restore any mailboxes that were backed up with the legacy backup method, the option Back up the information used to automatically recreate user accounts and mailboxes must have been selected for the backup job. See Backing up individual Exchange mailboxes on page 1219. 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 1207. 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. 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. 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.
1233
Exchange 5.5
Use the following options with Exchange v5.5 servers:
No loss restore (do not Check No loss restore (do not delete existing transaction logs) to delete existing transaction preserve the existing transaction logs on the Exchange 5.5 logs) 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. This option is not applicable to snapshot backups. Restore public folder Check Restore public folder to restore only the Information Stores public database (PUB.EDB). Although this database cannot be backed up separately from the Information Stores private database (PRIV.EDB), it can be restored separately. Check Restore private mailboxes to restore only the Information Stores private database. Although this database cannot be backed up separately from the Information Stores 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.
Restore private mailboxes
1234
Exchange 2000 and later Restore all transaction logs; do not delete existing transaction logs (no loss restore)
Use the following options with Exchange 2000 and later. 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. This option is not applicable to snapshot backups.
For continuous protection Note This option only supports restoring data from continuous jobs only, restore all protection backups. If you select this option to restore transaction logs until other types of backup data, the option is ignored, and a point-in-time; skip loss restore job runs. transaction logs after this Select this option to restore transactions from a transaction log time up to and including a point in time in the transaction log. After the point in time, recovery from the transaction log is stopped. 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. Purge existing data and restore only the databases and transaction logs from the backup sets 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. When you restore an Exchange 2007 database and you enable this option, Backup Exec adds a .DELETE file name extension to all existing Exchange log files that it finds in the destination storage group. For example, Backup Exec renames e0001.log to e0001.log.delete. Backup Exec preserves the existing Exchange log files in the storage group until you manually delete them. Appendix J, Symantec Backup Exec Agent for Microsoft Exchange Server 1235
Path on Exchange Server for temporary storage of 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, 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. This option is not applicable to snapshot backups.
Dismount database before Check Dismount database before restore if you want Backup restore 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. Commit after restore completes 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). This option is not applicable for snapshot backups. Mount database after restore Guide Me 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. Click Guide Me to start a wizard that helps you choose restore job properties for Exchange Server data.
For GRT-enabled backups on tape, on the Restore Job Properties pane, under Settings, click Advanced.
1236
Enter a location in the field Path on media server for staging temporary restore data when restoring individual items from tape. The default is \temp. See Advanced options for restore jobs on page 505.
To enter the path,
10 Select other restore options from the Properties pane as appropriate, and then start the restore job. If you restore data from a CPS Exchange backup, you must restart the continuous protection job and any associated recovery points. 11 Do the following in the order listed after the job completes:

On the navigation bar, click Job Monitor. Right-click the scheduled CPS Exchange backup job. Click Run now.
12 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 505. 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. 13 Run a full backup of the restored databases. Related Topics: About restoring Exchange mailboxes and public folders from mailbox backups on page 1230 Requirements for restoring Exchange 2000, 2003, and 2007 on page 1224
1237
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:
Table J-15 Redirected restore requirements Do this See About redirecting Exchange storage group and database restores on page 1238. See About redirecting Exchange Server 5.5 database restores on page 1239.
For requirements on redirecting this restore 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 See About redirecting restores of mailboxes or separately from the Information Store public folders that were backed up separately from the Information Store on page 1240.
Before starting the redirected restore job, review Restoring data on page 493 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 1242
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.
1238
You cannot redirect the restore of the following:
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 1238 Redirecting Exchange restore data on page 1242
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:
Table J-16 Restriction The Site and Organization names of the original and destination servers must match. Restrictions for redirecting restores of Exchange Server 5.5 databases Description 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 cannot The No loss restore option must be unchecked so that any be selected. 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.
1239
About redirecting Exchange restore data Table J-16 Restriction The Directory Store cannot be restored through redirection. Restrictions for redirecting restores of Exchange Server 5.5 databases (continued) Description You cannot redirect a restore job in which you have selected to restore one or more Exchange Server 5.5 Directory databases.
Before starting the restore job, review information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs. Related Topics: Restoring data by setting job properties on page 498 About redirecting Exchange restore data on page 1238 Redirecting Exchange restore data on page 1242
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 for 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 that the
1240
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 1185.
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 mailboxs 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.
Table J-17
Redirecting the restore of Mailbox 1 to Mailbox 2
1241
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.
Table J-18 Redirecting Mailbox 1\Top of Information Store\Folder 2 to Mailbox 2
Related Topics: About redirecting Exchange restore data on page 1238 About restoring Exchange mailboxes and public folders from mailbox backups on page 1230 Redirecting Exchange restore data on page 1242
Redirecting Exchange restore data

Use the following steps to redirect Exchange data. To redirect the restore of Exchange data 1 Create a restore job. See Requirements for restoring Exchange 2000, 2003, and 2007 on page 1224. 2 After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Microsoft Exchange Redirection.
1242

Redirect Exchange sets Restore to server Server logon account Check Redirect Exchange sets to enable the Restore to server and Server logon account fields. Enter the name of the computer to which you are restoring, using the format \\server name. 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. See Exchange mailbox access requirements on page 1185. Redirect using Volume Check Redirect using Volume Shadow Copy Service (VSS) Shadow Copy Service (VSS) snapshot provider to enable one of the following options. snapshot provider Redirect to Storage Group and Database (Exchange 2007 only) Restore to Storage Group Click this option to enable the Restore to Database and Restore to Storage Group fields. 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) 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) 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.
Restore to Database
1243
Redirect to drive and path Click this option to enable the Restore to drive and Restore to (Exchange 2003 and 2007) path fields. Restore to drive Select a destination drive on which to restore the Exchange database. Click the ellipsis button to view local and network drives. Type a path to where you want to restore the Exchange database. Check Redirect mailboxes or public folders to enable the options to redirect mailbox backup sets and public folder backup sets. Click this option to enable the redirection of mailbox backup sets. Enter the name of the mailbox to which you are redirecting this restore. The mailbox must already exist on the target server. 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.
Restore to path Redirect mailboxes or public folders Redirect mailbox sets Restore to mailbox Mailbox logon account
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.
Start the redirected restore job or select other restore options from the Properties pane. 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 505. 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.
1244
Preparing for disaster recovery of Exchange Server
For more information concerning the DS/IS consistency adjuster, refer to your Exchange documentation. 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 1238 About redirecting Exchange storage group and database restores on page 1238 About redirecting restores of mailboxes or public folders that were backed up separately from the Information Store on page 1240
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 the following items:

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 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
To perform the actual recovery, you will need the following items:

1245
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. See Preparing for disaster recovery of Exchange Server on page 1245. 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, you can use Intelligent Disaster Recovery to recover the Exchange server. See About Microsoft Exchange recovery notes on page 1534. To perform disaster recovery for Exchange 2000 or later 1 Recover the Windows server first. See Returning to the last known good configuration on page 661. 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. Start Backup Exec. Catalog the media that contains the latest backup of the Exchange 2000 Server or later storage groups you want to recover.
3 4
1246
5 6 7 8
On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. 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.
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).
1247
Disaster recovery for Exchange Server 5.5
14 If you want the databases to be immediately available to users after the recovery, check Mount database after restore. 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.

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. See Preparing for disaster recovery of Exchange Server on page 1245. 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, you can use Intelligent Disaster Recovery to recover your Exchange server. See About Microsoft Exchange recovery notes on page 1534 . To perform disaster recovery for Exchange Server 5.5 1 Recover the Windows server first. See Returning to the last known good configuration on page 661. 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 restart), recover the Exchange server. 2 3 4 5
1248
On the Exchange Server, click Start > Settings > Control Panel. Double-click Administrative Tools, and then double-click Services. Right-click Microsoft Exchange Directory service, and then click Properties. Restart the computer.
Upon restart, a message is displayed stating that not all services could be started. 6 Double-click the Microsoft Exchange Directory service, and then change the Startup Type to Automatic. Click OK. Verify that the Exchange System Attendant service is started. Start Backup Exec.
7 8 9
10 Catalog the tapes that contain the latest full, incremental, and differential backups of the Exchange Stores you want to recover. 11 On the navigation bar, click the arrow next to Restore. 12 Click Restore. 13 On the Properties pane, under Source, click Selections. 14 On the restore selections list, select the latest full backups of the Directory and Information Stores for restore. 15 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. 16 On the Properties pane, under Settings, click Microsoft Exchange. 17 Check Restore public folder and Restore private mailboxes. 18 Uncheck No loss restore (do not delete existing transaction logs). 19 Start the restore job. 20 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: 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
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. 21 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. 22 Click Start >Settings>Control Panel. 23 Double-click Administrative Tools, and then double-click Services. 24 Start all of the Exchange services that have Automatic as a Startup Type. This should include the following:

Microsoft Exchange Directory Microsoft Exchange Information Store Microsoft Exchange Message Transfer Agent Microsoft Exchange System Attendant
25 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. For more information about the DS/IS consistency adjuster, refer to your Microsoft Exchange Server documentation. 26 After completing the restore, it is recommended that a full backup of the restored databases be performed.
1250
Appendix
Symantec Backup Exec Agent for Microsoft SharePoint

The Symantec Backup Exec Agent for Microsoft SharePoint (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 Microsoft SharePoint 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 SharePoint Server 2007 Windows SharePoint Services 2.0 and 3.0
Related Topics: Using the SharePoint Agent with SharePoint Portal Server 2001 on page 1253 Using the SharePoint Agent with SharePoint Portal Server 2003 and Windows SharePoint Services on page 1263 About using the SharePoint Agent with SharePoint Server 2007 and Windows SharePoint Services 3.0 on page 1278
1251
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. The following table lists the ways you can install the SharePoint Agent:
Table K-1 To do this Install the SharePoint Agent if Backup Exec is not already installed SharePoint Agent installation Do this See Installing Backup Exec on page 61.
1252
Using the SharePoint Agent with SharePoint Portal Server 2001 Table K-1 To do this Install the SharePoint Agent if Backup Exec is already installed To install the Remote Agent SharePoint Agent installation Do this See Installing Backup Exec options to the local computer on page 75.
See Installing Backup Exec options to remote computers on page 82.
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 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
SharePoint Agent does not back up the following data:
Appendix K, Symantec Backup Exec Agent for Microsoft SharePoint
1253
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 1252 Installing the SharePoint Agent on page 1252 Backing up SharePoint Portal Server 2001 on page 1254 About restoring SharePoint Portal Servers and SharePoint Portal workspaces on page 1255 Redirecting SharePoint Portal Server restore jobs on page 1258 Disaster recovery of a SharePoint Portal Server on page 1260
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 267
Backing up the SharePoint Portal Server database

You can back up the entire SharePoint Portal Server database. To back up the SharePoint Portal Server database 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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.
1254
Start the backup job or select other backup options from the Properties pane.
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. From the Backup Selections pane, under Local Selections, expand Microsoft SharePoint Portal Workspaces. If SharePoint Portal Server is installed remotely, expand Remote Selections. Select the folders and/or documents in the workspace that you want to back up. Start the backup job or select other backup options from the Properties pane.
4 5
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.
1255
Note SharePoint Portal Server must be installed on the target server before you can restore a SharePoint Portal Server. Related Topics: Restoring data by setting job properties on page 498
Restoring a SharePoint Portal Server

You can restore the data from a SharePoint Portal Server database. 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 2 3 4 5 6 Place the media containing the data you want to restore in the storage device. On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the SharePoint Portal Server database you want to restore. On the Properties pane, set the appropriate options. 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. To restore SharePoint Portal workspace data 1 2 3 4 5 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the SharePoint workspace data you want to restore. On the Properties pane, set the appropriate options. Start the restore job.
Related Topics: Backing up folders and documents from a SharePoint Portal workspace on page 1255 Redirecting SharePoint Portal Server restore jobs on page 1258
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 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to the backup sets that contain the workspace data from which you want to restore. Under the backup set, expand the SHADOW folder and then navigate to the folder that contains the documents you want to restore. Redirect the restored workspace data to a file path.
1257
See Redirecting restored workspace data to a file path on page 1260.
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 2 3 4 5 6 Place the media containing the data you want to restore in the storage device. On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the SharePoint Portal Server database you want to restore. On the Properties pane, under Destination, click Microsoft SharePoint Redirection. Under SharePoint Portal Server 2001, select the Redirect SharePoint Portal Server 2001 sets check box. In the Restore to server field, enter the name of the SharePoint server to which you are restoring. Use the following format: \\servername. Use the default logon account as indicated, or click Change to select a different one. On the Properties pane, select other job properties that might be appropriate for your environment.
8 9
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 1254 Restoring a SharePoint Portal Server on page 1256
1258
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 2 3 4 5 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the SharePoint Portal workspace data you want to restore. On the Properties pane, under Destination, click Microsoft SharePoint Redirection. Select the Redirect SharePoint document sets check box, and then select Redirect to workspace or document library (Web Storage System-based only). In the Restore to server field, type the name of the SharePoint server to which you are restoring. Use the following format: \\servername. 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. Use the default logon account as indicated, or click Change to select a different one. On the Properties pane, select other job properties that might be appropriate for your environment.
8 9
10 Start the restore job. Related Topics: Backing up folders and documents from a SharePoint Portal workspace on page 1255 Restoring a SharePoint Portal workspace on page 1256
1259
Redirecting restored workspace data to a file path

You can redirect restored workspace data to a file path. To redirect restored workspace data to a file path 1 2 3 4 5 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the SharePoint Portal Server data you want to restore. On the Properties pane, under Destination, click Microsoft SharePoint Redirection. Select the Redirect SharePoint document sets check box, and then select Redirect to path. 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 8 Use the default logon account as indicated, or click Change to select a different one. On the Properties pane, select other job properties that might be appropriate for your environment. Start the restore job.
Related Topics: Backing up folders and documents from a SharePoint Portal workspace on page 1255 Restoring a SharePoint Portal workspace on page 1256
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. You must recover the Windows 2000 server first. 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 the following:

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. Related Topics: Getting started with IDR on page 1503 About SharePoint Portal Server recovery notes on page 1534 Manual disaster recovery of Windows computers on page 664
1261
Uninstalling and reinstalling the SharePoint Portal Server software

Part of the disaster recovery process is to uninstall and reinstall the SharePoint Portal Server software. You must remove SharePoint Portal Server and then reinstall it before the SharePoint data can be restored 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. 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. 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.
1262
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 the following:

Configuration database Portal sites and their associated databases, which include the following:

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 the following:

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 the following locations in the Selection tree:
1263
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the selection tree, right-click Microsoft SharePoint Server Farms and then click Add Server Farm. In the Web server name field, type the name of a Web server that belongs to the farm you want to add. 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.
1264
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the selection tree, right-click Microsoft SharePoint Server Farms, and then click Manage Server Farms. Select the farm that contains the Web server you want to disable or enable, and then click Properties. To prevent Backup Exec from communicating with a Web server, clear the check box next to that Web servers name. If the Web server is now available to communicate with Backup Exec, select the check box next to the Web servers 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.
1265
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the selection tree, right-click Microsoft SharePoint Server Farms, and then click Manage Server Farms. Select the farm whose name you want to change, and then click Properties. 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.
4 5
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the selection tree, right-click Microsoft SharePoint Server Farms, and then click Manage Server Farms.
1266
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. Select the SharePoint resources you want to back up. See Selecting SharePoint resources for backup on page 1263. 4 5 On the Properties pane, under Settings, select Microsoft SharePoint. Select the appropriate options as follows:
Backup method: Select one of the following backup methods:
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. 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.
Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual documents from the database backup (available for full backups only)
Check this option to enable the restore of individual documents from database backups. This option is only available when performing full backups. The option is not available if Differential - Back up database changes only has been selected as the backup method. Note If you use a backup-to-disk folder as the destination device and you enable the GRT option, review the requirements for using backup-to-disk folders. See Requirements for using backup-to-disk folders with GRT-enabled backup operations on page 407.
1267
Release the lock on the SharePoint farm topology if it is set (SharePoint 2003 only)
Check this option to have Backup Exec release the lock on the SharePoint farm topology before you run the backup or restore operation. Because another application may have locked the topology, you should check with your SharePoint administrator before you select this option.
Perform consistency Check this option to run a full consistency check (including check before backup of indexes) of the Microsoft SQL databases used by Microsoft Microsoft SQL databases SharePoint before backing up the databases. used by Microsoft SharePoint Continue with backup if consistency check fails Check this option to continue with the backup operation even if the consistency check fails.
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:
Table K-2 Node name Server Farm node Hierarchical tree view Node description 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. 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.
Individual Server nodes
1268
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. 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 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. 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 Select the appropriate options as follows:
Bring restored databases Select this option to bring the databases online after a restore job. online Reconnect previous database links When restoring portal sites or Windows SharePoint Services sites, this option re-establishes the link between the restored databases and their corresponding sites.
1269
Release the lock on the SharePoint farm topology if it is set (SharePoint 2003 only) Preserve existing Internet Services (IIS) Web site and application pool (SharePoint 2007 only).
Check this option to have Backup Exec release the lock on the SharePoint farm topology before you run the backup or restore operation. Because another application may have locked the topology, you should check with your SharePoint administrator before you select this option. If the Web site and application pool for the SharePoint Web application that you restore already exists in IIS, this option preserves them during restore. If you do not check this option, the Web site and application pool are deleted from IIS during the restore. After they are deleted, they are recreated in the default location that SharePoint specifies. 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.
Restore over existing documents (applies to SQL based document libraries only
Set additional restore options on the Properties pane or start the restore job.
Related Topics: Redirecting a restore job for SharePoint on page 1273.
1270
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 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Select the SharePoint Document Library data you want to restore. 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 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to the SharePoint Document Library that contains the documents you want to restore. Under the backup set, expand the SHADOW folder and then select the documents you want to restore.
1271
Redirect the restore job for individual documents to a file path. See Redirecting the restore of individual documents to a file path on page 1275.
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: Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual documents from the database backup (available for full backups only.) Note If you use a backup-to-disk folder as the destination device and you enable the GRT option, review the recommendations for using backup-to-disk folders. See Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407. 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 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to the backup set for the appropriate content database, and then select the documents or images that you want to restore. On the Properties pane, under Settings, click Microsoft SharePoint. 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
4 5
1272
Uncheck Restore over existing documents (applies to SQL based To prevent the replacement of existing document libraries only). files with files of the same name from the restore job.
If you are restoring from tape, do the following steps in the order listed:

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.
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 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. 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 5 On the Properties pane, under Settings, select Microsoft SharePoint Redirection. Under SharePoint Portal Server 2003, select Redirect SharePoint Portal Server 2003 sets. 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.
1273
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. 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 Do one of the following:

Use the default logon account as indicated. Click Change to select a different logon account.
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 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the SharePoint Portal document library data you want to restore.
1274
4 5
On the Properties pane, under Destination, click Microsoft SharePoint Redirection. Select the Redirect SharePoint document sets check box, and then select Restore to
workspace or document library (Web Storage System-based only).
In the Restore to server field, type the name of the SharePoint server to which you are restoring. Use the following format: \\servername. 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. Use the default logon account as indicated, or click Change to select a different one. On the Properties pane, select other job properties that might be appropriate for your environment.
8 9
10 Start the restore job.
Redirecting the restore of individual documents to a file path

Follow these steps to redirect the restored individual documents to a file path. To redirect individual documents to a file path 1 2 3 4 5 6 Place the media containing the data you want to restore in the storage device. On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the SharePoint documents that you want to restore. On the Properties pane, under Destination, click Microsoft SharePoint Redirection. Select the Redirect SharePoint document sets check box, and then select Redirect to path. 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.
1275
8 9
Use the default logon account as indicated, or click Change to select a different one. On the Properties pane, select other job properties that might be appropriate for your environment.
10 Start the restore job.
Setting default options for SharePoint Portal Server 2003 and later
You can set default options to use for all backup and restore jobs for SharePoint Portal Server 2003 and later. To set default options for SharePoint Portal Server 2003 and later 1 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Microsoft SharePoint. Select the appropriate options as follows:
Backup method Select one of the following methods:
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. 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.
Select this option to enable the restore of individual documents from database backups. This option is only available when performing full backups. The option not available if Differential Back up database changes only has been selected as the backup method. Note If you use a backup-to-disk folder as the destination device and you enable the GRT option, review the requirements for using backup-to-disk folders. See Requirements for using backup-to-disk folders with GRT-enabled backup operations on page 407.
1276
Perform consistency Select this option to run a full consistency check (including check before backup of indexes) of the Microsoft SQL databases used by Microsoft Microsoft SQL databases SharePoint before backing up the database. used by Microsoft SharePoint Continue with backup if consistency check fails Select this option to continue with the backup operation even if the consistency check fails.
Bring restored databases Select this option to bring the databases online after a restore job. online Reconnect previous database links Preserve existing Internet Services (IIS) Web site and application pool (SharePoint 2007 only). When restoring portal sites or Windows SharePoint Services sites, this option re-establishes the link between the restored databases and their corresponding sites. If the Web site and application pool for the SharePoint Web application that you restore already exists in IIS, this option preserves them during restore. If you do not check this option, the Web site and application pool are deleted from IIS during the restore. After they are deleted, they are recreated in the default location that SharePoint specifies. 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.
1277
About using the SharePoint Agent with SharePoint Server 2007 and Windows SharePoint Services 3.0
The Symantec Backup Exec Agent for Microsoft SharePoint (SharePoint Agent) includes support for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0. Backup Exec provides a hierarchical tree view of SharePoint resources in the Backup Selections pane. In the Backup Selections pane, Microsoft SharePoint Server Farms shows a logical view of the topology of each server farm on your network.
1278
About using the SharePoint Agent with SharePoint Server 2007 and Windows SharePoint Services 3.0 Microsoft Office SharePoint Server 2007 example (Backup Selections pane - View by Resource tab) All Resources Favorite Resources Domains Microsoft SharePoint Server Farms Server Farm 1 (Product) ConfigurationV3-DB (SQLSERVER\SharePoint_Config) Global Settings (SQLSERVER) SharedServices1 Windows SharePoint Services Help Search Windows SharePoint Services Web Application WSS_Administration SharePoint Server 2007 Server farm
Mixed SharePoint versions example (Backup Selections pane - View by Resource tab) All Resources Favorite Resources Domains Microsoft SharePoint Server Farms Server Farm 1 (Production) Configuration DB (SQLSERVER\SPS01_Config_DB) http://engineering http://finance ConfigurationV3-DB (SQLSERVER\SharePoint_Config) Global Settings (SQLSERVER) SharedServices1 Windows SharePoint Services Help Search Windows SharePoint Services Web Application Production Content-DB (SQLSERVER\WSS_Content_<guid_num>) WSS_Administration SharePoint Server 2007 SharePoint Portal Server 2003 Server farm
1279
About adding a server farm to the backup selections list

Before you can back up a Microsoft Office SharePoint Server 2007 server farm, you must add the farm to the backup selections list. See Adding a server farm to the backup selections list on page 1264
Backing up a Microsoft Office SharePoint Server 2007 or a Windows SharePoint Services 3.0 farm
Use the following steps to back up a Microsoft Office SharePoint Server 2007 or a Windows SharePoint Services 3.0 farm. To back up a Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0 farm 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Microsoft SharePoint Server Farms. Expand a server farm that contains the Microsoft Office SharePoint Server 2007 components that you want to back up. Select the SharePoint resources you want to back up. In the Backup Job Properties pane, under Settings, click Microsoft SharePoint. Select the appropriate options as follows:

5 6 7
Full - Back up entire database. Differential - Back up database changes only, which backs up only the changes that are made to the database since the last full backup. You cannot use the differential backup method to back up Index databases or Document Libraries. The Full backup method is used to back up these resources.
1280
Select this option if you want to restore individual documents from database backups. This option is available only when you perform full backups. The option is not available if you select the Differential backup method. Note If you use a backup-to-disk folder as the destination device and you enable the GRT option, review the recommendations for using backup-to-disk folders. See Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407.
Perform consistency Select this option to run a full consistency check (including check before backup of indexes) of the MS SQL databases that Microsoft SharePoint uses Microsoft SQL databases before backing up the database. used by Microsoft SharePoint Continue with backup if consistency check fails Select this option to continue with the backup operation even if the consistency check fails.
8 9
In the Properties pane, select other backup options as needed. Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

Backing up individual Web applications in a Windows SharePoint Services Application node

Use the following steps to back up individual Microsoft Office SharePoint Server 2007 Web applications. To back up individual Web applications in a Windows SharePoint Services Application node 1 2 On the navigation bar, click the arrow next to Backup. Click New Backup Job.
1281
3 4
In the Backup Selections pane, expand Microsoft SharePoint Server Farms. Expand the server farm that contains the SharePoint Web application that you want to back up. Expand the Windows SharePoint Services Web Application that contains the Web applications that you want to back up. Select the Web applications that you want to back up. In the Backup Job Properties pane, under Settings, click Microsoft SharePoint. Select the appropriate options as follows:

6 7 8
Full - Back up entire database. Differential - Back up database changes only, which backs up only the changes that are made to the database since the last full backup. You cannot use the differential backup method to back up Index databases or Document Libraries. The Full backup method is used to back up these resources.
Select this option if you want to restore individual documents from database backups. This option is available only when you perform full backups. The option is not available if you select the Differential backup method. Note If you use a backup-to-disk folder as the destination device and you enable the GRT option, review the recommendations for using backup-to-disk folders. See Recommendations for using backup-to-disk folders with GRT-enabled backup operations on page 407.
Perform consistency Select this option to run a full consistency check (including check before backup of indexes) of the MS SQL databases that Microsoft SharePoint uses Microsoft SQL databases before backing up the database. used by Microsoft SharePoint Continue with backup if consistency check fails Select this option to continue with the backup operation even if the consistency check fails.
In the Backup Job Properties pane, select other backup options as needed.
1282
10 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

About selecting SharePoint resources for restore

Backup Exec provides the following hierarchical views of SharePoint resources in the Selections pane when using the Resource View:
Table K-3 Node name Server Farm Hierarchical view Node description This node represents a logical view of the topology for the SharePoint resources that have been backed up from the farm. The node name 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, the backup sets for that component are displayed and can be selected for restore. Each server from which SharePoint components were backed up contains a Microsoft SharePoint Resources node. This node displays 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, the backup sets for that component are displayed and can be selected for restore.
Individual Server
Restoring SharePoint resources

You can restore the following SharePoint resources:
Web applications and their associated databases. Symantec recommends that you restore all Web application databases together. Individual documents that are contained in Document or Picture libraries.
1283
Configuration databases. A configuration database contains all of the configuration information for the entire SharePoint Server farm. Use caution when restoring this database. Any changes that you make to the farm topology before you restore from the backup are lost. Configuration databases can only be restored to their original locations. Single sign-on databases. Single Sign-on databases can only be restored to their original locations.
To restore SharePoint resources 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Expand the server farm that contains the SharePoint components that you want to restore. Expand the SharePoint resources that you want to restore. Select the backup sets for the SharePoint resources that you want to restore. In the Restore Job Properties pane, under Settings, click Microsoft SharePoint. Select the appropriate options as follows:
Bring restored databases Select this option to bring the databases online after a restore job. online Reconnect previous database links Release the lock on the SharePoint farm topology if it is set (SharePoint 2003 only) Preserve existing Internet Services (IIS) Web site and application pool (SharePoint 2007 only). When restoring portal sites or Windows SharePoint Services sites, this option re-establishes the link between the restored databases and their corresponding sites. Check this option to have Backup Exec release the lock on the SharePoint farm topology before you run the backup or restore operation. Because another application may have locked the topology, you should check with your SharePoint administrator before you select this option. If the Web site and application pool for the SharePoint Web application that you restore already exists in IIS, this option preserves them during restore. If you do not check this option, the Web site and application pool are deleted from IIS during the restore. After they are deleted, they are recreated in the default location that SharePoint specifies.
4 5 6 7
1284
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.
8 9
In the Restore Job Properties pane, select other restore options as needed. Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

Restoring a Microsoft Office SharePoint Server 2007 Shared Services Provider

Use the following steps to restore a Microsoft Office SharePoint Server 2007 Shared Services Provider. To restore a Microsoft Office SharePoint Server 2007 Shared Services Provider 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Expand the server farm that contains the Shared Service Provider that you want to restore. Expand the node for the Shared Services Provider that you want to restore. Select the backup sets for all of the components of the Shared Service Provider that you want to restore. Symantec recommends that you restore all Shared Service Provider components together. 6 In the Properties pane, under Settings, click Microsoft SharePoint.
1285
4 5
7 8 9
Check Bring restored databases online. Check reconnect previous database links. In the Restore Job Properties pane, select other restore options as needed.

Restoring a Microsoft Office SharePoint Server 2007 Web application to its original location
Use the following steps to restore a Microsoft Office SharePoint Server 2007 Web application to its original location. Note When you restore a Microsoft Office SharePoint Server 2007 Web application, all documents that are contained in the Web applications content databases are overwritten. To restore a Microsoft Office SharePoint Server 2007 Web application to its original location 1 2 3 4 5 6 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Expand the server farm that contains the Web application that you want to restore. Expand Windows SharePoint Services Application. Expand the Web application that you want to restore. Expand the content database, and then select the backup set that contains the content database that you want to restore.
1286
If the Web application contains multiple content databases, expand the other content databases and select the corresponding backup sets for those databases as well. 7 8 9 In the Restore Job Properties pane, under Settings, click Microsoft SharePoint. Check Bring restored databases online. Check Reconnect previous database links.
10 In the Restore Job Properties pane, select other restore options as needed. 11 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

Restoring individual documents from full database backups to their original locations
Use the following steps to restore individual documents to their original locations. To restore individual documents from full database backups to their original locations 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the View by Resource tab, expand the server farm that contains the Web application where the individual documents you want to restore reside. Expand Windows SharePoint Services Application. Expand the Web application that contains the content database from which you want to restore documents. Expand the content database that contains the documents you want to restore.
1287
4 5
7 8 9
Expand the backup set that contains the documents you want to restore. Expand the content database. Expand the folder that contains the documents you want to restore.
10 In the Results pane, select the documents that you want to restore. 11 In the Restore Job Properties pane, under Settings, click Microsoft SharePoint. 12 If you want to replace existing documents, check Restore over existing documents (applies to SQL-based document libraries only). 13 In the Restore Job Properties pane, select other restore options as needed. 14 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

Redirecting the restore of a Microsoft Office SharePoint Server 2007 Web application
Before you can redirect the restore of a Microsoft Office SharePoint Server 2007 Web application, the SharePoint software must be installed on the destination server. To redirect the restore of a Microsoft Office SharePoint Server 2007 Web application 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Expand the server farm that contains the Web application that you want to restore. Expand Windows SharePoint Services Application.
1288
Expand the Web application that contains the content database that you want to restore. Expand the content database, and then select the backup set that contains the content database that you want to restore. If the Web application contains multiple content databases, expand the other content databases and select the corresponding backup sets for those databases as well. You must restore all content databases for the Web application together.
In the Restore Job Properties pane, under Destination, click Microsoft SharePoint
Redirection.
Under SharePoint Portal Server 2003, check Redirect SharePoint Portal Server 2003 sets. In Restore to site, enter the name of the Web application that you want to restore. You also can enter the Web applications URL. Use the following format: <Web application name> or http://production1 The target Web application must exist and it must be configured with the same number of content databases as the original Web application.
10 In Using Web Server on an existing farm, enter the name of the Microsoft IIS server that hosts the Web server. You also can enter the Web servers IP address. 11. In SharePoint logon account, do one of the following:

Use the default logon account. Click Change to select a different logon account.
12 In the Restore Job Properties pane, under Settings, click Microsoft SharePoint. 13 Check Bring restored databases online. 14 Check Reconnect previous database links. 15 In the Restore Job Properties pane, select other restore options as needed. 16 Do one of the following: To run the job now Click Run Now.
1289
To schedule the job Do the following in the order listed: to run later

Redirecting the restore of individual documents to a file path

Use the following steps to restore individual documents to a file path. To restore individual documents to a file path 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the View by Resource tab, expand the server farm that contains the Web application where the individual documents you want to restore reside. Expand Windows SharePoint Services Application. Expand the Web application that contains the content database from which you want to restore documents. Expand the content database that contains the documents you want to restore. Expand the backup set that contains the documents you want to restore. Expand the content database. Expand the folder that contains the documents you want to restore.
4 5
6 7 8 9
10 In the Results pane, select the documents that you want to restore. 11 In the Restore Job Properties pane, under Destination, click Microsoft SharePoint Redirection. 12 Under SharePoint Portal Server 2003, check Redirect SharePoint document sets. 13 In Restore to drive and Restore to path, enter the drive letter and path to which you want to direct the restore.
1290
You also can type a UNC path (\\servername\share). 14. Do one of the following:

Use the default logon account. Click Change to select a different logon account.
15 In the Restore Job Properties pane, select other restore options as needed. 16 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

1291
1292
Appendix
Symantec Backup Exec Agent for Lotus Domino Server

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. You can use the Lotus Domino Agent to back up and restore Lotus Domino on local media servers and on remote computers. The Lotus Domino Agent backs up Lotus Domino databases and transaction logs. 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 the following:
Full, incremental, and differential online backups of Lotus Domino databases and transaction logs using Lotus Domino APIs. Restores of Lotus Domino databases and archived transaction logs, and point-in-time restores. Recycling of archived 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.
See Installing the Lotus Domino Agent on the media server on page 1295.
1293
Lotus Domino Agent requirements
Lotus Domino Agent requirements

The Lotus Domino Agent supports the backup and restore of Lotus Domino versions 6.x and 7.x. You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 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 the following:

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 the following:

Windows operating system Backup Exec Remote Agent for Windows Systems 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 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.
Following are requirements for backing up Lotus Domino transaction logs:
If the Lotus Domino databases are running in a Microsoft Cluster Server cluster, you must have the following:
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.
1294
Installing the Lotus Domino Agent on the media server
The Backup Exec Lotus Domino Agent must be installed on all nodes in the Microsoft Cluster Server cluster.
See Viewing and selecting Lotus Domino databases on page 1296.
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. It can protect local or remote Lotus Domino databases. The following table lists the ways you can install the Lotus Domino Agent:
Table L-1 To do this Lotus Domino Agent installation Do this
Install the Lotus Domino See Installing Backup Exec options to the local computer on Agent on the local media page 75. server Install the Remote Agent See Installing Backup Exec options to remote computers on page 82. on a remote resource Move 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 96.
Note If you install Lotus Domino on the same server on which Backup Exec is already installed, you must restart Backup Exec services to display Lotus Domino Database selections. See Starting and stopping Backup Exec services on page 114. Related Topics: Configuring default Lotus Domino options on page 1298 Backing up Lotus Domino databases on page 1299 Restoring Lotus Domino databases on page 1303
Appendix L, Symantec Backup Exec Agent for Lotus Domino Server
1295
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. Note Use the virtual computer name or the virtual IP address of the Domino server to browse or submit jobs in a Microsoft Cluster Server environment. To view databases created while Backup Exec is running

On the View menu, click Refresh. Press F5.
To back up the newly-created database, select it from the volume level, unless the entire volume is already selected for backup. To view Lotus Domino databases on the local server 1 2 3 On the navigation bar, click the arrow next to Backup Click New Backup Job. 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 Databases view
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.
1296
To select Lotus Domino databases
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.
Lotus Domino Database Selection
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 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Source, click Selections. Click Remote Selections, and then click Microsoft Windows Network.
1297
Configuring default Lotus Domino options
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 1299 Restoring Lotus Domino databases on page 1303 Preparing for disaster recovery on a Lotus Domino server on page 1308
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 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Lotus Domino. Select Lotus Domino backup default options. See Selecting backup options for Lotus Domino databases on page 1301. 4 Select Lotus Domino restore default options. See Selecting restore options for Lotus Domino databases on page 1306. 5 Click OK to save the options or select other options from the Properties pane.
1298
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. Related Topics: About Lotus Domino transaction logs on page 1300 Selecting backup options for Lotus Domino databases on page 1301 Selecting restore options for Lotus Domino databases on page 1306
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.
1299
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. The following types of Lotus Domino databases are supported:
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 backup methods. The database can be restored only to the point of the latest database backup.
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.
Selecting backup options for Lotus Domino databases
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.

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 you run the backup. The archived transaction logs are included automatically. See Creating a backup job by using the Backup Wizard on page 264. 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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Settings, click Lotus Domino.
1301

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.
Mark archive logs for recycling
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.
1302
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 1304 Redirecting restore jobs for Lotus Domino databases on page 1307
1303
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 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.
1304
Restoring Lotus Domino databases Empty data directory for Differential Backup 0002.
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 1307 Disaster recovery of a Lotus Domino server on page 1309
1305
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 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 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Settings, click Lotus Domino. 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. Select this option to restore the original database IDs.
Retain original IDs
1306
Selecting restore options for Lotus Domino databases
Assign new database ID Assign new database ID and replica ID
Select this option to assign new IDs to the database. 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. 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. This option may require additional time since the archived transaction logs are also restored.
Point in time restore
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 by setting job properties on page 498 About Lotus Domino transaction logs on page 1300
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 2 Select the media that contains the data you want to restore. On the navigation bar, click the arrow next to Restore.
1307
Preparing for disaster recovery on a Lotus Domino server
3 4 5
Click New Restore Job. Select the Lotus Domino databases. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click File Redirection. Select Redirect file sets. 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. Enter the logon account for the server in Server logon account. Enter the path to which you are restoring in Restore to path.
6 7
8 9
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 by setting job properties on page 498 Creating a new Backup Exec System Logon Account on page 154

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.
1308
Related Topics: Disaster recovery of a Lotus Domino server on page 1309 Disaster recovery of a Lotus Domino server using archive logging on page 1310 Disaster recovery of a Lotus Domino server using circular logging on page 1312
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 in the following ways:
Table L-2 Method Manually System recovery methods For more information See Manual disaster recovery of Windows computers on page 664.
By using Backup See Getting started with IDR on page 1503. Execs Intelligent Disaster Recovery Options
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. Restore the notes.ini, cert.id, and server.id files from the last full backup of the Lotus Domino server program directory.
1309
3 4
Use the Lotus Domino Agent to restore the databases to the Domino data directory. Start the Lotus Domino Server.
Related Topics: Disaster recovery of a Lotus Domino server using circular logging on page 1312 Returning to the last known good configuration on page 661 Restoring data by setting job properties on page 498 Selecting restore options for Lotus Domino databases on page 1306
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. Restart the Remote Agent for Lotus Domino.
1310
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 3 4 In the Restore Job Properties dialog box, under Settings, click General. Check Restore over existing files. 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 Lotus Domino, restore the last transaction log backed up prior to the loss of the active transaction log. Verify the transaction log restore was successful. Shutdown and then restart the Backup Exec Agent for Lotus Domino. Delete all transaction logs except the transaction log restored in step 5, from the Domino transaction log directory. 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.
6 7 8
1311
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. Restart the Remote Agent for Lotus Domino.
Related Topics: Selecting restore options for Lotus Domino databases on page 1306 Restoring data by setting job properties on page 498
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. 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. 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:
1312
translog_path=logdir 5 Use the Lotus Domino Agent to restore the databases to the Domino data directory.
Related Topics: Restoring data by setting job properties on page 498 Selecting restore options for Lotus Domino databases on page 1306

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.
1313
1314
Appendix
Symantec Backup Exec Agent for Microsoft SQL Server

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 the following:
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
1315
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. Database Consistency Checks (DBCC) before and after each backup job. Restores of transaction logs to a specific point in time. 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.
In SQL 7.0 installations, the SQL Agent provides support for the following:

In SQL 2005 installations, the SQL Agent provides support for the following:

Related Topics: Installing the SQL Agent on page 1317
1316
Requirements for using the SQL Agent
Requirements for using the SQL Agent

The following are required for 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 and can protect local or remote SQL Server databases. See Installing Backup Exec options to the local computer on page 75.
About 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. 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.
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server
1317
About using Backup Exec logon accounts for SQL resources 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.
Applying SQL user account credentials
The Backup Exec logon account containing the SQL user account credentials is applied to the SQL instance.
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.
Backup strategies for SQL
Related Topics: About selection lists on page 243 Creating a new Backup Exec System Logon Account on page 154

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. 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.
1319
When you develop a SQL backup strategy, consider the following:

Table M-1 Recommendations for backing up SQL Description To make sure SQL is completely protected, back up the following on a regular basis:

SQL Server backup strategies Protect the entire SQL Server.
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.
When you upgrade, run new full database backups. Run consistency checks after backups.
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. 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 the following:
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 data is changed in the master database. Back up the master database whenever procedures are run that change information in the database, especially after the following:

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.
1320
Backup strategies for SQL Table M-1 Recommendations for backing up SQL (continued) Description Do not schedule more than one backup to occur simultaneously against a database or its transaction log, or a filegroup. 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 Execs 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. 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. 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 Execs 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. See To create copies of the SQL 7.0 master and model databases on page 1369.
SQL Server backup strategies Run one backup at a time. Back up both system and user databases and transaction logs regularly.
1321
Consistency checks for SQL Table M-1 Recommendations for backing up SQL (continued) Description 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.
SQL Server backup strategies For SQL 7.0 only: 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

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 Execs consistency check uses the following SQL consistency check utilities:

CHECKDB CHECKCATALOG 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 1326
1322
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. See About SQL 2005 database snapshots on page 1337. Before you use snapshot technology with the SQL Agent, review the following information:
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 1322. 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.
1323
While performing database consistency checks both before and after backups impacts the time required for the backup jobs
Related Topics: Setting backup options for SQL on page 1326
Using AOFO 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 Microsofts 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 809
Protecting SQL on Windows 2000

When you protect Windows 2000, the SQL Agent only supports the VERITAS Storage Foundation for Window FlashSnap 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.
1324
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 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 809 Setting defaults for the Advanced Open File Option for backup jobs on page 816 About SQL 2005 database snapshots on page 1337
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 231

Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server 1325
Setting backup options for SQL
About selection lists on page 243 Consistency checks for SQL on page 1322

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 267. To select backup job options for SQL 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Settings, click Microsoft SQL.
1326
Select the appropriate options:

Backup method The following options are available:
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 1331.
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 1336.
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 1336.
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 1337.
1327
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.
Database snapshots to keep
(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 1337.
Consistency check before Select one of the following consistency checks to run before a backup 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.
1328
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. The following options are available:
Consistency check after 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.
Enable advanced log backup options
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.
No recover - Place Select this option to put the database in a loading state when the database in loading state 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.
1329
Standby - Place database Select this option to put the database in standby mode when the in standby state log file backup completes. Users can connect to and query the database when it is in standby mode, but cannot update it. You can convert a standby database to a live database by restoring the latest transaction log. Ensure that you select the following recovery completion state Leave the database ready to use; additional transaction logs or differential backup cannot be restored. This option is only available if Enable advanced log backup options has been selected. This option is not supported for SQL 7.0. Use checksums on backup Select this option to have SQL 2005 add checksums to the SQL (SQL 2005 only) 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. Create on-disk copies of SQL backups to be placed on the SQL server where the database is located 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 Guide Me Enter a path in which to save on-disk copies of SQL backups. Click this to start a wizard that helps you select backup job properties for SQL.
Related Topics: Selecting data to back up on page 231 About selection lists on page 243 Consistency checks for SQL on page 1322
1330
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 1331 About backing up SQL filegroups on page 1333 Displaying filegroups on the backup selections pane on page 1334
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.
1331
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. 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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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 About using Backup Exec logon accounts for SQL resources on page 1317. 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.
1332
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. Select options for the backup job. See Setting backup options for SQL on page 1326. 7 Start the backup job or select other backup options from the Properties pane, and then start the backup job.
Related Topics: Creating a backup job by setting job properties on page 267 Backing up SQL transaction logs on page 1336 Setting backup options for SQL on page 1326
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.
1333
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 1334 Backing up SQL filegroups on page 1334
Displaying filegroups on the backup selections pane

Filegroups do not appear on the backup selections pane by default. To display filegroups on the backup selections pane 1 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Microsoft SQL. Select Display filegroups when creating new backup jobs.
Related Topics: Backing up SQL filegroups on page 1334 Setting backup options for SQL on page 1326
Backing up SQL filegroups

You can back up specific filegroups. To back up SQL filegroups 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Source, click Selections. Select the data you want to back up. For information on using logon accounts when making backup selections:
1334
See About using Backup Exec logon accounts for SQL resources on page 1317. 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.
Selections options
To select SQL backup job properties, on the Properties pane, under Settings, click Microsoft SQL. 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: Creating a backup job by setting job properties on page 267 Setting backup options for SQL on page 1326.
1335
Backing up SQL transaction logs

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
1336
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 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. 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 About using Backup Exec logon accounts for SQL resources on page 1317. 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. 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 1326 About restoring SQL databases and filegroups on page 1344 Restoring from SQL transaction logs up to a point in time on page 1346 Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction on page 1347
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.
Appendix M, Symantec Backup Exec Agent for Microsoft SQL Server 1337
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 jobs 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 Execs 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 1338
Using the database snapshot (SQL 2005) backup method

The backup method, Database Snapshot (SQL 2005), enables you to do the following:

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
1338
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. 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 1339 Reverting SQL 2005 databases using database snapshots on page 1359
Creating database snapshots

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. To create database snapshots 1 2 3 4 5 6 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Source, click Selections. Select the SQL 2005 database for which you want to create a database snapshot. On the Properties pane, under Settings, click Microsoft SQL. In the Backup method field, select Database Snapshot (SQL 2005) - Read only, point-in-time copy of another database.
1339
Setting restore options for SQL
Set the number of database snapshots per database to keep, or accept the default of four. 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 1359

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 by setting job properties on page 498. To set restore options for SQL 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Settings, click Microsoft SQL. Select the appropriate options as follows:
Leave the database ready to use; additional transaction logs or differential backups cannot be restored. Select this option to have the restore operation roll back all uncompleted transactions when you restore the last database, differential, or log backup. After the recovery operation, the database is ready for use. If you do not select this option, the database is left in an intermediate state and is not usable. If you select this option, you cannot continue to restore backups. You must restart the restore operation from the beginning. Leave the database nonoperational; additional transaction logs or differential backups can be restored. Leave the database in read-only mode Select this option 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.
1340
Take existing destination Select this option if you want Backup Exec to automatically take database offline 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. Overwrite the existing database 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. Continue restoring if an error occurs during the restore (SQL 2005 only) 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.
Automate master database restore
1341
Run verify only; do not restore data
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 options 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 1326.
Consistency check after restore
The following options are available:
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.
1342
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.
Restore log up to named transaction
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.
Include the named transaction
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. Click this to start a wizard that helps you select restore job properties for SQL. 1343
Guide Me
About restoring SQL databases and filegroups
Related Topics: About restoring SQL databases and filegroups on page 1344. Restoring from SQL transaction logs up to a point in time on page 1346 Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction on page 1347 Restoring from SQL filegroup backups on page 1348

You can restore a database by using one job or using multiple jobs to restore all of the backup sets. The number of jobs you decide on depends on the types of backup jobs that protect the database or the file group. If you use one job to restore a database, select all the backup sets that you want to apply. Include the full backup, any differential backups, and any log backups. Also select the Leave the 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 the following:
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, ensure 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 the last job, you should specify the recovery completion state Leave the database ready to use. If you use this recovery state, additional transaction logs cannot be restored.
1344
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. 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 1354. 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 by setting job properties on page 498 Restoring from SQL transaction logs up to a point in time on page 1346 Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction on page 1347 Restoring from SQL filegroup backups on page 1348
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 by setting job properties on page 498. 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. See Reverting SQL 2005 databases using database snapshots on page 1359.
1345
To restore from SQL database backups 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. 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. On the Properties pane, under Settings, click Microsoft SQL. On the Restore Job Properties dialog box, click Leave the database ready to use; additional transaction logs or differential backups cannot be restored. See Setting restore options for SQL on page 1340. 7 Start the restore job or select other restore options from the Properties pane.
5 6
Related Topics: About restoring SQL databases and filegroups on page 1344 About SQL 2005 database snapshots on page 1337 Reverting SQL 2005 databases using database snapshots on page 1359
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 2 On the navigation bar, click the arrow next to Restore. Click New Restore Job.
1346
3 4
On the Properties pane, under Source, click Selections. 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. On the Properties pane, under Settings, click Microsoft SQL. On the Restore Job Properties dialog box, click Leave the database ready to use; additional transaction logs or differential backups cannot be restored. Select Point in time log restore, and then select a date and time. See Setting restore options for SQL on page 1340.
5 6
Start the restore job or select other restore options from the Properties pane.
Related Topics: Restoring data by setting job properties on page 498 About restoring SQL databases and filegroups on page 1344
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.
1347
To restore from SQL 2000 or SQL 2005 transaction logs up to a named transaction 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. 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. On the Properties pane, under Settings, click Microsoft SQL. On Restore Job Properties, click Leave the database ready to use; additional transaction logs or differential backups cannot be restored. 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 9 To include the named transaction in the restore, select Include the named transaction. 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. See Redirecting restores for SQL on page 1354. 10 Start the restore job or select other restore options from the Properties pane. Related Topics: Restoring data by setting job properties on page 498 About restoring SQL databases and filegroups on page 1344
5 6
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.
1348
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. 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 instances 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 1350 Restoring a missing or corrupted nonprimary filegroup on page 1351
1349
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 2 3 4 5 6 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. In the restore selections list, select the backup set containing the primary filegroup. On the Properties pane, under Settings, click Microsoft SQL. On the Restore Job Properties dialog box, click Leave the database nonoperational;
additional transaction logs or differential backups can be restored.
See Redirecting restores for SQL on page 1354. 7 8 Start the restore job. After the primary filegroup is restored, select the rest of the filegroup backup sets containing the latest full and differential backups. On the Restore Job Properties dialog box, click Leave the database nonoperational; additional transaction logs or differential backups can be restored, 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 dialog box, click Leave the database nonoperational; additional transaction logs or differential backups can be restored. This option restores all of the transaction logs. You also can 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.
See Restoring data by setting job properties on page 498. Related Topics: Restoring a missing or corrupted nonprimary filegroup on page 1351 About restoring SQL databases and filegroups on page 1344
Restoring a missing or corrupted nonprimary filegroup

Use the following steps to restore a missing or corrupted nonprimary filegroup. To restore a missing or corrupted nonprimary filegroup 1 2 3 4 5 6 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Source, click Selections. In the backup selections list, select the database. On the Properties pane, under Settings, click Microsoft SQL. Select the backup method Log No Truncate, select None for a consistency check, and then start the backup job. 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. On the Restore Job Properties dialog box, click Leave the database ready to use; additional transaction logs or differential backups cannot be restored. 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 1350 About restoring SQL databases and filegroups on page 1344 Restoring data by setting job properties on page 498
1351
Restoring the SQL master database

If the master database is damaged, symptoms may include the following:

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 Execs 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 Execs 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 Microsofts 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: 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\*.*
In a second installed instance of C:\Program Files\Microsoft SQL SQL 2005, the databases are in: Server\MSSQL.2\MSSQL\Data\*.*
1352
In a default installation of SQL 7.0, the databases are in:
C:\MSSQL7\Data
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.
Open a command prompt window, and delete the original master and model databases and their transaction logs. 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$4idr model$4idr modellog$4idr
master.mdf mastlog.ldf model.mdf 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. Continue with the next procedure to restore the latest changes to the master database.
1353
To restore the master database 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. On the restore selections list, select the backup set containing the last master database backup. On the Properties pane, under Settings, click Microsoft SQL. On the Restore Job Properties for SQL dialog box, select Automate master database
restore.
5 6
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 8 Select a consistency check to be run after the restore. Start the restore job. After the restore, SQL restarts in multi-user mode. Related Topics: Restoring data by setting job properties on page 498
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.
1354
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. A database from a 32-bit or 64-bit platform to any other platform.
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:

See Restoring from SQL database backups on page 1345. See Restoring from SQL transaction logs up to a point in time on page 1346. See Restoring from SQL 2000 or SQL 2005 transaction logs up to a named transaction on page 1347. See Restoring from SQL filegroup backups on page 1348.
After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Microsoft SQL Redirection. 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 Server Select this checkbox to enable redirection of SQL backup sets. Check Server to redirect the restore to a different server. After you check the check box, type the target server name. You can redirect a full database backup to a different server or database. If the drive configuration changes after the database backup was created, you must select either of the following options:

Default drive for restoring database files Restore all database files to the target instances data location.
See Setting restore options for SQL on page 1340.
1355
Instance
Check Instance 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.
Database
Check Database to redirect the restore to a different database on the destination server. After you check the check box, type the destination database name. You can redirect a full database backup to a different server or database. If the drive configuration changes after the database backup was created, you must select either of the following options:

Default drive for restoring database files Restore all database files to the target instances data location.
See Redirecting restores for SQL on page 1354. If you restore a differential or log backup, and the associated database backup was restored to a different server, type 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 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.
1356
Even when original drive does 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.
Use destination instances Select this option to restore files to the default data and log default data directory 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. See About using Backup Exec logon accounts for SQL resources on page 1317. 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. See About using Backup Exec logon accounts for SQL resources on page 1317.
1357
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. 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.
Check selections
1358
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 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections.
1359
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.
Click Run Now.
1360
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 2 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Microsoft SQL.
1361

Backup method The following methods are available: 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 1331.
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 1336. 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 1336.
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 1331.
1362
Consistency check before backup
Select one of the following consistency checks 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.
1363
Consistency check after backup
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. The following checks are available:
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.
Display filegroups when creating new backup jobs
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.
Use checksums on backup Select this option to have SQL 2005 add checksums to the SQL (SQL 2005 only) 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.
1364
Database snapshots to keep
(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 1337.
Create on-disk copies of SQL backups to be placed on the SQL server where the database is located
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.
Leave database ready to Select this option to have the restore operation roll back all use. Additional transaction uncompleted transactions when you restore the last database, logs cannot be restored differential, or log backup. After the recovery operation completes, the database is ready for use. If Leave the database ready to use is not performed, the database is left in an intermediate state and is not usable. If you select the option when an intermediate backup is applied, you cannot continue to restore backups. You must restart the restore operation from the beginning. This option is selected by default. Leave the database Select this option during a restore if you have additional nonoperational. Additional differential or transaction log backups to be restored in another transaction logs or restore job. differential backups can be restored Leave the 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.
1365
Consistency check after restore
Select one of the following consistency checks:
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 selected the option Leave the database ready to use, select one of the following consistency checks:
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.
Overwrite the existing database
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.
Related Topics: Setting backup options for SQL on page 1326 About restoring SQL databases and filegroups on page 1344
1366
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 Execs 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.
How to prepare for disaster recovery of SQL 2000 or SQL 2005

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\*.*
1367
The copies of the master and model databases are named:

Master$4idr Mastlog$4idr Model$4idr Modellog$4idr
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. Make sure you are prepared to recover the entire server, not just SQL. See Returning to the last known good configuration on page 661.
How to prepare for disaster recovery of SQL 7.0

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 1369. 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. Make sure you are prepared to recover the entire server, not just SQL. See Returning to the last known good configuration on page 661.
Requirements for SQL disaster recovery

To perform a recovery, you will need the following items:
1368
Disaster recovery of SQL
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.
Creating copies of the SQL 7.0 master and model databases

Use the following steps to create copies of the SQL 7.0 master and model databases. To create copies of the SQL 7.0 master and model databases 1 2 Use the SQL Server Service Manager to stop the SQL services. 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 1369

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 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.
1369
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 1534.
To restore only the SQL databases, review the following:
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, you should redirect the restore. See Redirecting restores for SQL on page 1354.
Related Topics: Recovering SQL manually on page 1370
Recovering SQL manually

If necessary, restore the Windows computer. See Manual disaster recovery of Windows computers on page 664. 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.
1370
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 the restore of the master database. See To restore the master database on page 1354. 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 A named instance of SQL 2000 An initial installation of SQL 2005 A second installed instance of SQL 2005 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\*.*
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:

Rename the copies of the databases back to their original names. The database names are as follows.
master$4idr
master.mdf
1371
master$4idr model$4idr modellog$4idr
mastlog.ldf model.mdf modellog.ldf
Do not use read-only files. The SQL services will not start with read-only files. 4 5 Use the SQL Service Control Manager to start SQL Server. Continue with the next procedure to restore the latest changes to the master database.
To restart SQL 7.0 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. In a default installation of SQL 7.0, the databases are in C:\MSSQL7\Data. 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:

Rename the copies of the databases back to their original names. The database names are as follows.
master$4idr master$4idr model$4idr modellog$4idr
master.mdf mastlog.ldf model.mdf modellog.ldf
1372
Do not use read-only files. The SQL services will not start with read-only files. 4 5 Use the SQL Server Service Manager to start SQL. Continue with the next procedure to restore the latest changes to the master database.
To restore the master database 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. On the restore selections list, select the backup set containing the last master database backup. On the Properties pane, under Settings, click Microsoft SQL. On the Restore Job Properties for SQL dialog box, select Automate master database
restore.
5 6
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 8 Select a consistency check to run after the restore. 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.
1373
To restore the remaining SQL databases 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. Select all the backup sets that you want to apply, including the full backup, any differential backups, and any log backups. Do not select the master database for restore at this time. If you are restoring the SQL databases from filegroup backups, you should be aware of the applicable conditions. See Restoring from SQL filegroup backups on page 1348. 5 6 On the Properties pane, under Settings, click Microsoft SQL. Click Leave the database ready to use; additional transaction logs or differential backups cannot be restored. Click Overwrite the existing database. In the Consistency Check After Database Restore field, click Full check, including indexes. Start the restore job or select other options from the Properties pane. See Redirecting restores for SQL on page 1354. 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 by setting job properties on page 498
7 8
1374
Appendix
Symantec Backup Exec Agent for Oracle on Windows or Linux Servers

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 or 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 Tivoli Storage Manager (TSM) devices as storage devices for Oracle backup jobs. The Oracle Management Server. Oracle backup and restore jobs running on the IPv6 protocol.
The following are not supported:

1375
Installation and configuration requirements for the Oracle Agent
Related Topics: Installation and configuration requirements for the Oracle Agent on page 1376 About upgrading the Backup Exec Oracle Agent on page 1389 What to do when Oracle instance information changes on page 1390
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:
Table N-1 Installing components for the Oracle Agent In this location For more information See Installing Backup Exec options to the local computer on page 75. After you install Oracle 8i on a computer that runs Backup Exec, you must restart the Backup Exec services. After you install Backup Exec on a computer that runs Oracle 8i, you must restart the Oracle services. 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 88. See Installing the Remote Agent for Linux or UNIX Servers on page 917.
Install this agent
Backup Exec Oracle Agent On the media server
1376
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:
Table N-2 Platform For Oracle instances on remote Windows computers Configuring the Oracle Agent For more information See Configuring the Oracle Agent on Windows computers on page 1377.
For Oracle instances on remote Linux See Configuring the Oracle Agent on Linux computers computers on page 1382.
You must then add the Oracle server name and logon account to the media servers list of authentication credentials. See Configuring database access on the media server for Oracle operations on page 1386. Related Topics: What to do when Oracle instance information changes on page 1390 About upgrading the Backup Exec Oracle Agent on page 1389

Before you can back up or restore Oracle databases, you must use the Remote Agent Utility to do the following:

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 on should be a member of the Oracle DBA group. You must have administrator privileges to run the Remote Agent Utility.
Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers
1377
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 Do the following in the order listed:

Click New. Go to step 4.
To edit an existing Oracle Do the following in the order listed: instance Select the instance that you want to edit.

Click Edit. Go to step 4.
To delete an Oracle instance
Select the instance that you want to delete, and then click Delete. Go to step 5.
Complete the appropriate options as follows:

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. 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-<dbname>-<dbid>, where dbname is the database name, and dbid is the database ID.
1378
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 Confirm password Use recovery catalog
Type the password for the Oracle instance user name. Type the password again to confirm it. 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 User name Password Confirm password Media server name or IP address
Type the Oracle Net Service name. Type the user name for the Oracle recovery catalog. Type the password for the Oracle recovery catalog. Type the password for the recovery catalog again to confirm it. 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. See Configuring DBA-initiated job settings for Oracle on page 1396.
Click OK.
1379
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 3 Click the Database Access tab. Complete the appropriate options as follows:
Enable media server Check Enable media server authentication for Oracle and DB2 authentication for Oracle operations to enter the credentials that the media server will use and DB2 operations 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. 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 1386. 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. For security reasons, the logon credentials are not stored on the remote computer.
1380
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 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. See Setting default backup network and security options on page 318.
Port number
Type the port number to use for operation requests that are sent to the media server.
4 5
Click OK. 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 servers backup selection tree. See Publishing the remote Windows computer to media servers on page 892.
1381
Configuring the Oracle Agent on Linux computers
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 servers list of authentication credentials. See Configuring database access on the media server for Oracle operations on page 1386.
Related Topics: About backing up Oracle resources on page 1390 About backing up Oracle RAC resources on page 1391 Configuring DBA-initiated job settings for Oracle on page 1396 Setting application defaults for Oracle on page 1398

Before you can back up or restore Oracle databases, you must use the Remote Agent Utility to do the following:

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, the user account with which you are logged on should be a member of the Oracle DBA group. To configure the Oracle Agent on Linux computers 1 On the Linux computer on which the Oracle instances are installed, open a Terminal window. Type the following command: cd /opt/VRTSralus/bin 3
1382
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 Proceed to step 6 to edit or delete the instance, or to view information about the instance. Proceed with step 7.
Do any of the following:

Edit an existing Oracle instance 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 8
Type 1 to select the Add a new Oracle Instance option, and then press Enter. Enter the name of the Oracle instance in upper case characters. For example, ORACLENAME.
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. 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.
1383
10 To display the Oracle database in a media servers 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 <computer name> <root>. Oracle RAC databases are listed in the media servers 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 1396. 14 Do one of the following:
To commit the new entry to the configuration Type Y, and then press Enter. file To cancel this entry Type N, and then press Enter.
15 To add more instances, repeat step 7 - step 13. 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. Type the user name that is in the beoper group on the Linux system. See About creating the beoper group on page 917.
1384
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. See Setting default backup network and security options on page 318. 6 Do one of the following:
To commit the Oracle operation settings to the Type Y, and then press Enter. configuration file To cancel this entry Type N, and then press Enter.
On the media server, add the Oracle server name and the logon account name to the list of authentication credentials. See Configuring database access on the media server for Oracle operations on page 1386.
Related Topics: About backing up Oracle resources on page 1390 About backing up Oracle RAC resources on page 1391 Configuring DBA-initiated job settings for Oracle on page 1396 Setting application defaults for Oracle on page 1398
1385
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 servers 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-<database name>-<database ID>. To configure database access on the media server for Oracle operations 1 2 3 On the media server, on Tools menu, click Options. On the properties pane, under Job Defaults, click Oracle. 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 5 Click New. Enter the name of the Oracle server on which the instance is installed. 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 Click New Select the logon account name that you want to add. On the Logon Account Selection dialog box, click New. See Creating a Backup Exec logon account on page 149.
1386
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 8 Click OK. 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 servers list of authentication credentials on page 1387 What to do when Oracle instance information changes on page 1390 Configuring the Oracle Agent on Windows computers on page 1377 Configuring the Oracle Agent on Linux computers on page 1382 Deleting an Oracle server name or logon account from the media servers list of authentication credentials on page 1388 About backing up Oracle resources on page 1390
Editing an Oracle server name or logon account on the media servers list of authentication credentials
If the Oracle server name or the logon account name for the Oracle server changes, you must update the media servers 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. 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 servers list of authentication credentials 1 2 3 On the media server, on Tools menu, click Options. On the properties pane, under Job Defaults, click Oracle. Click the Modify list button.
1387
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 5 6 Select the item that contains the server name or logon account that you want to edit. Click Edit. 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 1386 Configuring the Oracle Agent on Windows computers on page 1377 Configuring the Oracle Agent on Linux computers on page 1382 Deleting an Oracle server name or logon account from the media servers list of authentication credentials on page 1388
Deleting an Oracle server name or logon account from the media servers list of authentication credentials
You can delete an Oracle server name or logon account from a media servers list of authentication credentials. To delete an Oracle server name or logon account from the media servers list of authentication credentials 1 2 3 On the media server, on Tools menu, click Options. On the properties pane, under Job Defaults, click Oracle. 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. Click Delete.
1388
About upgrading the Backup Exec Oracle Agent
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 12 replaces the (legacy GRFS) 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:
Table N-3 Task Upgrading the Backup Exec Oracle Agent Description
Verify that the logon account for each See Changing and testing resource credentials for resource that was backed up by the restore jobs on page 527. previous Oracle Agent is valid for the new Oracle Agent. Use the Remote Agent Utility to See Configuring the Oracle Agent on page 1377. 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 See Configuring database access on the media server for account to the media servers list of Oracle operations on page 1386. authentication credentials. 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 12 automatically backs up the database control file whenever a table space or other resource on the Oracle server is backed up.
1389
What to do when Oracle instance information changes
Note If you have a backup selections list that contains the database control file as its single resource, 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. This applies only to selection lists created with the legacy GRFS Oracle Agent.
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 1377 Configuring the Oracle Agent on Linux computers on page 1382 Setting application defaults for Oracle on page 1398 About performing a DBA-initiated backup job for Oracle on page 1394 Configuring DBA-initiated job settings for Oracle on page 1396
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 1377. See Configuring the Oracle Agent on Linux computers on page 1382.
1390
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. See Restricting the backup of a selection list to specific devices on page 785. 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 <drive>. 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 1392 About performing a DBA-initiated backup job for Oracle on page 1394 Configuring DBA-initiated job settings for Oracle on page 1396
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 servers 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.
1391
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 1377. See Configuring the Oracle Agent on Linux computers on page 1382.
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 servers backup selections list. It is in the form RAC-<database name>-<database ID>.
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 1394 Configuring DBA-initiated job settings for Oracle on page 1396 Setting application defaults for Oracle on page 1398
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 1376. See About backing up Oracle resources on page 1390. To back up Oracle resources 1 2 On the navigation bar, click the arrow next to Backup. Click New Backup Job.
1392
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-<database name>-<database ID>. 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. 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 6 On the Properties pane, under Settings, click Oracle. Complete the appropriate options as follows:.
Backup method Select one of the following backup methods:
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.
Delete backed up archive Check Delete backed up archive log files to delete the archived log log files files automatically after the backup. Do not back up archived Check Do not back up archived logfiles that have already been logfiles that have already backed up to have Backup Exec skip any archived logfiles that been backed up have been backed up previously. Appendix N, Symantec Backup Exec Agent for Oracle on Windows or Linux Servers 1393
Perform the backup offline
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.
To configure multiple data streams for backup, under Destination, click Device and
Media.

Maximum number of devices to use for resources that support multiple data streams 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 391. This feature is not available for DBA-initiated jobs. Minimum number of devices, terminate job if fewer devices are available Enter the minimum number of devices that the job can use. If the job cannot acquire the minimum number of devices, the job fails. This feature is not available for DBA-initiated jobs.
Complete the remaining backup job properties as necessary. See Backing up data on page 263.
Related Topics: About backing up Oracle resources on page 1390 Setting application defaults for Oracle on page 1398 Troubleshooting the Oracle Agent on page 1408 Configuring DBA-initiated job settings for Oracle on page 1396
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:
Make sure that you have completed all of the preparations for configuring the Oracle Agent. See Configuring the Oracle Agent on page 1377. The channel is not released if the RMAN console is not exited, or if a new manual channel is not allocated on that console. See Troubleshooting the Oracle Agent on page 1408. 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.
In a CASO environment, the destination device that you select in the DBA-initiated job template must be locally attached to the central administration server. If the destination device includes a device pool, all devices in the pool must be locally attached to the central administration server.
Related Topics: What to do when Oracle instance information changes on page 1390 About backing up Oracle resources on page 1390
1395
Configuring DBA-initiated job settings for Oracle

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 1377. See Configuring the Oracle Agent on Linux computers on page 1382. 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 2 On the Tools menu, click Options, and then click DBA-initiated Job Settings. Do any of the following:
To create a new job template Do the following in the order listed:

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.
On the DBA-initiated Job Settings pane, under Destination, click Device and Media, and then complete the options as appropriate. See Device and media options for backup jobs and templates on page 272. Some options are not available for the DBA-initiated job settings.
On the DBA-initiated Job Settings pane, under Settings, click General, and then complete the options as appropriate. See General options for backup jobs and templates on page 275.
1396
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. See Encryption keys on page 332. 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. See Assigning notification recipients for completed jobs on page 573. 7 Click OK.
Related Topics: Troubleshooting the Oracle Agent on page 1408 Deleting a job template for DBA-initiated jobs for Oracle on page 1397
Deleting a job template for DBA-initiated jobs for Oracle

The job template contains the settings that Backup Exec applies to DBA-initiated jobs. To delete a job template for DBA-initiated jobs for Oracle 1 2 3 4 On the Tools menu, click Options, and then click DBA-initiated Job Settings. Select the job template that you want to delete. Click Delete. Click OK.
Related Topics: Configuring DBA-initiated job settings for Oracle on page 1396
1397
Setting application defaults for Oracle
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 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click Oracle. Complete the appropriate options as follows:
Backup Method Select one of the following backup methods:
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.
Delete backed up archive Check Delete backed up archive log files to delete the archived log log files files automatically after the backup job. Do not back up archived Check Do not back up archived logfiles that have already been logfiles that have already backed up to have Backup Exec skip any archived logfiles that been backed up have been backed up previously. Perform the backup offline Modify list 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. Click Modify list to add the Oracle computer name and the logon account name to the media servers list of authentication credentials for Oracle servers. See Configuring database access on the media server for Oracle operations on page 1386.
1398
About restoring and recovering Oracle resources
Click OK.
Related Topics: Troubleshooting the Oracle Agent on page 1408 What to do when Oracle instance information changes on page 1390 About backing up Oracle resources on page 1390

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. Note Symantec no longer supports the Symantec Backup Exec - Agent for Oracle Server and its use of GRFS technology. Files that are backed up using that agent can be restored as a file system restore. See Restoring from a legacy GRFS Oracle Agent database backup on page 1407. 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. Note Backup Exec does not support Oracle tablespace point-in-time restore (TSPITR) through server-initiated operations. 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.
1399
On the View by Resource tab, you can make restore selections from the online database or from control files.
Table N-4 Viewing restore selections for Oracle resources Description 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-<database name>-<database ID>. Control files Provides a list of all backed up control files. Each control file lists the date it was backed up and the control files 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. Additionally, when you restore a control file, the entire database reverts to the point in time of the restored control file.
View restore data in Online database
Related Topics: Restoring Oracle data on page 1401 Redirecting a restore of Oracle data on page 1405
1400
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 1377. See About restoring and recovering Oracle resources on page 1399. Note In a CASO environment, you can delegate an Oracle restore job to a managed media server. However, if the restore job uses encrypted Oracle backup sets from which to restore, the restore job may fail. An error message may appear that indicates the managed media server does not have the required encryption keys necessary to complete the job. You must create the encryption keys on the managed media server that runs the restore job. See Creating an encryption key on page 334. To restore Oracle data 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. Click the View by Resource tab.
1401
5 6
Expand the All Resources icon. Expand the system resource that contains the database instance that you want to restore. 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.
Expand either the Current Database or Control Files resource. 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.
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 Check Restore from full and/or incremental backups and then select an option to restore data from one of the following:

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. To the most recent available Select this option to restore the Oracle database to the most recent full and incremental backups that are available.
1402
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 Restore read-only files if they are not current Validate only; do not restore data
Select this option to restore up to and including a specific system control number (SCN). Type the SCN in the field provided. 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. 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.
Restore/recover data if validation completes without errors
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.
1403
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. 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.
After recovery, delete archived redo logs that are no longer needed Open database after recovery
12 Select other restore options from the Properties pane as appropriate, and then start the restore job. See Restoring data by setting job properties on page 498. 13 Run a full backup of the restored database. Related Topics: Configuring DBA-initiated job settings for Oracle on page 1396 About DBA-initiated restore and recovery for Oracle on page 1401 Troubleshooting the Oracle Agent on page 1408
1404
Redirecting a restore of Oracle data

In Backup Exec, you can redirect an Oracle instance or its files by redirecting the following:
An Oracle instance to another Oracle server.
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. To redirect a restore of Oracle data 1 Create a restore job for Oracle data. See Restoring Oracle data on page 1401. 2 After you select options on the Restore Job Properties dialog box for Oracle, on the Properties pane, under Destination, click Oracle Redirection. 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. Type the name of the server to which you want to redirect the restore job. Type a logon account that has rights to restore data to the server to which you want to redirect the restore job. Type a logon account for the Oracle instance that you want to restore.
Server Server logon account Instance logon account:
1405
Restore datafiles 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.
Restore archived log files to the following path
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
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 backing up Oracle resources on page 1390
1406
Restoring from a legacy GRFS Oracle Agent database backup
Restoring from a legacy GRFS Oracle Agent database backup

To restore legacy GRFS Oracle Agent datafile backups, you must use a redirected file system restore job. After you restore the datafiles, you must use your Oracle database administration tools to add the datafile to the intended Oracle instance. See your Oracle documentation for assistance. To restore a legacy GRFS Oracle Agent backup 1 2 3 4 5 6 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the Properties pane, under Source, click Selections. On the View by Resource tab, expand All Resources. Browse to the GRFS Oracle resource that you want to restore. On the results pane, check the check box of the Oracle datafile that you want to restore. In the Properties pane, under Destination, click File Redirection. Do not click Oracle Redirection. This is a file system restore process only. 8 9 Check the Redirect file sets checkbox. Type a drive letter in Restore to drive.
10 Type a path in Restore to path. 11 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

See Scheduling jobs on page 286
12 Rename the restored datafile to match the name of the original Oracle datafile.
1407
Troubleshooting the Oracle Agent
13 Add the datafile to the intended Oracle instance. See your Oracle documentation for assistance.
Troubleshooting the Oracle Agent

If you have a problem with the Oracle Agent, the questions and answers in this section may help you solve the problem. 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. The following table describes how to change the SQLplus time-out.
Table N-5 On this platform For Oracle instances on Windows computers Changing the SqlplusTimeout Do the following
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. Administrators Guide
1408
Troubleshooting the Oracle Agent Table N-5 On this platform For Oracle instances on Linux computers Changing the SqlplusTimeout Do the following
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. The following table describes how to change the default time-out.
Table N-6 On this platform For Oracle instances on Windows computers Changing the time-out for an automatic RMAN channel Do the following
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.
1409
Disaster recovery of the Oracle instance or database Table N-6 On this platform For Oracle instances on Linux computers Changing the time-out for an automatic RMAN channel Do the following
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 <time-out>
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 1377 Configuring the Oracle Agent on Linux computers on page 1382 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 1386 About creating the beoper group on page 917
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 1411 Disaster recovery scenario 2 on page 1413
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. To successfully complete the recovery using this scenario, you must have the following items:
Table N-7 Item DBID ControlFile piece ID A full system Oracle backup Oracle disaster scenario 1 requirements Description If you do not know the DBID, you can find it in the Backup Exec job log or in RMAN after you login. 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
The original Oracle server
To successfully recover the Oracle system using disaster recovery scenario 1, you must restore to the original Oracle server.
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. Find and rename the pwd<SID>.ora file. Create a new pwd<SID>.ora file.
2 3
To create a new pwd<SID>.ora file 1 2 Open a command prompt. Type the following command:
orapwd file=path\pwdsid.ora password=<password>
1411
To continue the disaster recovery 1 2 Open a command prompt and do the following: Type the following command:
RMAN
3 4 5 6 7 8 9
Type CONNECT TARGET <sys/password@sid>; Type SHUTDOWN ABORT; Type STARTUP NOMOUNT; Type SET DBID<dbid ID>; Move to the Backup Exec media server. On the navigation bar, click the arrow next to Restore. Click New Restore Job.
10 On the Properties pane, under Source, click Selections. 11 Select the appropriate ControlFile for restore. 12 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. 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
1412
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. To successfully complete the recovery, you must have the following items:
Table N-8 Item DBID ControlFile piece ID A full system Oracle backup Oracle disaster scenario 2 requirements Description If you do not know the DBID, you can find it in the Backup Exec job log or in RMAN after you login. 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 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. Find and rename the pwd<SID>.ora file. Create a new pwd<SID>.ora file.
2 3
To create a new pwd<SID>.ora file 1 2 Open a command prompt. Type the following command:
orapwd file=path\pwdsid.ora password=<password>
To continue the disaster recovery 1 2 In the command prompt, do the following: Type the following command:
1413
Disaster recovery of the Oracle instance or database RMAN
3 4 5 6 7 8 9
Type CONNECT TARGET <sys/password@sid>; Type SHUTDOWN ABORT; Type STARTUP NOMOUNT; Type SET DBID<dbid ID>; Move to the Backup Exec media server. On the navigation bar, click the arrow next to Restore. 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. 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 1414 Note the online redo log path and then update the path using the steps below. Administrators Guide
If an error does not occur
Do nothing. The disaster recovery is complete.
To update the online redo log file path 1 2 At the Oracle server, open a command prompt. Type the following command:
SQLPLUS /nolog
3 4
Type connect<sys/password@SID>; Type the following SQLPlus command:

SQLPLUS ALTER DATABASE RENAME FILE <old path from backup to any redolog file name> to <path to expected restored redolog file name>;
For example, ALTER DATABASE RENAME FILE D:\ORACLE\ORADATA\JACOB\REDO01.LOG to C:\ORACLE\ORADATA\JACOB\REDO01.LOG; 5 6 In the command prompt, type RMAN. Type the following command at the RMAN prompt:
Alter database open resetlogs;
Close the command prompt. The recovery is finished.
1415
1416
Appendix
Symantec Backup Exec Agent for SAP Applications

The Backup Exec Agent for SAP Applications (SAP Agent) lets you back up, restore, and archive SAP for Oracle and MaxDB databases using one of the following:

BACKINT, the backup and restore interface developed by SAP Oracles 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: Backup strategies for SQL on page 1319 About the Backup Exec Oracle Agent on page 1375
1417
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 1426 About encrypting SAP data on page 1422 Changing the backup network and security options for a job on page 322 General options for backup jobs and templates on page 275 About preserving the integrity of the SAP Agent catalog on page 1423
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.
1418
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: <x>:\Oracle\<SID>\sapbackup where <x> is the database installation drive and <SID> 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\<SID>\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 1428 About performing disaster recovery using the SAP Agent on page 1437
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: About the Backup Exec Oracle Agent on page 1375 About using the SAP Agent with RMAN on page 1419 The Remote Agent Utility for Windows Systems on page 889
Appendix O, Symantec Backup Exec Agent for SAP Applications
1419
Requirements for using the SAP Agent
Requirements for using the SAP Agent

You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 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. See Configuring biparam.ini on page 1425. The backup operator must be a member of the ORA_DBA group. You must create the ORA_<SID>_OPER group and add the backup user. 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 71 System requirements on page 69
1420
About installing the SAP Agent
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_<SID>_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\<SID>\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 71 Installing Backup Exec options to the local computer on page 75
1421
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 1422 Generating alerts on page 1423 About preserving the integrity of the SAP Agent catalog on page 1423 About performing disaster recovery using the SAP Agent on page 1437 Changing Windows security on page 65
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 1426 Encryption keys on page 332
1422
Generating alerts
Backup Exec generates alerts, which BACKINT handles in one of the following modes:
Table O-1 Item Alert modes Description
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 1425
1423
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 889. Add the Oracle Server to the media servers Modify list. See Configuring database access on the media server for Oracle operations on page 1386.
If you want to enter specific configuration information, you should also edit the biparam.ini file that is found in your Usr\sap\<SID>\sys\exe\run directory and the init<SAP>.sap file that is found in the <ORACLE_HOME>\database folder. Related Topics: Configuring biparam.ini on page 1425 Setting application defaults for Oracle on page 1398
1424
Configuring biparam.ini
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 <ORACLE_HOME> database\init<SID>.sap file specifies the path of the biparam.ini file.
Edit any of the following options in the biparam.ini file to configure the media server:
Server=<server name> Name of the Backup Exec server that will process this backup job. 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=<Job Name> Job Template= <DBA-initiated Job Template on Media Server> User-specified Job Name. The default is the media server generated Job Name. The job template that will be used for this job. The job template includes settings like device, media, and encryption key. The DBA-initiated Job Template has to be created at the media server. See Configuring DBA-initiated job settings for SAP on page 1426. 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.
1425
Backup Catalog=<On/Off>
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.
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 1425. 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 2 3 On the Tools menu, click Options. Click DBA-initiated Job Settings. Do any of the following:
To create a new job template Do the following in the order listed:

Click New. Proceed to step 4.

Select the job template that you want to edit. Click Edit. Proceed to step 4.
1426
To delete a job template

Select the job template that you want to delete. Click Delete.
On the DBA-initiated Job Settings pane, under Settings, click General, and then complete the options as appropriate. See General options for backup jobs and templates on page 275. Some options are not available for the DBA-initiated job settings.
On the Properties pane, under Settings, click Network and Security, and then complete the options as appropriate. See Encryption keys on page 332. Some options are not available for the DBA-initiated job settings.
If you want Backup Exec to notify someone when the backup job completes, click Notification, and then complete the options as appropriate. See Assigning notification recipients for completed jobs on page 573.
Click OK.
1427
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\<SID>\sys\exe\run
Related Topics: About performing disaster recovery using the SAP Agent on page 1437
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<ORACLE_SID>.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.
1428
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 <last | logfile name> -m <tablespace to restore>=\\ComputerB\D$\RestoreDirectory
1429
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.

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 889. You must modify the rman_send parameters in the Init<SID>.sap file as follows: rman_send = ( "channel sbt_1 'NBBSA_SAP_CONFIG_PATH=<INI file Path>'") where <INI file path> is the full path for the biparam.ini. For example: C:\oracle\ora92\database\biparam.ini. See Configuring biparam.ini on page 1425. Ensure that the ini file path mentioned in the parameter 'util_par_file' in the init<sid>.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<SID>.ora as follows: control_file_record_keep_time <n>, (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:
$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.
1431
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 889. You must modify the rman_send parameters in the Init<SID>.sap file as follows: rman_send = ( "channel sbt_1 'NBBSA_SAP_CONFIG_PATH=<INI file Path>'") where <INI Path > is the full path for the biparam.ini. For example: C:\oracle\ora92\database\biparam.ini. See Configuring biparam.ini on page 1425. Ensure that the ini file path mentioned in the parameter 'util_par_file' in the init<sid>.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<SID>.ora as follows: control_file_record_keep_time <n>, (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.
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 in the following situations:

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. 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.
Before migrating the data, do the following:
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 <Path for the _backint.mdb> <optional Path for Log file > 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.
1433
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.
1434
Backing up MaxDB databases
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. MaxDBs 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.
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. To prepare to back up MaxDB databases 1
Ensure that the following files are present:

SAP.PAR BSI.ENV
Ensure that the following parameters are set during the installation of MaxDB:

independent data path = C:\sapdb\data independent program path = C:\sapdb\programs dependant path to C:\sapdb\<sid>\db
Ensure that the following paths exist:

C:\sapdb C:\sapdb\programs C:\sapdb\data C:\sapdb\<sid> C:\sapdb\<sid>\db
1435
Restoring MaxDB databases
Ensure that the appropriate versions of the following applications are installed:

SQL studio DBMGUI
To back up MaxDB databases: 1 2 3 4 Copy BSI.ENV into C:\sapdb\data\wrk\<sid> Copy SAP.PAR into C:\sapdb\<sid>\db From the MaxDB Database Manager, select the Backup Wizard. Provide the appropriate inputs for the backup job, including the following:

Type of backup Pipe used Name of pipe
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. MaxDBs 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.
1436
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 Administrators 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\<SID>\sys\exe\run Schedule full online backups of your SAP database server regularly.
Related Topics: Configuring biparam.ini on page 1425
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: Creating a backup job by setting job properties on page 267
Appendix O, Symantec Backup Exec Agent for SAP Applications 1437
Recovering a remote SAP database server from a disaster

Recovering a remote SAP database involves re-installing the Microsoft Windows operating system and restoring files from a recent backup. 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. 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. 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. When the restore operation completes, open the CCMS console, and click Check and Repair Database. Click Automatic Recovery, and then follow the online prompts.
1438
Recovering a combination SAP database server and media server

Recovering a combination SAP database server and media server involves re-installing the Microsoft Windows operating system and restoring files from a recent backup. 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 3 Re-install Backup Exec. Recatalog the media containing the full flat file SAP database server file system backup, and the media containing the SAP database tablespace data files. 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. Select Automatic Recovery, and then follow the online prompts to complete Disaster recovery of the SAP database server.
1439
1440
Appendix
Symantec Backup Exec Agent for DB2 on Windows Servers

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.
You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1 Note Backup Exec does not support DB2 running as a 32-bit Windows-based application on a 64-bit Windows operating system.
1441
Installation and configuration requirements for the DB2 Agent
Backup Exec does not support DB2 backup and restore jobs running on the IPv6 protocol. Related Topics: Installation and configuration requirements for the DB2 Agent on page 1442 About DBA-initiated jobs for DB2 operations on page 1453

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:
Table P-1 Installing components for the DB2 Agent In this location On the media server On remote Windows computers For more information See Installing Backup Exec options to the local computer on page 75. See Installing the Remote Agent for Windows Systems on page 88.
Install this agent Backup Exec DB2 Agent 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:
Table P-2 Configuring the DB2 Agent Go to Configuring the DB2 Agent on Windows computers on page 1443. Configuring database access on the media server for DB2 operations on page 1448.
To configure DB2 Agent information On the computer on which the DB2 instances are installed On the media server
1442
Configuring the DB2 Agent on Windows computers

Before you can back up or restore DB2 databases, you must use the Remote Agent Utility or the Remote Agent Utility command line to do the following:

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 following:
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 with the Remote Agent Utility 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 3 Click the DB2 tab. Do one of the following:
To add a DB2 instance

Click New. Go to step 4. Select the instance that you want to edit. Click Edit. Go to step 4. Select the instance that you want to delete, and then click Delete. Go to step 5.
To change an existing DB2 instance
To delete a DB2 instance
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers
1443

Local instance name User name To add an instance, enter the name of the DB2 instance. If you are editing an instance, you cannot change the instance 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 1448. Password Confirm password Media server Type the password for the DB2 instance user name. Type the password again to confirm it. 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. See Configuring DBA-initiated job settings for DB2 on page 1459.
1444
Archive logs template name
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. 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. If this situation occurs when the device is a backup-to-disk folder, increase the number of concurrent operations allowed on the backup-to-disk folder. 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 1459. For more information about the user exit or VENDOR method: See Using the DB2 database archive logging methods on page 1455.
Click OK.
Related Topics: The Remote Agent Utility for Windows Systems on page 889 About the Remote Agent Utility Command Line Applet on page 895 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.
1445

Enable media server Check Enable media server authentication for Oracle and DB2 authentication for Oracle operations to enter the credentials that the media server will use and DB2 operations 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. 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. 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 1448. 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. 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.
1446
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 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 318.
Port number
Type the port number to use for operation requests that are sent to the media server.
4 5
Click OK. 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 servers list of authentication credentials.
Related Topics: Configuring database access on the media server for DB2 operations on page 1448 Using the DB2 database archive logging methods on page 1455 Backing up DB2 resources on page 1451 Configuring DBA-initiated job settings for DB2 on page 1459 Setting application defaults for DB2 on page 1461
1447
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 servers 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. To configure database access on the media server for DB2 operations 1 2 3 On the media server, on the Tools menu, click Options. On the properties pane, under Job Defaults, click DB2. 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 5 6 Click New. Enter the name of the DB2 server on which the instance is installed. To add the logon account name, do one of the following:
Click the arrow Click New Select the logon account name that you want to add. On the Logon Account Selection dialog box, click New. 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.
1448
Related Topics: Editing a DB2 server name or logon account on the media servers list of authentication credentials on page 1449 Configuring the DB2 Agent on Windows computers on page 1443 Backing up DB2 resources on page 1451 Setting application defaults for DB2 on page 1461 Configuring DBA-initiated job settings for DB2 on page 1459 Deleting a DB2 server name or logon account from the media servers list of authentication credentials on page 1450
Editing a DB2 server name or logon account on the media servers list of authentication credentials
If the DB2 server name or the logon account name for the DB2 server changes, you must update the media servers 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 servers list of authentication credentials 1 2 3 On the media server, on the Tools menu, click Options. On the properties pane, under Job Defaults, click DB2. 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 5 6 Select the item that contains the server name or logon account that you want to edit. Click Edit. Change the server name, or change the logon account name. See Editing a Backup Exec logon account on page 150.
1449
Click OK.
Related Topics: Configuring database access on the media server for DB2 operations on page 1448 Configuring the DB2 Agent on Windows computers on page 1443 Deleting a DB2 server name or logon account from the media servers list of authentication credentials on page 1450
Deleting a DB2 server name or logon account from the media servers list of authentication credentials
Delete a DB2 server name or logon account from the media servers list of authentication credentials if you no longer want to back up the DB2 server. If you later decide that you do want the media server to back up the DB2 server, you must add the DB2 server again to the media servers list of authentication credentials. See Configuring database access on the media server for DB2 operations on page 1448. To delete a DB2 server name and a logon account from the media servers list of authentication credentials 1 2 3 On the media server, on the Tools menu, click Options. On the properties pane, under Job Defaults, click DB2. 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. Click Delete. See Deleting a Backup Exec logon account on page 153. 6 Click OK.
1450
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 1442. 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.
To back up DB2 resources 1 2 3 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the backup selection list, under the Favorite Resources node, expand the Windows Systems node. 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 234. 5 Select the following objects as appropriate:
Instance Database Partition Tablespace Select an instance to back up all of the DB2 databases that it contains. Select a database to back up all of the partitions that it contains. Select a partition to back up all of the tablespaces and log folders that it contains. Select all tablespaces or individual tablespaces to back up.
On the Properties pane, under Settings, click DB2.
1451
Complete the appropriate options as follows:.

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.
Perform the backup offline
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.
Quiesce the database before offline backup
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.
To configure multiple data streams for backup, under Destination, click Device and
Media.

Maximum number of devices to use for resources that support multiple data streams 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 391. This feature is not available for DBA-initiated jobs.
1452
About DBA-initiated jobs for DB2 operations
Minimum number of devices, terminate job if fewer devices are available
Enter the minimum number of devices that the job can use. If the job cannot acquire the minimum number of devices, the job fails. This feature is not available for DBA-initiated jobs.
10 Complete the remaining backup job properties as necessary. See Creating a backup job by setting job properties on page 267. Related Topics: Configuring DBA-initiated job settings for DB2 on page 1459 Setting application defaults for DB2 on page 1461

Backup Exec supports DBA-initiated backup, restore, redirected restore, and recovery of DB2 databases. The Backup Exec DB2 Agent installs the following files:
Table P-3 File The vendor dll file db2sqluv.dll and the user exit program db2uext2.exe Files that are installed with the DB2 Agent Description 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 1455.
1453
About DBA-initiated jobs for DB2 operations Table P-3 File A configuration file named db2.conf Files that are installed with the DB2 Agent (continued) Description 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 1456. Example scripts for backup and restore 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
Review the following notes before you run DBA-initiated jobs for DB2:
Complete all of the preparations for installing and configuring the DB2 Agent. See Installation and configuration requirements for the DB2 Agent on page 1442. 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. With DBA-initiated jobs in a CASO environment, the destination device that you select in the DBA-initiated job template must be locally attached to the central administration server. This includes DBA-initiated DB2 archive log jobs. If the destination device includes a device pool, all devices in the pool must be locally attached to the central administration server.
Related Topics: About troubleshooting DB2 on page 1467 Using the DB2 database archive logging methods on page 1455
1454
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 following:

The source database for the archive logging operations. The destination database for any roll forward operations.
You must also add the DB2 server name that contains these instances to the media servers list of DB2 servers and authentication credentials. 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.:
Table P-4 Error 514 Errors that may occur while using db2sqluv.dll Description 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. See the Application log in the Windows Event Viewer for details about the error.
SQL2062N
Related Topics: Configuring the DB2 Agent on Windows computers on page 1443 Configuring DBA-initiated job settings for DB2 on page 1459 About troubleshooting DB2 on page 1467 About the db2.conf file on page 1456
1455
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. See Configuring DBA-initiated job settings for DB2 on page 1459. Related Topics: About DBA-initiated jobs for DB2 operations on page 1453 Editing a db2.conf file on page 1456
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 Execs 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. See Configuring DBA-initiated job settings for DB2 on page 1459. 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.
1456
3 4
Save and close the db2.conf file. 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 1453 Example db2.conf file on page 1457
Example db2.conf file

The sample db2.conf file is as follows:
# # 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 ------------------------# # # # # # Specifies an alternate restore Names the source instance that was backed up Names the source database alias that was backed up Names the destination instance name Names the destination database alias name Ends the object identifier
#OBJECTTYPE ALTERNATE #SRCINST srcinstname #SRCALIAS srcaliasname #DESTINST destinstname #DESTALIAS destaliasname #ENDOPER
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
1457

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. 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
1458
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 1443. 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.
To configure DBA-initiated job settings for DB2 1 2 On the Tools menu, click Options, and then click DBA-initiated Job Settings. 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. See Configuring the DB2 Agent on Windows computers on page 1443.
Proceed to step 3. Select the job template that you want to edit. Click Edit. Proceed to step 3.
1459
On the DBA-initiated Job Settings pane, under Settings, click General, and then complete the options as appropriate. See General options for backup jobs and templates on page 275. Some options are not available for the DBA-initiated job settings.
On the Properties pane, under Settings, click Network and Security, and then complete the options as appropriate. See Encryption keys on page 332. Some options are not available for the DBA-initiated job settings.
If you want Backup Exec to notify someone when the backup job completes, click Notification, and then complete the options as appropriate. See Assigning notification recipients for completed jobs on page 573.
Click OK.
Related Topics: Deleting a job template for DBA-initiated jobs for DB2 on page 1460
Deleting a job template for DBA-initiated jobs for DB2

You can delete a job template at any time. To delete a job template for DBA-initiated jobs for DB2 1 2 3 4 On the Tools menu, click Options, and then click DBA-initiated Job Settings. Select the job template that you want to delete. Click Delete. Click OK.
Related Topics: Configuring DBA-initiated job settings for DB2 on page 1459
1460
Setting application defaults for DB2
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 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click DB2. Complete the appropriate options as follows:
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.
Perform backups offline
Check Perform backups 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. Click Modify list to add the DB2 computer name and the logon account name to the media servers list of authentication credentials for DB2 servers. See Configuring database access on the media server for DB2 operations on page 1448.
Quiesce the database before offline backup
Modify list
Click OK.
Related Topics: Backing up DB2 resources on page 1451 Restoring DB2 data on page 1462
Appendix P, Symantec Backup Exec Agent for DB2 on Windows Servers 1461
Restoring DB2 data
About troubleshooting DB2 on page 1467
Restoring DB2 data

Before you restore DB2 resources, make sure that you have completed all of the preparations for installing and configuring the DB2 Agent. See Installation and configuration requirements for the DB2 Agent on page 1442. Note In a CASO environment, you can delegate a DB2 restore job to a managed media server. However, if the restore job uses encrypted DB2 backup sets from which to restore, the restore job may fail. An error message may appear that indicates the managed media server does not have the required encryption keys necessary to complete the job. You must create the encryption keys on the managed media server that runs the restore job. See Creating an encryption key on page 334. To restore DB2 data 1 2 3 4 5 6 On the navigation bar, click the arrow next to Restore. Click New Restore Job. On the Properties pane, under Source, click Selections. Click the View by Resource tab. Expand the All Resources icon. Expand the system resource that contains the database instance that you want to restore. Do one of the following:
To restore the entire database Check Current Database. If the database is offline, the Current Database is empty and you cannot make selections. Check a backup set, or a historical set. Expand either Current Database or a backup set, and then check any of the table spaces that you want to restore.
To restore a backup set To restore a table space
1462
Restoring DB2 data
8 9
On the properties pane, under Settings, click DB2. Complete the appropriate options as follows.
Restore database from full and/or incremental backups To the most recent available To a point in time Check Restore database 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. 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. For databases that have circular logging enabled, you must uncheck Roll forward using logs or the job will fail. To the most recent available To a point in time Select this option to roll the DB2 database forward to the most recent logs that are available. 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.
1463
Redirecting a restore of DB2 data
Override default log file path on DB2 server for this job
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 the full path for the archive logs location. Selecting this option does not change the archive log path configuration on the DB2 server.
Bring database online when finished rolling forward
Check Bring database online when finished rolling forward to ensure that the database is brought online as soon as the recovery is finished.
10 Select other restore options from the Properties pane as appropriate, and then start the restore job. See Restoring data by setting job properties on page 498. 11 Run a full backup of the restored database. Related Topics: Setting application defaults for DB2 on page 1461 About troubleshooting DB2 on page 1467

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 2 Follow the instructions for restoring DB2 data in Restoring DB2 data on page 1462. After you select options on the Restore Job Properties dialog box for DB2, on the Properties pane, under Destination, click DB2 Redirection. 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.
1464
Server Server logon account Redirect to a new instance
Type the name of the server to which you want to redirect the restore job. Type a logon account that has rights to restore data to the server to which you want to redirect the restore job. 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 Instance logon account
Type the name of the instance to which you are redirecting the restore of the database. 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. Check Restore to a new database to redirect the restore of the database to a new database other than the source server. Type the name of the database to which you want to redirect the restore job. Type a drive to which you want to redirect the DB2 database. Specify the full path of the location where you want the log files for the new database to reside. 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.
Restore to a new database
Database name Drive to restore to Restore log location Redirect containers
1465
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
DMS tablespace container relative path
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.
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 1467
1466
About troubleshooting DB2

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.
1467
1468
Appendix
Symantec Backup Exec Agent for Enterprise Vault
The Symantec Backup Exec for Windows Servers Agent for Enterprise Vault (EV Agent) is installed as a separate, add-on component of Backup Exec for Windows Servers.
About the EV Agent

The EV Agent provides data protection for key Enterprise Vault components, such as the following:

Sites Servers Databases Indexes Vault partitions
The EV Agent can help provide a disaster recovery solution for data that is archived with Enterprise Vault. Recovery of the archived data is not dependent on the archive source, such as Exchange Server or a specific file system. The EV Agent lets you do the following:
Back up and restore Enterprise Vault archives from open or closed vault store partitions. Back up individual Enterprise Vault servers from within an Enterprise Vault site. Back up Enterprise Vault sites.
When you back up Enterprise Vault servers the following Enterprise Vault components can be backed up along with the vault partitions:
Enterprise Vault Directory and Monitoring databases

1469
About the EV Agent

Enterprise Vault vault store databases Enterprise Vault indexing files
Backup Exec backs up Enterprise Vault by placing the Enterprise Vault services in read-only mode. Read-only mode ensures that database, database index, and vault store synchronization remains while the backup job runs. As a result, Enterprise Vault does not archive new data while in read-only mode. After the backup job successfully completes, Backup Exec takes the Enterprise Vault services out of read-only mode so that archival operations can continue. When you back up specific Enterprise Vault components, other Enterprise Vault components are automatically backed up at the same time. Backup Exec includes these components to hasten an Enterprise Vault recovery.
Table Q-5 Automatically backed up Enterprise Vault components Backup Exec automatically backs up this: Description Directory database Backup Exec automatically backs up the Directory database that is associated with the Enterprise Vault site. After Backup Exec sequentially backs up all of the selected servers, it finishes the backup job by automatically backing up the Directory database. Backup Exec places the Directory database in a backup set that remains separate from the sets that contain the server components. Backup Exec automatically backs up the vault store database that is associated with the open partition.
When you back up this: Enterprise Vault site
Enterprise Vault server or servers
Directory database or databases
Open partition
Vault store database
1470
EV Agent notes
EV Agent notes
Review the following requirements and notes before you use the EV Agent:
You must create at least one partition on an Enterprise Vault server before the Enterprise Vault server can advertise itself to Backup Exec. The EV Agent uses the Remote Agent to back up all NTFS shares on a remote computer that contains Enterprise Vault data. However, if the Remote Agent is not installed, the EV Agent uses Microsofts Common Internet File System (CIFS) to back up the data. For a device or a filer that does not support the Remote Agent, the EV Agent uses CIFS to back up the data. Symantec recommends that you create separate backup jobs when you want to do NDMP backups of Enterprise Vault data. You may see a significant performance improvement of NDMP backups with the Symantec Backup Exec NDMP Option.
You can find a list of compatible operating systems, platforms, and applications at the following URL: http://entsupport.symantec.com/umi/V-269-1
About installing the EV Agent

The EV Agent is installed locally as a separate, add-on component of Backup Exec. You can install the EV Agent in the following ways:
Install it automatically from the Backup Exec CD as part of a Remote Agent installation to the local Enterprise Vault server. After you finish the installation, you may need to configure the EV Agent to publish itself to a media server of your choice. See Publishing the remote Windows computer to media servers on page 892. Push-install it to a remote Enterprise Vault server from an existing Backup Exec media server. When you push-install the EV Agent from a media server, the EV Agent automatically publishes itself to the media server from which it was installed.
Related Topics: Installing Backup Exec options to the local computer on page 75. Installing Backup Exec options to remote computers on page 82.
Appendix Q, Symantec Backup Exec Agent for Enterprise Vault
1471
About the EV Agent and the Backup Selections pane
About the EV Agent and the Backup Selections pane

Backup Exec presents a hierarchical view of Enterprise Vault resources in the Backup Selections pane. You can back up the current open and closed vault store partitions, Directory and Monitoring databases, and vault databases.
Enterprise Vault hierarchy (Backup Selections pane - View by Resource tab) All Resources Production_Server_1 Favorite Resources Domains User-Defined Selections Enterprise Vault Directory on TEST Directory DB (TEST/EnterpriseVaultDirectory) Monitoring DB (TEST/EnterpriseVaultMonitoring) EV Site1 EV Server1 Index Locations VaultStore1 All Partitions Open Partition Closed Partitions Vault Store DB (TEST/EVVaultStore1) EV Server2 Directory on Marketing_1 Enterprise Vault server Enterprise Vault installation Vault store database Open and closed partitions Enterprise Vault site Enterprise Vault server Enterprise Vault installation
Related Topics: Backing up an open partition on page 1475 Backing up an Enterprise Vault server on page 1481 Backing up an Enterprise Vault site on page 1482 About restoring Enterprise Vault on page 1485
1472
About selecting a backup method for Enterprise Vault backup jobs

You can select a backup method that depends on the type of Enterprise Vault backup job that you run. Use the following table as a guide.
Table Q-6 To back up: Directory and Monitoring databases Vault database Backup methods to use with Enterprise Vault backup jobs Select: Full backup method Full or differential backup method Description By default, Directory and Monitoring database backups always use the full backup method, irrespective of the method you select for the overall backup job. Vault database backups can use both the full and differential backup methods, but not the incremental backup method. Backup Exec uses the differential method instead of the incremental method when it backs up the vault database. Note There are no operational differences between the incremental and differential backup methods when you back up a vault database. Full, differential, You can use all of the backup methods that are available for Standard file standard file system backup jobs. system backup or incremental jobs that do not backup methods. include any Enterprise Vault databases Standard file system backup jobs that include a vault database Full, differential, You can use all of the backup methods that are available for or incremental standard file system backup jobs. However, vault database backup methods. backups can only use full and differential backup methods. Backup Exec uses the differential method instead of the incremental method when it backs up the vault database.
When you combine Enterprise Vault components in a backup job, each component may use a backup method that differs from what you selected for the overall job. For example, you create a job that uses the incremental backup method to back up both a Directory database and a partition. However, because a Directory database is small, it cannot be backed up using the incremental method. Instead, Backup Exec uses the full backup method to back up the directory database. This results in fast and easy restores. When the partition is backed up, Backup Exec continues to use the incremental backup method.
1473
Use the following table as a guide.

Table Q-7 Actual backup methods that are used for Enterprise Vault components Full (F) F F F F Differential (D) F D D D Incremental (I) F D I I
Enterprise Vault component Directory and Monitoring database Vault store database Partition Index root path
Related Topics: Understanding backup methods and their advantages on page 224
Setting a default backup method for Enterprise Vault backup jobs

You can set a default backup method that you can use for all Enterprise Vault backup jobs. In some cases, Backup Exec may override the default backup method when you run a backup job. See About selecting a backup method for Enterprise Vault backup jobs on page 1473. To set a default backup method for the Enterprise Vault backup jobs 1 2 3 On the Tools menu, click Options. In the Properties pane, under Job Defaults, click Enterprise Vault. Select an appropriate backup method. Your choices include Full, Incremental, or Differential. Click OK.
1474
Backing up an open partition
Backing up an open partition

When you back up an open partition, Backup Exec automatically backs up the partitions associated vault store database in the same backup job. Backup Exec includes vault store database to help maintain synchronization between the vault store database and the open partition if a recovery operation is required. Use the following steps to back up a vault store open partition. To back up an open partition 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand a Directory on <Computer_name> that contains the partition you want to back up. Expand an Enterprise Vault site that contains the server where the vault store partition that you want to back up resides. Expand the Enterprise Vault server that contains the partition that you want to back up. Expand a vault store that contains the partition that you want to back up. Expand All Partitions. Check Open Partitions. You must select the open partition that you want to back up from the backup selections pane. You cannot select the open partition from the results pane. Backup Exec automatically includes the open partitions associated vault store database in the backup job when you select an open partition for backup. 10 In the Properties pane, under Settings, click Enterprise Vault. 11 Select a backup method. See About selecting a backup method for Enterprise Vault backup jobs on page 1473. 12 In the Properties pane, select other backup options as needed.
7 8 9
1475
Backing up vault store closed partitions

See Scheduling jobs on page 286. Related Topics: About restoring Enterprise Vault on page 1485
Backing up vault store closed partitions

Use the following steps to back up vault store closed partitions. To back up vault store closed partitions 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand a Directory on <Computer name> where the partition that you want to back up resides. Expand an Enterprise Vault site that contains the server where the vault store partition that you want to back up resides. Expand the Enterprise Vault server that contains the partition that you want to back up. Expand a vault store that contains the closed partitions that you want to back up. Expand All Partitions. Double-click Closed Partitions.
7 8 9
10 In the results pane, select the partitions that you want to back up.
Backing up the Directory database
11 In the Properties pane, under Settings, click Enterprise Vault. 12 Select a backup method. See About selecting a backup method for Enterprise Vault backup jobs on page 1473. 13 In the Properties pane, select other backup options as needed. 14 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

Backing up the Directory database

Use the following steps to back up the Directory database. To back up the Directory database 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand a Directory on <computer name> that contains the Directory database that you want to back up. Click Directory DB (<SQLServer/instance>/EnterpriseVaultDirectory). In the Properties pane, select other backup options as needed. Do one of the following: To run the job now Click Run Now.
5 6 7
1477
Backing up the Monitoring database

Backing up the Monitoring database

Use the following steps to back up the Monitoring database. To back up the Monitoring database 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand a Directory on <computer name> that contains the Monitoring database that you want to back up. Click Monitoring DB (<SQLServer/instance>/EnterpriseVaultMonitoring). In the Properties pane, select other backup options as needed. Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

5 6 7
1478
Backing up a vault store database
Backing up a vault store database

Use the following steps to back up a vault store database. To back up a vault store database 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand a Directory on <Computer_name> that contains the vault store database that you want to back up. Expand the Enterprise Vault site that contains the vault store database that you want to back up. Expand the Enterprise Vault server that contains the vault store that you want to back up. Expand the vault store. Click Vault Store DB (<VaultStore_SQL_Server_name/instance>/<vault_store database_name>). In the Properties pane, under Settings, click Enterprise Vault.
7 8
10 Select a backup method. See About selecting a backup method for Enterprise Vault backup jobs on page 1473. 11 In the Properties pane, select other backup options as needed. 12 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

1479
Backing up a vault store
Backing up a vault store

When you back up a vault store, all closed partitions, the vault store database, and the vault stores open partition are backed up. To back up a vault store 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand an Enterprise Vault directory that contains the vault store that you want to back up. Expand the Enterprise Vault site that contains the vault store that you want to back up. Expand the Enterprise Vault server that contains the vault store that you want to back up. Select a vault store. In the Properties pane, under Settings, click Enterprise Vault. Select a backup method. See About selecting a backup method for Enterprise Vault backup jobs on page 1473. 10 In the Properties pane, select other backup options as needed. 11 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

7 8 9
Related Topics: Backing up an open partition on page 1475

Backing up an Enterprise Vault server
Backing up vault store closed partitions on page 1476
Backing up an Enterprise Vault server

When you back up an Enterprise Vault server, the following items are backed up:

Index locations Vault stores Vault store closed partitions Vault store open partition, if present Vault store databases
Backup Exec also does an automatic backup of the Directory database when you back up a server. To back up an Enterprise Vault server 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand an Enterprise Vault directory where the server that you want to back up resides. Expand an Enterprise Vault site Select an Enterprise Vault server. In the Properties pane, under Settings, click Enterprise Vault. Select a backup method. See About selecting a backup method for Enterprise Vault backup jobs on page 1473. 9 In the Properties pane, select other backup options as needed.
5 6 7 8
10 Do one of the following: To run the job now Click Run Now.
1481
Backing up an Enterprise Vault site

Backing up an Enterprise Vault site

When you back up an Enterprise Vault site, you back up all of the Enterprise Vault servers within the site. Backup Exec also does an automatic backup of the Directory database when you back up a site. To back up an Enterprise Vault site 1 2 3 4 5 6 7 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand an Enterprise Vault directory that contains the site that you want to back up. Select the Enterprise Vault site. In the Properties pane, under Settings, click Enterprise Vault. Select a backup method. See About selecting a backup method for Enterprise Vault backup jobs on page 1473. 8 9 In the Properties pane, select other backup options as needed. Do one of the following: To run the job now Click Run Now.
1482
Backing up index locations


Use the following steps to back up Enterprise Vault index locations. To back up index locations 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. In the Backup Selections pane, expand Enterprise Vault. Expand a Directory on <Computer name> that contains the index locations that you want to back up. Expand an Enterprise Vault site that contains the index locations that you want to back up. Expand the Enterprise Vault server that contains the index locations that you want to back up. Do one of the following: To back up all index locations To back up individual index locations
Check Index Locations. Do the following in the order listed:

Click the Index Locations icon. In the results pane, select the individual index locations that you want to back up.
1483
8 9
In the Properties pane, under Settings, click Enterprise Vault. Select a backup method. See About selecting a backup method for Enterprise Vault backup jobs on page 1473.
10 In the Properties pane, select other backup options as needed. 11 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

1484
About restoring Enterprise Vault

Review the following before you begin an Enterprise Vault restore.
When you restore an Enterprise Vault installation, you should restore the Directory database in a separate restore job. After you successfully restore the Directory database, you can restore other Enterprise Vault components and partitions. See Restoring the Directory database on page 1486. You can individually restore Enterprise Vault components such as the Directory and Monitoring databases, vault store databases, indexes, and partitions. Before you begin the restore, these components must exist on the destination Enterprise Vault server. If they do not exist, you must create them by using Enterprise Vault before you begin the restore job. Symantec recommends that you use the Enterprise Vault service account or an account with rights to access the restore selections as the default logon account. Otherwise, you may have to enter proper credentials for each Enterprise Vault resource that you select for restore. After you restore Enterprise Vault, you may need to run Enterprise Vault recovery tools. The recovery tools are used to re-synchronize Enterprise Vault with the newly restored databases after you complete the restore. See your Enterprise Vault documentation.
Before you restore Enterprise Vault sites, servers or other components, you should have the following items installed on the destination computer:

Enterprise Vault The Backup Exec Remote Agent for Windows Systems
Note You must install the Remote Agent on remote Enterprise Vault computers where you want to restore Enterprise Vault components. Related Topics: Restoring the Directory database on page 1486 Restoring an open partition on page 1489 Restoring an Enterprise Vault server to its original location on page 1493 Redirecting the restore of the Directory database to a different Microsoft SQL Server computer on page 1496 Redirecting an Enterprise Vault restore job on page 1494
1485
About automatic redirection of Enterprise Vault components under an Enterprise Vault server
You can move a vault store database or a partition to a new location that differs from where it was originally backed up. During restores of the vault store database or a partition, the EV Agent detects the location change. It then automatically redirects the restores of these components to the new location. Related Topics: Restoring the Directory database on page 1486 Restoring an open partition on page 1489 Restoring an Enterprise Vault server to its original location on page 1493 Redirecting the restore of the Directory database to a different Microsoft SQL Server computer on page 1496 Redirecting an Enterprise Vault restore job on page 1494
Restoring the Directory database

Use the following steps to restore the Enterprise Vault Directory database. You also can redirect the restore of the Directory database to a different Microsoft SQL Server computer. See Redirecting the restore of the Directory database to a different Microsoft SQL Server computer on page 1496. To restore the Enterprise Vault Directory database 1 Stop the Enterprise Vault Admin and Directory services on the Enterprise Vault computer where you want to restore the Directory database. If other Enterprise Vault servers connect to the Directory database, stop the Admin and Directory services on those computers too. 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the View by Resource pane, expand an Enterprise Vault installation that contains the Directory database that you want to restore. For example, expand Directory on <computer name>. 5
1486
Expand Directory DB (<SQL Server name>/<instance>/EnterpriseVaultDirectory).

6 7 8
Select the full backup set. In the Restore Job Properties pane, under Settings, click Enterprise Vault. If you did not stop the Enterprise Vault services that are mentioned in step 1, check
Force the restore of Directory and Monitoring databases.
This option takes the shared Directory and Monitoring databases offline, so Backup Exec can replace them during a restore job. This option results in Enterprise Vault Admin and Directory services on all related Enterprise Vault servers to drop the connection to the Directory database that you restore. It also drops the connection to the Monitoring database. When the restore job completes, you must manually restart the Enterprise Vault Admin and Directory services on your Enterprise Vault server. After you restart the services, the services reconnect to the restored databases and Enterprise Vault begins archival operations again. 9 In the Restore Job Properties pane, select other restore options as needed.

See Scheduling jobs on page 286. 11 After the restore successfully completes, restart all Directory and Admin services.
Restoring the Monitoring database

Use the following steps to restore the Monitoring database to its original location. To restore the Monitoring database 1 Stop the Enterprise Vault Admin and Directory services on the Enterprise Vault computer where you want to restore the Monitoring database. If other Enterprise Vault servers connect to the Monitoring database, stop the Admin and Directory services on those computers too.
1487
2 3 4 5
On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the View by Resource pane, expand All Resources. Expand an Enterprise Vault installation that contains the Directory database that you want to restore. For example, expand Directory on <computer name>.
6 7 8 9
Expand Monitoring DB (SQL Server name/EnterpriseVaultDirectory). Select the full backup set. In the Restore Job Properties pane, under Settings, click Enterprise Vault. If you did not stop the Enterprise Vault services that are mentioned in step 1, check
Force the restore of Directory and Monitoring databases.
This option takes the shared Directory and Monitoring databases offline, so Backup Exec can replace them during a restore job. This option results in Enterprise Vault Admin and Directory services on all related Enterprise Vault servers to drop the connection to the Directory database that you restore. It also drops the connection to the Monitoring database. When the restore job completes, you must manually restart the Enterprise Vault Admin and Directory services on your Enterprise Vault server. After you restart the services, the services reconnect to the restored databases and Enterprise Vault begins archival operations again. 10 In the Restore Job Properties pane, select other restore options as needed. 11 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

See Scheduling jobs on page 286. 12 After the restore successfully completes, restart all Directory and Admin services.
Restoring an open partition

When you restore an open partition, Backup Exec automatically restores the partitions associated vault store database in the same restore job. By including the vault store database, Backup Exec maintains synchronization between the two components. Note Restoring an open partition means that the partition that you select for restore is currently open on the destination Enterprise Vault server. After the restore completes, you must run the Enterprise Vault recovery tool. The recovery tool maintains synchronization between the vault store database and its associated closed partitions. See your Enterprise Vault documentation. To restore an open partition 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the Restore Job Properties pane, expand All Resources. Expand a Directory on <Computer_name> that contains the open partition that you want to restore. Expand an Enterprise Vault site that contains the server where the open partition that you want to restore resides. Expand the Enterprise Vault server that contains the open partition that you want to restore. Expand a vault store that contains the open partition that you want to restore. Expand Partitions. Expand a partition that contains the open partition that you want to restore.
7 8 9
10 Select the full backup set. 11 In the Restore Job Properties pane, select other restore options as needed. 12 Do one of the following: To run the job now Click Run Now.
Appendix Q, Symantec Backup Exec Agent for Enterprise Vault 1489

See Scheduling jobs on page 286. 13 After the restore successfully completes, run the Enterprise Vault recovery tool. See your Enterprise Vault documentation. Related Topics: Restoring an Enterprise Vault server to its original location on page 1493 Redirecting the restore of the Directory database to a different Microsoft SQL Server computer on page 1496 Redirecting an Enterprise Vault restore job on page 1494
Restoring a closed partition

After you successfully restore a closed partition, you must run the Enterprise Vault recovery tool. The Enterprise Vault recovery tool maintains synchronization between the vault store database and the restored closed partition. Note Restoring a closed partition means that the partition that you select for restore is currently closed on the destination Enterprise Vault server. To restore a closed partition 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the Restore Job Properties pane, expand All Resources. Expand a Directory on <Computer_name> that contains the closed partition that you want to restore. Expand an Enterprise Vault site that contains the server where the closed partition that you want to restore resides.
1490
Expand the Enterprise Vault server that contains the closed partition that you want to restore. Expand a vault store that contains the closed partition that you want to restore. Expand Partitions. Expand a partition that contains the closed partition that you want to restore.
7 8 9
10 Select the full backup set. 11 In the Restore Job Properties pane, select other restore options as needed. 12 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

See Scheduling jobs on page 286. 13 After the restore successfully completes, run the Enterprise Vault recovery tool. See your Enterprise Vault documentation.
Restoring a vault store database

Use the following steps to restore a vault store database. To restore a vault store database 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the View by Resource pane, expand a Directory on <computer name> that contains the vault store database that you want to restore. Expand an Enterprise Vault site that contains the vault store database that you want to restore.
1491
Expand an Enterprise Vault server that contains the vault store database that you want to restore. Expand the vault store. Expand Vault Store DB (<SQL_Server_name>/<instance>/EVAVaultStore). Select the full backup set. In the Restore Job Properties pane, select other restore options as needed.
6 7 8 9

Restoring index locations

Use the following steps to restore index locations. To restore index locations 1 2 3 4 5 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the View by Resource pane, expand All Resources. Expand Enterprise Vault. Expand a Directory on <Computer name> that contains the index locations that you want to restore. Expand an Enterprise Vault site that contains the index locations that you want to restore.
1492
Expand the Enterprise Vault server that contains the index locations that you want to restore Expand Index Locations. Expand the path that contains the index locations that you want to restore.
8 9
10 Select the full backup set that contains the index locations that you want to restore. 11 In the Restore Job Properties pane, select other restore options as needed. 12 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

See Scheduling jobs on page 286
Restoring an Enterprise Vault server to its original location

Use the following steps to restore an Enterprise Vault server to its original location. You also can redirect the restore of the server to a different computer. See Redirecting an Enterprise Vault restore job on page 1494. To restore an Enterprise Vault server to its original location 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the Restore Job Properties pane, expand All Resources. Expand a Directory on <Computer_name> that contains the server that you want to restore Expand an Enterprise Vault site that contains the server that you want to restore. Expand an Enterprise Vault server.
5 6
1493
7 8 9
Expand the vault store. Expand Partitions. Expand each partition.
10 Select the backup sets for each partition. 11 Do one of the following: To run the job now Click Run Now. To schedule the job Do the following in the order listed: to run later

See Scheduling jobs on page 286. 12 After the restore successfully completes, restart all Directory and Admin services. Related Topics: Redirecting the restore of the Directory database to a different Microsoft SQL Server computer on page 1496 Redirecting an Enterprise Vault restore job on page 1494
Redirecting an Enterprise Vault restore job

Use the following steps to redirect an Enterprise Vault restore job. You also can restore the Directory database to a different Microsoft SQL Server computer. See Redirecting the restore of the Directory database to a different Microsoft SQL Server computer on page 1496. To redirect an Enterprise Vault restore job 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. In the Restore Job Properties pane, expand All Resources.
1494
Navigate to and select the Enterprise Vault components that you want to redirect during restore. In the Restore Job Properties pane, under Destination, click Enterprise Vault
Redirection.

If you want to redirect Enterprise Vault to a different computer Do the following in the order listed:

Check Redirect Enterprise Vault to server. In the server field, enter the name of the Enterprise Vault server to which you want to restore. Use the following format: \\servername.
If you want to redirect the Do the following in the order listed: Monitoring database Check Redirect to a new Microsoft SQL server.
In the server field, type the name of the Enterprise Vault server to which you want to restore. Use the following format: \\servername. Check Instance to redirect the restore to a named SQL instance, and then type the instance name. If you want to restore to the default instance, leave the field empty.
If you want to redirect Index root paths

Check Restore index root to a new location. In the Path field, type an alternate path. Use a UNC path if the alternate path is on a different server. You can specify an alternate path on the destination server. You also can redirect the index root location to an alternate path on the original server.

Use the default logon account as indicated. Click Change to select a different one
8 9
In the Restore Job Properties pane, select other restore options as needed. Do one of the following: To run the job now Click Run Now.
1495

Redirecting the restore of the Directory database to a different Microsoft SQL Server computer
Use the following steps to redirect the restore of the Enterprise Vault Directory database to a different Microsoft SQL Server computer. To redirect the restore of the Directory database to a different Microsoft SQL server computer 1 2 3 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Navigate to and select the Enterprise Vault Directory database that you want to restore. In the Properties pane, under Destination, click Enterprise Vault Redirection. Check Redirect to a new Microsoft SQL server. In the server field, type the name of the SQL Server name to which you want to restore. Use the following format: \\servername. 7 Check Instance to redirect the restore to a named SQL instance and then type the instance name. If you want to restore to the default instance, leave the field empty. In the Restore Job Properties pane, select other restore options as needed. Do one of the following: To run the job now Click Run Now.
4 5 6
8 9
1496

After the restore job completes, you must configure Enterprise Vault to use the new name of the SQL database server. 10 At each Enterprise Vault server, use Enterprise Vault to change the name of the previous SQL Server computer. Change the name to the name of the SQL Server computer that now holds the Directory database. See your Enterprise Vault documentation. 11 Restart the Enterprise Vault Admin service on all Enterprise Vault servers that use the Directory database. Two Directory names appear in the backup selections view after you restart the Enterprise Vault Admin service on the Enterprise Vault server. For example, Directory on <OldSQL_computer_name> and Directory on <NewSQL_computer_name>). 12 In Backup Exec, on the navigation bar, click the arrow next to Backup. 13 Click New Backup Job. 14 Expand Enterprise Vault. 15 Expand Directory on <SQL server computer where you moved the Directory database>. 16 Expand all items under Directory on <SQL server computer where you moved the Directory database>. The Directory and Monitoring databases, along with the Enterprise Vault sites, should appear. In addition, the Directory database should display the new SQL Server name and instance where it was redirected. When you configure a new Directory database backup job, you must select the Directory database from the current Directory server. Backup Exec automatically removes the previous Directory server name 13 days after you complete the Directory database move. 17 To manually remove the previous server name, right-click the server name. 18 Click Delete.
Appendix Q, Symantec Backup Exec Agent for Enterprise Vault 1497
1498
Appendix
Symantec Backup Exec Intelligent Disaster Recovery Option

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. 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. 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 servers hard drive, but Symantec recommends that you specify an alternate data path to store another copy of the *.dr file in case the media servers 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.
1499
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 1503 About creating and updating recovery media on page 1507
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. 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.
Encryption key files for all hard drives that you encrypt with Windows BitLocker Drive Encryption (Windows Vista and Windows Server 2008 only). 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 1508 Using an evaluation version of the IDR option on page 1501
1500
Installing the IDR 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 75 Installing Backup Exec options to remote computers on page 82 Installing the Remote Agent for Windows Systems on page 88 Getting started with IDR on page 1503
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.
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option
1501
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 the following: 1 Using the IDR Configuration Wizard to determine the alternate location where a copy of the *.dr file will be stored. Performing full backup jobs on the computers to be protected. Creating the bootable recovery media using the IDR Preparation Wizard.
2 3
Use the Configuration Wizard to set the alternate data path.
Tape
Do you want to create bootable tape or CD?
CD-ROM
Run the IDR Prep Wizard to create a tape image. Run a full backup Run an overwrite backup job.
Run the IDR Prep Wizard to create the bootable CD. Run the IDR Prep Wizard again to copy.dr files to diskette.
Run the IDR Prep Wizard again to update a diskette.
You can create the following 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)
1502
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 following table to decide which type of media to use.
Table R-1 Type of Media CD-R, CD-RW Bootable media comparison chart Advantages
Disadvantages
Can also be used to protect remote Windows computers on the network. Can create bootable CD images for remote computers. Requires less preparation and recovery time than diskettes Does not required a CD burner.
Requires a BIOS that supports booting from a CD. Requires a CD burner.
Bootable tape
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 the following:
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.
1503
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 servers hard drive, which is: C:\Program Files\Symantec\Backup Exec\idr\Data\<computer name>.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. When using Backup Execs Remote Administrator, specifying drive A: as the Alternate Data Path points to the media servers floppy disk drive. The remote computers 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.
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 1507 to continue disaster recovery preparation.
Related Topics: About recovering a computer and using the Disaster Recovery Wizard on page 1522 About creating and updating recovery media on page 1507 Creating a bootable tape image on page 1512 Backing up data on page 263
Manually setting data paths for the *.dr files

If you did not use the IDR Configuration Wizard to set an alternate data path for the *.dr files, you can set it manually.
1504
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 servers hard drive, which is C:\Program Files\Symantec\Backup Exec\IDR\Data\<computer name>.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 2 3 From the Tools menu, click Options. Under Settings, click Intelligent Disaster Recovery. 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 servers hard drive, which is C:\Program Files\Symantec\Backup Exec\IDR\Data\<computer name>.dr.
1505
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 servers hard drive is unavailable. To use a remote computers hard drive as the alternate data path, establish a valid connection to the remote computer. Specify a UNC path as the alternate path, and then check the directory 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 Execs Remote Administrator, specifying drive A: as the Alternate Data Path points to the media servers floppy disk drive. The remote computers 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.
1506
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 1512 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. Note For the local media server, update the bootable media after every successful full backup, or whenever you patch or upgrade your operating system software. Symantec also recommends that you update the bootable media when you reconfigure or update your storage drivers or network drivers. 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 contains 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 protected. Prepare and test bootable media before a disaster to make sure that the media was prepared correctly. See About recovering a computer and using the Disaster Recovery Wizard on page 1522. The bootable media also contains a text file called <computer name>-diskconf.txt, which contains information about the computers hard disk layout. Related Topics: Creating a bootable CD image on page 1510
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option 1507
Creating a bootable tape image on page 1512 Creating the Intelligent Disaster Recovery nonbootable CD image only on page 1513
Requirements for running the IDR Preparation Wizard

Before you run 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, do the following:
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. For Windows 2000/XP back up System State. For Windows Server 2003, back up Shadow Copy components. If utility partitions are present on the computer, select them for backup. See Utility Partition on page 234. Do not include or exclude files from the backup using the Advanced File Selection feature. Ensure 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, appears. If you install Backup Exec into an existing SQL instance, Symantec recommends that you periodically back up the SQL system databases using the optional SQL Agent.
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 manufacturers 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 manufacturers bootable CD in order to install the required RAID drivers.
1508
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 1507 Requirements for running the IDR Preparation Wizard on page 1508 Preparing IDR media by using other media servers on page 1518 Creating a bootable CD image on page 1510 Creating a bootable tape image on page 1512 Creating the Intelligent Disaster Recovery nonbootable CD image only on page 1513 Copying the disaster recovery files to a diskette on page 1516
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. 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 1510 Creating a bootable tape image on page 1512 Creating the Intelligent Disaster Recovery nonbootable CD image only on page 1513 Updating bootable media on page 1515.
Appendix R, Symantec Backup Exec Intelligent Disaster Recovery Option 1509
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 1508, 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.
To create a bootable CD image 1 Verify that the computer to be protected has been backed up using the full backup method. 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 On the Welcome screen, click Next. Click Choose a media server that has the IDR option installed. See Preparing IDR media by using other media servers on page 1518.
On the Create IDR Boot Media screen, under Create, select Bootable CD Image for use with CD Writers (ISO 9660) and then click Next. On the Starting CD Image Creation screen, click Next.
5
1510
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. 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. Click Next. 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.
8 9
10 Click Next. 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 If the files are stored on a network or the local computers hard drive If an .ISO image for operating system CD is available Type the CD drive letter. Type the path to files.
Specify the path to that image.
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.
1511
Related Topics: About recovering a computer and using the Disaster Recovery Wizard on page 1522 Creating the Intelligent Disaster Recovery nonbootable CD image only on page 1513
Creating a bootable tape 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. 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 manufacturers 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 1508. 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 On the Welcome screen, click Next. Click Choose a media server that has the IDR option installed. See Preparing IDR media by using other media servers on page 1518.
1512
Under Create, select Bootable Tape Image for use with bootable tape devices, and then click Next. Read the Starting Tape Image Creation screen, and then click Next. Type a path to store the bootable image until you perform a full backup, or click Browse to navigate to a storage location. Click Next. Type a path to the location of the Windows operating system files, or click Browse to navigate to the location. Click Next. When the bootable tape image has completed, click Next.
4 5
6 7
8 9
10 To view the computers 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 1515 About recovering a computer and using the Disaster Recovery Wizard on page 1522
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.
1513
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 To use another computer to create the Intelligent Disaster Recovery nonbootable CD image On the Welcome screen, click Next. Click Choose a media server that has the IDR option installed. See Preparing IDR media by using other media servers on page 1518.
3 4 5
Under Create, click Nonbootable disaster recovery CD Image and then click Next. On the Starting nonbootable CD Image Creation screen, click Next. Type a path to a storage location for the nonbootable CD image, or click Browse to navigate to a storage location. Click Next. The wizard begins creating the nonbootable image.
7 8 9
When the nonbootable CD image is complete, click Next. Click Finish. 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 263
1514
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

If you initially created a bootable image on CD and then you change the media servers 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 1510.
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 On the Welcome screen, click Next. update the bootable tape image To use another computer Click Choose a media server that has the IDR option installed. to update the bootable See Preparing IDR media by using other media servers on tape image page 1518.
The Create IDR Boot Media screen appears. 3 Under Create, click Bootable Tape Image for use with bootable tape devices, and then click Next.
1515
Copying the disaster recovery files to a diskette
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. Continue to follow the prompts until the wizard is complete. When the bootable image is complete, run an overwrite backup job so that the image is written to the tape.
5 6
Related Topics: About recovering a computer and using the Disaster Recovery Wizard on page 1522 Backing up data on page 263

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:
Ensure that full backups of each hard disk volume (C:, D:, etc.) were made. The *.dr files are not created or updated if you back up only individual directories. In addition, do the following:

For Windows 2000/XP, back up System State. For Windows Server 2003, back up the Shadow Copy and System State components.
If utility partitions are present on the computer, select them for backup.
1516
See Utility Partition on page 234.
Do not include or exclude files from the backup using the Advanced File Selection feature.
On the Tools menu, click Wizards> Intelligent Disaster Recovery Preparation Wizard. 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.

To use this computer to On the Welcome screen, click Next. copy the disaster recovery information files To use another computer On the Welcome screen, click Choose a media server that has the to copy the disaster IDR option installed. recovery information files See Preparing IDR media by using other media servers on page 1518.
Under Copy, click Disaster recovery information (.dr) file to a diskette, and then click
Next.
Select the computer or computers for which you want to update the disaster recovery information, and then click Next. 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.
Remove the diskette from the drive and store it with the computers disaster recovery media.
Related Topics: Preparing IDR media by using other media servers on page 1518
1517
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. To perform disaster recovery preparations on a different media server 1 2 On the Tools menu, click Wizards> Intelligent Disaster Recovery Preparation Wizard. On the IDR Preparation Wizard Welcome screen, click Choose a media server that has the IDR option installed, and then click Next. Click Browse to browse the network and select a media server that has the IDR option installed. Enter the credentials required to access the media server.
Media Server name User name Password Domain The name of the remote media server that is selected to run the restore job. The user name with administrator rights to the remote media server. The password required for access. The domain in which the remote media server is a member. If the media server is in a workgroup, leave this field blank.
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 1522 Performing an automated restore by using the Disaster Recovery wizard on page 1523 Performing a manual restore by using the Disaster Recovery Wizard on page 1531
1518
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: 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 1520. 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 1521. 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 1522.
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.
1519
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.
Related Topics: About changing hardware in the computer to be recovered on page 1520 About recovering a computer and using the Disaster Recovery Wizard on page 1522
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 computers main system board fails, you can restore the computers 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 manufacturers 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 1522
About encrypted backup sets and the Disaster Recovery Wizard on page 1522 Performing a manual restore by using the Disaster Recovery Wizard on page 1531
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 servers 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 1522
1521
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 computers 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 1531. 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. The media set that contains the full backup of the target computer being restored. If you want to recover a local computer, a storage device must be connected to the computer 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.
To restore data by using the Disaster Recovery Wizard, the following items are required:

Related Topics: Performing an automated restore by using the Disaster Recovery wizard on page 1523 Performing a manual restore by using the Disaster Recovery Wizard on page 1531
About encrypted backup sets and the Disaster Recovery Wizard

The Disaster Recovery Wizard supports the recovery of computers with previously encrypted backup sets.
1522
When you use the Disaster Recovery Wizards 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 The Disaster Recovery Wizard automatically retrieves the encryption keys. The Disaster Recovery Wizard prompts you to enter the pass phrase.
When you use the Disaster Recovery Wizards 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 Administrators Guide.
Performing an automated restore by using the Disaster Recovery wizard

Use the following steps to perform 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. After reading the IDR boot screen, press Enter. In the initial Symantec Intelligent Disaster Recovery panel, click Automated Recovery, and then click Next. If the Disaster Recovery Wizard fails to run and returns you to the initial IDR Recovery screen, click Start> View Log File. Use this log file when you contact Symantec technical support. 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. 4 Select the *.dr file for the computer that you want to recover, and then click Next.
1523
2 3
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. 5 If the *.dr file does not appear, copy the *.dr file from the alternate location to a diskette. Insert the diskette into drive A, and then click Browse to find the *.dr file. 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. After installing the network drivers, click Browse to find the file. For more information, see Installing network drivers on page 1530. If the evaluation period has expired, enter a valid license key after you select a *.dr file. 9 In the Hard Disks Layouts panel, do one of the following:
To use the current hard disk layout To restore the original hard disk layout (These steps pertain to Windows 2000/Vista/Server 2008 only) Click Keep current layout, and then click Next. Click Restore original layout, and then click Next.
6 7

If BitLocker Drive Do the following in the order listed: Encryption is enabled on Click Unlock. any of the existing hard In the BitLocker Drive Recovery panel, select the file that drives to which you are contains the encryption key, or enter the recovery password. recovering Click Next. If BitLocker Drive Go to step 11. Encryption is not enabled
11 In the Restore Hard Disk Layout panel, click Next.
1524
12 In the Modify Hard Disk Layout panel, do one of the following:

To use the original configuration from the *.dr file To make additional changes to the partition information Click Next.

Click Run Disk Management. Modify the disk layout. Click Next. For more information on the Windows Disk Management program and fault tolerant configurations, see your Windows documentation. See About altering hard drive partition sizes on page 1531.
If a *.dr file does not exist Do the following in the order listed: for the computer being Click Run Disk Management. recovered Modify the partition layout.
Click Next.
13 Select one of the following methods to access the storage device.

Use locally attached media device 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. See Restoring from a locally-attached media device on page 1526. Install networking, and Select this option if your backup-to-disk folders are located on then restore from remote remote computers. backup-to-disk folders See Restoring from remote backup-to-disk folders on page 1527. Install networking and then restore from a remote media server Select this option if you want to submit the restore jobs from remote media servers. SeeRestoring from a remote media server on page 1529.
Related Topics:
Restoring from a locally-attached media device on page 1526 Restoring from remote backup-to-disk folders on page 1527 Restoring from a remote media server on page 1529
1525
Restoring from a locally-attached media device

Use the following steps to restore 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. 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 1531. 3 Do one of the following:
If you are restoring from a stand-alone tape drive, insert the correct media and then click Next. 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 6 Click Next. 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. Click Next. 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.
7 8
1526
No
The Disaster Recovery Wizard updates the hard disk drivers and then finishes the recovery process.
On the You have completed the Disaster Recovery Wizard screen, you can run the following:
Run CMD.exe Edit Boot.ini The Disaster Recovery Wizard lets you open a command window that you can use to make further modifications to your computer. 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. (Windows 2000/XP/2003 only) Click the Messages button to review messages that were generated by the Disaster Recovery Wizard during the recovery process.
Messages
10 Click Finish. Remove the CD after the computer restarts but before the start process finds the startup CD drive. 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. Related Topics: About changing hardware in the computer to be recovered on page 1520
Restoring from remote backup-to-disk folders

Use the following steps to restore 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.
Click Next. The Disaster Recovery Wizard attempts to detect and install the correct network drivers.
After networking is installed, click Next.
1527
The Disaster Recovery Wizard attempts to detect the remote backup-to-disk folders. After it finds them, a Connect to <computer_name> screen appears, prompting you for access credentials to the remote computer where the backup-to-disk folders reside. 4 5 Enter the credentials that are required to access the remote computer. 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 8 Click Next. On the Insert Media into Restore Device screen, select the backup-to-disk folder that contains the required media that you want to restore. Click Next.
10 When the automated restore process finishes, click the appropriate response.
Yes No The Disaster Recovery Wizard prompts you to select another media set from which to continue the restore process. 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 Edit Boot.ini The Disaster Recovery Wizard lets you open a command window that you can use to make further modifications to your computer. 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. Click the Messages button to review messages generated by the Disaster Recovery Wizard during the recovery process.
Messages
12 Click Finish. Remove the CD after the computer restarts but before the start process finds the startup CD drive.
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

Use the following steps to restore 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. Click Next. The Disaster Recovery Wizard attempts to detect and install the correct network drivers. 3 4 After networking is installed, click Next. On the Connect to Media Server screen, enter the credentials that are required to access the media server.
Server Name Domain User Name Password The name of the remote media server that you selected to run the restore job. The domain in which the remote media server is a member. The user name that has administrator rights to the remote media server. The password that is required for access.
Click Next. On the Restore Data screen, all backup sets that are required to fully restore the computer are checked by default.
6 7
Click Next. 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.
1529
No
The Disaster Recovery Wizard updates the hard disk drivers and then finishes the recovery process.
On the You have completed the Disaster Recovery Wizard screen, you can run the following:
Run CMD.exe Edit Boot.ini The Disaster Recovery Wizard lets you open a command window that you can use to make further modifications to your computer. 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. (Windows 2000/XP/2003 only) Click the Messages button to review messages generated by the Disaster Recovery Wizard during the recovery process.
Messages
Click Finish. Remove the CD after the computer restarts but before the start process finds the startup CD drive. 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.
Installing network drivers

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 2 Click Install Network. 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 1523 Performing a manual restore by using the Disaster Recovery Wizard on page 1531
1530
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 1520
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.
1531
Place the bootable IDR CD in the CD drive of the computer to be recovered and then start the computer. After you read the IDR boot screen, press Enter. In the initial Symantec Intelligent Disaster Recovery panel, click Manual Recovery, and then click Next. If the Disaster Recovery Wizard fails to run returns you to the initial IDR Recovery panel, click Start > View Log File. Use this log file when you contact Symantec technical support. 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 drivers or RAID drivers are not found, click the Have Disk icon to install the required drivers, and then click OK.
2 3

If BitLocker Drive Do the following in the order listed: Encryption is enabled on Click Unlock. any of the existing hard In the BitLocker Drive Recovery panel, select the file that drives to which you are contains the encryption key, or enter the recovery password. recovering Click Next. If BitLocker Drive Go to step 5. Encryption is not enabled
5 6
On the Modify Hard Disk Layout screen, click Run Disk Management. Recreate the hard disk partition layout to match the computers original partition layout. After you create the hard disk partition layout, click Next. Select one of the following methods to access the storage device.
Use locally attached media device 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. See Restoring from a locally-attached media device on page 1526.
7 8
1532
Install networking, and Select this option if your backup-to-disk folders are located on then restore from remote remote computers. backup-to-disk folders See Restoring from remote backup-to-disk folders on page 1527. Install networking and then restore from a remote media server Select this option if you want to submit the restore jobs from remote media servers. See Restoring from a remote media server on page 1529.
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:
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 Click Skip Media To skip the restoration of this backup set and search the media for another backup set from which to restore. To eject the media and replace it with different media.
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 1520
1533
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 1323 Symantec Backup Exec Advanced Disk-based Backup Option on page 831
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.
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.
1534
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 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.
1535
Best Practices for IDR
Best Practices for IDR

The following table presents best practices when using IDR
.
Table R-2 Item Remote IDR
Best practices for IDR Description 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. 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.
Disaster Recovery
1536
Appendix
Symantec Backup Exec Library Expansion Option

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 355 Configuring multi-drive robotic libraries on page 1538
1537
Setting up robotic library hardware

Before installing Backup Exec, make sure that the robotic library hardware is configured properly as follows:
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.
You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2
Configuring multi-drive robotic libraries

Configuring Backup Exec to work with multiple drive robotic libraries is accomplished by making associations between the robotic librarys 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 drives 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). 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.
1538
Installing the Library Expansion Option
In the following example, if your robotic library has two drives, the drive with the lowest drive element address should be assigned the lower SCSI ID
Table S-1 Example configuration for a multi-drive robotic library SCSI ID 4 5 6 Drive Element Address N/A 00008000 00008001
Data Transfer Element (Storage Devices) Robotic Arm Storage Device 0 Storage Device 1
See Bar code rules in mixed media libraries on page 193
Installing the Library Expansion Option

Backup Execs optional Library Expansion Option installation requires the following:
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 Execs Library Expansion Option installation copies all necessary robotic library-related files including the software needed to control the robotic arm and storage devices. See Installing Backup Exec options to the local computer on page 75.
Appendix S, Symantec Backup Exec Library Expansion Option
1539
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. The Configure Library Drives dialog box shows how the devices appear to Backup Exec.
1540
Starting Backup Exec after installing the Library Expansion Option Detected hardware dialog box
Robotic library Devices in the robotic library
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 1538 Using the Getting Started with Backup Exec page on page 127 Viewing a devices configuration properties on page 346
Viewing robotic libraries

The following is an example of how robotic libraries are depicted when Devices is selected from the navigation bar:
1541
Starting Backup Exec after installing the Library Expansion Option 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.
Robotic library properties for Library|Configuration tab
After completing the configuration of your robotic library, perform an Inventory operation to update the Backup Exec media database.
1542
Related Topics: Inventorying media on page 368
1543
1544
Appendix
Symantec Backup Exec SAN Shared Storage Option

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.
1545
Example of the SAN Shared Storage Option using FC-SW
Workstation LAN Server A Databas e Server B Server C
Fibre Channel Switched Fabric Fibre-to-SCSI Bridge
SCSI Tape
SCSI Tape
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. 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 1558 Scheduling and viewing jobs in a SAN SSO environment on page 1557 Requirements for the SAN Shared Storage Option on page 1547
1546
Requirements for the SAN Shared Storage Option
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/2003/2008 must be installed. You cannot use SAN SSO with the Windows Server Core installation option of Windows Server 2008. 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. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2 All hardware drivers must be up to date and started. You can find a list of compatible drivers at the following URL: http://entsupport.symantec.com/rd/bews-drivers.htm The primary server must have enough space for the catalogs of all the servers in the SAN. 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).
For a fibre channel-connected installation, note the following additional requirements:
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.
Appendix T, Symantec Backup Exec SAN Shared Storage Option
1547
Installing the SAN Shared Storage Option
Related Topics: Installing the SAN Shared Storage Option on page 1548
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. See Installing Backup Exec to a local computer on page 71. If you have already installed Backup Exec, you can install additional options. See Installing Backup Exec options to the local computer on page 75. 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. See Uninstalling Backup Exec on page 115.
1548
About devices in the shared storage environment
Related Topics: Starting Backup Exec on page 126 Scheduling and viewing jobs in a SAN SSO environment on page 1557 Best practices for SAN SSO on page 1566 About enabling a SQL instance behind a firewall on page 330

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, use the 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 Configuring multi-drive robotic libraries on page 1538. If you need to add a new device to the SAN after you install Backup Exec, follow your storage network vendors 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 vendors instructions because some vendors do not support booting multiple servers concurrently or booting any server while active jobs are running. Backup Execs 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.
1549
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 1551 Using device operations with the SAN Shared Storage Option on page 1552
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. You can view drive properties for shared devices. See Viewing storage device properties on page 343. 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 645 Viewing a devices configuration properties on page 346
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. See Viewing media in storage devices on page 212.
Related Topics: Using drive pools with the SAN Shared Storage Option on page 1551 Using device operations with the SAN Shared Storage Option on page 1552 Scheduling and viewing jobs in a SAN SSO environment on page 1557
Using drive pools with the SAN Shared Storage Option

When Backup Exec is installed, the All Drives (<Server Name>) is created by default. In a non-shared storage environment, this default drive pool contains the servers 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. See Creating device pools on page 412. 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 Bs 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.
1551
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: Scheduling and viewing jobs in a SAN SSO environment on page 1557 About devices in the shared storage environment on page 1549 Sharing media on page 1558
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 354
1552
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: Library sharing prerequisites on page 1553 Configuring media servers for robotic library sharing on page 1554
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.
1553
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. On the navigation bar, click Devices. The tree pane contains a list of any fibre-attached or locally-attached devices. 3 4 5 Select the robotic library you want to share. Under Robotic Library Tasks in the task pane, select Configure partitions. Set up your partitions. See Creating robotic library partitions on page 363. 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. Delete the drive to ensure no jobs run to the unused partition.
7
1554
8 9
Repeat steps 6 and 7 for all drives in the unused partition. Reboot all other Windows servers and make sure you can see the shared robotic library on each server. 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, do the following in the order listed:

Click Drives. Click Partitions. Right-click the partition you want to delete, and click Delete. When prompted, click OK.
To delete a partition from the Administration Console for NetWare, do the following in the order listed:

Select Drives. Select Partitions. Select the partition you want to delete, and press DEL. When prompted, press Y.
Create the partitions in the shared library to be used by Backup Exec for NetWare Servers. To create a partition from the Administration Console, do the following in the order listed:

From the Administration Console, click Drives. Right-click Partitions. Click New Partition.
1555

Enter options on the New Partition dialog box. Click OK.
4 5 6
Enter options in the New Partition General dialog box. Enter options in the New Partition Configuration dialog box. Click OK. To create a partition from the Administration Console for NetWare, do the following in the order listed:

From the Administration Console for NetWare, select Drives. Select Partitions. Press INS. Select a drive to be included in this partition. Ensure Configuration is selected, and press ENTER to view or edit options on the Configuration dialog box. Press F2 to return to the General dialog box. Select Advanced Configuration and then press ENTER to view or edit options on the Advanced Configuration dialog box. Press F2 to return to the General dialog box. Press F2.
If you plan to share more than one library, repeat step 2 and step 3 for each library that will be shared. Restart Backup Exec for NetWare Servers on the group servers and make sure you can see the shared library on each server.
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 3 Select Drives. Select Drive Pools.
1556
4 5
Select All Drives. 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 7 8
Select Configuration. Enter the starting slot and number of slots to be used by NetWare servers. From the Administration Console, click OK. From the Administration Console for NetWare, press F2.
Restart Backup Exec for NetWare Servers on the group servers and make sure you can see the shared library on each server.
Related Topics: Viewing robotic libraries on page 1541
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.
Appendix T, Symantec Backup Exec SAN Shared Storage Option 1557
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: Viewing and changing completed jobs on page 465
Sharing media
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.
1558
Designating a new database server and setting up servers
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 196
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 1557

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 the following reasons:

A newer, faster server has become available. The database server has stopped functioning.
1559
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 servers 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. 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.
1560
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. Use BEUtility to create a media server group that contains all the servers you added in step 1. 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. 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. 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.
1561
Use BEUtility to restore the database you copied in step 6. Be sure to select the Drop existing database and reload from backup option. Use BEUtility to start the Backup Exec services on all the media servers in the media server group.
Related Topics: Getting started with IDR on page 1503 Restoring data by setting job properties on page 498
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. See Starting and stopping Backup Exec services on page 114.
Reconfiguring the SAN SSO Environment

You can change the primary server to which a secondary server is assigned. First, you must make the secondary server into a stand-alone server. Otherwise, all of the SAN SSO device configuration data migrates to the primary server database. When you configure a stand-alone server as a SAN SSO secondary server, the Backup Exec database creates a new data partition on the primary server. Initially, the partition is empty and data from previous server operations is lost. When the ADAMM service restarts, the standard device discovery process rediscovers the physical devices that are attached to the server. However, you cannot recover original backup-to-disk specifications. You must recreate the backup-to-disk folder and enter the original path where the folder resides. You must then run an inventory job to discover the backup-to-disk media. Before you can restore data, catalog the media. To reconfigure the management of a secondary server 1 2 Use BEUtility to convert the secondary server to a stand-alone server. Use BEUtility to set the primary SAN SSO server.
1562
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 vendors documentation. Related Topics: Checklist for troubleshooting devices that have gone offline on page 1563
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. You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2 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, you may need to troubleshoot the device. See SAN hardware tips on page 1564. 3 4 For robotic libraries, verify that robotic library support is installed. 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 1564. You may need to contact your hardware vendor.
1563
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, do the following in the order listed:

On the navigation bar, click Devices. Select the library, and then under Robotic Library Tasks, click Initialize.
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. 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. 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. 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 1565
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 2 3 Verify that the proper device drivers were installed. Verify that the fibre cable is securely connected to the HBA and the switch. 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.
1564
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. Reset the SAN, which may identify problem hardware components and may resolve fibre problems.
Resetting the SAN

Resetting the SAN involved powering down the components of the SAN, and then powering them on in a specific order. 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 3 4 5 6 7 Power on the library. After the library initialization is complete, power on the bridge. Verify that the switch recognizes the library. Power on the primary SSO server. Verify that the operating system recognizes the library and drives. 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.
1565
Best practices for SAN SSO
To bring a device online after an unsafe device removal event 1 2 Verify that no Backup Exec jobs are running in the SAN. 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. If the library is offline or if the drives are offline after initialization, stop all Backup Exec services and then restart them. If the device is not online, you may need to troubleshoot the device. See SAN hardware tips on page 1564.

Review the following recommendations 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 vendors 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.
1566
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. You must manually refresh Backup Exec administration consoles in a SAN SSO configuration if a member server updates the database. To manually refresh the user interface, right-click the proper component, and then press F5.
1567
1568
Appendix
Symantec Backup Exec NDMP Option

The Symantec Backup Exec for Windows Servers NDMP Option uses the Network Data Management Protocol (NDMP) to back up and restore 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 cannot share a storage device. Duplicating NDMP backup sets is not supported. Related Topics: Requirements for using the NDMP Option on page 1569 About installing the NDMP Option on page 1570
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/Server 2008. Backup Exec for Windows Servers 12 and later. An NDMP server with the Network Data Management Protocol enabled. A supported storage device that is attached to an NDMP server.
In addition, you must have the following:

1569
About installing the NDMP Option
You can find a list of compatible devices at the following URL: http://entsupport.symantec.com/umi/V-269-2 You can find white papers that discuss support for NDMP NetApp or EMC devices at the following URL: http://entsupport.symantec.com/umi/V-269-3
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. See Installing Backup Exec options to the local computer on page 75.
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. See Adding a user-defined selection to the User-defined Selections node on page 238. 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 2 3 On the navigation bar, click Devices. In the task pane, under NDMP Tasks, click Add NDMP Server. In the Add NDMP Server dialog box, enter the following information:
NDMP Server Enter the name of the NDMP Server.
1570
Backing up NDMP resources
Port Logon Account NDMP server supports ICMP ping operations
Enter the port to be used for communications between the Backup Exec server and the NDMP server. Select the Logon Account for the NDMP server. Check NDMP server supports ICMP ping operations to ensure that the Backup Exec can use ping to locate the NDMP server.
4 5
Click OK to add the NDMP server. 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 114

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. See Restoring NDMP data on page 1573.
To back up NDMP resources 1 2 3 4 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the Properties pane, under Source, click Selections. In the backup selections tree, expand either NDMP Servers or User-defined Selections.
1571
Appendix U, Symantec Backup Exec NDMP Option
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 7 8 9 On the Properties pane, under Destination, click Device and Media. In the Device list, select a storage device that is attached to an NDMP server. On the Properties pane, under Settings, click NDMP. 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. (NetApp filers only). Select this option to back up NetApp Access Control Lists. 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.
Back up Access Control Lists Disable file history

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
1572
Restoring NDMP data
Creating a backup job by setting job properties on page 267 Configuring Backup Exec to use the NDMP Option on page 1570 Restoring NDMP data on page 1573
Restoring NDMP data

During the restore process, you can select individual files for restore if file history was enabled 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 494. To restore NDMP data 1 2 3 4 On the navigation bar, click the arrow next to Restore. Click New Restore Job. Select the data you want to restore. 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 527. 5 On the Properties pane, under Source, click Device. See Device options for restore jobs on page 502. 6 7 On the Properties pane, under Settings, click NDMP. Select any of the following options:
Restore Access Control Lists (NetApp filers only). Select this option to restore NetApp Access Control Lists.
1573
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.

Start the restore job. Select other restore options from the Properties pane, and then start the restore job.
Related Topics: Setting catalog defaults on page 494 Restoring data by setting job properties on page 498 Backing up NDMP resources on page 1571 Setting default backup and restore options for NDMP on page 1574

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 2 3 On the Tools menu, click Options. On the Properties pane, under Job Defaults, click NDMP. 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.
1574
Back up Access Control Lists Disable file history
(NetApp filers only). Select this option to back up NetApp Access Control Lists. 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. (NetApp filers only). Select this option to restore NetApp Access Control Lists. 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 Access Control Lists Enable Direct Access Recovery
Click OK.
Related Topics: Backing up NDMP resources on page 1571 Restoring NDMP data on page 1573
1575
Viewing NDMP server properties
Viewing NDMP server properties

You can view details for all NDMP servers that appear on the View by Resources tab. To view NDMP server properties 1 2 3 4 5 6 On the navigation bar, click the arrow next to Backup. Click New Backup Job. On the View by Resource tab, expand NDMP Servers. Right-click the name of an NDMP server. Click Properties. The following properties appear:
Name Media server status Displays the assigned name or IP address of the NDMP server. Displays the status of the NDMP server when it is in use as a Backup Exec media server. Media server status includes Online, Pause, Unavailable, and Offline. See Viewing a media servers general properties on page 140. Description Pingable Displays a user-definable description of the NDMP server. Check Pingable to allow Backup Exec to communicate with the NDMP server. You can turn this option off in environments where ping requests are blocked. Displays the identifier number that is generated by the NDMP server. Displays the version of the operating system running on the NDMP server.
Host ID System version
Click OK.
1576
Appendix
Accessibility and Backup Exec
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 1578 General keyboard navigation within the GUI on page 1578 Keyboard navigation within dialog boxes on page 1579 Keyboard shortcuts on page 1580 Support for accessibility settings on page 1584
1577
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. See Keyboard shortcuts on page 1580. Items in the task pane that do not have keyboard shortcuts can be accessed by using the operating systems "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.
1578
Keyboard navigation within dialog boxes

Dialog boxes contain groups of controls necessary to set options or settings for programs. The following list contains 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:
Table V-1 Keyboard input CTRL+PAGE DOWN or CTRL+TAB CTRL+ PAGE UP Keyboard navigation within tabbed dialog boxes Result Switches to the next tab and displays the page.
Switches to the previous tab and displays the page.
Appendix V, Accessibility and Backup Exec
1579
Keyboard navigation and shortcuts in Backup Exec Table V-1 Keyboard input RIGHT ARROR or LEFT ARROW Keyboard navigation within tabbed dialog boxes (continued) Result When the focus is on a tab selector, chooses the next or previous tab in the current row and displays the page.
List boxes
List boxes display a column of available choices. There are different kinds of list boxes with the following 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
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:
Table V-2 Backup Exec Accelerator ALT Keyboard shortcuts unique to Backup Exec Backup Exec Mnemonic F Result 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.
1580
Keyboard navigation and shortcuts in Backup Exec Table V-2 Backup Exec Accelerator ALT Keyboard shortcuts unique to Backup Exec (continued) Backup Exec Mnemonic E Result 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
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
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
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. move to a new window or view.
ALT ALT
W H
The Window menu expands. Use the Window menu to 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.
1581
The following table lists the shortcut keys in Backup Exec Utility.:
Table V-3 Backup Exec Accelerator ALT Keyboard shortcuts unique to Backup Exec Utility Backup Exec Mnemonic F Result 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. The Edit menu expands. From the Edit menu, you can
ALT ALT ALT
E V H
rename, delete, and select items
The View menu expands. From the View menu, you can change the information that displays on the screen. 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:
Table V-4 Keyboard shortcuts unique to Backup Exec Desktop and Laptop Option Administration Console Backup Exec Mnemonic F E Result The File menu expands. From the File menu, you can create new Profiles and Storage Locations, and add users. The Edit menu expands. From the Edit menu, you can restore files, search for files to restore, manage alerts, and delete items. The View menu expands. From the View menu, you can change the information that displays on the screen. The Network menu expands. Use the Network menu to
Backup Exec Accelerator ALT ALT
ALT ALT
V N
work with administrator accounts, connect to media servers on the network, or to reconnect to a local media server.
ALT
The Tools menu expands. Use the Tools menu to set global excludes, access all DLO wizards, and manage service credentials.
1582
Keyboard navigation and shortcuts in Backup Exec Table V-4 Keyboard shortcuts unique to Backup Exec Desktop and Laptop Option Administration Console (continued) Backup Exec Mnemonic W H Result The Window menu expands. Use the Window menu to move to a new window or view. The Help menu expands. Use the Help menu to access Backup Exec documentation and various Symantec Web sites.
Backup Exec Accelerator ALT ALT
The following table lists the shortcut keys in the Backup Exec Desktop and Laptop Option Desktop Agent:
Table V-5 Backup Exec Accelerator ALT ALT ALT ALT ALT Keyboard shortcuts unique to Backup Exec Desktop and Laptop Option Desktop Agent Backup Exec Mnemonic F V K T H Result The File menu expands. From the File menu, you can minimize or exit the Desktop Agent. The View menu expands. From the View menu, you can change the information that displays on the screen. The Tasks menu expands. Use the Tasks menu to run a job or refresh the view. The Tools menu expands. Use the Tools menu to reset dialog boxes and accounts. The Help menu expands. Use the Help menu to access the online help for the Desktop Agent.
1583
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. 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 2 On the Start menu, select Settings, and then select Control Panel. 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.
1584
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. agent A component that allows workstations or other computers, for example, Microsoft SQL Server, to interact with the Backup Exec media server. alert 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 The classification of an alert that lets you determine the severity of the alert. Alert types include Error, Warning, Information, and Attention Required. allocated media The media that are associated with a media set and that have current append and overwrite protection periods. 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.
1585
audit log 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. 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 files 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. backup 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.
1586
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. 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. 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.
Glossary 1587
device 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. device pool 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. 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. 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 An action that occurs during a Backup Exec operation; for example, job cancellation. 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.
1588
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. Granular Recovery Technology (GRT) A backup option that is available with some Backup Exec Agents. Granular Recovery Technology lets you restore individual items from database backups. A separate backup of the individual items is not required for you to recover one item. 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 A report of what happened during the processing of the job (statistics, errors, and so on).
Glossary
1589
job log 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. 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. 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 medias overwrite protection period. 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.
1590
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. 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. 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. policy A method for managing backup jobs and strategies. Policies contain templates, which provide settings for jobs.
Glossary 1591
primary 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. 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. replicated 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. 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.
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. 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, or on some alerts. These codes contain hyperlinks that you can click to go to the Symantec Technical Support Web site. You can access technical notes and troubleshooting tips that are related to a specific error. Working Set - Back up files - Changed today A backup method that backs up all files that were created or modified today.
Glossary
1593
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.
1594
Index
A accelerator, defined, 1580 accessibility Desktop and Laptop Option, 1176 dialog boxes, 1176, 1579 keyboard navigation, 1176, 1578 keyboard shortcuts, 1176, 1580 overview, 1577 settings, 1176, 1584 active alerts defined, 538 responding to, 545 viewing, 538 Active Alerts by Media Server Report, 618 Active Alerts report, 618 Active Directory backing up in Exchange, 1188 for Automated User Assignments in DLO, 1030 for connection policies, 1151 Active Directory Recovery Agent about, 875 about restoring individual objects, 879 installing, 875 passwords, 880 recreating purged objects, 883 requirements, 873 tombstones, 880 Use Backup Exec Granular Recovery Technology (GRT) to enable the restore of individual objects from Active Directory backups option, 877, 878 Active File Exclusion, 1189 Exchange data, 1299 active jobs canceling, 454 placing scheduled occurrences on hold, 455 removing hold, 455 viewing properties, 451 ADAMM, defined, 1585 add users in DLO, CSV file to, 1043 administration console defined, 1585 Desktop Agent Console, 1129 Desktop and Laptop Option (DLO), 982 overview, 128 role in backup process, 59 Advanced Device and Media Management (ADAMM) database overview, 1545 device management overview, 138 Advanced Disk-based Backup Option baseline, setting, 832 best practices for offhost backup, 859 host computer, defined, 855 offhost backup for Exchange Server with Granular Recovery Technology, 865 offhost backup overview, 855 offhost backup requirements, 857 offhost backup snapshot provider, choosing, 862, 864 offhost backup, List Snapshot Providers option, 861 offhost backup, single volume snap, choosing, 863, 865 synthetic backup policy, example, 839 template requirements, 835 synthetic backup template rules, 844 synthetic backup template rules, example, 839 synthetic backup, creating, 839 synthetic backup, encryption in, 841 synthetic backup, option to enable, 837 transportable snapshots, defined, 855 true image restore, creating, 850 true image restore, option to enable, 837 true image restore, overview, 846 true image restore, requirements, 849 VSFW FlashSnap option, using with offhost backup, 858 Advanced File Selection options, 241 Advanced Open File Option cache file location, 822 cache file size, setting, 826 changing default settings for Symantec 1595
VSP, 822 databases, backing up, 811 encrypted files, backing up, 813 installing using the command line, 815 minimum quiet time, setting, 827 overview, 809 requirements, 813 Snap Start for VSFW volumes, 821 snapshot providers, 812 Symantec Volume Snapshot Provider, 817 using with Exchange Agent, 1192 wizard, 824 Advanced options for backup, 280 Agent for Microsoft SharePoint about, 1263 about restoring a SharePoint Server or Workspace, 1255 adding a server farm, 1264, 1280 backing up SharePoint Portal Server 2003 resources, 1267 disaster recovery, 1260 installing, 1252 overview, 1251 redirecting a restore for SharePoint Portal Server 2003, 1273 redirecting restore jobs, 1258 selecting SharePoint Portal Server 2003 resources for backup, 1263 setting default options, 1276 SharePoint Server 2007, 1278 system requirements, 1252 agent, defined, 1585 Agents, Backup Exec evaluating, 112 list of agents with descriptions, 53 upgrading on remote computers, 124 alert category, defined, 1585 alert history defined, 538 viewing, 538 Alert History report, 619 alert notification in DLO, printers, 1091 alert notification, printers, 566, 568 alert source, defined, 1585 alert type, defined, 1585 alerts alert types, 537 assigning recipients, 572 1596
clearing recipients, 572 defined, 537, 1585 defined for DLO, 1071 deleting in DLO, 1076 displaying in DLO, 1074 filters, 538, 539 grooming in DLO, 1071 handling with SAP Agent, 1423 managing in DLO, 1075 monitoring in DLO, 1071 properties, 542 responding to, 545 viewing, 539 viewing job log, 544 views, 538 all media, defined, 170 allocated media defined, 1585 overwriting, 186 append period defined, 172, 177, 1585 setting for media set, 177 append to media option, 273 Application Event Log report, 621 archive bit, defined, 228 archive logging Lotus Domino, 1301 recovery of Lotus Domino, 1310 archiving freeing disk space, 297 NTFS and VFAT file systems, 297 using disk grooming, 297 ARCserve media, restoring data from, 517 ASR files in IDR, 1503 audit log defined, 1586 for media operations, 190 viewing, 161 Audit Log report, 621 AUTOEXEC.NCF file, Remote Agent for NetWare Servers, 903 auto-inventory media after import job completes, 379 Automated System Recovery, 664 Automated User Assignment creating, 1027 defined, 949 deleting, 1032 modifying, 1030 Administrators Guide
priority, changing, 1031 properties, viewing, 1031 Automated User Assignment in DLO, 1027 using Active Directory, 1030 automatic exclusion of files during volume level backups, 1299, 1331 automatic updates, scheduling, 118 availability windows, 250 B back up on log on/off option in DLO, 1048 backing up Microsoft clusters local disks, 715 shared disks, 715 VERITAS clusters database files, 729 local disks, 728 shared disks, 728 BACKINT handling alerts, 1423 overview, 1422 using with CCMS console, 1428 backup overview, 263 Backup Exec accessibility, 1577 dialog boxes, 1579 keyboard shortcuts, 1580 build and version information, 685 installing command line installation, 101 silent mode installation, 101 uninstalling, 115 upgrading, 123 using Repair option, 114 options, 53 overview how it works, 59 new features, 49 system requirements, 69 ports, 327 repairing, 114 starting after installing Library Expansion Option, 1540 System Summary viewing, 485 upgrading options on remote computers, 124 Index
overview, 123 using with Symantec Endpoint Protection, 324 Backup Exec Environment Check, 62 Backup Exec for Windows Servers, described, 47 Backup Exec License Assessment Tool, 123 Backup Exec Retrieve description, 975 retrieving files, 1163 using with DLO, 975 Backup Exec Server in SAN, 1545 Backup Exec service account, defined, 1586 Backup Exec services Backup Exec Services Manager dialog box, 114 stopping and starting, 114 backup job Advanced options, 280 choices for creating, 263 copying to another server, 448 creating manually, 267 creating using the wizard, 264 Device and Media options, 272 pre/post commands, 284 scheduling, 286 selecting devices and data, 231 Selections options, 269 tasks to do before, 264 Backup Job Properties dialog box SQL Agent, 1326 Backup Job Success Rate, 622 backup methods defined, 1586 selecting, 276 setting default, 308 using modified time, 229 backup network changing for a backup job, 322 configuring, 318 overview, 316 setting up, 318 backup on log on/off option in DLO, 1048 backup options, Configure desktop and laptop, 982 Backup Selection dialog box in DLO, 1134 backup selections adding in DLO, 1004 macros in DLO, 1012 1597
backup selections, changing order, 269 Backup Set Details by Resource report, 623 backup set, defined, 1586 Backup Sets by Media Set report, 624 Backup Size by Resource report, 625 backup strategies choosing resources to back up, 223 defined, 221, 1586 frequency of backups, 222 increase throughput with Remote Agent for Windows Systems, 887 length of data retention, 223 multiple resources per job, 224 one job per resource, 223 protecting against viruses, 223 backup types archive, 224 copy, 224 daily, 225 differential, 225 full, 224 incremental, 225 working set, 225 Backup Wizard, launching, 264 backup-to-disk file defined, 388 deleting, 403 erasing, 404 recreating a deleted file, 404 renaming, 402 backup-to-disk folder advanced options, 395 auto detect settings, 395 Backup-to-disk Wizard, 391 buffered reads, 396 changing the path, 399 concurrent jobs, 387, 393 creating, 391 creating more disk space, 272 defined, 387, 1586 deleting, 400 low disk space threshold, 395 maximum number of backup sets, 393 maximum size, 392 maximum size, allocate at, 393 overview, 387 pausing and resuming, 402 recommendations for using with Granular Recovery Technology, 407 1598
recreating, 401 renaming, 399 requirements, 389 requirements for removable, 390 set global defaults, 396 sharing, 398 bandwidth settings, DLO, for users in, 989 bar code labels and media ID, 191 default, 192 mixed media libraries, 193 overview, 192 robotic library support, 192 bar code rules changing, 194 deleting, 194 enabling, 361 setting up, 193 baseline defined, 1586 setting for synthetic backup, 832 bediag.fax file, 912 bediag.nlm utility, saving configuration information, 912 besernum.xml file, importing license keys with, 72, 76, 80 BESTART command, to start Remote Agent for NetWare Servers, 903 BESTOP command, to stop Remote Agent for NetWare Servers, 903 biparam.ini options, 1425 overview, 1418 specifying Backup Exec parameters, 1425 BKUPEXECDLO MSDE database instance, 1100 blackout window, setting in DLO, 1053 block size, setting for devices, 347 boot managers, restoring in IDR, 1519 bootable media for IDR CD image, creating, 1510 comparing types, 1503 tape image, creating, 1512 types of media, 1502 BRRESTORE, restoring data with, 1429 BRTOOLS, using with SAP Agent, 1428 buffer count, setting for devices, 348 buffer size, setting for devices, 347 Administrators Guide
build and version information, displaying, 685 byte count, incorrect, 678 C cache file location, for AOFO, 822 cache file size, setting for AOFO, 826 calendar, viewing the job workload from, 483 cascaded drive pools adding drives, 420 creating, 419 defined, 411, 1586 deleting, 421 deleting drives, 420 overview, 418 properties, 422 renaming, 422 requirements for using, 418 using hardware compression in, 418 CASO alerts, configuring, 778 Backup Exec Utility, running, 767 catalog location changing, 781 displayed, 799 overview, 780 central administration server installing, 750 pausing storage devices from, 803 port number, SQL 2000 or 2005 instance, 759 port number, SQL Express instance, 757 setting for a managed media server, 766 centralized catalog, overview, 781 centralized restore multiple storage devices, 793 overview, 792 communication status, none, 776 communications, disabling and enabling, 803 configuring, 769 device and media data, location of, 749 distributed catalog, overview, 780 duplicate backup data job requirements, 792 features in, 746 Index
job delegation, 743, 783 job history options, setting, 776 managed media server alias, creating for SQL 2000 or 2005, 760 alias, creating for SQL Express, 758 device and media data, choosing the location of, 754 firewall, installing across, 757 installing, 751 installing for SAN Shared Storage Option, 754 job history options, 776 job log options, 776 pausing and unpausing, 802 stalled, 776 status messages, 798 viewing properties, 805 media server pool advantages of, 784 apply settings to all servers in a pool, 790 deleting, 787 filter data for, 784 overview, 783 removing a managed media server, 788 renaming, 787 statistics, viewing, 789 media server, changing to a managed media server, 766 monitor jobs on local managed media server, 772 network interface cards, using any available, 779 network traffic, reducing, 770 notification, configuring, 779 overview, 743 recovered jobs, 775, 776 recovering failed jobs, 778, 800 replicated catalog, overview, 781 requirements, 747 selection list, restrict backup of, 785 stopping and starting Backup Exec services, 804 synthetic backup job requirements, 792 time differences between servers, 773 upgrading, 760 catalog 1599
defined, 1587 levels, 495 media in drive, 196 searching, 524 catalog database, in SAN Shared Storage Option, 1558 catalog operation errors, DLT tape drive hangs, 677 CCMS console, using with SAP Agent, 1428 cell phone,notification, 553 central administration server, defined, 1587 centralized catalog defined, 1587 in CASO, 781 centralized restore best practices, 795 defined, 1587 CHECKCATALOG utility, 1322 CHECKDB utility, 1322 CHECKFILEGROUP utility, 1322 checkpoint restart on Microsoft cluster failover enabling or disabling, 700 overview, 699 circular logging Exchange Agent, reviewing in, 1189 Lotus Domino, 1301 recovery of Lotus Domino server, 1312 cleaning jobs, submitting for robotic libraries, 377 Cleaning tab for device properties, 351 clone CD image creating, 110 overview, 110 clrest command, 720 Cluster Failover error-handling rule, 487, 491 clusters backing up SAP database, 1434 Desktop and Laptop Option, 1100 disaster recovery entire cluster manually, 734 nodes using IDR, 732 using IDR to prepare, 732 installation of Backup Exec on a VERITAS cluster server, 723 Microsoft, 716 adding or removing a failover 1600
node, 701 all drives pool, 698 backing up shared disks, 715 BEUtility, 702 changing the order in which nodes fail over, 701 configurations, 704, 706, 707, 709 creating drive pools, 698 database server, designating new in SAN SSO, 702 disaster recovery, 735, 736, 738 disaster recovery of Backup Exec on a cluster using IDR, 733 failover restart, 692 installation, 694, 696 local disks, 715 Open File Option, and using, 696 overview, 714 Remote Agent, installing, 694 restoring, 717, 718, 719 system state, backing up, 715 uninstalling Backup Exec, 696 virtual servers, backing up, 716 restoring specifying a new drive letter for the Microsoft cluster quorum disk, 721 SAP Agent, 1434 sizes for FAT partitions, 679 troubleshooting, 738 using with Backup Exec, 691 VERITAS backing up, 727, 728, 729 disaster recovery, 731, 737 overview, 726 Remote Agent, installing, 723 restoring Windows 2000 and Windows 2003, 730 virtual servers, backing up, 729 combination SAP database server/media server recovery, 1439 command line installation of Backup Exec, 101 common encryption keys, 332 defined, 1587 completed jobs, job log overview, 471 compression delta file transfer, 1010, 1137 delta file transfer in DLO, 1016 Administrators Guide
DLO backup selections, setting, 1010, 1137 enable hardware compression option, 347 hardware, 347 in cascaded drive pools, 418 setting backup defaults, 310 using with encryption, 330 Configuration Settings report, 626 configuration settings, copying to another server, 156 Configuration tab for device properties, 347 for robotic library, 361 configuration wizard for DLO, 987 Configure Alerts dialog box (DLO), 1074 Configure desktop and laptop backups option, 982 configuring devices, 346 holidays, 296 robotic library, 356 connection based policies configuring in DLO, 999, 1149 using Active Directory, 1151 consistency check options Exchange Agent, 1215 SQL Agent, 1320 continuing Active Directory backup if consistency check fails, 877, 879 continuing Exchange backup if consistency check fails, 1215 Continuous backup option for Exchange data, 1213 continuous protection Exchange data, best practices, 1202 Exchange data, configuring for, 1200 for Exchange data, overview, 1197 job statuses in Exchange, 1203 requirements for Exchange, 1198 review disk space, 1204 copy jobs, selection lists, and policies, 448 creating more disk space for backup folder, 272 current jobs custom filters, 477 custom error-handling rule, defined, 1587 custom filter, defined, 1587 custom reports Index
copying, 608 creating, 593 deleting, 609 editing, 609 filter criteria and expressions, 592 graph options, 602 grouping fields, 600 overview, 592 previewing, 608 setting filters, 595 sorting fields, 601 D daily backups, defined, 225 Daily Device Utilization report, 628 damaged media, removing, 208 database, 953 database files backing up, 716 backing up in a Microsoft cluster, 716 backing up in a VERITAS cluster, 729 database instance, BKUPEXECDLO MSDE, 1100 database maintenance configuring, 163 overview, 162 database server defined, 1545 in Microsoft clusters, 702 Date Modified tab, 526 DB2 Agent archive logging methods. using with Backup Exec, 1455 archive logs template name, configuring for DB2 instance, 1445 authentication, configuring on DB2 instance, 1445 backing up, 1451 credentials, updating for instance, 1444 database access, configuring on media server, 1448, 1449, 1450 db2.conf configuration file, 1454 db2.conf file, creating, 1456 db2.conf file, overview, 1456 DBA-initiated job settings, configuring, 1459 DBA-initiated jobs, about, 1453 DBA-initiated jobs, job template name for, 1444 1601
defaults for backup and restore, 1461 example script, for command line processor, 1454 features, 1441 installation and configuration, 1442 multiple data streams, specifying, 1452 overview, 1441 port, configuring for DB2 operations, 1447 redirected restore, 1464 restoring, 1462 troubleshooting, 1467 user exit db2uext2.exe, installed, 1453 user exit method, configuring for, 1443 vendor library db2sqluv.dll, installed, 1453 vendor library method, configuring for, 1443 DBA-initiated job settings for SAP, 1426 DBA-initiated job settings, SAP Agent, 1426 default options backup and restore for Exchange Agent, 1207 IDR, setting, 1505 NDMP backup and restore, 1574 overview, 60 restore, 531 setting, 134 setting for backup jobs, 307 SQL Agent, backup and restore, 1361 default preferred configuration settings for devices, 348 default settings changing for DLO, 969 deleting Automated User Assignments in DLO, 1032 device pools, 416 devices from pools, 415 DLO desktop computer, 1052 media, 209 revisions in DLO, 1011 Storage Location in DLO, 1027 user entry from DLO, 1045 vault, 202 delta file transfer, 1010, 1016, 1137 Desktop Agent installing, 958 1602
see also Desktop and Laptop Option (DLO) Desktop Agent (DLO) advanced view option, 1134 backing up data, 1130 Backup Selection dialog box, 1134 backup selections compression, setting, 1137 modifying, 1132 overview, 1130 console, 1129 customizing installation, 958 Desktop User Data Folder, moving, 1148 filter options, History view, 1165 glossary, 1176 History view, 1164 include/exclude, 1135 install set default location, 1123 installing, 957 log files, overview, 1164 menu bar, described, 1129 overview, 1121 Reset accounts option, 1127 reset dialogs option, 1127 Restore dialog box, 1160 restoring files, 1159 revision control tab, 1136 revisions, deleting automatically, 1137 schedule, customized, 1048, 1143 scheduling backup jobs, 1143 standard view option, 1132 Status view, 1155 storage limits for user data, 1146 synchronization create new sets, 1152 delete synchronized folder, 1154 Synchronized Selections view, 1151 tasks bar, described, 1129 views menu, described, 1129 Desktop Agent Users, managing, 1041 desktop and laptop backups option, Configure, 982 Desktop and Laptop Option (DLO), 949 see also Desktop Agent access, disabling/enabling, 1044 adding user, 1042 administration console, 982 administrator accounts, 965 Administrators Guide
administrators, creating, 965 alert history, 1074 alert notification, printers, 1092 alerts categories, defined, 1071 Configure Alerts dialog box, 1074 deleting, 1076 displaying, 1074 managing, 1075 monitoring, 1071 Automated User Assignment creating, 1028 defined, 949 deleting, 1032 modifying, 1030 priority, changing, 1031 properties, viewing, 1031 backup selection adding, 1001 deleting, 1015 modifying, 1014 BEUtility.exe utility, using, 1100 clustering, 1100 command line interface, 1103 assignSL, 1104 changeserver, 1107 -emergencyrestore, 1115 -enableuser, 1106 -keytest, 1108 -listprofile, 1109 -listsl, 1110 -listuser, 1111 -logfile, 1112 remote server options, 1103 -setrecoverypwd, 1116 syntax, 1103 -update, 1113 Computer History pane, 1065 Configuration Wizard, 987 configuring, 987 deleting entry from DLO database, 1052 encryption, setting for backup selection, 1010, 1137 filter options, History view, 1067 glossary, 1176 History view, 1065 import multiple users in CSV file, 1043 include/exclude, 1006, 1135 installing, 956 Index
Job History pane, 1066 Move priority down option, 1031 Move priority up option, 1031 MSDE database instance, maintaining, 1100 overview, 949 profile creating, 988 defined, 949 edit schedule, 997 log on/off option, 1048 logging options, 997, 1049 Schedule tab, 995, 1048 properties, changing user, 1044 removing user, 1045 reset dialogs and accounts, 1127 restoring, 1055 revisions defined, 1008 deleting automatically, 1011 setting number to keep in DLO, 1009, 1136 Search history log file option, 1070 storage limits for user data, 990 Storage Location defined, 949 deleting, 1027 moving users, 1046 summary status, 984 user bandwidth settings, 989 User Data Folder, 1021 User Properties dialog box, 1044 View history log file option, 1068 viewing users, 1048 Desktop data, backing up with DLO, 1130 device allocation in a shared storage environment, 1549 selecting for backup job, 272 device and media data, location of in CASO, 749 Device and Media options for backup job, 272 device management, 138 device operations See also robotic library cataloging media, 196 ejecting media, 376 Enable Hardware Compression 1603
Option, 347 erasing media (quick or long), 370 formatting media, 373 inventorying a drive, 368 labeling media, 374 overview of utility jobs, 367 retensioning a tape, 372 using with SAN Shared Storage Option, 1552 Device pool properties dialog box, 418 device pools adding devices, 413 creating, 412 defined, 411 deleting, 416 deleting devices, 415 overview, 411 prioritizing devices, 414 properties, 417 renaming, 417 using the default device pool, 412 viewing properties, 418 device pools, defined, 1588 device properties Configuration tab, 346 General tab, 344 Media Types tab, 353 SCSI Information tab, 349 viewing, 343 Device Summary Report, 1550 Device Summary report, 628 Device Usage by Policy report, 629 devices block size, 347 buffer count, 348 buffer size, 347 configuring, 346 default settings, 348 defined, 1588 high water count, 348 Hot-swappable Device Wizard, 341 iSCSI-attached, adding, 341 pausing, resuming, renaming, 354 SCSI information, 349 specifying media types for, 353 statistics on usage, 350 statistics since cleaning, 351 Symantec Device Driver Installation Wizard, 342 1604
troubleshooting, 1563 USB tape devices, reconnecting, 341 viewing with Library Expansion Option, 1541 dialog box (DLO), Move User, 1046 dialog boxes, overview, 131 differential - Back up changed files since last full, 1587 differential - Using modified time, 1587 differential backups advantages and disadvantages, 227 defined, 225 disable device for Backup Exec, 345, 360, 392 Disable file history, 1572, 1575 disaster preparation Disaster Preparation Plan (DPP), 660 emergency repair disk, 663 Exchange Server, 1245 hardware protection, 660 Lotus Domino Agent, 1308 off-site storage, 660 overview, 659 SQL 2000, 1367 disaster recovery clusters Backup Exec on a Microsoft cluster using IDR, 733 entire cluster manually, 734 nodes using IDR, 732 using IDR to prepare, 732 data protected by Backup Exec agents, 664 different types of computers, overview, 664 Exchange 5.5, 1248 Exchange Server, 1246 local Windows 2000 computers (non-authoritative), 665 Lotus Domino Agent, 1309 manual recovery of Windows system, 664 Microsoft clusters Backup Exec, 738 data files, 735 shared disks, 736 overview, 664 performing using SAP Agent, 1437 Remote Agent for NetWare Servers, 913 Administrators Guide
remote Windows 2000 computers (non-authoritative), 669 VERITAS clusters overview, 731 shared disks, 737 disaster recovery alternate data path, in IDR, 1506 disaster recovery data path, in IDR, 1505 disaster recovery file (*.dr file) in IDR defined, 1503 setting locations for, 1504 Disaster Recovery Wizard requirements, 1522 running, 1522 disk grooming, using for archive job, 297 distributed catalog defined, 1588 in CASO, 780 Distributed file system (Dfs) backing up, 240 restoring, 517 DLO Administration Console, restoring from, 1055 DLO Administration Server, connecting to, 985 DLT tape, drive hangs when cataloging, 677 Domain Controller, using redirected restore to install from media, 529 domains, host and target, defined, 66 drive pools creating in a Microsoft cluster, 698 default for SAN Shared Storage Option, 1551 SAN Shared Storage Option, 1549 drivers, download latest, 675 duplicate backup data template, 1588 duplicate backup sets template adding to a policy, 444 overview, 443 duplicating backup data, 298 E editions of Backup Exec, listed and described, 47 eject media after job completes, 274 from a drive, 376 e-mail configuring MAPI notification, 555 Index
configuring MAPI notification in DLO, 1078 configuring SMTP notification, 553 configuring SMTP notification in DLO, 1077 configuring VIM notification, 556, 1079 emergency repair disk, creating, 663 Enable Direct Access Recovery, 1574, 1575 enabling device for Backup Exec option, 345, 360, 392 encrypted files, backing up with AOFO, 813 encryption about, 330 hardware, 331 in DLO backup selections, 1010, 1137 SAP data, 1422 software, 331 types, 330 encryption keys 128-bit AES, 330 256-bit AES, 330 common, 332 creating, 334 deleting, 337 encryption types, 330 managing, 334 overview, 332 pass phrases, 333 restoring encrypted data, 338 restricted, 332 selecting for a backup job, 335 setting a default, 318 using with compression, 330 Environment Check, running for Backup Exec, 62 erase media operation, quick or long, 370 error codes, Unique Message Identifier, viewing, 470, 546 error-handling rules Cluster Failover rule, 487, 491 configuring, 487 custom rules, defined, 486 default rules, defined, 486 defined, 1588 overview, 486 Recovered Jobs custom rule, 486 EV Agent automatic redirection of Enterprise 1605
Vault components, 1486 Automatically backed up components, 1470 available backup methods, 1473 backup selections, 1472 closed partition backing up, 1476 restoring, 1490 Directory database backing up, 1477 restoring, 1486 restoring to a different SQL Server, 1496 Enterprise Vault server backing up, 1481 restoring, 1493 Enterprise Vault site backing up, 1482 index locations backing up, 1483 restoring, 1492 installing, 1471 Monitoring database backing up, 1478 restoring, 1487 open partition backing up, 1475 restoring, 1489 selecting a backup method, 1473 setting a default backup method, 1474 vault store backing up, 1480 vault store database backing up, 1479 restoring, 1491 evaluation version agents and options, 112 installing Backup Exec, 72, 80 Event Recipients report, 632 event, defined, 1588 example policies, 427 Exchange 5.5, restoring defaults, 1209 redirecting database restores, 1239 Exchange Agent Active Directory, backing up, 1188 automatic exclusion of files during volume level backups, 1189 backing up, recommended 1606
selections, 1187 backup methods, 1208, 1213 best practices, 1183 change password when recreating mailboxes, 1210 circular logging, reviewing, 1189 Continuous backup option, 1213 continuous protection, best practices, 1202 continuous protection, overview, 1197 continuous protection, requirements, 1198 continuous protection, review disk space, 1204 continuous protection,configuring, 1200 creating backup job, 1212 disaster recovery, 1246 Exchange 2003 with VSS, backing up, 1191 Exchange 2007 in LCR/CCR configurations, 1216 Exchange 2007 snapshot backup method, 1193 exclude specific folders, 1218 excluding files during volume level backups, 1189 Granular Recovery Technology (GRT) option, setting for backup, 1214 Granular Recovery Technology (GRT), overview, 1190 Granular Recovery Technology (GRT), requirements for, 1181 Guide Me wizard for backup, 1214 installation, 1183 Internet Information Service (IIS) metabase, backing up, 1187 Key Management Service (KMS), backing up, 1188 legacy mailbox backup options, 1209, 1217 mailbox access requirements, 1185 mount database after restore option, 1236 no loss restore option, 1234 offhost backup, with Granular Recovery Technology (GRT), 865, 1190 overview, 1179 process logical volumes one at a Administrators Guide
time, 1192 protecting Exchange using VSS, 1191 recovery point option, 1214 recovery points, 1206 recreating mailboxes and user accounts, 1233 redirecting data, 1238 redirecting mailboxes, 1240 redirecting storage groups and databases, 1238 Redirection dialog box, 1242 requirements, 1180 resource discovery feature, using with, 1181 restore defaults, 1207 restore from continuous protection backups, 1228 Restore Job Properties dialog box, 1232 restore of individual items, requirements for, 1181 restore over existing messages and folders when restoring individual items, 1233 restore public folder option for Exchange 5.5, 1234 restore requirement, 1224 restore requirements for 5.5, 1224 restoring commit after restore completes option, 1236 DS/IS consistency adjuster after restore, 1244 temporary location for log and patch files, 1236 restoring an Exchange 2007 database to a recovery storage group, 1226 restoring data to server, 1224 restoring Exchange 2003 and 2007 with Recovery Storage Group, 1225 restoring individual items from Information Store backups, 1229 restoring individual public folder messages from tape, 1231 restoring mailboxes and public folders, overview, 1230 restoring mailboxes and user accounts, 1233 services accounts, overview, 1180 Site Replication Services (SRS) Index
database, backing up, 1188 snapshot technology, and, 1191 storage groups, backing up, 1211 strategies for backing up, 1186 system state, backing up, 1187 troubleshooting snapshot and offhost jobs, 1193 volume level backups, automatic exclusion of files, 1189 Exchange Redirection page, 1242 Exchange Server Agent, excluding files during volume level backups, 1299 executing a command after backup, 285 after restore, 509 before backup, 284 before restore, 509 export media template, 433 exporting media, 380 F failback, defined, 692 Failed Backup Jobs report, 632 failover adding or removing a failover node, 701 changing the order in which nodes fail over, 701 defined, 691 restart, 692 farms adding, 1264, 1280 changing the default farm name, 1266 deleting, 1266 FAT cluster size, 679 partition, 679 father/son media rotation strategy, 217 file permissions, restoring, 511 file to add users in DLO, CSV, 1043 filegroups backing up SQL, 1333 displaying, 1334 restoring nonprimary SQL 2000, 1344 primary SQL 2000, 1344 SQL Agent, 1348 filter criteria for reports, 592 filter expressions for reports, 592 filters 1607
custom current jobs, 477 job history, 479 jobs, 476 for alerts, 538, 539 for jobs, 475 History view filters, setting in Desktop Agent, 1165 History view filters, setting in DLO, 1067 finding media in a location or vault, 201 firewall browsing systems through, 329 enabling a SQL instance behind, 330 installing a managed media server across, 757 using Backup Exec with, 326 formatting media, 373 frequently asked questions about using Backup Exec, 131 full backups advantages and disadvantages, 226 Archive the files,defined, 1589 Copy the files, defined, 1588 defined, 224 Using archive bit (Reset Archive Bit), defined, 1588 Using modified time, defined, 1588 fully qualified computer name, 238 G general job defaults, setting, 138 general media properties, viewing, 210 general options for restore jobs, 503 Getting Started with Backup Exec page, 127 global excludes adding, 1032, 1033, 1034, 1036, 1037 deleting, 1032, 1033, 1034, 1036, 1037 macros, 1040 glossary for DLO, 1176 glossary of terms, 1176 grandfather media rotation strategy, 218 Granular Recovery Technology (GRT) backup-to-disk folder about using for Granular Recovery Technology operations, 406 Exchange data, 1190 Exchange data, offhost backup, 1190 reclaiming disk space for, 409 1608
recommendations for using backup-to-disk folders with, 407 temporary staging location, setting as a default, 533 temporary staging location, setting for a job, 508 Granular Recovery Technology (GRT), defined, 1589 grooming files in DLO, 1008 groups, configuring recipients, 568, 1092 H hardware compression in cascaded drive pools, 418 creating profile, 662 enable hardware compression option, 347 protection in case of disaster, 660 high water count, setting for devices, 348 hold jobs, 462 holding jobs that back up selection lists, 246 host domain, defined, 66 hot key, defined, 1580 I IBM computers, recovering with IDR, 1521 IDR Configuration Wizard, 1503 IMG subfolders, described, 388 imported media defined, 1589 labeled by Backup Exec, 192 overwriting, 186 importing media, 378 importing templates, 434 include/exclude Desktop Agent backup selections, 1135 DLO backup selections, 1006 Incremental - Back up changed files since last full or incremental - Using archive bit, 1589 Incremental - Back up changed files since last full or incremental - Using modified time, 1589 incremental backups advantages and disadvantages, 227 defined, 225 initialize robotic library panel, 382 Administrators Guide
install from media, 529 installation parameter file creating, 109 defined, 109 using, 109 installed updates, viewing, 120 installing additional Backup Exec options on a Microsoft cluster, 696 Backup Exec, 71 Backup Exec in a Microsoft cluster, 694 Backup Exec in a VERITAS cluster, 723 besernum.xml file, import license keys, 72, 76, 80 Desktop Agent, 957 Desktop Agent options, 958 Desktop and Laptop Option, 956 Domain Controllers from media, 529 Environment Check, running pre-install, 62 Evaluation version, 72, 80 import license keys, 72, 76, 80 Library Expansion Option, 1539 locally additional options, 75 using clone CD image, 111 methods, 61 Microsoft Data Access Components (MDAC), 66 Microsoft SQL Server 2000 Desktop Engine (MSDE 2000), 66 NDMP Option, 1570 Remote Administrator, 99 remotely using clone CD image, 111 SharePoint Agent, 1252 silent install of DLO, 958 storage devices, 62 to an existing Microsoft SQL Server 2000 instance, 67 using installation program on CD, 71 using Repair option, 114 using Terminal Services, 71 Windows Management Instrumentation performance counter, 580 Windows Management Instrumentation SNMP provider, 580 instance, BKUPEXECDLO MSDE database, 1100 Index
Intelligent Disaster Recovery (IDR) alternate data path on a remote computer, 1506 ASR files, 1503 automated restore, 1523 boot managers, 1519 catalog entries, added to *.dr file, 1499 clusters recovering Backup Exec on a Microsoft Cluster, 733 recovering nodes, 732 disaster recovery file (*.dr file), defined, 1503 encrypted backup sets, 1522 First Time Startup Configuration Wizard, 1503 hard drive partition, altering sizes using IDR, 1531 IBM computers, 1521 installing, 1501 Microsoft Exchange Server, recovering, 1534 Microsoft SQL Server, recovering, 1534 Options - Set Application Defaults dialog box, 1505 OS/2 boot manager, restoring, 1519 overview, 1499 Recovery Wizard, running, 1522 requirements, 1500 restoring from a locally-attached media device, 1526 restoring from a remote media server, 1529 restoring from remote backup-to-disk folders, 1527 SharePoint Portal Server, recovering, 1534 System Commander boot manager, restoring, 1519 utility partitions, backing up, 1508 virtual devices, using in, 388 Windows Automated System Recovery (ASR) files, 1503 Internet Information Services (IIS) metabase, backing up, 1187 inventory all drives when Backup Exec starts, 370 drives, 368 inventorying 1609
all drives on startup, 136 IPv4, 318 IPv6, 318 iSCSI-attached devices, adding, 341 J job delegation, 1589 in CASO, 743 Job Distribution by Device report, 633 job history custom filters, 479 defined, 1589 deleting report, 591 History view filters in DLO, setting in DLO, 1067 saving report, 590 viewing, 466 viewing report, 589 job history (DLO) viewing in Desktop Agent, 1164 job log configuring default options, 473 defined, 1590 setting options in CASO, 776 status overview, 471 job monitor viewing DLO jobs, 1065 views, 450 job priority setting for cleaning jobs, 378 setting for eject job, 376 setting for erase job, 405 setting for export job, 380 setting for format job, 374 setting for import job, 379 setting for inventory job, 369 setting for label media job, 375 setting for retension job, 373 job progress indicators, displaying, 136 job queue, hold, 462 job status, and setting thresholds for, 491 jobs calendar view of workload, 483 calendar, managing jobs from, 484 changing priority for scheduled, 463 configuring default Lotus Domino options, 1298 configuring default schedule, 297 configuring error-handling rules, 487 1610
configuring new recipients, 573 configuring schedule, 286 creating from policies, 440 defined, 1589 deleting jobs created from policies, 442 deleting scheduled, 465 edit recipients, 573 filtering, 475 filters, 475 hold queue, 462 holiday scheduling, 296 Lotus Domino backup properties, 1301 managing custom filters, 476 removing hold active jobs, 455 scheduled jobs, 462 run report, 587 running scheduled job, 461 running scheduled test job, 464 scheduled, modifying, 457 scheduled, viewing, 457 scheduling, 286 selecting recipients for notifications, 573 setting general defaults, 138 viewing and scheduling in a SAN, 1557 viewing completed, 465 Jobs Summary report, 634 junction points backing up, 281 K Key Management Service (KMS) database, backing up, 1188 keyboard navigation dialog boxes, 1579 shortcuts, 1578 standards, 1578 keyboard shortcuts, 1580 L labeling media creating default labels, 188 imported media label, 192 in drive, 374 renaming, 195 using bar code labels, 192 last known good menu, 661 legacy mailbox backup methods, in Exchange, 1217 Administrators Guide
Library Expansion Option overview, 1537 SCSI addresses for hardware, 1538 setting up hardware, 1538 library sharing, configuring server for, 1554 license information finding in your environment, 123 license keys Backup Exec adding and removing, 72, 76, 80, 122 viewing, 120 finding in your environment, 123 Remote Agent for Windows Systems, 888 list boxes, navigation, 1580 LiveUpdate about, 116 running manually, 119 scheduling automatic updates, 118 load balancing, defined, 1590 local media server, breaking connection with, 100 location, media in Backup Exec, 199 lock open files for backup, 283, 313 lock robotic library panel, 381 logon account, defined, 1590 logon accounts changing default, 154 changing for a resource being backed up, 270 default, defined, 147 deleting, 153 editing, 151 overview, 146 replacing, 152 SQL resources, 1317 system logon account, 148 testing, 270 logon information, copying to another server, 159 Lotus Domino Agent APIs, 1299 archive logging, 1301 backup options, 1301 circular logging, 1301 configuring default options, 1298 database backup overview, 1299 database backup requirements, 1294 Index
disaster preparation, 1308 disaster recovery archive logging, 1310 circular logging, 1312 of server, 1309 Microsoft Cluster Server, 1294 restoring, 1303 overview, 1293 redirecting restore, 1307 requirements, 1294 restore overview, 1303 selecting for restore, 1304 selecting restore options, 1306 supported configurations, 1300 viewing databases, 1296 Lotus Notes, backing up nsf files with DLO, 1141 low disk space threshold, backup-to-disk folder option, 395 M Machines Backed Up report, 634 macros, global excludes, 1040 mailbox access requirements for Exchange, 1185 mailboxes exclude specific folders, 1218 redirecting restores, 1240 restore overview, 1230 maintenance server (DLO), delegation maintenance server (DLO), 1018 majority node in a cluster, 693 managed media server copying jobs to, 791 defaults, setting, 770 defined, 1590 installing, 751 network connection speed to central administration server, 771 network interface card, using any available, 779 pools, 783 upgrading, 760 Managed Media Servers report, 635 manually update server list, for NetWare, 912 MAPI configuring recipients, 560 e-mail notification method, 555 1611
e-mail notification method in DLO, 1078 MAPI, configuring recipients, 1083 master database (SQL) backup, 1320 restore, 1341 MaxDB databases protecting with SAP Agent backing up, 1435 overview, 1417 restoring, 1436 media adding to the offline location or user-defined media vault, 203 all media, defined, 170 append backup to, 273 associating with a media set or vault, 210 categories, 169 creating default labels, 188 damaged, 208 deleting, 209 deleting vault, 202 displaying media ID, 210 drag and drop, to move media, 206 finding in a location or vault, 201 general properties, 210 moving to a location or vault, 202 overwrite for backup, 273 overwrite options, 182 overwriting allocated or imported, 186 properties, 210 retired, defined, 171 scanning bar code labels, 203 scheduling a job to move media, 204 scratch, defined, 171 setting default options, 186 sharing, 1558 statistical properties, 213 testing integrity of, 302 Vault Wizard, to move media, 205 with excessive errors, 208 Media Audit report, 637 media capacity, testing before backup runs, 306 media catalogs, 1545 Media Errors report, 637 media ID, defined, 191, 1590 media label 1612
bar code rule changing, 194 deleting, 194 in mixed media libraries, 193 bar codes, 192 defined, 1590 imported, 192 overview, 191 renaming, 195 media location, updating, 206 media operations associating media with media sets, 210 audit log for, 190 deleting media, 209 viewing media properties, 210 media overwrite protection level, defined, 182, 1590 media overwrite protection, overview, 176 Media Required for Recovery report, 638 media rotation, 423 defined, 1590 in SAN, 1559 strategies father/son, 217 grandfather, 218 son, 217 media server defined, 1591 properties, general, 140 viewing properties, 139 media server pool, defined, 1591 media server, connecting to in DLO, 985 media servers configuring for robotic library sharing, 1554 media set creating, 176 default, 175 defined, 170 deleting, 179 overwrite and append properties, 180 renaming, 180 selecting for backup job, 273 shared storage environments, and, 1558 vault rule properties, 200 wizard, running, 178 Media Set report, 638 media set, defined, 1591 Administrators Guide
media types, specifying for devices, 353 media vault defined, 199, 1591 deleting, 202 finding media in a vault, 201 moving media, 202 renaming, 202 user-defined, 199, 200 Media Vault Contents report, 639 media view, 493 menu bar, overview, 128 menus, described Help, 1583 Window, 1581 menus, described, Help, 1176 messages, error, 677 Microsoft Cluster Server, using with Backup Exec, 692 Microsoft clusters database files, 716 Microsoft clusters, clrest command, 720 Microsoft Data Access Components (MDAC), installing, 66 Microsoft SQL Server 2000 Desktop Engine (MSDE), installing, 66 Microsoft Terminal Services, and installing Backup Exec, 71 Microsoft Volume Shadow Copy Service (VSS), and AOFO, 818 minimum quiet time, setting for AOFO, 827 Missed Availability report, 640 mixed media library bar code labeling, 193 mnemonic, defined, 1580 Mobile phone notification, 553 Monitor jobs on local managed media server, 772 mounted local drives backing up, 281 mounted local drives, backing up files and directories, 281 Move Media to Vault report, 641 Move priority options in DLO, 1031 Move User dialog box in DLO, 1046 moving media, using drag and drop, 207 MSCS, using with Backup Exec, 692 MSDE, 953 2000 components, installed with Backup Exec, 66 database instance, Index
BKUPEXECDLO, 1100 database instance, DLO, 1100 multi-stage backup strategy, 443 N Name & Resource dialog box, 525 named transaction include in restore, SQL 2000, 1343 restore up to, SQL 2000, 1343, 1347 navigation list boxes, 1580 tabbed pages, 1579 navigation bar, overview, 129 NDMP Option backing up data with, 1570 backing up resources, 1571 installing, 1570 overview, 1569 requirements, 1569 resources, 1571 restoring data, 1573 Net Send, configuring recipients, 565, 1089 network changing a backup network for a job, 322 overview of backup networks, 316 setting up a backup network, 318 Network Attached Storage (NAS), protecting, 1569 network traffic, reducing in CASO, 770 network user data folder, creating, 1041 nodes configurations in a Microsoft cluster, 704 defined, 691 disaster recovery using IDR, 732 Microsoft adding or removing a failover node, 701 changing the order in which nodes fail over, 701 nonlogged operations occurring in SQL 7.0, 1336 notification, recipients, 1081 notifications assigning alert categories, 572 assigning recipients to alerts, 572 clearing recipients, 572 configuring MAPI e-mail, 555 1613
configuring MAPI e-mail in DLO, 1078 configuring pager, 556, 1080 configuring SMTP e-mail, 553 configuring SMTP e-mail in DLO, 1077 configuring SNMP, 575 configuring VIM e-mail, 556, 1079 defined, 538 modifying recipient properties, 570 scheduling recipients, 569 selecting recipients for jobs or selection lists, 573 notifications (DLO) modifying recipient properties, 1094 nsf files backing up with DLO, 1141 NTFS cluster size, 679 partition, 678 numbering, specify for media label, 189 O offhost backup best practices, 859 efined, 1591 for Exchange Server, with Granular Recovery Technology (GRT), 865 host computer, defined, 855 List Snapshot Providers option, 861 overview, 855 requirements, 857 single volume snap, choosing, 863, 865 snapshot provider, choosing, 862, 864 staging location, for offhost GRT-enabled Exchange backup to tape, 313 transportable snapshots, defined, 855 VSFW FlashSnap option, using with, 858 offline media location adding media to, 203 defined, 199, 1591 offline, when devices display as, 345, 360, 392 off-site storage of backups, 660 online media location, 199, 1591 online, putting device back, 345, 360 open files backing up with AOFO, 809 unable to back up, 678 1614
Operations Overview report, 642 optimizing remote backups, 282 options default for job log, 473 Set Application Defaults Preferences, 136 options, additional Backup Exec options described, 53 Oracle Agent authentication for Oracle operations, 1386 back up with, 1390 channel time-out, change default for, 1409 configure, 1376 database time-out, change default, 1408 DBA-initiated backup, 1395 DBA-initiated job settings, create template for, 1396 DBA-initiated jobs, job template name for, 1379, 1384 DBA-initiated restore, 1401 defaults for backup and restore operations, 1398 features, 1375 install, 1376 legacy GRFS Oracle Agent database backups restore from, 1407 Linux, configure instances on, 1382 logon account, enter on Remote Agent Utility, 1380 media server authentication on Remote Agent Utility, 1380 multiple data streams,specify, 1394 Oracle instances in CASO, 1391 Oracle Net Service name, 1379 port, configure for DB2 and Oracle operations, 1381, 1385 publish Oracle databases on Linux, 1384 Real Application Cluster (RAC), 1381, 1384, 1391 recovery catalog, 1379, 1384 redirected restore, 1405 restore, 1399 troubleshooting, 1408 update credentials for instances, 1379, 1383, 1390 Administrators Guide
upgrade, 1389 Windows, configure database access on, 1380 Windows, configure instance on, 1377 Oracle instances Linux, configure on, 1382 Windows, configure on, 1377 Outlook PST files, backing up with DLO, 1140 overwrite default media label, 188 overwrite media option, specifying for backup job, 273 overwrite protection levels full, 187 none, 187 partial, 187 overwrite protection period defined, 172, 177, 1591 setting for media set, 177 overwrite protection, disabling, 187 P pager configuring recipients, 562, 1085 notification method, 556, 1080 partial overwrite protection, 187 partition creating for robotic library, 363 FAT, 679 NTFS, 678 redefining for robotic library, 366 pass phrases, 333 password database, Remote Agent for NetWare Servers, 904 pausing device, 354 performance, increase during backups of remote Windows computers, 888 physical check, SQL 2000, 1320, 1329 PHYSICAL_ONLY utility, 1322 placing scheduled job on hold if test run fails, 306 point in time log restore option SQL Agent, 1343, 1346 policy adding a backup template, 430 adding a duplicate backup sets template, 444 adding an export media template, 433 changing template rules, 439 Index
copying to another server, 448 creating jobs, 440 creating manually, 424 creating synthetic backup using the Policy Wizard, 838 creating true image restore, 850 creating using the Policy Wizard, 425 defined, 1591 deleting, 426 deleting a template, 436 deleting jobs created from policies, 442 deleting template rules, 439 duplicate backup sets template overview, 443 editing a template, 435 importing templates, 434 overview, 423 setting template schedules, 432 template rules, 436 using an example policy, 427 using templates, 429 Policy Jobs by Resource Summary report, 644 Policy Jobs Summary report, 645 Policy Properties report, 647 Policy Protected Resources report, 647 portal support, 380 ports used by Backup Exec, 327 post-job command setting for backup job, 285 setting for restore job, 508 prefix, creating for media label, 188 pre-job command setting for backup job, 284 setting for restore job, 508 preserve tree option for backup job, 277 for restores, 504 primary database server, defined, 1592 primary server defined, 1545 printer, configuring recipients, 566, 1091 priority Automated User Assignment, changing in DLO, 1031 changing for scheduled job, 463 for selection lists, 250 options in DLO, Move, 1031 setting for devices in pools, 414 setting for drives in pools, 394 1615
setting for restore job, 503 Problem Files report, 648 Process logical volumes for backup one at a time, with Exchange Agent, 1192 profile (DLO) back up on log on/off option, 1048 copying, 1000 creating, 988 defined, 949 edit schedule, 997 logging options, 997, 1049 prompt before overwriting allocated or imported media, 187 properties active job, 451 alerts, 542 Lotus Domino, 1301 media general, 210 statistical, 213 report, 611 user, changing in DLO, 1044 PST files, backing up with DLO, 1140 publish default interval, 893 disable on remote computer, 893 to media servers, using Remote Agent for Windows Systems, 892 Q QuickStart Edition of Backup Exec, described, 48 R RALUS.CFG about, 922 editing, 922 format components, 922 reassigning how slots appear, 361 Recently Written Media report, 649 recipients assigning alert categories, 572 clearing recipients, 572 configuring, 561 configuring groups, 568 configuring MAPI e-mail, 560 configuring Net Send, 565 configuring new for jobs or selection lists, 573 configuring pager, 562, 566, 1091 1616
configuring SMTP, 558 defined, 557 selecting for notifications, 573 recipients (DLO) configuring groups, 1092 configuring MAPI e-mail, 1083 configuring Net Send, 1089 configuring pager, 1085 configuring SMTP, 1081 configuring SNMP Trap, 1088 configuring VIM e-mail, 1084 recipients(DLO) defined, 1081 Recovered Jobs custom error-handling rule, 486 recovering jobs, threshold for, 491 recovery password, setting in DLO, 962 recovery points default interval in Exchange, 1206 in Exchange, overview, 1206 setting in Exchange, 1214 recovery requirements in IDR, 1519 Recovery Storage Group, 1225 recyclable media, defined, 1592 redirected restore Exchange data, 1238 SAP data, 1429 using to install Domain Controllers from Media, 529 redirecting scheduled jobs, 416 Remote Administrator running, 100 system requirements, 100 remote administrator defined, 1592 Remote Agent for Linux or UNIX Servers installation overview, 917 manual install and uninstall, 931 manually starting the RALUS daemon, 932 manually stopping the RALUS daemon, 933 requirements, 916 setting Linux/Unix properties, 925 uninstalling, 927 using, 924 using the Installer, 918 Remote Agent for Macintosh Systems backup job properties, 943 Administrators Guide
installation overview, 936 manually starting the RALUS daemon, 946 manually stopping the RALUS daemon, 947 RALUS.CFG about, 940 editing, 940 format components, 941 requirements, 936 uninstalling, 945 using the installer, 937 Remote Agent for NetWare Servers AUTOEXEC.NCF file, 903 backing up BEDIAG.NLM utility, 912 create BEDIAG.FAX, 912 decompressed files, 911 password database, 904 rights for backup, 904, 905 single server backup strategies, 905 strategies for multiple administrators, 906 strategies for single administrator, 906 installing, 901 overview, 899 restoring, 909 system requirements, 900, 901, 910 Remote Agent for Windows Systems hardware requirements, 888 installing 64-bit using the installation program, 95 installing on a Microsoft cluster, 694 installing on a VERITAS cluster server, 723 installing on x-64 based operating systems, 95 installing using command script, 97 installing using the command line, 96 license keys, 888 publish to media servers, 892 Remote Agent Utility, 890 stopping, 889 uninstalling using the command line, 97 Remote Agent Utility command line applet, 895 DB2 archive logs job template name, Index
adding, 1445 DB2 DBA-initiated job template name, adding, 1444 DB2 instance, configure for database access, 1380 DB2 instances, configuring for database access, 1445 DB2 instances, configuring information about, 1443 default publishing interval, 893 Event Viewer, open, 890 job template name for DBA-initiated jobs, 1384 Linux, configure Oracle instance on, 1382, 1384 Oracle instances, configure logon account for, 1380 Oracle instances, media server authentication for, 1380 port, configure for DB2 and Oracle operations, 1381, 1385 port, configuring for DB2 and Oracle operations, 1447 publish to media servers, 892, 893 Real Application Cluster (RAC), publish to media server, 1381 refresh interval, 892 Registry Editor, open, 890 Services, open, 890 start the utility at log on, 892 update credentials for Linux instances, 1383 view status, 891 Windows, configure Oracle instance on, 1377, 1380 remote agent, defined, 1592 remote storage backing up, 282 remote storage, back up data, 282 renaming cascaded drive pools, 422 device pools, 417 libraries and drives in shared environment, 1552 media labels, 195 robotic library or device, 355 vault, 202 replicated catalog defined, 1592 1617
in CASO, 781 reports active alerts, 618 Active Alerts by Media Server, 618 alert history, 619 application event log, 621 audit log, 621 available in Backup Exec, 613 Backup Job Success Rate report, 622 Backup Set Details by Resource, 623 backup sets by media set, 624 Backup Size by Resource, 625 configuration settings, 626 Daily Device Utilization, 628 deleting in job history, 591 device summary, 628 Device Usage by Policy, 629 Event Recipient, 632 Failed Backup Jobs, 632 Job Distribution by Device, 633 Jobs Summary, 634 Machines Backed Up, 634 Managed Media Servers, 635 media audit, 637 media errors, 637 Media Required for Recovery, 638 media set, 638 media vault contents, 639 Missed Availability, 640 Move Media to Vault, 641 operations overview, 642 overview, 583 Policy Jobs by Resource Summary, 644 Policy Jobs Summary, 645 Policy Properties, 647 Policy Protected Resources, 647 Problem Files, 648 Recently Written Media, 649 Resource Backup Policy Performance, 649 Resource Risk Assessment, 650 Restore Set Details by Resource, 651 Retrieve Media from Vault, 652 running, 584 running job, 587 saving, 590 Scheduled Server Workload, 654 scheduling report jobs, 591 Scratch Media Availability, 654 1618
setting notification recipients, 591 test run results, 656 viewing, 584 viewing in job history, 589 viewing properties, 611 reports (DLO), 1096 running, 1097 viewing, 1096 requirements Central Admin Server Option, 747 Exchange Agent, 1180 Lotus Domino Agent, 1294 NDMP Option, 1569 SAN Shared Storage Option, 1547 system, for Backup Exec, 69 reset accounts option, in DLO Desktop Agent, 1127 Reset Cleaning Statistics, 351 reset dialogs option, in DLO Desktop Agent, 1127 resource credentials, changing for restore job, 527 defined, 1592 order, changing, 269 Resource Backup Policy Performance report, 649 resource discovery creating job, 255 defined, 1592 used with Exchange Agent, 1181 Resource Risk Assessment report, 650 responding to active alerts, 545 Restore dialog box DLO Desktop Agent, 1160 restore job Advanced File Selection, 522 advanced options, 505 canceling, 535 copying to another server, 448 creating through dialog boxes, 498 creating with wizard, 497 file permissions, 511 general options, 503 Lotus Domino options, 1306 over existing files, 503 pre/post commands, 508 preserve tree option, 504 redirecting, 528 Administrators Guide
redirecting Lotus Domino, 1307 redirecting SAP data, 1429 security, 504 Selections options, 500 setting defaults, 531 Restore Job Properties dialog box, SQL Agent, 1340 Restore Set Details by Resource report, 651 restore to named instance, 1356 restoring ARCserve tapes, 517 byte count does not match, 680 creating a selection list, 520 Distributed file system (Dfs), 517 encrypted data, 338 Exchange data, 1224 files, using DLO Administration Console, 1055 files, using DLO Desktop Agent, 1159 Lotus Domino Agent, 1304 media view, 493 Microsoft clusters cluster quorum for Windows 2000 and Windows Server 2003, 718 cluster quorum on node running Active Directory, 719 Windows 2000/2003, 717 NDMP data, 1573 Remote Agent for NetWare Servers volume restrictions, 912 resource view, 493 searching for files, 524 selecting data, 519 SQL master database, 1352 using the media view, 519 using the resource view, 519 VERITAS clusters Windows 2000 and Windows Server 2003, 730 with Backup Exec Retrieve, 1163 restricted encryption key defined, 1592 restricted encryption keys defined, 332 resuming a device, 354 retargeting job, 416 retensioning a tape, 372 retired media defined, 171, 1592 Index
moving damaged media, 208 Retrieve Media from Vault report, 652 returning to a previous configuration, 661 revisions deleting automatically in Desktop Agent, 1137 deleting automatically in DLO, 1011 number to keep, setting in Desktop Agent, 1136 number to keep, setting in DLO, 1009, 1136 Revision Control tab, Desktop Agent, 1136 Revision Control tab, DLO, 1009 revisions (DLO), 1008 RMAN backing up with SAP Agent, 1430 restoring with SAP Agent, 1432 using SAP Agent with, 1419 using to protect SAP for Oracle databases, 1417 robotic library cleaning jobs, 377 configuring, 357 configuring partitions, 363 creating partitions, 363 displaying storage devices, 1540 example configuration, 1539 importing media, 378 initialization on startup, 361 lock front panel, 381 portal support, 380 problem with not displaying, 676 redefining partitions, 366 setting up hardware, 1538 unlock front panel, 383 using with Backup Exec, 355 viewing, 1541 robotic library properties Configuration tab, 361 General tab, 359 SCSI Information tab, 362 robotic library sharing between Windows and NetWare servers, 1553 prerequisites, 1553 S SAN Shared Storage Option (SSO) 1619
device allocation, 1549 device operations, 1552 installing, 1548 requirements, 1547 SAP Agent about disaster recovery, 1437 backing up with RMAN, 1430 before backing up, 1424 database server, restoring remote server, 1438 database, system level backup jobs, 1428 disaster recovery requirements, 1437 features, 1418 how it works, 1418 installing, 1421 overview, 1417, 1418 privileges, 1422 requirements, 1420 restoring with RMAN, 1432 security, 1422 submitting jobs from remote computers, 1429 using for backups and restores, 1428 SAP Agent catalog manually migrating, 1433 migrating from _backint.mdb to _backint.xml, 1433 preserving integrity, 1423 restoring, 1423 schedule, exclude dates from, 296 scheduled jobs changing priority, 463 configuring, 286 configuring default options, 297 deleting, 465 hold, 462 modifying, 457 removing hold, 462 running immediately, 461 running test job, 464 viewing, 457 Scheduled Server Workload report, 654 scheduling automatic updates using LiveUpdate, 118 backup jobs in Desktop Agent, 1143 backup jobs in DLO, 995, 1048 notification recipients, 569 1620
report jobs, 591 SAN SSO jobs, 1557 setting for templates, 432 scratch media creating, 186 defined, 171 Scratch Media Availability report, 654 scratch media, defined, 1593 SCSI address for devices, 1538 information about devices, 349 information about robotic library, 362 setting address for robotic library drives, 1538 SCSI bus, configuring for tape devices in a Microsoft cluster, 707 SCSI pass-through mode, setting for devices, 349 search catalogs, 524 log file history, 1070 Section 508 of the Rehabilitation Act, compliance, 1577 security changing for Windows systems, 65 restoring, 504 security options changing, 322 setting defaults, 318 select into/bulk copy option, SQL 7.0, 1336 selecting devices and data to back up, 231 selection list defined, 1593 selection lists configuring new recipients, 573 copying to another server, 448 creating, 244 creating separate for each computer or resource, 252 defined, 243 deleting, 247 editing, 248 excludes, 249 holding jobs that back them up, 246 merging and replacing, 246 notification, 243 searching, 254 selecting recipients for notifications, 573 Administrators Guide
setting priority and availability, 250 selections Desktop Agent, backup, 1130 DLO, backup, 1001 options for backup job, 269 user-defined, adding, 239 user-defined, using TCP/IP addresses, 239 selections lists set up notification, 245 server list adding and removing servers, 115 manually update for NetWare, 912 server properties viewing, 140, 141, 142, 143 viewing media server information, 140 service account changing, 115 service credentials in DLO, managing, 964 service state, 258 services starting and stopping, 114 starting and stopping on multiple servers, 1562 Set Application Defaults, Preferences, 136 Set Remote Agent Priority, 282 setting notification recipients for reports, 591 Shadow Copy Components file system, 258 upgrading backup jobs to version 12, 261 shared catalogs, using, 1545 SharePoint Agent about, 1251 adding a server farm, 1264, 1280 backing up folders and documents from a portal workspace, 1255 backing up SharePoint Portal Server 2003 resources, 1267 best practices for SharePoint Portal Server 2001, 1262 changing the default name of a farm, 1266 default backup and restore options, 1276 deleting a farm, 1266 disabling or enabling communication between Web servers and Backup Index
Exec, 1265 disaster recovery, 1260 installing, 1252 overview, 1251 redirecting restore jobs, 1258 redirecting restore jobs for SharePoint Portal Server 2003, 1273 redirecting workspace data to a file path, 1260 redirecting workspace data to another workspace, 1259 requirements, 1252 restoring a SharePoint Portal Server, 1256 restoring a SharePoint Portal Workspace, 1256 restoring a SharePoint Server 2007 Web application, 1286 restoring SharePoint Portal Servers and Workspaces, 1255 selecting SharePoint Portal Server 2003 resources for backup, 1263 system requirements, 1252 uninstalling and reinstalling the SharePoint Portal Server software, 1262 using with SharePoint Portal Server 2003, 1263 using with SharePoint Server 2007, 1278 SharePoint Portal Server disaster recovery, 1260 redirecting restore jobs, 1258 redirecting SharePoint Server 2007 Web application restores, 1288 SharePoint Services, 259 sharing a backup-to-disk folder, 398 sharing media, 1545, 1558 silent install of DLO, 958 silent mode installation, 61, 101 simple recovery model, SQL 2000, 1316 single block mode, setting for devices, 348 single instance backup for NTFS, 280 Site Replication Services (SRS) database, backing up, 1188 size, cluster, 679 slot base configuration, 361, 1542 Small Business Server Edition of Backup Exec, described, 48 1621
SMTP configuring e-mail recipients, 558 e-mail notification method, 553 e-mail notification method in DLO, 1077 Snap Start, for VSFW volumes, 821 snapshot technology used in Advanced Open File Option, 809 using with Exchange Agent, 1191 SNMP configuring notification, 575 configuring system service for Windows 2000, 579 installing WMI provider, 580 object identifier prefix, 575 traps, defined, 575 WMI, 580 SNMP Trap configuring e-mail recipients, 1081 configuring recipients, 1088 notifications, 1088 software license agreement, 99 son media rotation strategy, 217 Specified Backup Network feature configuring, 318 described, 316 specify a date and time for restoring named transaction, 1343 splash screen, show at startup, 136 SQL 2000 disaster recovery, 1369 disaster recovery preparation, 1367 filegroups, 1348 Guide Me wizard, 1330 Intelligent Disaster Recovery (IDR) option, 1367 loading state, 1329 named transaction, 1347 named transaction, include, 1343 named transaction, restoring to a, 1343 physical check after backup, 1320 primary and nonprimary filegroups, 1344 restoring to named instance, 1356 simple recovery models, 1316 standby database, 1315 standby mode, 1329 SQL 7.0 1622
agent features, 1316 nonlogged operations occurring, 1336 select into/bulk copy option, 1336 truncate log on checkpoint option, 1336 SQL Agent backing up backup methods, 1327 consistency check after backup, 1329 consistency check recommendations, 1320 databases, 1331 filegroups, 1334 strategies for, 1319 transaction logs, 1337 Windows registry, 1320 Backup Job Properties dialog box, 1326 consistency check, recommendations, 1320 Database Consistency Check (DBCC), recommendations, 1320 default options, 1361 excluding files during volume level backups, 1331 features, 1315 installation, 875, 1317 logon accounts, 1317 overview, 1315 requirements, 1317 restoring automate master database restore, 1341 create standby database, 1340 database files to target instance, 1357 filegroups, 1348 Guide Me wizard, 1343 master database, 1352 point in time log restore option, 1346 redirecting restores, 1354 Redirection dialog box, 1355 Restore Job Properties dialog box, 1340 specify date and time for named transaction, 1343 very large databases, 1345 transaction logs, 1336 SQL database backups, restoring Administrators Guide
from, 1345 SQL Server, 953 staging data, 443 stalled job status, threshold for, 491 standby database creating SQL Agent, 1340 SQL 2000, 1315 starting Backup Exec, 126 services, 1562 starting, Desktop and Laptop Option (DLO), 982 statistical properties for media, 213 statistics device usage, 350 devices, since cleaning, 351 Status tab for a robotic library, 363 stopping services, 1562 storage devices installing, 62 storage limits for user data Desktop Agent, 1146 DLO, 990 Storage Location (DLO), 1021 defined, 949 deleting, 1027 Symantec Backup Exec for Windows Servers, described, 47 Symantec Device Driver Installation Wizard, 342 Symantec Endpoint Protection creating backup jobs for, 325 using with Backup Exec, 324 viewing a summary of, 485 Symantec Volume Snapshot Provider changing defaults, 822, 824 with AOFO, 817 synchronization (DLO) create new sets, 1152 overview, 1151 synchronization(DLO) delete synchronized folder, 1154 Synchronized Selections view, in DLO Desktop Agent, 1151 synthetic backup baseline, 832 creating, 838, 839 defined, 1593 Index
encryption, requirements for, 835 requirements, 835 template rules, 844 template rules, example, 839 system logon account, 148 system requirements Backup Exec, 69 System State, restoring, 512 System Summary, viewing, 485 T tabbed dialog boxes, navigation, 1579 tapeinst.exe, Symantec Device Driver Installation Wizard, 342 tapes, DLT tape drive, 677 target domain, defined, 66 task pane, overview, 129 TCP/IP adding for user-defined shares, 239 required for RALUS Agent, 916 required for RAMS agent, 936 templates adding a duplicate backup sets template to policies, 444 adding an export media template to a policy, 433 adding backup templates to a policy, 430 backup template file exclusions, 431 changing template rules, 439 defined, 1593 deleting from a policy, 436 deleting template rules, 439 duplicate backup sets template overview, 443 editing in a policy, 435 importing into a policy, 434 rule, defined, 1593 setting template rules, 436 setting the schedule, 432 using in policies, 429 test run job creating, 304 defined, 303 running for scheduled job, 464 setting defaults, 305 Test Run Results report, 656 testing logon accounts, 270 ThreatCon levels, 324, 325 1623
to a local computer, 71 transaction logs Lotus Domino DBIID, 1300 overview, Lotus Domino, 1300 recycling, Lotus Domino, 1302 viewing Lotus Domino, 1296 transaction logs, backing up SQL Agent, 1336 troubleshooting clusters, 738 true image restore CASO and, 850 creating a policy for, 850 defined, 1593 icons, 852 overview, 846 requirements, 849 troubleshooting, 853 true image catalogs, 851 truncate log on checkpoint option, SQL 7.0, 1336 U unattended backup jobs, 418 uninstalling Backup Exec, 115 Backup Exec from a Microsoft cluster, 696 using command line, 108 Windows Management Instrumentation SNMP provider, 580 Unique Message Identifier (UMI) error code defined, 1593 viewing, 470, 546 unlock, robotic library panel, 383 Update vault using wizard, 206 updating, DLO, 976 USB tape devices, reconnecting, 341 User Data Folder in DLO, 1021 User Properties dialog box in DLO, 1044 user-defined media vault, 199 adding media to, 203 creating, 200 user-defined selections about, 238 adding, 238 Users properties, changing in DLO, 1044 removing from DLO, 1045 1624
viewing in DLO, 1048 users access, disabling/enabling in DLO, 1044 adding in DLO, 1042 Desktop Agent access via profile, 1121 import in CSV file in DLO, 1043 managing in DLO desktop agent, 1041 using RMAN to protect SAP for Oracle databases, 1417 utility jobs, overview, 367 utility partitions backing up in IDR, 1508 restoring, 515 selecting for backup, 234 V vault drag and drop, to move media, 206 finding media, 201 moving media to, 202 scan bar code labels to move media, 203 scheduling a job to move media, 204 Vault Wizard, to move media, 205 vault rules for media sets, 200 Vault wizard, 206 vaults, moving media, 206 verify after backup completes, 278 after duplicate backup completes, 300, 843 verify job creating, 302 defined, 302 VERITAS clusters Windows 2000/2003, 727 version and build information, displaying, 685 view history, 254 viewing active alerts, 538 active job properties, 451 alert history, 538 alert job log, 544 alert properties, 542 alerts, 539 Automated User Assignment properties in DLO, 1031 completed job, 466 job monitor, 450 Administrators Guide
job workload from the calendar, 483 jobs, 1557 Lotus Domino databases, 1296 Lotus Domino transaction logs, 1296 scheduled jobs, 457 system summary, 450 users in DLO, 1048 views, alerts, 538 VIM configuring recipients, 561, 1084 e-mail notification method, 556, 1079 virtual devices, using in IDR, 388 virtual machines about, 260 backing up, 301 Virtual Server Host, 301 Virtual Server Host about, 260 backing up, 301 virtual servers, backing up in a Microsoft cluster, 716 virtual servers, backing up in a VERITAS cluster, 729 virus, effect on data storage requirements, 223 volume level backups, automatic exclusion of files, 1331 volume restrictions, Remote Agent for NetWare Servers, 912 VSS perform consistency check before Active Directory backup, 877, 878 perform consistency check before Exchange backup, 1215 using to protect Exchange data, 1191
W Window menu, 1581 Windows Automated System Recovery (ASR) files, in IDR, defined, 1503 Windows Change Journal option to use for backup job, 277 using to determine backed up status, 230 Windows Management Instrumentation (WMI), adding WMI capability, 580 Windows registry, backing up with SQL Agent, 1320 Windows Server 2003 backing up, 258 disaster recovery, 664 Windows Server 2008 backing up, 258 Read Only Domain Controller, 69 Server Core, 69 Windows XP, disaster recovery, 664 wizard for DLO, configuration, 987 WMI installing performance counter provider, 580 installing SNMP provider, 580 performance counters, 580 uninstalling SNMP provider, 580 working set back up files changed today, defined, 1593 back up files last accessed in (x) days, defined, 1594 backups, defined, 225
Index
1625
1626

Backup Exec 2012 Administrators Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Backup Exec 2012 Administrators Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Symantec Backup ExecTM 12 for Windows Servers

12666659 November 2007

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Introducing Backup Exec

Backup Exec Edition Symantec Backup ExecTM for Windows Servers

Backup Exec Edition Small Business Server Editions (SBSE)

Whats new in Backup Exec

Whats new in Backup Exec

Chapter 1, Introducing Backup Exec

Chapter 1, Introducing Backup Exec

Whats new in Backup Exec

Whats new in the Advanced Disk-based Backup Option

Whats new in the Desktop and Laptop Option

DLO Administration Server DLO Maintenance Server

Support for Microsoft Windows Vista

Pictures Music Video

Backup Exec agents and options

Backup Exec agents and options

Media server options

Chapter 1, Introducing Backup Exec

See About the Active Directory Recovery Agent on page 875.

Backup Exec agents and options

Client protection options

Chapter 1, Introducing Backup Exec

Backup Exec agents and options

Backup Exec agents and options

Online database agents

Chapter 1, Introducing Backup Exec

Backup Exec agents and options

Disaster recovery option

How Backup Exec works

How Backup Exec works

Backup Exec media server

Chapter 1, Introducing Backup Exec

How Backup Exec works

Installing Backup Exec

Before you install

Before you install

Checking your environment before installing

Before you install

One of the following results are reported for each item:

Chapter 2, Installing Backup Exec

Before you install

To add the name of a computer manually

About the Backup Exec services account

Before you install

Manage auditing and security log.

Changing Windows security

Chapter 2, Installing Backup Exec

Before you install

Before you install

Chapter 2, Installing Backup Exec

Before you install

About Backup Execs standard features