Be Admin

VERITAS Backup Exec for Windows Servers
Administrators Guide
October 2002 N096948
Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. Copyright Copyright October 2002 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, VERITAS Backup Exec for Windows Servers, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the USA and/or other countries. Other product names mentioned herein may be trademarks or registered trademarks of their respective companies. October 2002 VERITAS Software Corporation 350 Ellis Street Mountain View, CA 94043 USA Phone 6505278000 Fax 6505272908 www.veritas.com
Administrators Guide - Table of Contents

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Chapter 1. Introducing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Whats New in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Backup Exec Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 How Backup Exec Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Chapter 2. Installing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Changing Windows Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Installing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Installing Backup Exec Using the Installation Program . . . . . . . . . . . . . . . . . . . . . . . 47 Installing Backup Exec Options on a Local Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Installing Backup Exec Media Servers to Remote Computers . . . . . . . . . . . . . . . . . 51 Installing Backup Exec Remote Agents and Options on Remote Servers . . . . . . . . 54 Installing Backup Exec from the Command Line (Silent Mode) . . . . . . . . . . . . . . . . 56 Registering Backup Exec Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Repairing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Starting and Stopping Backup Exec Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Uninstalling Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Installing the Backup Exec Remote Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Using VERITAS Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Upgrading from Previous Versions of Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Upgrading Backup Exec Options on Remote Computers . . . . . . . . . . . . . . . . . . . . . . . . 71
1
Chapter 3. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Before Starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 First Time Startup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Using the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Using Backup Exec Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Using the Overview View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Using the Backup Exec Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Backup Exec Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Changing Default Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Changing General Job Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Chapter 4. Managing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Viewing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Viewing Media Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Configuring Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Hot Swap for Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Pausing, Resuming, and Renaming Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Using Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Creating Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Adding Drives to a Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Setting Priorities for Drives in a Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Deleting Drives from a Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Deleting Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Retargeting Jobs from a Deleted Drive Pool or Media Set . . . . . . . . . . . . . . . . . . . 103 Renaming a Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Viewing Drive Pool Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Using Cascaded Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Requirements for Using Cascaded Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Adding Drives to a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Deleting Drives from a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Deleting a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Renaming a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Viewing Properties of a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Viewing Server Properties and Running Server Diagnostics . . . . . . . . . . . . . . . . . . . . 112 Viewing and Using Drive Properties and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Viewing General Drive Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Viewing Drive Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Viewing Drive SCSI Information Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Viewing Drive Statistics Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Viewing Drive Cleaning Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Viewing and Specifying a Drives Media Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Using Robotic Libraries with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Configuring a Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Viewing Properties of a Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Creating Robotic Library Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Redefining Robotic Library Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Using Backup-to-Disk Folders and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Adding a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Renaming a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Changing the Path of a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Deleting a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Recreating a Backup Folder and Its Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Pausing and Resuming a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Viewing Backup Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Renaming a Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Deleting a Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Recreating a Deleted Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Administrators Guide - Table of Contents 3
Viewing and Changing Backup File Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Using Microsofts Removable Storage Feature with Backup Exec . . . . . . . . . . . . . . . 161 Using Media in Drives Managed by Removable Storage . . . . . . . . . . . . . . . . . . . . 162 Creating Utility Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Inventorying Media in Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Erasing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Erasing Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Retensioning a Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Formatting Media in a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Labeling Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Ejecting Media from a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Setting Up Cleaning Jobs for Robotic Library Drives . . . . . . . . . . . . . . . . . . . . . . . 178 Importing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Exporting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Locking the Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Unlocking the Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Chapter 5. Managing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Media Overwrite Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Default Media Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Media Overwrite Protection Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Media Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Media Overwrite Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Media Append Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Overwriting Allocated or Imported Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Removing Damaged Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Media Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Imported Media Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Bar Code Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Renaming Media Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Setting Default Media Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Media Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Creating User-defined Media Vaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Finding Media in a Location or Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Renaming a User-defined Media Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Adding Media to the Offline Location or a User-Defined Vault . . . . . . . . . . . . . . . 211 Moving Media by Dragging and Dropping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Deleting a User-defined Media Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Media Rotation Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Son Media Rotation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Father/Son Media Rotation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Grandfather Media Rotation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Running the Media Rotation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Media Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Deleting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Moving Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Viewing General Media Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Viewing Media Management Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Viewing Media Statistical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Viewing Media Cleaning Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Media Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Running the Media Set Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Creating Media Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Deleting a Media Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Renaming a Media Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Editing and Viewing Media Set Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Chapter 6. Backing Up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Creating a Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Using the Backup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Creating a Manual Backup Job by Configuring Job Properties . . . . . . . . . . . . . . . 236 Selecting Data to Back Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 About Selecting Distributed File System (Dfs) Links for Backup . . . . . . . . . . . . . 261 Including or Excluding Files for Backup Using Advanced File Selection . . . . . . 262 Changing the Order for Processing Backup Selections . . . . . . . . . . . . . . . . . . . . . . 265 Changing Logon Accounts for Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Using Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Creating Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Using Selection Lists to Create a Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Merging and Replacing Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Deleting Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Editing Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 About the Excludes Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Setting Up User-defined Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Using Backup Job Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Creating a New Backup Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Editing a Backup Job Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Creating a Copy of a Backup Job Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Creating a New Backup Job from a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Reapplying a Template to Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Using Backup Execs Windows Explorer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Specifying or Changing Backup Settings for Windows Explorer . . . . . . . . . . . . . 287 Submitting a Backup Job from Windows Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 290 Running a One-button Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Archiving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Archiving Data Using Disk Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Using Resource Discovery to Search for New Resources . . . . . . . . . . . . . . . . . . . . . . . 295
6 Administrators Guide
General Options for Resource Discovery Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Resources Options for a Resource Discovery Job . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Duplicating Backed Up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 General Options for a Duplicate Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Advanced Options for a Duplicate Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Verifying a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Creating a Test Run Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 General Options for Test Run Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Setting Test Run Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Setting Default Backup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Setting Default Pre/Post Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Specifying Backup Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Specifying the Default Backup Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Changing the Backup Network for a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Using Backup Exec with Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Browsing Systems Through a Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Protecting Windows.NET Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Backing Up Utility Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Backing Up NetWare Network Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 About Backup Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Choosing a Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Understanding Backup Methods and Their Advantages . . . . . . . . . . . . . . . . . . . . 340 Understanding the Archive Bit and Backup Methods . . . . . . . . . . . . . . . . . . . . . . . 344 Understanding Modified Time and Backup Methods . . . . . . . . . . . . . . . . . . . . . . . 345
Chapter 7. Administrating Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Configuring Logon Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Default Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Backup Exec System Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Creating a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Editing a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Replacing a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Deleting a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Changing Your Default Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . 355 Creating a New Backup Exec System Logon Account . . . . . . . . . . . . . . . . . . . . . . . 355 Viewing and Clearing the Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Scheduling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Editing the Job Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Configuring Default Schedule Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Configuring Holiday Scheduling for Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Viewing and Filtering Jobs in the Job List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Viewing and Filtering Jobs in the Calendar View . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Viewing and Changing Active Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Viewing and Modifying Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Viewing Completed Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Error-Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Configuring Error-Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 Configuring Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Using ExecView in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Configuring ExecView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Chapter 8. Restoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 Restore Operations and the Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Cataloging Media in a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Setting Catalog Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Catalog Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Restoring Data to a Server or Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 Using the Restore Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 Creating a Manual Restore Job by Configuring Job Properties . . . . . . . . . . . . . . . . 404 Restoring File Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Restoring System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Restoring Utility Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Restoring Distributed File System (Dfs) Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 Restoring Media Created With Other Backup Software . . . . . . . . . . . . . . . . . . . . . 425 Selecting Data to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Using the Resource View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Using the Media View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Changing Resource Credentials for Restore Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 Using Advanced File Selection to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 Searching for Files to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Restore Operations and Media Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Redirecting a Restore Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Using Redirected Restore to Install Domain Controllers from Media . . . . . . . . . . 439 Setting Restore Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Specifying the Restore Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Canceling a Restore Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 Catalog Icon Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Chapter 9. Alerts and Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Viewing and Filtering Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 Viewing Alert Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Responding to Active Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Viewing the Job Log for Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 Clearing Informational Alerts from the Active Alerts Pane . . . . . . . . . . . . . . . . . . . . . 462 Enabling or Disabling Alerts from the Active Alerts Pane . . . . . . . . . . . . . . . . . . . . . . 462 Configuring Alert Category Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 Viewing and Clearing the Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 Deleting Alerts from the Alert History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 Configuring E-mail and Pager Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Configuring SMTP E-Mail for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Configuring MAPI E-Mail for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 Configuring VIM E-Mail for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 Configuring a Pager for Alert Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Configuring Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Configuring SMTP Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Configuring MAPI Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 Configuring VIM Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 Configuring a Pager for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Configuring a Net Send Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Configuring a Printer Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 Configuring a Group Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Scheduling Notification for Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Editing Recipient Notification Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 Editing Recipient Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 Removing Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Assigning Recipients to Alert Categories for Notification . . . . . . . . . . . . . . . . . . . . . . 491 Selecting Recipients for Job Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 Configuring SNMP Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Adding Windows Management Instrumentation Capability . . . . . . . . . . . . . . . . . . . . 499 Uninstalling WMI Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 Chapter 10. Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 Running and Viewing a New Report Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 Viewing Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 Available Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 Active Alerts Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 Alert History Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 Audit Log Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 Backup Sets by Media Sets Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 Configuration Settings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Device Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 Error-Handling Rules Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 Event Logs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 Media Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 Media Vault Contents Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 Operations Overview Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 Robotic Library Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 Scratch Media Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 Test Run Results Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 Chapter 11. Disaster Preparation and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 Key Elements of a Disaster Preparation Plan (DPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 Disaster Preparation of the Windows Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 Returning to the Last Known Good Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 Creating a Hardware Profile Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534 Creating an Emergency Repair Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 Using Windows Automated System Recovery and System Restore to Recover a
Windows XP or Windows .NET System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537 Creating and Using an Emergency Boot Diskette . . . . . . . . . . . . . . . . . . . . . . . . . . 537 Manual Disaster Recovery of Windows Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 Disaster Recovery of a Local Windows NT Computer . . . . . . . . . . . . . . . . . . . . . . 541 Disaster Recovery of a Remote Windows NT Computer . . . . . . . . . . . . . . . . . . . . 543 Disaster Recovery of a Local Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) . . . . . . . . 546 Disaster Recovery of a Remote Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) . . . . . . . . 549 Chapter 12. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 General Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 Hardware-related Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558 Backup Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 Restore Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Chapter 13. VERITAS Backup Exec - Workstation Agents . . . . . . . . . . . . . . . . . . 569 The Backup Exec Windows 98 and Windows Me Agents . . . . . . . . . . . . . . . . . . . . . . 570 Requirements for Running the Backup Exec Windows 98/Me Agent . . . . . . . . . 570 Installing the Backup Exec Windows 98/Me Agent on the Workstation . . . . . . . 571 Configuring the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . 572 Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 The Backup Exec Macintosh Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 Requirements for Running the Backup Exec Macintosh Agent . . . . . . . . . . . . . . . 578 Installing and Configuring the Macintosh Agent on a Mac OS X Workstation . . 579 Modifying the NetInfo Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 About the Backup Exec UNIX Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Requirements for Running the Backup Exec UNIX Agent . . . . . . . . . . . . . . . . . . . 584
Installing the Backup Exec UNIX Agent on the Workstation . . . . . . . . . . . . . . . . . 585 Configuring the Backup Exec UNIX Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 Chapter 14. VERITAS Backup Exec Command Line Applet . . . . . . . . . . . . . . . . . . 591 Command Line Applet Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 Using the Command Line Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 Using Command Line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 Switches Used With All Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 Backup Job Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 Switches for Administrating Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 Restore Job Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 Switches for Viewing and Responding to Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 Switches for Error Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 Switches for Managing Media and Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624 Backup Exec Services Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641 Logon Account Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642 Report Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643 Setting Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645 Using Backup or Restore Job Script Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 Creating a Backup Job Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 Creating a Restore Job Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686 Saving and Launching the Backup or Restore Job Script File . . . . . . . . . . . . . . . . . 704 Using Scripts and Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704 Creating a Selection List Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704 Using Scripts and Backup Job Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Creating a Backup Job Template Script File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Creating a Backup Job Template Using a Script File . . . . . . . . . . . . . . . . . . . . . . . . 729 Creating a Backup Job from a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 Using a Schedule Script with Device and Media Operations . . . . . . . . . . . . . . . . . . . . 730 Understanding Job Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
13
Chapter 15. Using VERITAS Backup Exec with Server Clusters . . . . . . . . . . . . . . 739 How Backup Exec Works in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740 Requirements for Installing Backup Exec on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . 741 Installing Backup Exec on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742 Installing Additional Backup Exec Options on a Cluster . . . . . . . . . . . . . . . . . . . . 743 Uninstalling Backup Exec From A Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744 Creating Drive Pools for Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745 Using Checkpoint Restart on Cluster Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746 Enabling or Disabling Checkpoint Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747 Specifying A Different Failover Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749 Designating a New SAN SSO Database Server in a Cluster . . . . . . . . . . . . . . . . . . . . . 751 Configurations for Backup Exec and Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752 Two-node Cluster with Locally-attached Storage Devices . . . . . . . . . . . . . . . . . . . 753 Two-node Cluster with Tape Devices on a Shared SCSI Bus . . . . . . . . . . . . . . . . . 754 Two-node Clusters on a Fibre Channel SAN with the SAN SSO . . . . . . . . . . . . . . 758 Four-node Clusters on a Fibre Channel SAN with the SAN SSO . . . . . . . . . . . . . 760 Backing Up Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762 Backing Up Windows 2000 and Windows.NET Features . . . . . . . . . . . . . . . . . . . . 763 Backing Up Local Disks in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764 Backing Up Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764 Backing Up Database Files in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765 Restoring Data To Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767 Restoring Windows 2000 and Windows.NET Features . . . . . . . . . . . . . . . . . . . . . . 767 Restoring the Cluster Quorum for Windows 2000 and Windows.NET Systems 768 Restoring the Cluster Quorum to a Windows 2000 or Windows.NET Node Running Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 769 Specifying a New Drive Letter for the Cluster Quorum Disk . . . . . . . . . . . . . . . . 771 Disaster Recovery of A Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773 Using IDR to Prepare for Disaster Recovery of A Cluster . . . . . . . . . . . . . . . . . . . 774 Recovering Nodes on the Cluster Using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
14
Recovering Backup Exec on a Cluster Using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . 775 Recovering the Entire Cluster Using a Manual Disaster Recovery Procedure . . . 776 Recovering the Cluster Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777 Recovering All Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778 Recovering Clustered Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 Troubleshooting Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 Chapter 16. VERITAS Backup Exec Web Administration Console . . . . . . . . . . . . . 781 Requirements for BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781 Installing BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782 Starting BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782 Differences Between BEWAC and Backup Exec for Windows Servers . . . . . . . . . . . . 782 Accessing Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 Navigating in BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785 Viewing, Clearing, and Responding to Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786 Chapter 17. Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787 Starting the Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789 Completing Tasks using the Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790 Running Backup Exec Utility General Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792 Add a New Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792 Create a New Media Server Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793 Delete a Media Server from the All Media Servers Subnode . . . . . . . . . . . . . . . . . 794 Delete a Media Server Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795 Run Backup Exec Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796 View Media Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797 Running Backup Exec Utility Services Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798 Stop Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798 Start Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Change Service Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799 Edit Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801 Running Backup Exec Utility SAN SSO Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804 Set the Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804 Remove the Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 Configure the SAN SSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806 Promote a Media Server to a Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . 806 Move the Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808 Running Database Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809 Check the Database Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810 Age the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810 Compact a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811 Dump a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811 Rebuild Media Server Database Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812 Repair a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812 Recover a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813 Change the SQL Server sa Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814 Change Database Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815 Running Media Server Group Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816 Add Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816 Remove a Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817 Running Cluster Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818 Edit Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818 Appendix A. VERITAS Backup Exec - Remote Agent . . . . . . . . . . . . . . . . . . . . . . 821 Requirements for the Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822 Installing the Remote Agent to Remote Windows Servers . . . . . . . . . . . . . . . . . . . . . . 823 Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823 Stopping and Starting the Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824 Backing Up Data in a Mixed Environment Using the Remote Agent . . . . . . . . . . . . . 825
Appendix B. VERITAS Backup Exec - Admin Plus Pack Option . . . . . . . . . . . . . . . 827 Installing the Admin Plus Pack Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827 Using a Clone CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828 Creating a Clone CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828 Installing Locally Using a Clone CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829 Installing to a Remote System Using a Clone CD Image . . . . . . . . . . . . . . . . . . . . . 830 Copying Jobs, Selection Lists, and Job Templates Between Servers . . . . . . . . . . . . . . 831 Advanced Reporting Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832 Scheduling Report Jobs and Setting Notification Recipients . . . . . . . . . . . . . . . . . . 835 Active Alerts by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835 Alert History by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836 Backup Job Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837 Backup Set Details by Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838 Backup Size By Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839 Backup Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840 Daily Job Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841 Daily Network Device Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842 Device Usage by Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843 Event Recipients Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843 Failed Backup Jobs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844 Job Distribution by Device Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845 Job Queue Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845 Job Templates Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846 Machines Backed Up Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847 Media Required for Recovery Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848 Move Media to Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849 Overnight Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849 Problem Files Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850 Recently Written Media Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851 Resource Risk Assessment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
Retrieve Media from Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853 Scheduled Server Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853 Template Definition Usage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854 Appendix C. VERITAS Backup Exec - Intelligent Disaster Recovery Option . . . 855 Requirements for Using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858 Installing the IDR Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858 Using an Evaluation Version of the IDR Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 859 Getting Started with IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859 Setting Data Paths for the *.dr Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862 Creating and Updating Recovery Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865 Choosing Generic or Current SCSI Drivers for Windows NT . . . . . . . . . . . . . . . . 867 Requirements for Running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . . 868 Running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870 Creating A Full Set of Diskettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871 Creating a Bootable CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875 Creating a Bootable Tape Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877 Creating the Intelligent Disaster Recovery Diskette Only . . . . . . . . . . . . . . . . . . . 879 Updating the Full Set of Disaster Recovery Diskettes . . . . . . . . . . . . . . . . . . . . . . . 881 Updating the Intelligent Disaster Recovery Diskette Only . . . . . . . . . . . . . . . . . . . 883 Updating Bootable Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886 Preparing IDR Media Via Other Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889 Using IDR to Recover a Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891 Changing Hardware in the Computer to be Recovered . . . . . . . . . . . . . . . . . . . . . 892 Using IDR To Recover IBM Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893 Using IDR To Recover Windows 2000 Computers . . . . . . . . . . . . . . . . . . . . . . . . . 893 Booting the Computer in an IDR Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894 Using the Windows Setup in an IDR Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897 Using the Disaster Recovery Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899 Altering Hard Drive Partition Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
18
Recovering Computers Requiring OEM-Specific SCSI Drivers . . . . . . . . . . . . . . . 904 Performing a Manual Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905 Performing Remote IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906 Microsoft SQL Server Recovery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 Microsoft Exchange Recovery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 SharePoint Portal Server Recovery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 Appendix D. VERITAS Backup Exec - SAN Shared Storage Option . . . . . . . . . . . . 911 Tips for Maintaining the Database Server and the ADAMM Database . . . . . . . . . 913 Requirements for the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . 914 Installing the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915 About Devices in the Shared Storage Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916 Monitoring Drives in the Shared Storage Environment . . . . . . . . . . . . . . . . . . . . . . 917 Viewing Media in the Shared Storage Environment . . . . . . . . . . . . . . . . . . . . . . . . 919 Using Drive Pools with the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . 920 Using Device Operations with the SAN Shared Storage Option . . . . . . . . . . . . . . 921 Sharing Robotic Libraries Between Backup Exec for NetWare and Backup Exec for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922 Scheduling and Viewing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929 Sharing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931 Cataloging Media in SAN SSO Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931 Media Rotation in SAN SSO Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932 Designating a New Database Server and Setting Up Servers . . . . . . . . . . . . . . . . . . . . 933 Starting and Stopping Backup Exec Services on Multiple Servers . . . . . . . . . . . . . 933 Troubleshooting and Recovering Failed Components . . . . . . . . . . . . . . . . . . . . . . . . . . 934 Checklist for Troubleshooting Devices That Have Gone Offline . . . . . . . . . . . . . . 934 Replacing a Fibre to SCSI Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936 Replacing the Hub or Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
19
Appendix E. VERITAS Backup Exec for Windows Servers ServerFree Option and Intelligent Image Option . . . . . . . . . . . . . . . . . . . . . . . . . . 939 The ServerFree Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939 Understanding ServerFree Backup Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939 ServerFree Backup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942 Installing the ServerFree option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944 Running the ServerFree Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945 Restoring A ServerFree Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947 The Intelligent Image Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948 Requirements for the Intelligent Image Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949 Installing the Intelligent Image Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949 Selecting the Intelligent Image Option for a Single Backup Job . . . . . . . . . . . . . . . 950 Selecting the Image Option as the Default for All Backup Jobs . . . . . . . . . . . . . . . 951 Checking the Job Log When Using An Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952 Restoring Files From An Intelligent Image Backup . . . . . . . . . . . . . . . . . . . . . . . . . 954 Appendix F. VERITAS Backup Exec for Windows Servers Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955 Understanding the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955 Snapshot Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956 Requirements for Using the Advanced Open File Option . . . . . . . . . . . . . . . . . . . 958 Installing the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959 Installing and Uninstalling the Advanced Open File Option to Remote Windows Servers Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . 960 Uninstalling the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961 Changing the Advanced Open File Option Default Settings . . . . . . . . . . . . . . . . . . . . 962 Using the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964 Selecting the Advanced Open File Option for a Single Backup Job . . . . . . . . . . . 964 Setting Advanced Open File Option as the Default Setting for All Backup Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966 Checking the Job Log When Using the Advanced Open File Option . . . . . . . . . . 968 Snap Starting a VERITAS Volume Manager Volume . . . . . . . . . . . . . . . . . . . . . . . . . . 969
Advanced Open File Option Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970 Appendix G. VERITAS Backup Exec - Agent for Microsoft SQL Server . . . . . . . 975
Requirements for Using the SQL Agent with SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . 976 Installing the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977 Using Backup Exec Logon Accounts for SQL 2000 Resources . . . . . . . . . . . . . . . . . . . 978 Backup Strategies for SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980 Consistency Checks for SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982 Using the Advanced Open File Option with SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . 983 Setting Backup Options for SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984 Backing Up SQL 2000 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988 Backing Up SQL 2000 Filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990 Backing Up SQL 2000 Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992 Restore Options for SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994 About Restoring SQL 2000 Databases and Filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . 999 Restoring from SQL 2000 Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001 Restoring from SQL 2000 Transaction Logs Up to a Point in Time . . . . . . . . . . . 1002 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction . . . . . . 1003 Restoring from SQL 2000 Filegroup Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004 Restoring the SQL 2000 Master Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007 Redirecting Restores for SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009 Setting Default Backup and Restore Options for SQL 2000 . . . . . . . . . . . . . . . . . . . . . 1012 Preparing for Disaster Recovery of SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018 Disaster Recovery of SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020 Manual Recovery of SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020 About the Agent for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024 Requirements for Agent for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025 Installing the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026 Using Backup Exec Logon Accounts for SQL 7.0 Resources . . . . . . . . . . . . . . . . . . . . 1027 Backup Strategies for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
21
Consistency Checks for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031 Setting Backup Options for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032 Backing Up SQL 7.0 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035 Backing Up SQL 7.0 Filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037 Backing Up SQL 7.0 Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039 Restore Options for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041 About Restoring SQL 7.0 Databases or Filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045 Restoring from SQL 7.0 Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047 Restoring from SQL 7.0 Transaction Logs Up to a Point in Time . . . . . . . . . . . . 1048 Restoring from SQL 7.0 Filegroup Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049 Restoring the SQL 7.0 Master Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051 Redirecting Restores for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053 Setting Default Backup and Restore Options for SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . 1056 Preparing for Disaster Recovery of SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061 Disaster Recovery of SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063 Manual Recovery of SQL 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064 Appendix H. VERITAS Backup Exec - Agent for Microsoft Exchange Server . . 1067 Requirements for Using the Exchange Agent with Exchange 2000 . . . . . . . . . . . . . . 1068 Installing the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068 Using Backup Exec Logon Accounts with Exchange 2000 Resources . . . . . . . . . . . . 1069 Backup Strategies for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070 Recommended Configurations for Exchange 2000 Server . . . . . . . . . . . . . . . . . . 1073 Backup Options for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074 Backing Up Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078 Reviewing Circular Logging for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . 1079 Backing Up Exchange 2000 Mailboxes and Public Folders . . . . . . . . . . . . . . . . . . . . . 1080 Restore Options for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085 Restoring Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088 Restoring Exchange 2000 Mailboxes and Public Folders . . . . . . . . . . . . . . . . . . . . . . 1089
22
Redirecting Exchange 2000 Storage Group and Database Restores . . . . . . . . . . . 1091 Redirecting Mailbox and Public Folder Restores in Exchange 2000 . . . . . . . . . . . 1093 Setting Default Backup and Restore Options for Exchange 2000 . . . . . . . . . . . . . . . . 1097 Preparing for Disaster Recovery of Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101 Disaster Recovery for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102 About Using the Exchange Agent with Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . 1105 Requirements for Using the Exchange Agent with Exchange 5.5 . . . . . . . . . . . . . . . 1105 Installing the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106 Using Backup Exec Logon Accounts with Exchange 5.5 Resources . . . . . . . . . . . . . . 1106 Backup Strategies for Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107 Recommended Configurations for Exchange 5.5 Server . . . . . . . . . . . . . . . . . . . . 1109 Backup Options for Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110 Backing Up Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114 Reviewing Circular Logging for Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115 Backing Up Exchange 5.5 Mailboxes and Public Folders . . . . . . . . . . . . . . . . . . . . . . 1115 Restore Options for Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119 Restoring Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121 Restoring Exchange 5.5 Mailboxes and Public Folders . . . . . . . . . . . . . . . . . . . . . . . . 1123 Redirecting Exchange 5.5 Database Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125 Redirecting Mailbox and Public Folder Restores in Exchange 5.5 . . . . . . . . . . . . 1127 Setting Default Backup and Restore Options for Exchange 5.5 . . . . . . . . . . . . . . . . . 1132 Preparing for Disaster Recovery of Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137 Disaster Recovery for Exchange Server 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138 Appendix I. VERITAS Backup Exec - Library Expansion Option . . . . . . . . . . . . . 1143 Setting Up Robotic Library Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143 Configuring Multi-drive Robotic Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145 Installing the Library Expansion Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146 Starting Backup Exec After Installing the Library Expansion Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146 Viewing Robotic Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
Appendix J. VERITAS Backup Exec - Agent for Oracle Server
. . . . . . . . . . . . . 1151
Requirements for Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152 Backup Strategies for An Oracle Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152 Types of Oracle Database Data You Can Protect . . . . . . . . . . . . . . . . . . . . . . . . . . 1153 Requirements for Configuring the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154 Creating a New Oracle User Account for the Oracle Agent . . . . . . . . . . . . . . . . . 1154 Verifying ARCHIVELOG Mode and Automatic Archival Settings . . . . . . . . . . . 1155 Running Multiple Database Instances on a Single Server . . . . . . . . . . . . . . . . . . . 1157 Using Fully Specified Paths for Oracle Data Files . . . . . . . . . . . . . . . . . . . . . . . . . 1158 Understanding the Oracle Agent Configuration Utility . . . . . . . . . . . . . . . . . . . . 1159 Installing the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160 Configuring the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161 Adding Media Servers to Use with the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . 1164 Backing Up Data Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 Backing Up an Entire Online Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 Backing Up Individual Online Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 Backing Up a Closed Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168 Restoring the Oracle Database Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . 1169 Restoring an Online Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170 Restoring a Closed Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171 Restoring Individual Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172 Restoring the Database Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173 Disaster Recovery Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174 Disaster Recovery Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174 Recovering a Remote Oracle Database Server from a Disaster . . . . . . . . . . . . . . 1175 Recovering a Combination Oracle Database Server/Media Server . . . . . . . . . . 1176 Oracle Agent Error Message Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
24
Appendix K. VERITAS Backup Exec - Agent for Lotus Domino . . . . . . . . . . . 1179 Lotus Domino Agent Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180 Installing the Lotus Domino Agent on the Media Server . . . . . . . . . . . . . . . . . . . . . . 1181 Viewing and Selecting Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182 Configuring Default Lotus Domino Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184 Backing Up Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185 Supported Lotus Domino Database Configurations . . . . . . . . . . . . . . . . . . . . . . . . 1185 Lotus Domino Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186 Backup Options for Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187 Restoring Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189 Selecting Lotus Domino Databases for Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1190 Restore Options for Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192 Redirecting Restore Jobs for Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . 1194 Preparing for Disaster Recovery on a Lotus Domino Server . . . . . . . . . . . . . . . . . . . 1195 Disaster Recovery of a Lotus Domino Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196 Disaster Recovery of a Lotus Domino Server Using Archive Logging . . . . . . . . 1197 Disaster Recovery of a Lotus Domino Server Using Circular Logging . . . . . . . . 1198 Appendix L. VERITAS Backup Exec - Agent for R/3 for Oracle Server . . . . . . . . 1199 Backup Exec R/3 Agent Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200 Backup Exec Alerts and the BACKINT Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 1200 Requirements for Backup Exec R/3 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201 Installing the Backup Exec R/3 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201 Using the R/3 Agent to Back Up the R/3 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202 Specifying Backup Exec Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1202 Backing Up the R/3 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205 Restoring the R/3 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206 Disaster Recovery Using the Backup Exec R/3 Agent . . . . . . . . . . . . . . . . . . . . . . . . . 1206 Disaster Recovery Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1207 Recovering a Remote R/3 Database Server from a Disaster . . . . . . . . . . . . . . . . . 1208
25
Recovering a Combination R/3 Database Server/Media Server . . . . . . . . . . . . . 1209 Appendix M. VERITAS Backup Exec - Agent for Microsoft SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211 Requirements for the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212 Installing the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213 Backing Up a SharePoint Portal Server or Workspace . . . . . . . . . . . . . . . . . . . . . . . . 1213 Backing Up Folders and Documents from a SharePoint Portal Workspace . . . . 1213 Restoring SharePoint Portal Servers and SharePoint Portal Workspaces . . . . . . . . 1215 Restoring a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215 Restoring a SharePoint Portal Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216 Redirecting SharePoint Portal Server Restore Jobs . . . . . . . . . . . . . . . . . . . . . . . . 1217 Redirecting SharePoint Portal Workspace Restore Jobs . . . . . . . . . . . . . . . . . . . . 1218 Disaster Recovery of a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221 Uninstalling and Reinstalling the SharePoint Portal Server Software . . . . . . . . 1222 Restoring SharePoint Portal Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1222 Appendix N. VERITAS Backup Exec - Remote Agent for NetWare . . . . . . . . . . 1223
Requirements for the Remote Agent for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224 Maximizing Remote Agent Performance on the NetWare Server . . . . . . . . . . . . 1224 Installing the Remote Agent for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225 Using NetWare 5.x and 6.x in a TCP/IP Only Environment . . . . . . . . . . . . . . . . 1226 Adding BESTART to the AUTOEXEC.NCF File on the NetWare Server . . . . . . 1226 Unloading the Remote Agent for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227 About Backing Up NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1228 Backing up the NetWare Directory Services (NDS) . . . . . . . . . . . . . . . . . . . . . . . . 1229 Backing Up NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231 About Restoring NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233 Restoring NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233 Default Settings for the Remote Agent for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . 1235 Saving Configuration Information for the NetWare Server . . . . . . . . . . . . . . . . . . . . 1238
Disaster Recovery of NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239 Appendix O. VERITAS Backup Exec - Tivoli Storage Manager Option . . . . . . . . 1241 Requirements for the TSM Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241 Backup Exec as a TSM Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1242 TSM Backup Exec Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243 Preparing the TSM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245 Allocating Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1245 Creating The bexpi.dsm Storage Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246 Running the BEX.MAC Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248 Enabling TSM Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249 Changing the Defaults for Backup Exec for Windows Servers . . . . . . . . . . . . . . . . . . 1249 BEX.MAC Macro Command Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256 Viewing TSM-related Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256 TSM Problem Resolutions for Backup Exec for Windows Servers . . . . . . . . . . . . 1257 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269
27
28
Using Backup Exec Documentation

This comprehensive manual provides detailed information and procedures for using VERITAS Backup Exec for Windows Servers. Topics covered in this manual require the reader to have a working knowledge of the Windows operating environment.
Conventions
The following conventions are used in this manual:
Steps Text that you type
Numbered steps are listed as 1.,
2., etc.
Text that you are required to type on the keyboard is preceded by the word "Type" and may be followed by any keys that you must press: For example: Type a:install and press <Enter>.
Text that you replace
Text that you must replace is shown in an italic font. For example: JOB_PRIORITY=priority
Items on the interface
Items that are on the Backup Exec interface are shown in a bold font. For example: On the Properties pane, under Settings, click Exchange
Keys
Keys appear in angle brackets (< >). For example: <Enter>, <Esc>, <Del>, etc. When two or more keys need to be pressed simultaneously to perform a function, they appear in angle brackets with a plus sign. For example: <Shift + F1>
29
Conventions
30
Introduction
Introducing Backup Exec
Backup Exec is a high-performance data management solution for Windows servers networks. With its client/server design, Backup Exec provides fast, reliable backup and restore capabilities for servers and workstations across the network. Backup Exec is available in configurations that can accommodate multi-platform networks of all sizes:
VERITAS Backup ExecTM for Windows Servers
Installs on and protects any supported version of Microsoft .NET, Windows 2000, or Windows NT 4. Also includes Backup Exec agent software to protect unlimited remote workstations running on Windows XP Professional, Windows 2000 Professional, Windows NT 4 Workstation, Windows Me, Windows 98, UNIX, and Macintosh platforms. This edition supports unlimited stand-alone drives. 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. Support for protecting additional .NET, Windows 2000, or Windows NT 4 servers, NetWare servers, databases, open files, and more can be purchased separately.
31
Small Business Server
Installs on and protects any supported version of Microsoft Small Business Server for Windows NT 4 or Windows 2000. Also includes Backup Exec agent software for workstations running on Windows XP Professional, Windows 2000 Professional, Windows NT 4 Workstation, Windows Me, Windows 98, UNIX, and Macintosh platforms. This edition supports unlimited stand-alone drives. 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. The Small Business Server Edition includes an Exchange Agent, SQL Agent, and IDR Option (IDR is not supported in SBS 2000 environments). Protecting additional Windows 2000, or Windows NT 4 servers, NetWare servers, or databases is not supported and would require an upgrade to the Backup Exec for Windows Servers Edition.
QuickStart Edition (OEM release only)
Installs on and protects any supported version of Microsoft Windows NT 4 or Windows 2000. Also includes Backup Exec agent software for workstations running on Windows XP Professional, Windows 2000 Professional, Windows NT 4.0 Workstation, Windows Me, Windows 98, UNIX, and Macintosh platforms. This edition supports unlimited stand-alone drives. 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.
See also: Backup Exec Options on page 36
32
Introduction
Whats New in This Release

This release of Backup Exec includes the following new features and capabilities:
Updated graphical user interface
Provides a more intuitive graphical user interface, featuring a task pane that makes launching Backup Exec operations easier, and incorporating a media server summary, which provides a quick listing of recent Backup Exec activity on your server. Also offers an Information Desk, a quick and convenient way of accessing detailed information on how to use Backup Exec. Provides a web-based administration console for Microsoft Windows Powered and .NET servers displaying task-oriented features designed to protect data on Windows servers. Allows you to quickly view and schedule jobs through a calendar format similar to Microsofts Outlook. Fully supports installation on and protection of .NET and Windows XP Professional systems running in a domain and continues to provide protection for Windows 2000 and Windows NT systems.
VERITAS Backup Exec Web Administration Console Calendar-based job scheduler .NET and Windows XP support
Duplication of backup data Allows duplication of existing backup sets or of backup sets that will be created during a scheduled backup 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. 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. Test Run of backup jobs Determines if a scheduled job will complete successfully. If it appears that there are problems that could prevent successful job completion, the problems are identified. Notification of potential problems appears on the Administration Console and can also be sent via e-mail or pager. Allows for creation of a job to automatically detect new backup resources, including local and remote databases or volumes. Allows the setting up of rules, based on error categories, for how Backup Exec will handle failed jobs.
Automatic discovery of new resources Error handling rules
Chapter 1, Introducing Backup Exec
33
Job history enhancements Provides color-coded HTML-formatted job logs and presents a summary of errors in a history log. Also provides more details of job history without requiring the viewing of the log. Enhanced specify network Allows the use of a dedicated LAN to reduce network traffic on the for backup and restore production LAN. A default LAN can be specified for all jobs, or a jobs LAN can be specified on a per job basis for both backup and restore jobs. A drop-down selection list of all available network interfaces on the media server makes configuration easier for both setting the default network and specifying network use on a per job basis. Enhanced alert and notification setup Allows configuration of alerts and set up of recipients who will receive e-mail or pager notification when alerts occur. Also provides alert filtering to specify the types of alerts that will display on the Administration Console. In addition to active alerts, allows viewing of alert history. Provides offsite tracking of media through the creation of user-defined media vaults. Allows viewing of remaining media capacity. Checks the VERITAS web site at user-specified intervals for any available Backup Exec updates and informs you when software updates are available. Automates installation and configuration of Backup Exec media servers operating in a Windows cluster environment. Allows the creation and modification of user accounts with access to back up and restore specific systems.
Tracking of media by location Media capacity tracking Dynamic product update
Cluster install and configuration wizard User accounts for protecting specific systems Job summary view Reordering of job selections Prioritizing of job order Scheduling of utility jobs
Provides an optional summary of the backup job being submitted. Allows editing of the order in which resources selected for backup are processed. Allows changing of the priority order of jobs. Utility jobs, such as cleaning, inventory, and erase, can be scheduled to run as a once-only job or as a recurring job.
34
Introduction
Enhanced reporting capabilities
Provides additional reports for administrating media servers and remote systems and allows report output to be saved. With the new Admin Plus Pack, reports can be scheduled as jobs and e-mailed to specified recipients. Now you can replace or add tape drives on a Backup Exec media server without rebooting the server. The Hot-swappable Device Wizard guides you through the process. Ensures all files are protected even if they are being used and allows the use of VSP, VSS, and VM Flashsnap. Also includes Backup Exec Remote Agent for Windows Servers. Enables the off-loading of the backup process onto a third-party data mover within a SAN. Provides features designed for distributed data management of your media and remote servers, including the ability to clone servers and copy jobs, selection lists, and templates between media servers. This option also provides advanced reporting capabilities, such as scheduling a report and e-mailing report output. Allows granular backup and restore of an individual workspace and document.
Hot-swappable Device Wizard
Advanced Open File Option
ServerFree Option
Admin Plus Pack Option
Enhanced Agent for Microsoft SharePoint Portal Server Lotus Domino Rnext Support Enhanced Agent for Microsoft Exchange
The Backup Exec Agent for Lotus Domino now provides Rnext support. The Backup Exec Agent for Microsoft Exchange allows single instance storage of attachments during mailbox level backups and allows restores of individual public folders.
35
Backup Exec Options
Backup Exec Options

You can purchase the following options for your Backup Exec configuration:
VERITAS Backup Exec Library Expansion Option (LEO) enables support for 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 allows you to assign specific robotic library slots for backup targets. For more information, see VERITAS Backup Exec Library Expansion Option on page 1143. VERITAS 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. For more information, see VERITAS Backup Exec for Windows Servers Advanced Open File Option on page 955. VERITAS Backup Exec Intelligent Disaster Recovery Option (IDR) provides a recovery solution for both local and remote Windows systems. This option eliminates the need to manually re-install the entire operating system after a system crash. Using diskettes, CD-R/CD-RW or bootable tape, IDR gets you back online fast allowing you to restore from your last complete backup set - including full, incremental, differential and working set backups. For more information, see VERITAS Backup Exec Intelligent Disaster Recovery Option on page 855. VERITAS Backup Exec Admin Plus Pack Option provides features designed for distributed data management of your media and remote servers, including the ability to create a clone CD image so you can install Backup Exec on additional servers using the same installation settings. This option also allows you to copy jobs, selection lists, and templates between media servers and provides advanced reporting capabilities, such as scheduling a report and e-mailing report output. For more information, see VERITAS Backup Exec - Admin Plus Pack Option on page 827. VERITAS Backup Exec Agent for Microsoft Exchange Server provides a fast and flexible way of protecting your online Exchange 5.5 and Exchange 2000 Server data. This agent provides complete individual mailbox backup (also utilizing single instance restore), including protection for embedded messages, objects, attributes and all Outlook components. For more information, see VERITAS Backup Exec - Agent for Microsoft Exchange Server on page 1067. VERITAS Backup Exec Agent for Microsoft SQL Server fully protects active databases and verifies all of your SQL v7.0 and SQL 2000 data automatically. SQL 7.0 and SQL 2000 users can customize their data protection needs down to the filegroup level. For fast point-in-time backups, you can use this option to run transaction log backups
36
Introduction
Backup Exec Options
with truncation. Redirected restores allow you to easily restore SQL data to other SQL servers on the network. Multi-pipe support along with SQL VDI provides users the easiest and fastest way to complete SQL database protection. For more information, see VERITAS Backup Exec - Agent for Microsoft SQL Server on page 975.
VERITAS Backup Exec Remote Agent for NetWare Servers expands network-wide data protection by providing a Client Access License (CAL), fully protecting all NDS information across NetWare 4.2, 5.1, and 6.x environments. In addition to backing up NetWare servers from your Windows media server, you get 100 percent SMS compatibility supporting the current versions of NetWare. The exclusive Agent Accelerator technology maximizes backup performance and reduces network traffic by using source level compression and distributed processing. For more information, see VERITAS Backup Exec - Remote Agent for NetWare on page 1223. VERITAS Backup Exec Remote Agent for Windows Servers provides a Client Access License (CAL) to enable protection of remote Windows servers. With its exclusive Agent Accelerator technology, the Remote Agent uses source compression and distributed processing to optimize backup performance. For more information, see VERITAS Backup Exec - Remote Agent on page 821. VERITAS Backup Exec Agent for Oracle provides seamless online backup protection for Oracle Database Server versions 8.0.5, 8i-8.1.6, 9i and Oracle Application Server 9i. Integrating Oracle backup with the advanced features of Backup Exec provides data protection of both individual table spaces as well as complete Oracle databases. You can also include archived redo files and control files without taking them offline. For more information, see VERITAS Backup Exec - Agent for Oracle Server on page 1151. VERITAS Backup Exec Agent for R/3 for Oracle Server provides superior data protection by allowing backups of critical data while the application is still online and in use. The R/3 Agent, certified by SAP, is a reliable solution that allows Backup Exec to provide both local and remote protection of the latest versions of SAPR/3 databases utilizing the SAP (BC-BRI BACKINT) interface while enabling you to efficiently manage your data. For more information, see VERITAS Backup Exec Agent for R/3 for Oracle Server on page 1199. VERITAS Backup Exec Agent for Lotus Domino provides seamless online backup protection for versions 5 and 6. Using Lotus Domino APIs, the Agent for Lotus Domino now fully supports transactional logging, providing users with uncompromising data protection of the entire Lotus Domino server. For more information, see VERITAS Backup Exec - Agent for Lotus Domino on page 1179. VERITAS Backup Exec SAN Shared Storage Option (SAN SSO) allows Backup Exec to operate in a Storage Area Network (SAN), providing a high performance LAN-free backup solution. SAN SSO allows multiple distributed media servers to share common, centralized storage devices connected over a SAN. This configuration provides greater efficiency and fault tolerance. In addition to increasing performance
37
Backup Exec Options
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. For more information, see VERITAS Backup Exec - SAN Shared Storage Option on page 911.
VERITAS Backup Exec - Tivoli Storage Manager (TSM) Option lets you combine the speed and localized control of Backup Exec with the TSM policy-based system of centralized storage management. This option allows the TSM servers storage resources to appear as a robotic library in the list of target devices on the Backup Exec server. Backup Exec administrators can then direct the output of any Backup Exec job to the TSM server simply by selecting the name of the TSM robotic library as the destination when submitting the job. For more information, see VERITAS Backup Exec - Tivoli Storage Manager Option on page 1241. VERITAS Backup Exec - Agent for Microsoft SharePoint Portal Server protects all of the files and attributes associated with an installation of SharePoint Portal Server. Backup Exec, which offered the first complete backup and recovery solution for SharePoint Portal Server, now allows backup and restore of individual workspaces and documents. Restores can be made to the original SPS information store or redirected to another SPS information store without affecting other workspaces. For more information, see VERITAS Backup Exec - Agent for Microsoft SharePoint Portal Server on page 1211. VERITAS Backup Exec - Intelligent Image Option (IIO) provides fast backup performance with less CPU processing. The IIO backs up all of the information about the files themselves (meta data), and then separately backs up all the data in the files as one image. The decrease in the overall volume of the backup increases the speed of the backup. For more information, see VERITAS Backup Exec for Windows Servers ServerFree Option and Intelligent Image Option on page 939. VERITAS Backup Exec - ServerFree Option enables you to increase backup performance by freeing up media server processor resources and moving the backup processing operations to hardware solutions that may be installed in your storage area network environment. Use of this option requires VERITAS Backup Exec Advanced Open File Option and VERITAS Backup Exec SAN Shared Storage Option. For more information, see VERITAS Backup Exec for Windows Servers - ServerFree Option and Intelligent Image Option on page 939.
38
Introduction
How Backup Exec Works

In Backup Exec, backup, restore, and utility operations, called jobs, are submitted using the Administration Console. Administrators can run the Administration Console from the media server, a Windows server with storage hardware attached, or from a remote system. After jobs are created, they are processed by the Backup Exec server components running on the media server. All interaction to the Backup Exec system, such as submitting jobs, viewing results, and performing device and media operations, can be done through the Administration Console. The following diagram illustrates how the components work together to provide complete backup and restore functionality to the entire network:
How Backup Exec Works Backup Exec administration console
Backup Exec database
storage devices and media
Backup Exec media server running the Backup Exec engine
Backup Exec workstation and server agents
Through the Administration Console, you configure settings, called default options, that you want Backup Exec to use for most jobs. However, you can select to override these default options while setting up a specific jobs, 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.
39
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. 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 drive pools. Through the media management function, you can organize, track, and troubleshoot all of the media in your library. You can define overwrite protection periods to ensure that media is not accidentally overwritten, set up automatic media labeling, and 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.
40
Installation
Installing Backup Exec

Backup Exec installation on the media server includes:
Installing the storage device hardware (controller, drives, robotic libraries) in the media server. Refer to the documentation 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.) Installing Backup Exec software on the media server. All Backup Exec program files are installed on the media server from the Backup Exec installation CD. During installation, files required for workstation agent installation are also copied to the media server. Rebooting the media server to initialize changes (when necessary).
The installation program installs Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) components required to run Backup Exec. These include SQL Server 2000 core components, MDAC v2.62, and ODBC 3.0. With ODBC, the installation program installs and configures the base 32-bit ODBC administrator v3.0, including runtime DLLs, and the ODBC driver for the Backup Exec catalogs. 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 compatible with the MDAC.
41
System Requirements
If SQL Server 2000 is already installed on the server, you are prompted to do one of the following:

Install the required Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) components with Backup Exec and create a default Backup Exec instance. Select a SQL Server 2000 instance that already exists on which to run Backup Exec.
Note If you choose to install Backup Exec into an existing SQL 2000 instance, make sure that SQL 2000 service pack 2 or later is installed before you continue with the installation. When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. After installing Backup Exec on the media server, Backup Exec Workstation Agent software can be installed and configured on remote workstations on the network. --300.
System Requirements
The following are the minimum system requirements for running this version of Backup Exec:
Minimum System Requirements Operating System Microsoft Windows NT Workstation v4.0 or Microsoft Windows NT Server Operating System v4.0; Service Pack 6a or later. Windows 2000 Professional version, Windows 2000 Server version, Windows 2000 Advanced Server, or Windows 2000 Datacenter. .NET server family. Internet Browser Processor Internet Explorer 5.01 or later; however, version 5.5 is recommended. Pentium system.
42
System Requirements Minimum System Requirements (continued) Memory Required: 128 MB RAM (32 MB for System Services, 96 MB for administration console).
Installation
Recommended: 256 MB (or more for better performance). Virtual Memory Recommendations: 20 MB above Windows recommended size for total paging file size (total for all disk volumes). To view or set the paging file size: On Windows NT, click the Start button, point to Settings, and then click Control Panel. Double-click System, and then click the Performance tab. On Windows 2000 or .NET, click the Start button, point to Settings, and then click Control Panel. Double-click System, click the Advanced tab, and then click Performance Options. Disk Space 550 MB hard disk space required after Microsoft Windows is installed (typical installation). (Recommended if remote activity is to be performed) Network interface card or a virtual network adapter card. CD-ROM drive. (Optional) Printer supported by Microsoft Windows. (Recommended) A mouse. (Optional for pager notification) Modem supported by Windows. Storage Hardware Backup Exec requires at least one storage media drive and/or robotic library and the appropriate controller card. Removable storage devices and non-removable hard drives can also be targeted for backups. Refer to the Backup Exec hardware compatibility list for a complete list of devices that are supported. Support for multi-drive robotic libraries is available separately. Refer to the Windows Hardware Compatibility list for a complete list of supported SCSI controllers.
Other Hardware
Chapter 2, Installing Backup Exec
43
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 one of the following procedures, as appropriate for the environment.

For Windows NT 4.0, use the User Manager for Domains tool in the Administrative Tools group. For Windows 2000, use the Active Directory Users and Computers tool and Domain and Trusts tool in the Active Directory administrative tools group.
If You Are Backing 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.
If You Are Backing Up Servers and Selected Workstations in One Domain: 1. Add the name of an existing or new Service Account (for example, Administrator) as a member of the Global Domain Admins group. 2. Ensure that on each workstation in the domain you want to back up, the Global Domain Admins group is a member of the workstations local Administrators group.
44
If You Are Backing 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): a. In the Host Domain, permit the Target Domains to trust the Host Domain. b. In each Target Domain, trust the Host Domain. 2. In each Target Domain, add the Host Domains name of an existing or new Service Account (for example, Administrator) in the local Administrators group.
Installation
If You Are Backing Up Servers and Workstations in More Than One Domain: 1. Establish a One Way Trust Relationship between the Host and Target Domains: a. In the Host Domain, permit the Target Domains to trust the Host Domain. b. In each Target Domain, trust the Host Domain. 2. In each Target Domain, add the Host Domains name of an existing or new Service Account (for example, Administrator) in the Local Administrators group. 3. On each workstation to back up, add the Host Domains name of an existing or new Service Account (e.g., Administrator) in the Local Administrators group.
45

When installing Backup Exec, use the installation program on the Backup Exec CD, or install it from the command line, which is referred to as Silent Mode Installation. The silent mode installation uses the setup.exe program on the Backup Exec CD. If you are installing an evaluation version of Backup Exec, you can install any additional options. To install the Backup Exec Web Administration Console, you must be installing Backup Exec on a server appliance or on a Windows.NET server with the Remote Administration (HTML) components installed. Please note the following information before installing Backup Exec:
Minimum system requirements Hardware Make sure that storage device hardware and associated drivers are properly installed and recognized by the Windows operating system. Exit all programs before installing Backup Exec. To install Backup Exec, Administrator rights are required, or the account must belong to an Administrator-equivalent group. All Backup Exec services on the media server run in the context of a user account configured for Backup Execs system services. This account can be created during Backup Execs installation, or an existing user account can be used. To create a service account for Backup Exec during installation, supply a user name and password when prompted. The account designated for Backup Execs services whether it is a new account or an existing user account - will be 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). Manage auditing and security log. Due to security implementations in Microsoft Small Business Server, the service account must be "Administrator."
System Rights
The Backup Exec Service Account
46
See also: Installing Backup Exec Using the Installation Program on page 47 Installing Backup Exec from the Command Line (Silent Mode) on page 56
Installation
Installing Backup Exec Using the Installation Program

The Backup Exec CD includes an installation program that guides you through the installation process.
To install Backup Exec using the installation program: 1. From the installation CD browser, select the option to install VERITAS Backup Exec. The Welcome window appears. 2. Click Next to proceed with the installation. The License Agreement appears. 3. Select I accept the terms of the license agreement, and then click Next. 4. Do any of the following: To install to a local computer, select Local Install and Install Backup Exec software and options, click Next, and then continue with step 5 on page 47. To install the Remote Administrator, go to Installing the Backup Exec Remote Administrator on page 67. To install Backup Exec media servers and options to remote computers, go to Installing Backup Exec Media Servers to Remote Computers on page 51. To install the Backup Exec Remote Agent for Windows Servers or the Advanced Open File Option to remote computers, or the Backup Exec NetWare Agent to a remote NetWare server, go to Installing Backup Exec Remote Agents and Options on Remote Servers on page 54.
5. If Backup Exec Setup detects an existing installation of MS SQL Server 2000, you can allow the required Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) components to be installed with Backup Exec and create a default Backup Exec instance, or you can choose to use a SQL Server 2000 instance that already exists on which to run Backup Exec. Select an option, and then click Next. A dialog that requests your serial numbers appears.
47
6. You can manually enter the serial numbers for Backup Exec and any options, or you can import an existing besernum.xml file to enter the serial numbers. To manually enter the serial numbers for Backup Exec and any additional options, type the serial number into the field, and then click Add. When finished, click Next. To import the serial numbers from a file, click Import, and then browse for and select an existing besernum.xml file. When finished, click Next.
Note When you click Next, the serial numbers you entered are saved to the file besernum.xml, located in the Windows directory. If another installation of Backup Exec 9.0 for Windows Servers is found on the computer, the serial number appears in the Existing Serial Numbers field. To remove an older serial number, select the number and click Remove. A serial number is not required for Backup Execs fully functional evaluation version. To install a 60-day evaluation copy of the software, click Next without entering serial number information. Installing an evaluation copy enables many options that must be purchased separately and are not included as part of Backup Exec. Note For information about clustering Backup Exec, see Installing Backup Exec on a Cluster on page 742. 7. Review the local features to be installed. All features that are not to be installed have an "X" displayed in the feature icon. To enable any of these options, click the icon to clear the X, and then follow the prompts to install it. If the feature icon is gray, the option is not available for change. 8. To accept the local features for installation, and to accept the default Destination Folder for Backup Exec, click Next. To select another destination folder for Backup Exec, click Change, and follow the prompts. 9. Provide a user name and password that the Backup Exec system services can use (see The Backup Exec Service Account on page 46), and then click Next. 10. If prompted, select how to 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 VERITAS device drivers for all tape devices. 11. If you are prompted, enter information or choose settings for additional options being installed. Click Next after each selection.
12. Read the Backup Exec installation review, and then click Install. The MSDE 2000 (if selected), VERITAS Update, and Backup Exec program files are installed.
Installation
13. When the installation is complete, you can choose to register Backup Exec online, view the readme, create a shortcut to Backup Exec on the desktop, and restart the computer. If Restart System appears, restart the computer in order for the configuration to take effect. If the installation fails, an installation job log named bkupinst.log is created in the Windows root directory on the computer where Backup Exec is installed; this file lists any errors that may have occurred during installation. When prompted, click View Installation Log. See also: Getting Started on page 73
Installing Backup Exec Options on a Local Server

You can install additional options, such as the Library Expansion Option, when you are installing Backup Exec by following the procedures described in Installing Backup Exec Using the Installation Program on page 47. However, if you have already installed Backup Exec and want to install additional options, you should first review the section on that option to ensure that you have met all minimum requirements and then continue with the following steps. If you have installed the evaluation version of Backup Exec or have installed the Not For Resale (NFR) or the Open Option Suite edition, you can install evaluation versions of the additional options. 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. Note You can also install Backup Exec options using Add/Remove Programs in the Windows Control Panel.
To install an option on a local media server: 1. Start Backup Exec for Windows Servers or verify that it is running. 2. On the Tools menu, click Serial Numbers and Installation.
49
3. Click Next when the Welcome window appears. 4. Make sure Local Install and Additional Options are selected, and then click Next. 5. Type the options serial number and click Add, or click Import to import the serial number from an existing besernum.xml file, and then click Next. 6. Review the local features to be installed, and then click Next. All features that are not to be installed have an "X" displayed in the feature icon. To enable any of these options, click the icon to clear the X, and then follow the prompts to install it. If the feature icon is gray, the option is not available for change. 7. If you are prompted, enter information or choose settings for additional options being installed. Click Next after each selection. 8. Read the Backup Exec installation review, and then click Install. When the installation is complete, you can choose to register Backup Exec online, view the readme, create a shortcut to Backup Exec on the desktop, and restart the computer. 9. Make your selections, and then click Finish. If Restart System appears, you should restart the computer in order for the configuration to take effect. If the installation fails, an installation job log named bkupinst.log is created in the Windows root directory on the computer where Backup Exec is installed; this file lists any errors that may have occurred during installation. If prompted, click View Installation Log, and check this log. 10. After the computer has rebooted, restart Backup Exec for Windows Servers.
50
Installing Backup Exec Media Servers to Remote Computers

You can install Backup Exec media servers and options to remote computers. To install a Backup Exec media server to a remote computer, you must have one of the following installed on the local media server:

Installation
The Admin Plus Pack option An evaluation version of Backup Exec The Not For Resale (NFR) option
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.
To install Backup Exec to a remote computer: 1. Do one of the following: If you are installing Backup Exec for the first time, from the installation CD browser, select the option to install VERITAS Backup Exec, and then when prompted, click Next to proceed with the installation. Select I accept the terms of the license agreement, and then click Next. If Backup Exec is already installed, make sure that it is running, and then on the Tools menu, click Serial Numbers and Installation. Click Next when the Welcome window appears.
Note You can also use Microsofts Add/Remove Programs utility to install Backup Exec to a remote computer. See your Microsoft documentation for more information. 2. To install Backup Exec media servers and options to remote computers, select Remote Install, and then click Next. Note If you do not need to install any Backup Exec options to the local computer, clear the Local Install selection. 3. On the Backup Exec Remote Features dialog box, in the Destinations Systems pane, right-click Windows Media Servers.
51
4.
Do one of the following: Select Add Remote Computer, browse to select the remote server, and then click Next. Select Add Remote Computer Manually, type the Domain and Computer Name, and then click OK.
5. Enter the user name, password and domain credentials of an account that has administrative rights on the remote computers, and then click OK. 6. Select one of the following options:
Item Remote install with serialized options
Description Select this option to enter serial numbers for the remote computers. During the install, you are prompted for the serial numbers for the remote computers. If you select this option to install a Backup Exec media server (Windows Media Server) 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 53.
Remote install with cloned local settings
Select this option to install remotely using all of the installation options installed on the local computer. When this option is used, you cannot change any settings on the remote computer. For example, if you have installed the Intelligent Disaster Recovery option locally, this option will also be installed remotely. After selecting this option, continue with step 13 on page 49.
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 62). When this option is selected, you can browse to a parameter file. After selecting this option, continue with step 13 on page 49.
A dialog that requests your serial numbers appears. Note Each remote computer targeted for an option installation must have a unique option serial number.
52
7. Do one of the following: Enter the serial numbers for Backup Exec and any additional options, clicking Add after entering each serial number. When finished, click Next.
Installation
Click Import, and then browse for and select an existing besernum.xml file. When finished, click Next.
Note When you click Next, the serial numbers you entered are saved to the file besernum.xml, located in the Windows directory. 8. Provide a user name and password that the Backup Exec system services can use (see The Backup Exec Service Account on page 46), and then click Next. 9. If prompted, select how to 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 VERITAS device drivers for all tape devices. 10. If you are prompted, enter information or choose settings for additional options being installed. Click Next after each selection. 11. Review the features to be installed, and then click Next. All features that are not to be installed have an "X" displayed in the feature icon. 12. Read the Backup Exec installation review, and then click Install. 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 affect. If the installation fails, an installation job log named bkupinst.log is created in the Windows root directory on the computer where Backup Exec is installed; this file lists any errors that may have occurred during installation. If prompted, click View Installation Log, and check this log.
53
Installing Backup Exec Remote Agents and Options on Remote Servers

You can install the Backup Exec Remote Agent to remote Windows computers, the Backup Exec Advanced Open File option to remote computers, and the Backup Exec NetWare Agent to remote NetWare computers. 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. If you are installing Backup Exec remote 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.
To install a feature to a remote computer: 1. Do one of the following: If you are installing Backup Exec for the first time, from the installation CD browser, select the option to install VERITAS Backup Exec, and then when prompted, click Next to proceed with the installation. Select I accept the terms of the license agreement, and then click Next. If Backup Exec is already installed, make sure that it is running, and then on the Tools menu, click Serial Numbers and Installation. Click Next when the Welcome window appears.
Note You can also use Microsofts Add/Remove Programs utility to install Backup Exec to a remote computer. See your Microsoft documentation for more information. 2. To install Backup Exec remote agents and options to remote computers, select Remote Install, and then click Next. Note If you do not need to install any Backup Exec options to the local computer, clear the Local Install selection. 3. On the Backup Exec Remote Features dialog box, in the Destinations Systems pane, right-click either of the following: Windows Agent/Options Computers. Enables you to install the Backup Exec Remote Agent to a remote Windows computer, or to install the Advanced Open File Options to a remote computer. NetWare Agent Server. Enables you to install the Backup Exec NetWare Agent to a remote NetWare server.
54
4.
Do one of the following: Select Add Remote Computer, browse to select the remote server, and then click Next.
Installation
Select Add Remote Computer Manually, type the Domain and Computer Name, and then click OK. This option is not available for NetWare servers.
5. Enter the user name, password and domain credentials of an account that has administrative rights on the remote computers, and then click OK. 6. Review the features to be installed, and then click Next. All features that are not to be installed have an "X" displayed in the feature icon. To enable any of these options, click the icon to clear the X, and then follow the prompts to install it. If the feature icon is gray, the option is not available for change. 7. Read the installation review, and then click Install. 8. 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. If the installation fails, an installation job log named bkupinst.log is created in the Windows root directory on the computer where Backup Exec is installed; this file lists any errors that may have occurred during installation. If prompted, click View Installation Log, and check this log.
55
Installing Backup Exec from the Command Line (Silent Mode)

Installing Backup Exec from 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. Silent mode installation is only supported if Backup Exec is being installed on a computer for the first time. Requirements for Command Line Installation include:

Backup Exec installation CD. Administrator privileges on the computer where you want to install, configure, or uninstall Backup Exec.
To install Backup Exec from the command line: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL. 4. Type setup /TS: and the appropriate switches. For example: setup /TS: /USER:<user> /DOM:domain /PASS:password /SNO:serial number -S For descriptions of the switches, see Command Line Switches for Backup Exec Silent Mode Installation on page 57. 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 serial number appearing on the installation dialog boxes. 5. Press <Enter>. An installation job log named bkupinst.log is created in the Windows root directory on the computer where Backup Exec is installed; this file lists any errors that may have occurred during installation, and is the only source of feedback when running setup.exe. Check this job log to determine if you need to reboot the computer to complete the installation.
56
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:
Installation
Substitute values appropriate for your environment for values shown in italics; for example substitute your password for password. Enclose the value in quotation marks if it contains spaces, such as Operations Weekly Backup.
Note Additional switches appearing in BOLD are required.

Command Line Switches for Silent Mode Installation of Backup Exec Switch /TS: Additional Switches Description Installs Backup Exec using the options specified with the additional switches. The /USER:"user" /DOM:"dm" /PASS:"pw" is required. /USER:"user" /DOM:"dm" /PASS:"pw" /DEST:"path" Required. Specifies an existing user, domain, and password for the Backup Exec system service account. Silent mode installation will not create a user. Specifies the path where Backup Exec will be installed. Otherwise, the default path Program Files\VERITAS\Backup Exec\NT 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.
/DOCS: /NOINSTALL:
57
Installing Backup Exec Command Line Switches for Silent Mode Installation of Backup Exec (continued) Switch Additional Switches /SNO:serial number Description Specifies one or more serial numbers to use for installing Backup Exec and additional options. Serial numbers are not required to install the Remote Administrator. You may specify up to 99 serial numbers. If none are specified, then an Evaluation copy of Backup Exec is installed. The following examples show how the /SNO switch can be used: /SNO:s1 /SNO:s1 s2 s3 s4 /SNO:s1 /SNO:s2 /SNO:s3 /SNO:s4 /TD:NEW or ALL /TD:NEW installs tape drivers only for drives that do not have drivers loaded. /TD:ALL installs tape drivers for all drives. /CPF:"file name" 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. Note The following switches are designed for use with Not For Resale, Open Option, and Evaluation versions of Backup Exec only. /LOADER: /IDR: Installs the Library Expansion Option. Installs the Intelligent Disaster Recovery Option. Installs the Backup Exec Agent for R/3 for Oracle Server. Installs the Advanced Open File Option. Administrators Guide
/XML:"file name"
/R3:
/OFO: 58
Installing Backup Exec Command Line Switches for Silent Mode Installation of Backup Exec (continued) Switch Additional Switches /TSM:IP address:port /SSO: Description Installs the IBM ADSM/TSM 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 Intelligent Image Option. Installs the Agent for Microsoft SharePoint Portal Server. Installs the Agent for Microsoft Exchange Server. Installs the Agent for Lotus Domino. Installs the Agent for Oracle Server. Installs the Agent for Microsoft SQL Server. Installs the Remote Agent for Windows Servers. Installs the NetWare Agent. Installs the ServerFree Option. Installs the Backup Exec Web Administration Console Installs the ExecView Communication Module. Type setup.exe /? to get the syntax. For example: setup.exe /ECM:myserver1 myserver2 myserver3 -s If a server is not specified, ECM will not be enabled.
Installation
/SSO:server name
/IIMAGE: /SHAREPT:
/EXCH:
/LOTUS: /ORACLE: /SQL:
/NTA:
/NWA: /SVRFREE: /BEWSA:
/ECM:<EIS server 1> <EIS server 2>...
59
See also: Installing Backup Exec Using the Installation Program on page 47 Uninstalling Backup Exec from the Command Line on page 61
Installing the Remote Administrator from 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 from the command line: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL 4. Type setup /RA: and the appropriate switches. For example: setup /RA: -s The command line switches used for silent mode installation of the Remote Administrator are described in the following table. Remember the following general rules for using these switches: Substitute values appropriate for your environment for values in italics; for example, substitute your password for password. Enclose the value in quotation marks if it contains spaces, such as Program Files\VERITAS\Backup Exec\NT.
Command Line Switches for Remote Administrator Silent Mode Installation Switch /RA: 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\VERITAS\Backup Exec\NT is used. Installs online documentation. Administrators Guide
/DOCS: 60
Installing Backup Exec Command Line Switches for Remote Administrator Silent Mode Installation (continued) Switch Additional Switches /NOINSTALL: Description 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. 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.
Installation
/CPF:"file name"
/XML:"file name"
Uninstalling Backup Exec from the Command Line

If Backup Exec is already installed, you can use the setup.exe program to uninstall Backup Exec program files and Backup Exec data.
To uninstall Backup Exec using the command line: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL. 4. To remove the Backup Exec program files but keep all of the Backup Exec data, type: SETUP
/UNINSTALL: /REMOVEALL:
To remove the Backup Exec program files and the Backup Exec data, type: SETUP
61
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:serial number The Backup Exec installation program is launched. The screens that allow you to enter the logon credentials and the serial number will appear with the information you provided on the command line. Unless you are installing a Not For Resale (NFR) or Open Options Suite edition, you do not have to enter commands for installing options such as Agent for Microsoft SQL Server or Agent for Microsoft Exchange Server. 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 a parameter file for Backup Exec: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL. 4. Type setup /TS: and the appropriate switches, including /CPF: and the full path name of the parameter file. For example, type: setup /TS: /USER:user /DOM:domain /PASS:password /SNO:serial number /CPF:"A:\file name" -S Backup Exec will be installed on your server and a parameter file containing the user name, domain, password, and serial number will be saved to a floppy diskette. You can use this parameter file to install to another computer.
To use this parameter file: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL. 4. Type: SETUP /PARAMS:"A:\file name" -S
62
Registering Backup Exec Online
5. If you want to overwrite a parameter, specify the new parameter. For example, to change the password, type: SETUP /PARAMS:"A:\file name" /PASS:new password -S
Installation
Note 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. See also: Installing Backup Exec from the Command Line (Silent Mode) on page 56 Command Line Switches for Backup Exec Silent Mode Installation on page 57
Registering Backup Exec Online

Launch the VERITAS Backup Exec Online Registration Wizard from either the install program or from the Help menu.
To register Backup Exec online from the Administration Console: 1. On the Help menu, click Register VERITAS Backup Exec. 2. Follow the wizard prompts. The Online Registration Wizard guides you through submitting a registration form to VERITAS Software Corporation and provides a survey designed to aid VERITAS in understanding how you use the product and in better understanding your needs.
63
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 Backup Exec installation program and select 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 run the Repair option: 1. Close the Backup Exec application. 2. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs. 3. Do one of the following: For Windows NT, on the Install/Uninstall tab on the Add/Remove Programs Properties dialog box, select VERITAS Backup Exec, and then click Add/Remove. For Windows 2000, Windows XP, or .NET, at the Add/Remove Programs dialog box, select VERITAS Backup Exec for Windows Servers, and then click Change.
4. Click Next. 5. Select Local Install and Repair, and then click Next. Note Make sure the option Remote Install is not selected. 6. Select Install. 7. Click Finish.
64
Starting and Stopping Backup Exec Services
Starting and Stopping Backup Exec Services
To stop or start Backup Exec services:
Installation
1. On the Tools menu, click Backup Exec Services. 2. Select the appropriate options as follows:
Backup Exec Services Manager options Item Server Description 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 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 Services credentials
Refresh Remove Server(s)
65
Uninstalling Backup Exec
Uninstalling Backup Exec

Use Microsofts Add/Remove Programs option to remove Backup Exec from a computer. For additional information on Add/Remove Programs, refer to your Microsoft documentation. Note When using the Shared Storage Option, you must uninstall Backup Exec from the secondary servers before uninstalling from the primary server.
To uninstall Backup Exec: 1. Close the Backup Exec application. 2. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs. 3. Do one of the following: For Windows NT, on the Install/Uninstall tab on the Add/Remove Programs Properties dialog box, select VERITAS Backup Exec, and then click Add/Remove. For Windows 2000, Windows XP, or .NET, at the Add/Remove Programs dialog box, select VERITAS Backup Exec for Windows Servers, and then click Remove.
4. When prompted to confirm the deletion of Backup Exec from your computer, click Yes. 5. When prompted to remove Backup Exec program files or all data, click Yes; click No to retain user-created data such as catalogs and job information. 6. If the uninstall program fails, click the View Installation Log File button for additional information. 7. When the uninstall is completed, click Finish. 8. If prompted, reboot the computer after uninstalling Backup Exec. Uninstalling Backup Exec also removes VERITAS tape class drivers. If you reinstall Backup Exec and want to use VERITAS tape class drivers, you must reinstall them. See also: Uninstalling Backup Exec from the Command Line on page 61
66
Installing the Backup Exec Remote Administrator

The Backup Exec Remote Administrator allows you to administrate the media server from a remote Windows server or workstation.
Installation
To remotely administrate both Backup Exec 8.6 and 9.0 media servers, install the Remote Administrator for both versions on the same computer but in different directories. To support the Remote Administrator, the media server requires that the Backup Exec system services must be running. Note The Remote Administrator for Backup Exec 9.0 for Windows Servers is not compatible with previous versions of Backup Exec. The Remote Administrator and the media server to which it is connecting must be the same version.
To install the Backup Exec Remote Administrator: 1. From the installation CD browser, choose to install VERITAS Backup Exec. The Welcome window appears. 2. Click Next. The Software License Agreement appears. 3. Select I accept the terms of the license agreement, and then click Next. 4. Select Local Install and Install Administration Console only, and then click Next. A dialog box appears requesting the destination directory for your Backup Exec program files. 5. Click Next to install the Backup Exec program files in the default directory, or click Change to select another directory for the installation, and then click Next. 6. Click Install. The installation copies the Backup Exec program files to the computer. 7. Click Finish. The Remote Administrator is installed. You can begin using Backup Exec. For more information, see Getting Started on page 73.
67
To run the Remote Administrator: 1. Click Start. 2. Point to Programs, and then click VERITAS Backup Exec for Windows Servers. Note 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:
Connect to Server dialog options Item Server Description Select the name of the media server from the Server drop-down list box 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. Note Each Windows 2000 server in the domain that has Backup Exec installed will automatically appear 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. Login Information User name Type an administrator user name for the server to which you are connecting. 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.
Password Domain
68
Installing the Backup Exec Remote Administrator Connect to Server dialog options (continued) Item Services Description 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.
Installation
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 will now connect 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 (e.g., domain1\howard). This also applies to workgroup accounts (e.g., machinename\george).
69
Using VERITAS Update
Using VERITAS Update

VERITAS Update, which allows users of Backup Exec to be informed of updates, upgrades, and new versions of Backup Exec, automatically installs with Backup Exec. If you enable the automated option, you can configure VERITAS Update to poll the main VERITAS web server for any available updates. You can select to have VERITAS Update poll on a daily, weekly, or monthly interval, and can configure when the polling will start. If updates are available, VERITAS Update alerts you of the update so you can download and install any selected updates.
To configure VERITAS Update: 1. On the Tools menu, click VERITAS Update. 2. On the VERITAS Update Welcome screen, click Configure. 3. Click Notify me when new updates are available. 4. Select the date and time for Backup Exec to start polling for updates. 5. Select the Frequency for polling to occur. Options are: Daily. If you selected Daily as the polling Frequency, Backup Exec polls every day at the time you selected. Weekly. If you selected Weekly as the polling Frequency, Backup Exec polls every week on the same day of the week and at the same time you selected. Monthly. If you selected Monthly as the polling Frequency, Backup Exec polls every month on the same date and at the same time you selected.
6. Enter Local Task Credentials. 7. Click Apply.
70
Upgrading from Previous Versions of Backup Exec
Upgrading from Previous Versions of Backup Exec

This current version of Backup Exec for Windows Servers replaces any previous versions; no separate migration or upgrade utility is necessary. Most settings and all data from previous versions of Backup Exec (for example, when the TSM option adds registry settings) are kept. At the end of the installation, the upgrade process is summarized. Only Backup Exec version 8.0 and later can be migrated to this release. When upgrading, only the Backup Exec for Windows Servers options for which you have provided serial numbers are upgraded. Components that are already selected in the Backup Exec Install Options dialog box in the install program must remain selected so that all licensed components are upgraded. It is recommended that you add all previous version serial numbers before installing the new version of Backup Exec so that these options are automatically upgraded. Note Evaluation versions of Backup Exec for Windows Servers will replace any current installation. You cannot have separate installations of different versions on the same server.
Installation
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 Servers. For more information, see Installing the Remote Agent to Remote Windows Servers on page 823. Backup Exec NetWare Agent. For more information, see Installing the Remote Agent for NetWare on page 1225 and Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. Backup Exec Agent for Lotus Domino. For more information, see Installing the Lotus Domino Agent on the Media Server on page 1181. Backup Exec Advanced Open File Option. For more information, see Installing the Advanced Open File Option on page 959.
To reinstall these options, repeat the installation steps for each option.
71
Upgrading Backup Exec Options on Remote Computers
72
Getting Started
In Getting Started, youll find:

3
Getting Started
A checklist that will help you prepare for the First Time Startup Wizard. Details on the Backup Exec Assistant, Administration Console, and the Information Desk. Details of default options set when Backup Exec is installed. Layouts and descriptions of Backup Exec menus.
Before Starting Backup Exec

For best results before starting Backup Exec, do the following: Make sure your storage devices are connected and configured properly. Decide if your backup will be to a tape device or a disk device. You will be able to configure both during the First Time Startup Wizard. If youre backing up to a tape device, verify that the device is supported. You can install drivers for the devices during the First Time Startup Wizard. 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. For more information, see Using Backup-to-Disk Folders and Files on page 143.
Understand how Backup Exec provides overwrite protection for your media. For more information, see Media Overwrite Protection on page 185. Understand the default media set and its infinite overwrite protection period. For more information, see Media Overwrite Protection Levels on page 190.
73
Starting Backup Exec
Learn about creating new media sets with weekly, monthly, or quarterly retention periods. For more information, see Default Media Set on page 189. Decide what 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. Youll be prompted for a default Backup Exec logon account during the First Time Startup Wizard. For more information, see Configuring Logon Accounts on page 347.
Starting Backup Exec
To start the Backup Exec Administration Console, click Start, point to Programs, and then click VERITAS 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.
See also: Using the Administration Console on page 76 Using Backup Exec Dialog Boxes on page 79
First Time Startup Wizard

The first time you run Backup Exec, the First Time Startup Wizard appears. The First Time Startup Wizard is a collection of wizards that help you set up the important features of Backup Exec, including media sets, overwrite protection settings, devices, and logon accounts. You must complete the applicable sections of this wizard as it guides you in preparing Backup Exec for operations. To begin the wizard, click Next on the Welcome page. The following wizards are part of the First Time Startup Wizard:

Media Management with Media Sets. To learn more about managing media through media sets, read Media Overwrite Protection on page 185. Preferred Overwrite Media Type. Review the circumstances and order in which Backup Exec searches for overwritable media in Media Overwrite Options on page 192. Overwrite Protection Level. The media overwrite protection levels are global settings that designate groups of media as overwritable or write-protected. For more information, see Media Overwrite Protection Levels on page 190. Detected Hardware. The Device Configuration wizard allows you to verify that all of the storage devices attached to your system appear, and to verify that robotic libraries and storage devices are properly configured.
74
First Time Startup Wizard
If you do not see one or more of your attached storage devices in the Backup Devices window, click the Configure Devices button. This will guide you through installing the appropriate drivers for the storage hardware connected to your system. Detected Backup-to-Disk Folders. Click the Add Backup-to-Disk Folder button to set up folders on your hard drive to target for backup jobs. For more information, see Using Backup-to-Disk Folders and Files on page 143. The backup folders you add here will be included in the All Drives drive pool, which is Backup Execs default target for backup jobs. Backups submitted to the All Drives drive pool may be processed on an attached media device or to one of the backup folders on your hard disk. Drive Configuration. Verify that Backup Exec has configured all of your drives correctly. If all of your drives do not display on the list, follow the instructions in the wizard to install the VERITAS device drivers.
Getting Started
Configure IDR Options. If you installed the Intelligent Disaster Recovery Option, youll be prompted to configure IDR. For details, read Getting Started with IDR on page 859. Logon Accounts. Use the Logon Account Wizard to set up Backup Exec logon accounts to access resources such as servers, shares, and databases. For details, read about logon accounts in Configuring Logon Accounts on page 347.
After you use the First Time Startup Wizard, you can access some of the wizards that make up the First Time Wizard individually. To access the wizards individually, from the Tools menu, select Wizards, and then select the wizard you want to use.
Chapter 3, Getting Started
75
Using the Administration Console

Backup Execs Administration Console has been updated with this release to incorporate new features and to make it easier for you to take advantage of Backup Execs features and capabilities. Note If you are using Backup Exec Web Administrative Console (BEWAC), the Administration Console displays differently. For more information, see Navigating in BEWAC on page 784.
Administration Console Menu bar Navigation bar
Columns
Task pane Results pane Preview pane
Selection pane Status bar
The main Administration Console screen includes the following components:
Menu bar. Backup Execs menu bar appears across the top of your screen. To display a menu, click the menu name. Backup Exec operations can be launched by clicking options from a menu. Some options may be unavailable until an item is selected from the console screen. For example, Rename cannot be selected from the Edit menu unless you have first selected an item to be renamed from either the Devices or Media views. For detailed information about the menus and their options, see on page 87.
76
Navigation bar. The navigation bar appears under the menu bar and allows you to quickly create a backup or restore job or to navigate to Backup Execs seven views. Click Backup or Restore to create a job. Change views by clicking the name of the view you want. The seven views that can be accessed through the navigation bar include: Overview. Use this view to access the Information Desk, view a summary of the system you are logged on to, or launch and configure the connection settings for ExecView. 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.
Getting Started
Note If you are using BEWAC, the Outlook-like calendar is not available. 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.
Note If you are using BEWAC, the Alerts view is not available. You can access alerts through the Status area. For more information, see Viewing, Clearing, and Responding to Alerts on page 786. Reports. Use this to view, print, save, and schedule reports about your media server, its operations, and its device and media usage. 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. Selection pane. The Selection pane is where you select items to work with. For example, it is where you select files to back up or restore.
77
Results pane. The Results pane is the large pane on the right side of the screen that usually contains a list or tree view of items that correspond to items that are selected in the Selection pane. For example, if you select a Backup-to-Disk folder in the Selection pane, the Backup-to-Disk files that are contained in the folder display in the Results pane. This pane may be divided to display a preview pane. Preview pane. The preview pane displays on the bottom right of the Administration Console. It displays information about the item selected in the list or tree view. This pane can be hidden by selecting View, and then selecting Preview Pane.
Note If you are using BEWAC, the Preview pane is not available.
Status bar. The status bar appears on the bottom of the Administration Console and provides information about the media server, jobs running or scheduled to run on the server, alerts, and services running. Columns. You can change the location of columns by dragging and dropping them. In addition, you can 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.
78
Using Backup Exec Dialog Boxes

When an option is selected from a menu, a shortcut menu, or the task pane, a dialog box usually displays.
Dialog box
Nodes
Getting Started
Subnodes
Properties pane
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.
Using the Overview View

The Overview view includes the Information Desk and the System Summary. From the Overview view you also can configure ExecView connection settings. When Backup Exec is started for the first time, the Administration Consoles Information Desk appears. The Information Desk has links to the list of new features in this release, the technical support web site, the supported device list, device configuration information, default options for Backup Exec, and tasks such as backing up data and monitoring jobs. Links are also provided to the ReadMe, the online Administrators Guide, the wizards, and the VERITAS company web site.
79
To view the Information Desk:
On the navigation bar, click Overview, and then under Views on the task pane, click Information Desk.
Information Desk
The System Summary briefly details Backup Exec activity for the last 24, 48, or 72 hours, such as the number of jobs that were run, the number of jobs that failed, the amount of data backed up, and the number of media used. You can also see the number and type of active alerts, the number of scratch media available in the storage devices, a list of upcoming jobs, and the number of jobs that are currently running.
80
To view the System Summary:
On the navigation bar, click Overview, and then under Views on the task pane, click System Summary.
System Summary
Getting Started
81
Frequently Asked Questions
Using the Backup Exec Assistant

The Backup Exec Assistant provides easy access to commonly used features, such as Backup Execs wizards, the job monitor, and job setup. If you want the Backup Exec Assistant to display each time Backup Exec is started, on the Tools menu, select Backup Exec Assistant, and then select the Always show me this at startup checkbox. The Backup Exec Assistant is not available in BEWAC.
Backup Exec Assistant

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.

If you are new to Backup Exec, you can use the Backup Wizard, which helps guide you through the setup of a backup job. If you are an experienced Backup Exec user: On the navigation bar, click Backup to set up the options for a backup job. On the navigation bar, click Job Setup to create a template to use for multiple backup jobs.
82
To quickly create a backup job to back up the media server, click the one-button backup link on the Information Desk. Use Windows Explorer to create a backup job.
For details about the various ways to create a backup job, see Creating a Backup Job on page 235. Where can I find the wizards?

On the Information Desk. On the navigation bar, click Overview, then under View on the task pane, click Information Desk.
Getting Started
On the Tools menu, click Backup Exec Assistant, or further down the Tools menu, click Wizards.
Where can I find the Readme file?
On the Information Desk. On the navigation bar, click Overview, then under View on the task pane, click Information Desk. Under Documentation, click View ReadMe file. In the directory where Backup Exec was installed. On the Help menu, click View ReadMe File.
Where can I find the online documentation for Backup Exec?
On the Information Desk. On the navigation bar, click Overview, then under View on the task pane, click Information Desk. Under Documentation, click View VERITAS Backup Exec Administrators Guide. On the Help menu, click Topics to see the online help. Or on the Help menu, click View VERITAS Backup Exec Administrators Guide to view an online version of the System Administration Guide in the Adobe Portable Document Format (PDF).
How do I get in touch with Technical Support?
From the Information Desk. On the navigation bar, click Overview, then under View on the task pane, click Information Desk. Under Technical Support, click VERITAS Backup Exec support.
83
Backup Exec Defaults

When you start Backup Exec for the first time, defaults are already set. 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 will probably want to 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 also: Setting Default Backup Options on page 312 Setting Restore Defaults on page 441 Setting Test Run Default Options on page 310 Setting Default Pre/Post Commands on page 319 Configuring Default Job Log Options on page 384 Specifying the Default Backup Network on page 325 Setting Advanced Open File Option as the Default Setting for All Backup Jobs on page 966 Setting Default Backup and Restore Options for SQL 2000 on page 1012 Setting Default Backup and Restore Options for SQL 7.0 on page 1056 Setting Default Backup and Restore Options for Exchange 2000 on page 1097 Setting Default Backup and Restore Options for Exchange 5.5 on page 1132 Configuring Default Lotus Domino Options on page 1184 Default Settings for the Remote Agent for NetWare on page 1235 Configuring Default Schedule Options on page 363 Changing Default Preferences on page 85 Setting Catalog Defaults on page 399 Setting Default Media Options on page 203 Bar Code Labeling in Mixed Media Libraries on page 199 Configuring Database Maintenance on page 389
84
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. On the Tools menu, click Options. 2. On the Properties pane, under Settings, click Preferences.
Getting Started
3. Select the appropriate options as follows:.

Options - Set Application Defaults - Preferences Item Show splash screen at startup Description 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 media in the storage devices when Backup Execs services are starting. Depending on the number of storage devices attached to your system, this process may take a few minutes. If you are using a robotic library, all of the robotic librarys slots are inventoried. Select this option to create and submit backup jobs from Windows Explorer. For more information, see Using Backup Execs Windows Explorer Interface on page 286. If this option is cleared, you will not be able to submit backups using the Backup Exec Windows Explorer interface. Select this option to have Backup Exec display a summary of the backup job options you selected before submitting the job to the job queue.
Inventory all drives on Backup Exec services startup
Enable backup from Windows Explorer
Display the job summary dialog before creating a backup job
85
Backup Exec Defaults Options - Set Application Defaults - Preferences (continued) Item Display progress indicators for backup jobs (requires additional time to pre-scan devices) Description Select this option to display the percent completed number while a backup job is processing. These indicators appear in the Job Activity tab, and they allow you to monitor the progress of the job. Backups might take a little longer to complete when this option is selected because the target resources must be scanned to determine the amount of data to be backed up. Note Due to the time required to scan the target resources, selecting this option when backing up remote resources is not recommended. Alerts Automatically display new alerts Select this option to have alerts automatically appear on the desktop when they are sent. If you do not choose this option, you are required to view and respond to alerts through the Alerts view. Select this option to have Backup Exec send an audible tone when an alert is generated. Information about alerts can be found in the Alerts view.
Play sound after receiving alert
86
Changing General Job Defaults

You can set the default priority, device, and media set to use for each job created.
To change general job defaults: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click General. 3. Select the appropriate options as follows:
Options-Set General Application Defaults Item Job priority Description Select the default priority that you want to assign to all jobs. The choices are Highest, High, Medium, Low, and Lowest. You can change this default for each job individually. Select the device that you want to be used 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.
Getting Started
Device
Media set
87
88
Managing Devices
Device management in Backup Exec simplifies how you organize and allocate the storage devices recognized by Backup Exec, including:

Tape drives or robotic libraries physically attached to a media server. Virtual devices called Backup-to-Disk Folders created through Backup Execs Backup-to-Disk feature. Shared devices used in a SAN environment. Removable storage devices shared by applications through the use of Microsofts Removable Storage Feature.
Managing Devices
With Backup Exec, you can maximize your hardware investment by organizing your drives in one or both of the following methods:
Drive pools. Drives are grouped so that jobs assigned to the drive pool are run on the first available drive. Setting up drive pools offers the following benefits: Automatic job rescheduling. If a drive 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 drive pool. Concurrent processing. Drives in the drive pool run different jobs at the same time, allowing maximum hardware efficiency. Dynamic load balancing. Jobs are more evenly distributed between all of the drives included in the drive 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.
Or, you can use the storage devices as they are configured by Backup Exec at installation, without making any changes. The default drive pool, All Drives (Server Name) is the default destination device when you create a backup job. By default, the All Drives drive pool contains all locally-attached drives, or if you are using the SAN Shared Storage Option, both locally-attached and shared storage devices appear in All Drives (Server Name).
89
Viewing Devices
In addition to drive pools and cascaded drive pools, Backup Exec provides other device management capabilities. You can:

Identify and monitor the current status of all storage devices. Change physical tape devices without rebooting the Backup Exec server. Monitor device usage statistics and track hardware errors. Backup Exec keeps track of the 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 drives 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 drive can still take full advantage of Backup Execs device monitoring to help make sure their drives are working properly. See also: VERITAS Backup Exec - SAN Shared Storage Option on page 911
Viewing Devices
When Backup Exec is installed, all storage devices connected to the media server are automatically recognized as either robotic libraries or stand-alone drives. Note Support for a single robotic library drive is included with Backup Exec for Windows Servers. Licenses for additional robotic library drives are available for purchase. If you group one or more robotic library slots into partitions, the partition drive pools appear in the Devices view under the Drive Pools icon. For information about partitioning robotic library slots, see Creating Robotic Library Partitions on page 140. Click Devices on the navigation bar to see how devices are organized logically in drive pools, and how drives are arranged physically on servers. All devices that are displayed under All Devices are available, including drive pools, stand-alone drives, robotic libraries, backup-to-disk folders, and cascaded drive pools. If the Shared Storage Option is installed, you can also view available secondary storage devices on the storage area network.
90
Viewing Devices Devices view
Managing Devices
All logical groupings of the physical drives are displayed under Drive Pools and Cascaded Drive Pools. Cascaded drive pools are displayed under servers because they only consist of drives from that server; they effectively act as a single device under that server. The default drive pool All Drives (Server Name) contains the servers locally attached drives as well as any Backup-to-Disk Folders created. Backup-to-Disk Folders are destination devices for backups that are directed to your hard disk. The data from these backups is saved on disk as backup files. If you are using the SAN Shared Storage Option, each server on the SAN will have an All Drives (Server Name) node that contains both local and shared devices available to the server. At installation, all storage devices are automatically assigned to All Drives (Server Name). See also: Viewing Media Information on page 92 Viewing Drive Pool Properties on page 105 Viewing Properties of a Cascaded Drive Pool on page 111 Viewing and Using Drive Properties and Statistics on page 116 About Devices in the Shared Storage Environment on page 916
Chapter 4, Managing Devices
91
Viewing Devices
Viewing Media Information

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. Information appearing includes:

Slot number. Number of the slot. This field only appears if Slots has been selected. Bar Code. Label obtained from a bar code reader. This field only appears if Slots has been selected. Bar code information only appears if the robotic library has a bar code reader and a bar code label is on the media. Media Label. Name of the media label. The name can be: Assigned automatically by Backup Exec. Assigned or changed by the administrator. A pre-assigned bar code label.
Media Description. By default, displays the original media label if the media is imported media. If the media description has been edited, the new description appears. Otherwise, this field is blank. Allocated Date. Date and time that the media was allocated to a media set as a result of an overwrite operation. Media Set. Name of the media set in which the media is assigned. Overwrite Protected Until. Date and time on which the medias overwrite protection ends. Until that date and time, the media cannot be overwritten. Appendable Until. Date and time until which the media can be appended. 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.
92
Configuring Devices
Bytes Written. The amount of data that has been written into blocks on the media. Bytes written may differ from Used capacity due to the effects of data compression and media flaws. Data compression will tend to increase Bytes written when compared to Used capacity. Media flaws will decrease Bytes written when compared to Used capacity. 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.
See also: VERITAS Backup Exec - Library Expansion Option on page 1143 About Devices in the Shared Storage Environment on page 916
Configuring Devices
Backup Exec provides two wizards for configuring and adding storage devices to your media server:
Managing Devices
The Device Configuration Wizard. This wizard, which appears when Backup Exec is first started, allows you to verify that all of the storage devices attached to your system appear, and to ensure that robotic libraries and storage devices are properly configured. You can also use the Device Configuration Wizard to configure Backup Folders on your hard disk. On the Tools menu, point to Wizards, and then select Device Configuration Wizard to run this wizard at any time. The Hot-swappable Device Wizard. This wizard allows you to replace or add storage devices without having to reboot the media server.
If you are using a robotic library, make sure the robotic library hardware is configured properly. See also: First Time Startup Wizard on page 74 Hot Swap for Storage Devices on page 94 Setting Up Robotic Library Hardware on page 1143
93
Configuring Devices
Hot Swap for Storage Devices

You can replace or add a hot-swappable tape drive on a Backup Exec media server without having to reboot the server, provided the media server is not a Windows NT 4.0 server. The Hot-swappable Device Wizard guides you through the process. After you start the Hot-swappable Device Wizard and close the Backup Exec Administration console, the Hot-Swappable Device Wizard waits until any jobs that were processing are completed. The wizard pauses the Backup Exec 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 console. The new storage device is displayed in the Devices view, and usage statistics for the drives begin accumulating. You may want to add the new drive to a drive pool or cascaded drive pool. The replaced storage device is displayed in the Devices view with a status of Offline. To remove the storage device from Backup Exec, you must disable it and then delete it from the Devices view. Note Only tape drives are supported for hot swapping and adding. The tape drives must be hot-swap capable. See the owners manual for your tape drive for more details.
To start the Hot-swappable Device Wizard: 1. On Tools menu, point to Wizards, and then click Hot-swappable Device Wizard. 2. Follow the on-screen prompts.
Pausing, Resuming, and Renaming 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 also rename the media servers storage devices as well as any attached robotic libraries.
To pause or resume the media server: 1. On the navigation bar, click Devices. 2. Click the server icon.
94
Configuring Devices
3. Under Drive 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 drive: 1. On the navigation bar, click Devices. 2. Click the robotic library drive or stand-alone drive. 3. Under Drive Tasks in the task pane, select Paused. A check mark appears next to the Paused option if the drive is currently paused. If the drive was not already paused, it is now paused. If the drive was already paused, it is now resumed.
To rename a robotic library or drive: 1. On the navigation bar, click Devices. 2. Click the robotic library or drive that you want to rename. 3. Under General Tasks in the task pane, click Rename. 4. On the Rename dialog box, type the new name, and then click OK. See also: Renaming a Backup Folder on page 148 Pausing and Resuming a Backup Folder on page 151 Renaming a Drive Pool on page 104 Renaming a Cascaded Drive Pool on page 111
Managing Devices
95
Using Drive Pools
Using Drive Pools

A drive pool is a grouping of drives for Backup Exec operations. Drives can belong to more than one drive pool, unless a drive is in a cascaded drive pool. Drive pools can contain different types of drives, including specific drives in multi-drive robotic libraries. In a drive pool, Backup Exec selects the oldest recyclable media in all of the drives in the drive pool to use first. If more than one media meeting the requirements is found, Backup Exec then searches the drives in a drive pool according to drive priority and uses the oldest recyclable media in the drive that has the highest priority. When you submit a backup job to a drive pool, the job is automatically sent to the first available storage device in that drive pool. As other jobs are created and started, they can run concurrently on other storage devices in the drive pool. By dynamically allocating drives as jobs are submitted, Backup Exec processes jobs quickly and efficiently. Drive pools also provide automatic job rescheduling. For example, if a drive pool contains four stand-alone devices 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 drive pool. You can assign priorities to drives in a drive pool so that a specific drive is used before other drives in the drive pool. The priority assigned to a drive in one drive pool is unrelated to that drives priority in any other drive pool. For example, if Drive 1 is placed in both Drive Pool A and Drive Pool B, you can assign different priorities to it in each drive pool. Drive 1 can have a high priority in Drive Pool A and a low priority in Drive Pool B. You can also send backup jobs to specific drives in a drive pool. However, if that drive is busy, the job must wait until the drive becomes available. When a specific drive is assigned, the job cannot be automatically routed to the next available drive. All Drives (Server Name) is the default drive pool, created when Backup Exec is installed. All devices recognized by Backup Exec at startup are automatically assigned to All Drives (Server Name). You can create other drive pools to meet your particular requirements, and assign and reassign storage devices to these pools. For example, you may want to separate high-performance drives from lower performance drives in a separate drive pool in order to send high-priority jobs to the fast drive pool for quicker completion. See also: Using Cascaded Drive Pools on page 106
96
Using Drive Pools
Creating Drive Pools

You can place any stand-alone drives, and any drives in single or multiple drive robotic libraries, into a drive pool. Drives that are in a cascaded drive pool are not available to be placed in another drive pool unless they are deleted from the cascaded drive pool first.
To create a drive pool: 1. On the navigation bar, click Devices. 2. Click Drive Pools. 3. Under Drive Pool Tasks in the task pane, select New drive pool.
New Drive Pool dialog box
Managing Devices
4. Select the appropriate options as follows:

New Drive Pool fields Item Drive Pool Name Description Type the name of the new drive pool that you want to create.
Select the drives to be Select the drives you want to include in the new drive pool. included in this Drive Pool
5. Click OK. See also: Using Cascaded Drive Pools on page 106 Creating a Cascaded Drive Pool on page 107
97
Using Drive Pools
Adding Drives to a Drive Pool

You can add a drive to an existing drive pool, unless the drive is in a cascaded drive pool. Drives that are in a cascaded drive pool will be automatically deleted from the cascaded drive pool if they are placed in another drive pool.
To add a drive to a drive pool: 1. On the navigation bar, click Devices. 2. Select the drive pool. 3. Under Drive Pool Tasks in the task pane, select Add device.
Add Drives to Drive Pool dialog box

Add Drives to Drive Pool options Item Drive Pool Name Description Displays the name of the drive pool to which you want to add drives.
Select the drives to be Select the drives you want to include in the drive pool. included in this Drive Pool
5. Click OK.
98
Using Drive Pools
Setting Priorities for Drives in a Drive Pool

You can set a priority that determines the order in which the drives in a drive pool are used. The default priority is 10 so all drives have the same priority initially. The drive to which you assign the lowest number is the first drive to be used in the drive pool; for example, a drive with a priority of 1 is used before a drive with a priority of 5. You can set a priority of 1 to 99. Note Overwrite and append periods for media take precedence over drive priority. The Priority option is only displayed when viewing drive properties under a drive pool icon. Drives displayed under the Stand-alone Drives icon or Robotic Libraries icon do not display a Priority option because the drive may belong to multiple drive pools and have a different priority in each drive pool.
To set drive priority in a drive pool: 1. On the navigation bar, click Devices. 2. Under Drive Pools, select the drive pool containing the drive for which you want to set a priority. 3. Select the drive. 4. Under General Tasks in the task pane, select Properties.
Managing Devices
99
Using Drive Pools
5. Click Configuration.
Configuration tab
6. In Priority, Type a number from 1 to 99, with 1 designating this drive as the first drive to be used in the drive pool. 7. Click OK. See also: Viewing Drive Configuration Properties on page 119
100
Using Drive Pools
Deleting Drives from a Drive Pool

You can delete a drive from a drive pool. The drive will still be in the Backup Exec device database and will still be available for use in other drive pools. It is not necessary to delete drives from a drive pool before you delete that pool; the drives are automatically removed when the pool is deleted.
To delete a drive from a drive pool: 1. On the navigation bar, click Devices. 2. Under Drive Pools, select the drive pool from which you want to delete a drive. 3. Select the drive you want to remove from the drive pool. Make sure you select a drive under Drive Pools and not under the server icon; if you delete a drive under the server icon, the drive is deleted from the database, not just from the drive pool. 4. Under Drive Pool Tasks in the task pane, select Remove device.
Managing Devices
Delete Drive From Drive Pool dialog box
5. To remove the displayed drive from a drive pool, click Yes.
101
Using Drive Pools
Deleting Drive Pools

It is not necessary to delete drives from a drive pool before you delete that pool; the drives are automatically removed when the pool is deleted. You cannot delete the All Drives drive pool, but you can delete all of the drives in it. If there are scheduled jobs assigned to the deleted drive pool, you are prompted to redirect them to another drive pool.
To delete a drive pool: 1. On the navigation bar, click Devices. 2. Under Drive Pools, select the drive pool you want to delete. 3. Under General Tasks on the task pane, select Delete.
Delete Drive Pool dialog box
4. Click Yes or Yes to All to delete the drive pool or pools that are displayed. 5. If there are scheduled jobs assigned to the deleted drive pool, you are prompted to redirect the jobs to another drive pool or stand-alone device. See also: Deleting Drives from a Drive Pool on page 101 Retargeting Jobs from a Deleted Drive Pool or Media Set on page 103
102
Using Drive Pools
Retargeting Jobs from a Deleted Drive Pool or Media Set

If a drive pool or media set is deleted, and there are scheduled jobs assigned to that drive pool or media set, you are prompted to redirect the jobs to another drive pool or stand-alone device, or to another media set.
To redirect a scheduled job: 1. When prompted to redirect the jobs, click Yes.
Retarget Job dialog box
The job to be redirected is displayed in the Retarget Job dialog box. If there are scheduled jobs assigned to the deleted drive pool or media set, you are prompted to redirect the jobs to another drive pool or media set. 2. Click the <Down arrow> to see more drive pools, and then select the new drive pool, standalone drive, or media set to which you want to redirect the scheduled jobs. 3. Click Yes or Yes to All to redirect the job or jobs that are displayed to the new drive pool, drive, or media set. Note If you choose not to retarget a job, the job will fail. To later target the job to another device, you will need to manually edit the job.
Managing Devices
103
Using Drive Pools
Renaming a Drive Pool

The default All Drives drive pool cannot be renamed, but you can rename any user-created drive pool using either the Rename option or the drive pools Properties dialog box.
To rename a drive pool: 1. On the navigation bar, click Devices. 2. Under Drive Pools, select the drive pool you want to rename. 3. Under General Tasks, select Rename. 4. On the Rename dialog box, type the new name to assign to this drive pool, and then click OK. The drive pool is listed with the new name. See also: Viewing Drive Pool Properties on page 105
104
Using Drive Pools
Viewing Drive Pool Properties

Use Properties to view properties for a drive pool, or to rename the drive pool.
To view properties for a drive pool: 1. On the navigation bar, click Devices. 2. Under Drive Pools in the tree view, select the drive pool. 3. Under General Tasks in the task pane, select Properties.
Drive Pool Properties dialog box
Managing Devices
105
Using Cascaded Drive Pools
The Drive Pool Properties dialog box provides the following information:
Drive Pool properties Item Name Description Displays the name of the drive pool. Rename the drive pool by typing a new name in this field. The date and time that this drive pool was created. Displays the drive pool name.
Creation date Full name
4. After viewing the drive pool properties, click OK.

You can cascade (link) multiple stand-alone drives together to create one logical drive. By cascading the drives, backup jobs can automatically roll to the media in the next drive when the media is filled. Although multiple 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. Drives in a cascaded drive pool are not available for concurrent operations. Only one drive is used at a time. The next 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. See also: Using Drive Pools on page 96
106
Requirements for Using Cascaded Drive Pools

In order to cascade drives, the drives must be the same drive type, such as DLT 32K. To determine the drive type, look in the drives property page. For more information, see Viewing and Using Drive Properties and Statistics on page 116. Caution If a drive 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, which could make restore operations difficult.
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. Note Overwrite and append periods for media take precedence over drive priority.
Managing Devices
To create a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Select Cascaded Drive Pools. 3. Under Drive Pool Tasks in the task pane, select New drive pool.
New Cascaded Drive Pool dialog box
107

New Cascaded Drive Pool options Item Drive Pool Name Description Type the name of the new cascaded drive pool that you want to create. Select the type of drive you want to use in this cascaded drive pool. After you select a drive type, only drives of that same type are displayed in the selection list.
Drive Type
Select the drives to be Add the drives you want to include in the new cascaded drive pool included in the by selecting the drive. Cascaded Drive Pool. Any drives moved to a cascaded drive pool will be removed from any drive pools they are currently in.
5. Click OK. The new cascaded drive pool is displayed in the Cascaded Drive Pool list in the Devices view. See also: Deleting Drives from a Cascaded Drive Pool on page 109 Deleting a Cascaded Drive Pool on page 110
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 normal drive pool will be removed from the other pool when added to a cascaded drive pool. Also, drives added to a cascaded drive pool will be removed from other drive pools.
To add a drive to a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Select the cascaded drive pool to which you want to add a drive. 3. Under Drive Pool Tasks in the task pane, select Add device.
108

Add Drives to Cascaded Drive Pool fields Item Drive Pool Name Description Displays the name of the drive pool to which you want to add drives.
Select the drives to be Select the drives you want to include in the drive pool. included in this Drive Pool
5. Click OK.
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 drive 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.
Managing Devices
To delete a drive from a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Select the cascaded drive pool from which you want to delete a drive. 3. Select the drive you want to delete from the cascaded drive pool.
109
4. Under Drive Pool Tasks in the task pane, select Remove device.
Delete Drive From Cascaded Drive Pool dialog box
The name of the drive you want to remove from the cascaded drive pool is displayed. 5. Click Yes to remove this drive from the cascaded drive pool. See also: Deleting a Cascaded Drive Pool on page 110 Erasing Media on page 168
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 there are scheduled jobs assigned to the deleted cascaded drive pool, you are prompted to redirect them to another device or drive pool.
To delete a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Under Cascaded Drive Pools, select the drive pool you want to delete. 3. Click Delete on the shortcut menu. The name of the cascaded drive pool you selected to delete appears. 4. Click Yes. 5. If there are scheduled jobs assigned to the deleted drive pool, you are prompted to redirect the jobs to another drive pool or stand-alone device. See also: Retargeting Jobs from a Deleted Drive Pool or Media Set on page 103
110
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. On the navigation bar, click Devices. 2. Under Cascaded Drive Pools, select the drive pool you want to rename. 3. Under General Tasks in the task pane, select Rename. 4. On the Rename dialog box, type the new name for the cascaded drive pool, and 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.
Managing Devices
To view properties of a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Under Cascaded Drive Pools, select the drive pool for which you want to view properties. 3. Under General Tasks in the task pane, select Properties. The Cascaded Drive Pool Properties dialog box provides the following information:
Cascaded Drive Pool properties Item Name Description Displays the name of the drive pool. Rename the drive pool by typing a new name in this field. Displays the date and time that this drive pool was created. Displays the drive pool name.
Creation Date Full Name
4. After viewing the properties of the cascaded drive pool, click OK.
111
Viewing Server Properties and Running Server Diagnostics

Use Properties to view information about your media server, including the version of Backup Exec installed, and system information. From the properties System tab, you can also run BE Diagnostics, a Backup Exec diagnostic utility. This utility creates a file (bediag_(machine_name).txt) that includes useful configuration information for the server. For more information on using BE Diagnostics, see Using Backup Execs Diagnostic Utility BEDIAG on page 554. Technical services can use the results of BE Diagnostics to troubleshoot problems. Note You can also run BE Diagnostics for a remote server (see Running Diagnostics on Remote Server on page 556).
To view server properties: 1. On the navigation bar, click Devices. 2. Select the server from the tree view. 3. Under General Tasks in the task pane, select Properties.
Server tab
112
The Server Properties Server tab provides the following information:

Server tab Item Name Status Description The name of the media server. The status of the media server. An active media servers status displays Running. Backup Exec version and revision information. The type of server. The serial number under which Backup Exec is installed. Eval Edition is displayed if a serial number was not provided during Backup Execs installation.
Version Description Serial #
Server time
Managing Devices
Start date and time
The date and time Backup Exec was initially installed and launched on this media server. The current date and time.
Current date and time Statistics Number of devices
The 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. The number of jobs currently in progress on this media server. The total number of alerts generated on this media server since the Backup Exec services were last started. The total number of jobs executed on this media server since the Backup Exec services were last started.
Number of active jobs Total number of alerts since server startup Total number of jobs completed since server startup
113
4. Click System to view additional information about the media server.

System tab
The Server Properties System tab provides the following information:

System tab for media server Properties dialog box Item Operating system Type The type of operating system currently running on this media server. The version of the operating system. The build number of the operating system. Description
Version Build Processor Type Level
The type of processor installed in this media server. The processor level on this server.
Number of processors The number of processors on this server.
114
Viewing Server Properties and Running Server Diagnostics System tab for media server Properties dialog box (continued) Item Memory Physical Page size Virtual remaining Page file Run diagnostics The amount of hardware RAM installed in the media server. The size of a single Windows NT virtual memory page. The amount of virtual memory remaining on the system. The size of the Windows NT virtual memory paging file. Note If you call Technical Support with a problem, they may request that you run Diagnostics and provide them with the results. Technical Support can use the results of this utility to pinpoint your problem and quickly solve it. Click to run the Diagnostics utility to a file (bediag(machine_name).txt) that includes useful configuration information for the server such as: Account groups, account privileges, and environment settings. Backup Exec Software version and registry information, Backup Exec Agent listing, Windows NT version information, SCSI hardware configuration, SQL Server information, Driver services information, and NT Services information. File Server information, supported shared directories, and Windows sockets information. Description
Managing Devices
5. After viewing Properties for the media server, click OK.
115
Viewing and Using Drive Properties and Statistics

Backup Exec provides details on each drive 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 drive properties tabbed pages are for information only.
To view a drives properties: 1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. 3. Select the drive you want to view properties for.
4. Under General Tasks in the task pane, select Properties. See also: Viewing General Drive Properties on page 117 Viewing Drive Configuration Properties on page 119 Viewing Drive SCSI Information Properties on page 125 Viewing Drive Statistics Properties on page 126 Viewing Drive Cleaning Properties on page 128
116
Viewing General Drive Properties

The Drive Properties General tab provides information about the drive. Most of this information is for viewing only; however, you can rename your drive from this tabbed page by typing the new name in the Name field.
General drive properties
Managing Devices
The General tab for drive properties provides the following information:
General drive properties Item Name Description The name of the drive. You can also rename the device by typing a new name in this field. The name of the vendor of the drive. The product ID from the SCSI Inquiry string. The version of the firmware used in the device. The media and memory specifications of the device. The type of media used in the drive.
Vendor Product ID Firmware version Drive type Media type
117
Viewing and Using Drive Properties and Statistics General drive properties (continued) Item Date in service Description The date this device was first detected by this installation of Backup Exec. Displays the drive name and server name. The serial number of the drive.
Full name Serial number
See also: Viewing and Using Drive Properties and Statistics on page 116 Viewing Backup Folder Properties on page 152
118
Viewing Drive Configuration Properties

The Drive Properties Configuration tab allows you to:

Enable or disable a device. Enable or disable hardware compression (if compression is supported by the drive). Pause and resume 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.
Configuration drive properties
Managing Devices
119
The Configuration tab for drive properties provides the following information:
Drive configuration properties Item Enable device for Backup Exec Description 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. Pause device Select this check box to pause the device, and then click OK. To resume the device, clear the check box and click OK. 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. The device is displayed as offline if: The device was turned off after Backup Exec was started. The device was being used by another application (such as a Windows backup utility) when Backup Exec was started. The device is removed from the computer. A tape drive failure occurred. A tape is stuck in the drive. The firmware of the drive was updated; Backup Exec will behave as if the drive with its old name or identity no longer exists. To put the device online, try the following: Check to make sure the device has power and that cables are properly attached. Turn the device on and reboot the server, or stop and restart the Backup Exec services. Stop the utility that is using the device, and then reboot the server, or stop and restart the Backup Exec services. To restart the Backup Exec services: For Windows NT 4.0, go to Settings, select Control Panel, and then select Services. For Windows 2000, Windows XP, and.NET, go to Computer Management, select System Tools, select Services, and then select Applications. If the drive 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.
Device offline
120
Viewing and Using Drive Properties and Statistics Drive configuration properties (continued) Item Enable compression Description 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 drive on which hardware compression is disabled (even though it is supported), hardware compression is considered unavailable and is not used. If a drive 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. Priority The Priority field is only available when the drive belongs to a drive pool and is selected for viewing under the drive pool icon. Drive properties displayed under the Robotic Libraries or Stand-alone Drives icon do not display the Priority field. For more information, see Setting Priorities for Drives in a Drive Pool on page 99. Set a priority for a drive that determines the order in which the drives in a drive pool are used. In the Priority box, type a number from 1 to 99, with 1 designating this drive as the first drive to be used in the drive pool, or click the arrows to select a value. The default priority is 10 so all drives have the same priority initially. The drive to which you assign the lowest number is the first drive to be used in the drive pool; for example, a drive with a priority of 1 is used before a drive with a priority of 5. Note Overwrite and append periods for media take precedence over drive priority.
Managing Devices
121
Viewing and Using Drive Properties and Statistics Drive configuration properties (continued) Item Preferred configuration Note 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. 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 drives) provide better performance when larger block sizes are used. The preferred block size can range from 512 bytes to 64 kilobytes. Backup Exec does not ensure that the requested block size is in fact supported by that drive. You should check the drive specifications to make sure that the block size is supported. If the drive does not support a block size, it will default to its standard block size. If the drive 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 drive 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 drive performance. Each type of drive requires a different buffer size to achieve maximum throughput. 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 drive performance. Each type of drive 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. 122 Administrators Guide Description
Viewing and Using Drive Properties and Statistics Drive configuration properties (continued) Item High water count Description The default is the preferred number of buffers to be filled before data is first sent to the drive, and any time after that if the drive 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 drive 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 drive has a high water count default of 0, it should be left at 0. Default Settings Click this button to return all the Preferred Configuration settings to their defaults, and then click OK. Select this check box to have this device read only one block of data at a time. If this check box is selected, the drive will read a single block of data at a time, regardless of the size of the buffer block. VERITAS recommends selecting this option if the drive 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. VERITAS recommends selecting this option if the drive is a shared storage device. 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 driver and allows more detailed information in the event device errors occur. VERITAS recommends selecting this option if the drive is a shared storage device.
Managing Devices
Read single block mode
123
Viewing and Using Drive Properties and Statistics Drive configuration properties (continued) Item Write SCSI pass-through mode Description 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 in the event device errors occur. VERITAS recommends selecting this option if the drive is a shared storage device.
See also: Viewing and Using Drive Properties and Statistics on page 116
124
Viewing Drive SCSI Information Properties

Drive Properties SCSI Information tab
Managing Devices
The Drive Properties SCSI Information tab provides the following information about the Small Computer System Interface (SCSI):
Drive SCSI properties Item Inquiry Port Description The device information read from the device firmware. The identifying number of the port on the server to which the device is attached. The identifying number of the bus to which the device is attached. The unique SCSI ID number (physical unit number). The Logical Unit Number of the device.
Bus Target ID LUN
125
Viewing Drive Statistics Properties

The Drive Properties Statistics tab provides the date the drive was last mounted, drive totals such as the total number of bytes written and read, and drive 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.
Drive Properties Statistics tab
The Statistics tab provides the following information:

Drive statistics properties Item Last mount date Drive totals Total Bytes written Total Bytes read Total mounts 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. Description Last date that media was mounted by this device.
126
Viewing and Using Drive Properties and Statistics Drive statistics properties (continued) Item Total seeks Description The total number of seek operations (performed when a specific piece of information is being located) that have been performed by this device. The total number of hours that this drive has been in use (performing read, write, mount, and seek operations).
Total Hours in use
Drive errors Seek errors Soft read errors The number of errors encountered while trying to locate data. 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 device and perform maintenance on it, and check the media for damage. The 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. 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 device and perform maintenance on it, and check the media for damage. The 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
Managing Devices
Soft write errors
Hard write errors
127
Viewing Drive Cleaning Properties

The Drive Properties Cleaning tab 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 that appear on the Drive Properties Cleaning tab are automatically updated when a cleaning job successfully completes. (Cleaning jobs can only be created for a robotic library drive.) If you want to maintain accurate cleaning statistics for your stand-alone drives, click Reset Cleaning Statistics after the drive has been manually cleaned.
Drive Properties Cleaning tab
The Cleaning tab provides the following information:

Drive cleaning properties Item Last cleaning date Hours since last cleaning Description The last time a cleaning operation was performed on the drive. The number of hours that the drive has been in use since the last cleaning. Click this to reset all cleaning statistics to zero (stand-alone drives only). Administrators Guide
Reset Cleaning Statistics
128
Viewing and Using Drive Properties and Statistics Drive cleaning properties (continued) Item Totals since last cleaning Bytes written 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. The 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. The total number of hours that this drive has been in use (performing read, write, mount, and seek operations) since the last cleaning. Description
Bytes read
Total mounts
Total seeks
Hours in use
Managing Devices
Errors since last cleaning Seek errors The number of errors encountered since the last cleaning while trying to locate data. The number of recoverable read errors encountered since the last cleaning. 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. The 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. The number of recoverable write errors encountered since the last cleaning. 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.
Soft read errors
Hard read errors
Soft write errors
129
Viewing and Using Drive Properties and Statistics Drive cleaning properties (continued) Item Hard write errors Description The 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.
Viewing and Specifying a Drives Media Types

Through the Media Types tab of a drives Properties dialog box, you can view all known media types that can be placed in the drive and specify whether these media types can be used for Read or Write operations.
Drive Properties - Media Type tab
130
The Media Types tab provides the following information:

Media type options for a drive Item Media Type Description 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 drive; otherwise, displays No. Displays Yes if this media type can be written to by the drive; otherwise, displays No.
Read
Write
Backup Execs ADAMM database maintains a list of media types, such as 4MM, and then further defines the subcategories or specifics 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, the Media Types tab for a drive lists all known media type categories and allows all media types to be used for both read and write operations. If a number appears in brackets behind the media type, that media entry is available for use when creating a bar code rule. You can specify that the drive be limited to performing read and write operations on specific media types. For example, if your drives documentation states that the drive cannot perform write operations to a 4MM DDS-4 tape, you can select that media type from this dialog box, clear the Write check box, and then click OK. This information is then incorporated in the ADAMM database, allowing Backup Exec to exclude this media type when searching for media to be used for an operation (such as a backup job) requiring the writing of data to the media. See also: Viewing and Using Drive Properties and Statistics on page 116 Bar Code Labeling in Mixed Media Libraries on page 199
Managing Devices
131
Using Robotic Libraries with Backup Exec

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. 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 fine 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 media is physically added. 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. For example: An operator has a robotic library with six slots. She puts in 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 more Scratch 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, that is, media in slot 2 would be chosen over 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 the overwrite protection period expiring for a media currently in the robotic library, the skipped job will run. See also: VERITAS Backup Exec - Library Expansion Option on page 1143
132
Configuring a Robotic Library

Before installing Backup Exec, make sure the SCSI addresses of the robotic library and the storage device are configured properly. If you have not already enabled robotic library support, rerun the installation program and select Enable Robotic Library Support found in the list of install components. Enable Robotic Library Support provides support for a single-drive robotic library or for the first drive in a multi-drive robotic library. For support for each additional single-drive robotic library, or for each additional drive in a multi-drive robotic library, you must purchase and install a Library Expansion Option. After enabling robotic library support, check your robotic librarys configuration in the Device Configuration Wizard. This wizard appears automatically the first time Backup Exec is started, or it can be launched from the Tools menu by selecting Wizards, and then selecting Device Configuration Wizard. Make sure that each device in the robotic library is properly associated with the robotic library. If a robotic library storage device appears in the device list as a stand-alone device, you can correct the association by clicking and dragging the drive over the robotic library entry. If the robotic arm is not shown, run the installation program and select the Enable Robotic Library Support option. 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, you should perform an Inventory operation to update Backup Execs media database. During startup, Backup Exec expects the storage devices in the robotic library to be empty. If there is media in the device, Backup Exec tries to return the media to its original magazine slot. If, for any reason, it cannot return the media to the slot, an error message appears requesting that the media be ejected from the storage device. See also: Setting Up Robotic Library Hardware on page 1143 Installing Backup Exec on page 46 First Time Startup Wizard on page 74 Setting Up Cleaning Jobs for Robotic Library Drives on page 178
Managing Devices
133
Viewing Properties of a Robotic Library

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 properties of a robotic library: 1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries. 3. Select the robotic library. 4. Under General Tasks in the task pane, select Properties. See also: Viewing General Robotic Library Properties on page 135 Viewing Robotic Library Configuration Properties on page 136 Viewing SCSI Information for a Robotic Library on page 138 Viewing Status Information for a Robotic Library on page 139
134
Viewing General Robotic Library 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.
General robotic library properties
Managing Devices
The General tab provides the following information:

General properties options for robotic library Item Name Description The name of the robotic library. You can rename the device by typing a new name in this field. The name of the vendor of the robotic library. The product ID from the SCSI Inquiry string. The version of the firmware used in the device. The manufacturer and model number of the robotic library. The date this device was first detected by Backup Exec.
Vendor Product ID Firmware version Robotic Library type Date in service
135
Using Robotic Libraries with Backup Exec General properties options for robotic library Item Full name Description Displays the robotic library name and server name; for example, robotic library name(server name). Serial number of the robotic library.
Serial number
See also: Viewing Properties of a Robotic Library on page 134
Viewing Robotic Library Configuration Properties

Through the Configuration tab of a Robotic Librarys Properties dialog box, you can enable or disable the robotic library for use by Backup Exec, enable startup initialization for the robotic library, enable bar code rules, enable Removable Storage, and specify slot base numbering.
Robotic library configuration properties
136
The Configuration tab provides the following information:

Configuration properties options for robotic library Item Enable device for Backup Exec Description Select this check box to have Backup Exec use this device. Clear this check box to disable the device, and allow it to be available for other applications. If the check box is clear, the device is disabled, and cannot be used by Backup Exec. 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 Labeling in Mixed Media Libraries on page 199). Select this option if you want to allow Removable Storage to share the devices in robotic libraries between two or more applications. If the device is enabled in Removable Storage, Backup Exec uses Removable Storage for device and media operations; if the device is disabled in Removable Storage, Backup Exec controls the device directly. For more information about using Removable Storage with Backup Execs Advanced Device and Media Management feature, see Using Microsofts Removable Storage Feature with Backup Exec on page 161 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.
Enable startup initialization
Enable bar code rules
Enable Removable Storage (RSM)
Managing Devices
137
Viewing SCSI Information for a Robotic Library

Robotic library SCSI information
The SCSI Information tab of a robotic librarys Properties dialog box displays the following information:
SCSI Information for a robotic library Item Inquiry Port Description The device information read from the device firmware. The identifying number of the port on the server to which the device is attached. The identifying number of the bus to which the device is attached. The unique SCSI ID number (physical unit number). The Logical Unit Number of the device.
Bus Target ID LUN
138
Viewing Status Information for a Robotic Library

Robotic library status properties
Managing Devices
The Status tab of a robotic librarys Properties dialog box provides the following information:
Status information for a robotic library Item Slot count Drive element count Total mounts Mount errors Description 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.
139
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 drive pool for each partition. Jobs targeted to a partition drive 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 drive pool containing slots 1 and 2. The partition drive pools appear in the Devices view under the Drive 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, that is, media in slot 2 would be chosen over equivalent media in slot 4. In order to fully benefit from Backup Execs partition management feature, VERITAS recommends that you create a partitioning scheme that best matches the manner in which you want to control your backups. For example, some administrators may feel that network backups are best managed by allowing access to partitions based on users and groups, while others may want to base their partitions on operation types (Backup, Tape Rotation, Archive, etc.).
To create partitions: 1. On the navigation bar, click Devices. 2. Expand the server icon, and then click Robotic Libraries. 3. Select the robotic library containing the slots that you want to partition. 4. Under Robotic Library Tasks in the task pane, select Configure partitions.
140
5. Select the robotic library slots to include in each partition by clicking the slots on which each new partition should begin. A partition divider listing the range of slots included in the partition is inserted wherever you click. For example, if you want to create two, 5-slot partitions on a robotic library with 10 slots, click Slot 1 and Slot 6. In this example, Slots 1-5 will be included in the first partition and Slots 6-10 will be included in the second. Partitions can include any number of robotic library slots; however, the first partition cannot be moved or deleted when other partitions exist. Note Depending upon your robotic library configuration, the first slot could be numbered 1 or 0. If your 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.
Configure Partitions dialog box Partition Divider
Managing Devices
6. While defining your partitions, use the following buttons to help you make selections:
Configure Partitions dialog box Item Remove Partition Description 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 Up
141
Using Robotic Libraries with Backup Exec Configure Partitions dialog box Item Move Down Description 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.
Remove All
7. Click OK after completing the configuration of your partitions. 8. Click Yes to accept the partitions. The partition drive pools appear under Robotic Libraries for the robotic library on which they were created. All partition drive pools for a robotic library have the same name and display the slot ranges for the partition in parentheses within the name. 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. 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. Suppose, for example, your current setup is a 6-slot robotic library with two partitions (partition 1 = slots 1-3 and partition 2 = slots 4-6). If 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.
142
Using Backup-to-Disk Folders and Files
For example, if a robotic library that had been partitioned with partition 1 containing slots 1-2, partition 2 containing slots 3-4, and partition 3 containing slots 5-10 is repartitioned so that partition 1 contains slots 1-4, partition 2 contains slots 5-6, and partition 3 contains slots 7-10. Any jobs targeted to the old partition 2 (slots 3-4) will need to be retargeted. Note If a job is targeted to a particular robotic library drive (or a drive pool that is not a partition drive pool), the job defaults to the first partition in the robotic library. See also: Creating Robotic Library Partitions on page 140 Retargeting Jobs from a Deleted Drive Pool or Media Set on page 103

Backup Exec includes a feature called Backup-to-Disk, which allows you to back up data to a folder on a hard disk instead of to a tape device. Backup-to-Disk provides a faster method of backing up and restoring files, which is useful when you have a short amount of time to back up or restore data. You can use it as part of a two-stage backup process where you back up data to disk first and then transfer the data to a tape when more time is available. Before you can start using Backup-to-Disk, you need to create a backup folder, which is a virtual device that Backup Exec treats as any real tape device. Backup folders can be part of drive pools, but not cascaded drive pools. When you create a new backup folder, Backup Exec automatically assigns a name and a path to it, but you can change both. You can create as many backup folders as you need. When you back up to disk, Backup Exec places the data in a backup file in the backup folder you specify. Backup files are virtual media where backed up data is stored. Backup files are like any other type of media, so you can inventory, catalog, erase, and restore them. Since Backup Exec recognizes the backup folders as devices, you can view them by selecting Devices on the navigation bar. You can view the backup files from both the Devices view and the Media view in Backup Exec. In Windows Explorer, the backup folders display in the path you specified when you added the folders, and the backup files display with a.bkf file extension. Each backup folder also contains a changer.cfg file and a folder.cfg file, which store information about the backup files. Note You should not delete or edit the changer.cfg or folder.cfg files.
Managing Devices
143
If you use Backup Execs Intelligent Disaster Recovery (IDR) option, you must use remote IDR to recover computers that include backup-to-disk files. The backup folders must be available to the Backup Exec server you are using to restore the data. See also: Viewing Devices on page 90
Adding a Backup Folder

Before you can start using the Backup-to-Disk feature, you must create at least one backup folder. When you create a new backup folder, it is recommended that you create it on a different physical disk than the disk you want to back up. You can create either a backup-to-disk folder or a removable backup-to-disk folder. You can create a backup-to-disk folder in any location where you can write a file, such as:

NTFS partitions (local or remote) Network Attached Storage (NAS) devices DFS shares FAT/FAT32 partitions (local or remote) VERITAS Volume Manager partitions RAID drives with any configuration Mapped drives NFS volumes
You can create removable backup-to-disk folders on any removable device, provided the device appears as a drive letter and is formatted with a file system. Removable devices can include:

CDR CDR-W DVD-R DVD-RW ZIP JAZZ Removable hard disk
For CDR, CDR-W, DVD-R, and DVD-RW, third-party software must be used to format the media with a file system before it can be used with Backup Exec.
You can use the following steps to manually add a new backup folder. You also can use the Device Configuration Wizard to create a new backup folder.
To add a backup folder: 1. On the navigation bar, click Devices. 2. Select Backup-to-Disk Folder. 3. Under Backup-to-Disk Tasks in the task pane, select New folder. Note If a Backup-to-Disk Warning appears, read it and then verify that the disk where you want to create the backup folder has sufficient free space. If you do not want to see this message every time you add a new folder, select Do not display this message again. Then, click OK. The Add New Backup-to-Disk Folder dialog box appears.
Add New Backup-to-Disk Folder dialog box
Managing Devices

New Backup-to-Disk Folder options Item Name Description Type a name for this folder. Note Backup folder names must not exceed 243 characters.
145
Using Backup-to-Disk Folders and Files New Backup-to-Disk Folder options Item Path or Drive Description Enter the location where the folder is to reside. Path is required if the option Backup-to-Disk folder is selected. Drive is specified if the Removable Backup-to-Disk folder option is selected. Note If you do not know the exact path, click the button next to the Path field to select the correct path. Backup-to-Disk folder Select this option if the folder is to exist on a device that has non-removable media. This type of folder supports concurrent operations from one or more media servers. You can create a backup folder in any location where you can write a file, such as: NTFS partitions (local or remote) Network Attached Storage (NAS) devices DFS shares FAT/FAT32 partitions (local or remote) VERITAS Volume Manager partitions RAID drives with any configuration Mapped drives NFS volumes Note Backup Exec does not determine if the device is a non-removable device; however, VERITAS recommends that you do not select this option if you want to use removable media, such as a zip drive.
146
Using Backup-to-Disk Folders and Files New Backup-to-Disk Folder options Item Removable Backup-to-Disk folder Description Select this option if the folder is to exist on a device that has removable media. This type of folder supports spanning of backup sets from one piece of media to another, but does not support concurrent operations. This type of folder should not be shared between media servers. When creating this type of folder, you must specify only a device, not a path. You can create removable backup-to-disk folders on any removable device, provided the device appears as a drive letter and is formatted with a file system. Removable devices can include: CDR CDR-W DVD-R DVD-RW ZIP JAZZ
Managing Devices
Removable hard disk For CDR, CDR-W, DVD-R, and DVD-RW, third-party software must be used to format the media with a file system before it can be used with Backup Exec. Set Default Path Click this button if you want to set a default path for all future backup folders. Then, type or select the default path.
5. Click OK. The folder appears on the Devices tab below the Backup-to-Disk Folders icon and the All Drives icon. It also appears in Windows Explorer as a folder. You can back up data to this folder now. See also: Viewing Devices on page 90
147
Renaming a Backup Folder

When you use the Backup Exec Rename option to rename a backup 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, use the Windows Rename option.
To change the name of a backup folder: 1. On the navigation bar, click Devices. 2. Under Backup-to-Disk Folders, click either Fixed Backup-to-Disk Folders or Removable Backup-to-Disk Folders. 3. Select the backup folder you want to rename. 4. Under General Tasks in the task pane, select Rename. 5. On the Rename dialog box, type the new backup folder name, and then click OK. Note Backup folder names must not exceed 243 characters. 6. If you want to rename the Windows folder in Windows Explorer, use the Windows Rename option.
Changing the Path of a Backup Folder

If you want to change the path of a backup folder, you cannot just move it from one place to another. First, you create a new backup folder. Then you move the backup files from the original backup folder to the new backup folder.
To change the path of a backup folder: 1. Add a new backup folder with a name and path that is different than the original backup folder. 2. In Windows Explorer, copy and paste the backup files from the original backup folder to the new backup folder. 3. On the Backup Exec navigation bar, click Devices. 4. Right-click the new backup folder, and then click Refresh on the shortcut menu, or select the new backup folder and press <F5>.
148
5. Click the new backup folder and verify that the backup files appear in the right pane. 6. To rename the new backup folder to match the name of the original backup folder, delete the original backup folder and then rename the new folder. See also: Adding a Backup Folder on page 144 Renaming a Backup Folder on page 148. Deleting a Backup File on page 156
Deleting a Backup Folder

When you use the Backup Exec Delete option to delete a backup folder, the backup folder is removed from Backup Exec, but the backup 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 folder or files after you delete them from the disk.
Managing Devices
To delete a backup folder: 1. On the navigation bar, click Devices. 2. Under Backup-to-Disk Folders, click either Fixed Backup-to-Disk Folders or Removable Backup-to-Disk Folders. 3. Select the backup folder you want to remove. 4. Under General Tasks in the task pane, select Delete. 5. Click Yes. The backup folder is removed from Backup Exec, but the files and the folder still exist on the disk. You can still recreate the backup 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. Caution If you delete the folder from the disk you cannot recreate it later. You lose all the files from the folder.
149
7. Select the folder you want to delete, and then under General Tasks in the task bar, select Delete. 8. Click Yes. The folder is removed from the disk. You cannot recreate the folder or the files.
Recreating a Backup Folder and Its Contents

If you have deleted a backup folder from Backup Exec, but have not deleted it from the disk, you can recreate the backup folder and the files in it. You must know the name and path of the original backup folder in order to recreate it. If you deleted a backup folder from the disk, you cannot recreate it.
To recreate a backup folder and the files in it: 1. Add a new folder to Backup Exec using the same name and path as the deleted folder. 2. On the navigation bar, click Devices. 3. Expand either Fixed Backup-to-Disk Folders or Removable Backup-to-Disk Folders. 4. Select the new folder. 5. Under Media Tasks in the task pane, select Inventory and create and run an inventory job. When the inventory is complete, the files display on the results pane. See also: Adding a Backup Folder on page 144 Inventorying Media in Devices on page 165
150
Pausing and Resuming a Backup Folder

When you pause a backup folder, backup jobs do not run on it. If a backup job is already running on a backup folder when you pause it, the job will complete, but any subsequent backup jobs will not run until the folder is resumed. If a backup job fails and the backup folder goes offline, you must pause and resume the folder after you correct the problem.
To pause or resume a backup folder: 1. On the navigation bar, click Devices. 2. Expand the icon for the workstation where the backup folder is located. 3. Under Backup-to-Disk Folders, click either Fixed Backup-to-Disk Folders or Removable Backup-to-Disk Folders. 4. Select the backup folder you want to pause or resume. A check mark appears next to the Pause option if the backup folder is currently paused. 5. Under Backup-to-Disk 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.
Managing Devices
151
Viewing Backup Folder Properties

Use Properties to view information about the backup folder, and in some cases, to change configuration information for the backup folder. Information that can be changed through the Properties dialog box includes the folders name, file management settings, disk space settings, device settings, and concurrent operations settings.
To view or change the properties of a backup folder: 1. On the navigation bar, click Devices. 2. Expand the icon for the workstation where the backup folder is located. 3. Under Backup-to-Disk Folders, click either Fixed Backup-to-Disk Folders or Removable Backup-to-Disk Folders. 4. Select the folder you want to view. 5. Under General Tasks in the task pane, select Properties.
General properties of backup folder
152
General properties of the backup folder include:

General Backup Folder Properties dialog box Item Name Path Enable device for Backup Exec Description Name of the backup folder. You can type a new folder name here. The path to the folder. You cannot change the path here. Select this check box to have Backup Exec use this device. Clear this check box to disable the device, and allow it to be available for other applications. If the check box is clear, the device is disabled, and cannot be used by Backup Exec. After changing the option, click OK. The Priority field is only available when the backup folder belongs to a drive pool and is selected for viewing under the drive pool icon. Backup folder properties displayed under the Backup-to-Disk Folders and Removable Backup-to-Disk icons do not display the Priority field. For more information, see Setting Priorities for Drives in a Drive Pool on page 99. Set a priority for a backup folder that determines the order in which the devices in a drive 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 drive 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 drive pool; for example, a device with a priority of 1 is used before a device with a priority of 5. Note Overwrite and append periods for media take precedence over drive priority. Pause device Select this check box to pause the device, and then click OK. To resume the device, clear the box and click OK. Displays either Backup -to-Disk Folder or Removable Backup-to-Disk Folder, depending on which type of device this folder exists. This option cannot be changed.
Priority
Managing Devices
Folder Type
153
6. Click Advanced to view or change configuration information.

Advanced properties of book folder
7. Select from the following options:

Advanced book folder property options Item Description
Backup-to-Disk file management 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 as small as 1 MB or as large as 4096 GB. The default is 1 GB. 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.
Maximum number of backup sets per Backup-to-Disk file
154
Using Backup-to-Disk Folders and Files Advanced book folder property options Item Disk Space Settings Disk space reserve Type the minimum number of megabytes or gigabytes of disk space that can remain before the backup-to-disk folder stops accepting jobs. If the backup-to-disk folder is a removable storage folder, the jobs will span to new media after the reserved disk space reaches this minimum. Description
Device settings Auto detect settings Clear this check box if you have a storage device for which you can set buffer reads or writes. Otherwise, when this option is selected Backup Exec will detect the preferred settings for your device. Select this check box if you do not want Backup Exec to auto-detect device settings and you know that your device allows buffered reads which is, the reading of large blocks of data. Select this check box if you do not want Backup Exec to auto-detect device settings and you know that your device allows buffered writes, which is the writing of large blocks of data.
Buffered reads
Managing Devices
Buffered writes
Concurrent Operations Allow x concurrent operations for this Backup-to-Disk Folder for this server. This option only appears if the backup-to-disk folder is a non-removable folder. Type the number of concurrent operations that can be performed on this folder. This number can range from 1 to 16.
8. Click OK.
Renaming a Backup File

When you rename a backup file, the name changes in Backup Exec and also on disk. The media label also changes.
To rename a backup file: 1. On the navigation bar, click Devices. 2. Double-click the icon for the workstation where the backup folder is located.
155
3. Double-click Backup-to-Disk Folders. 4. Click the folder that contains the file you want to rename. 5. On the results pane, select the file you want to rename. 6. Under General Tasks in the task pane, select Rename. 7. Type a new name for the file, and then click OK.
Deleting a Backup File

You must move backup files to the Retired Media set before you can delete them. When you delete a backup 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 files if you have not used Windows Explorer to delete them from the disk.
To delete a backup file: 1. On the navigation bar, click Media. 2. Click the media set that contains the backup file. 3. Use the Windows drag-and-drop feature to move the backup file into the Retired Media set. 4. On the results pane, select the backup file you want to delete. 5. Under General Tasks in the task pane, select Delete. 6. Click Yes, or if you selected multiple backup files, click Yes to All. The backup file is deleted from Backup Exec, but not from the disk. To delete the backup file from the disk, continue to step 7. If you do not want to delete the backup file from the disk, you have completed this procedure. Caution If you perform step 7 to delete the backup file from the disk, you can no longer restore the deleted file. 7. Using Windows Explorer, navigate to the location where the backup file is stored. 8. Right-click the backup file. 9. Click Delete, and then click Yes.
156
Recreating a Deleted Backup File

If you deleted a backup 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 file: 1. On the navigation bar, click Devices. 2. Expand the icon for the workstation where the backup folder is located. 3. Under Backup-to-Disk Folders, click either Fixed Backup-to-Disk Folders or Removable Backup-to-Disk Folders. 4. Select the folder where the backup file was located before you deleted it. 5. Under Backup-to-Disk Tasks in the task pane, select Inventory and create and run an inventory job. The backup file appears on the results pane when the inventory job completes.
Managing Devices
See also: Inventorying Media in Devices on page 165
Viewing and Changing Backup File Properties

The file properties that you can view include the:

File name and description. Creation, allocation, and modification dates. Number of bytes written and read, total mounts and seeks, and hours in use. Types of errors encountered on the file.
In addition to viewing properties, you also can change the file name and description from the Properties dialog box.
To view or change backup file properties: 1. On the navigation bar, click Devices. 2. Expand the icon for the workstation where the backup folder is located. 3. Under Backup-to-Disk Folders, click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices.
157
4. Click the backup folder that contains the file you want to view or change. 5. On the results pane, select the file you want to view or change. 6. Under General Tasks in the task pane, select Properties.
Backup-to-Disk File General Properties dialog box
The General properties of a backup-to-disk file include:

General properties of a backup-to-disk file Item Name Description Name of the backup file. You can change the name of the backup file by entering a new file name. Description of the backup file. The description displays on the Devices tab. You can type a new description here.
Description
158
7. Click Management.
Backup-to-Disk File Management Properties dialog box
Managing Devices
The Management properties of a backup-to-disk file include:

Management properties of a backup to disk file Item Creation date Allocation date Description The date and time this backup-to-disk file was created. The date and time that the backup-to-disk file was allocated to a media set. The date and time when data was last written to the backup-to-disk file.
Modification date
159
8. If you want to view the statistics and errors for this file, select the Statistics tab.
Backup-to-Disk File Statistics Properties dialog box
The following information appears:

Statistics properties of a backup-to-disk file Item Totals Total Bytes Written Total Bytes Read Total Mounts Total Seeks Number of bytes that have been written to this media. Number of bytes that have been read from this media. Number of times this media has been mounted. Total number of seek operations (performed when a specific piece of information is being located) that have been performed on this media. Total number of hours that this media has been in use. Description
Total Hours in Use Errors Seek Errors
The number of errors encountered while trying to locate data.
160
Using Microsofts Removable Storage Feature with Backup Exec Statistics properties of a backup-to-disk file (continued) Item Soft Read Errors Hard Read Errors Soft Write Errors Hard Write Errors Description The number of recoverable read errors encountered. The number of unrecoverable read errors encountered. The number of recoverable write errors encountered. The number of unrecoverable write errors encountered.
9. After viewing properties for the backup-to-disk file, click OK.
Using Microsofts Removable Storage Feature with Backup Exec

Removable Storage is a feature of Windows 2000, Windows XP, and .NET systems that allows applications to share removable storage devices. Removable Storage performs requests for device access from different applications on a first in, first out basis. It also tracks media usage for online media (media currently mounted in a robotic library) and for offline media that has been installed previously in a robotic library. Removable Storage does not manage single-slot tape drives. On the media server, you can allow Removable Storage to share the devices in robotic libraries between two or more applications, or you can allow some or all devices in robotic libraries to be controlled and used exclusively by Backup Execs Advanced Device and Media Management (ADAMM). If the device is enabled for Removable Storage through the robotic librarys Properties (see Viewing Robotic Library Configuration Properties on page 136), Backup Exec uses Removable Storage for device and media operations; if the Enable Removable Storage is cleared, Backup Exec controls the device directly. Note In some situations, Removable Storage does not support a robotic library, but may still support some drives in the robotic library. When this happens, Removable Storage disables the robotic libraries but enables the supported drives in the robotic libraries. You should use the Removable Storage snap-in in an MMC to disable all of the drives in the robotic library. This allows Backup Exec to control the robotic library and all of the drives.
Managing Devices
161
If you do not need to share the devices, exclusive use by Backup Exec will allow faster tape backups and restores. If you allow exclusive use by Backup Exec, you can still enable or disable devices in Removable Storage while Backup Exec is running; Backup Exec will respond by switching to other devices in the robotic libraries as appropriate. Note You should not enable Removable Storage for devices used with the SAN Shared Storage Option (SAN SSO). RSM does not appropriately manage devices and media used by multiple servers. The Removable Storage database is automatically backed up by Backup Exec, and can be restored if necessary. For more information, see Advanced options for restore on page 412. Note The Backup Exec services account must have Administrator rights to protect the Removable Storage database. If the account does not have Administrator rights, the following error message is recorded in the job log: "An error occurred while exporting the RSM Database files. The RSM Database could not be backed up." Only Microsoft tape class drivers can be used if you plan on using Backup Exec and the Removable Storage feature. If you want to use a third party tape class driver or a VERITAS tape class driver, you must disable the device through Removable Storage before installing the driver.
Using Media in Drives Managed by Removable Storage

Use the Removable Storage snap-in to manually control the movement of media into and out of the robotic libraries managed by Removable Storage, to allocate media to one application process or another, and to prepare new, imported, or unrecognized media for use within the Removable Storage domain. You must use appropriate processes to move media between applications. Media that is assigned by Removable Storage to an application other than Backup Exec cannot be accessed by ADAMM. Media in the Removable Storage Import and Free media pools are available for use in Backup Exec, and can be assigned to Backup Exec using one of the following methods:
In Computer Management on the local machine, under the Storage node, open Removable Storage, and then open Media Pools. Move media from the Import or Free media pools into a Backup Exec media pool (see your Microsoft Windows 2000 documentation or online help for details). The next time that Removable Storage is scanned, any media that is in the Backup Exec pool is allocated to Backup Exec and marked as "in use" by Backup Exec. Acquire available media through normal Backup Exec operations. This media is then placed in the Removable Storage Import pool and can be accessed by Backup Exec using the policies you established for Imported media.
162
Media that is in the Removable Storage Free media pool or that is unrecognizable by Removable Storage is marked as unknown media within Backup Exec. You must launch an Inventory job to mount and read the media header. The media is imported into Backup Exec and marked as "in use" by Backup Exec. If you do not want that media used by Backup Exec, delete it from the ADAMM database. For more information, see Deleting Media on page 218. Backup Exec cannot append to media prepared initially by Removable Storage. To be able to use this media, you must run an overwrite operation. If media is introduced for the first time into Removable Storage, but it was previously possessed by Backup Exec or written to by Backup Exec during a mount operation, even on another server, then that media is allocated to Backup Exec for exclusive use.
Using Backup Exec Exclusively with Some Devices

If you want to use Backup Exec exclusively on some devices, ensure the Enable Remote Storage (RSM) option is cleared on the robotic librarys Configuration tab; to allow other applications on the server to access Removable Storage to share other devices, select the Enable Remote Storage (RSM) option (see Viewing Robotic Library Configuration Properties on page 136). VERITAS recommends enabling or disabling devices using Removable Storage only when the device is not in use and the internal drives are empty.
Managing Devices
Monitoring Backup Exec and Removable Storage
To view the Removable Storage Work Queue: 1. Click Start and then point to Programs. 2. Point to Administrative Tools, and then click Computer Management. 3. Expand the tree view of Storage. 4. Expand Removable Storage, and then click Work Queue. You can also track the location and status of media by viewing the media and drive objects associated with the loader being shared with Backup Exec. The status of the media is updated as the media is moved.
163
Creating Utility Jobs
Removing the Backup Exec Pool from Removable Storage

If you must uninstall Backup Exec at some time, you may want to delete the Removable Storage Backup Exec pool. Refer to your Microsoft documentation for details on how to use the Removable Storage snap-in to delete an application media pool.

Backup Exec allows creation of utility jobs to aid in managing devices and media. You can specify a job priority and select to have a recipient notified when these jobs run. Utility jobs, like backup and restore jobs, generate job history records and an XML job log when they run. Several of these jobs can be scheduled as recurring jobs. These include:

Inventory robotic library or drive Erase media in a robotic library or drive Import media Export media Lock robotic library Unlock robotic library Clean drive
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, include:

Label media Format 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.
164
Inventorying Media in Devices

Run Inventory to mount the media in the drive 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 drive, run Inventory so that the current media in the drive is displayed in the views; otherwise, the previous media is still displayed as being in the drive. You should run an inventory operation when Backup Exec is launched 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: 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.
Managing Devices
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 startup is recommended if media is often moved between robotic libraries, but Backup Exec may take longer to start.
To have Backup Exec perform an inventory each time Backup Exec starts: 1. On the Tools menu, click Options. 2. In the Properties pane, under Job Defaults, click Preferences.
165
3. Click Inventory all drives on Backup Exec services startup. 4. Click OK.
Creating an Inventory Job
To create an inventory job: 1. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, or if the device resides in a robotic library, click Robotic Libraries. 3. If you want to inventory a drive or slot, select the drive or slot containing the media you want to inventory, or select Slots. 4. If you want to inventory a backup file: a. Double-click the icon for the workstation where the backup folder is located. b. Double-click Backup-to-Disk Folders. c. Double-click either Fixed Backup-to-Disk Folders or Removable Backup-to-Disk Folders. d. Click the backup folder that contains the file you want to inventory. e. On the results pane, select the file you want to inventory.
166
5. Under Media Tasks in the task pane, select Inventory.

General options for inventory job
Managing Devices

Inventory Job Properties options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
7. If you want a person or group to be notified when the job completes, on the Properties pane, under Settings, click Notification and select the options you want (see Selecting Recipients for Job Notification on page 492).
167
8. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). 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. See also: Media Labeling on page 196 Inventory all drives on Backup Exec services startup on page 85
Erasing Media
You can choose to erase media using either Quick erase or Long erase. Not all devices support a long erase; those that do not will always 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. Long erase instructs the drive to physically erase the entire media. If you have sensitive information on the media and you want to dispose of it, use Long erase. Running Long erase on media can take several minutes to several hours to complete (depending on the drive and the media capacity). Quick and Long erase do not change the media label. To change a media label, use Label Media or Rename prior to the Erase operation.
To erase media: 1. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, or if the device resides in a robotic library, click Robotic Libraries. 3. Select the drive or slot containing the media you want to erase.
168
4. Under Media Tasks in the task pane, select either Erase media, quick or Erase media, long. Note If the drive does not support a long erase, Erase media, long will not be available. The following warning is displayed: Caution This operation will be performed on the current media in the drive or slot. If the media has been changed since the last inventory operation was performed, the media label in the next dialog may not match the media in the drive or slot selected. 5. Click OK to continue. The media displayed was read during the last inventory operation; the display does not change until another inventory operation occurs. Therefore, if you change media in the slot or drive but did not run Inventory, the media label displayed may not match the actual media in the slot or drive. 6. When prompted, click Yes to erase the media. 7. Select the appropriate options as follows:
Erase media options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
Managing Devices
169
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 Selecting Recipients for Job Notification on page 492). 9. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). You can monitor the Erase operation through the Job Monitor. You cannot cancel an Erase operation after it has started; however, you can use Cancel to stop a queued erase operation.
Erasing Backup Files

Erasing backup files removes the data from both the backup folder and the disk, and removes the file references from the catalog. However, the backup file remains for use with future backup jobs. You cannot restore the data after you erase it. If you want to remove data from Backup Exec and restore it later, delete the file from the Media view (For more information, see Deleting a Backup File on page 156.) Unlike other types of devices, when you erase a file from a backup folder you cannot choose whether to perform a quick erase or a long erase. Backup Exec performs only a quick erase on backup files in backup folders.
To erase a backup file: Caution You cannot restore the data that you erase. Before you erase files, be sure that you no longer need them. 1. On the navigation bar, click Devices. 2. Expand the icon for the workstation where the backup folder is located. 3. Under Backup-to-Disk Folders, click the backup folder that contains the file you want to erase. 4. On the results pane, select the file you want to erase. 5. Under Media Tasks in the task pane, select Erase media, quick. 6. Click OK to continue. 7. Click Yes, or if more than one file was selected, click Yes to All.
170

Erase media options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
Managing Devices
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 358).
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. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. 3. Select the drive or slot containing the media you want to retension.
171
4. Under Media Tasks in the task pane, select Retension media. 5. Select the appropriate options as follows:
Retension options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
6. If you want a person or group to be notified when the job completes, on the Properties pane, under Settings, click Notification, and select the options you want (see Selecting Recipients for Job Notification on page 492). 7. Click Run now. The job will be submitted as a Run now job, unless you submitted the job on hold. You can monitor the Retension operation from the Job Monitor. You cannot cancel a Retension operation after it has started; however, you can use Cancel to stop a queued retension operation.
172
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. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. 3. Select the drive or slot containing the media you want to format. 4. Under Media Tasks in the task pane, select Format media. The media label that is displayed was read during the last inventory operation. The media label displayed does not change until another inventory operation occurs. Therefore, if you changed media in the slot or drive but did not run Inventory, the media label displayed may not match the actual media in the slot or drive. 5. To format the media that is displayed, click Yes. 6. Select the appropriate options as follows:
Format media options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
Managing Devices
173
7. If you want a person or group to be notified when the job completes, on the Properties pane, under Settings, click Notification, and select the options you want (see Selecting Recipients for Job Notification on page 492). 8. Click Run now. The job will be submitted as a Run now job, unless you submitted the job on hold. You can monitor the Format operation from the Job Monitor. You cannot cancel a Format operation after it has started; however, you can use Cancel to stop a queued Format operation.
Labeling Media
Use Label media to immediately write a new media label on the media in the selected device; this operation destroys any data on the media. To change the media label without destroying the data on the media (until an overwrite operation occurs), use Rename.
To label media: 1. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. 3. Select the drive or slot containing the media you want to label. 4. Under Media Tasks on the task pane, select Label media. The following warning is displayed: Caution 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.
174
5. Click OK.
New Media Label dialog box
6. Type the name you want to use as the recorded media label for this media. Note This media will be overwritten. 7. Click OK to erase all data on the media and re-label the media.
Label Media Job Properties
Managing Devices
175

Label media options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
9. If you want a person or group to be notified when the job completes, on the Properties pane, under Settings, click Notification and select the options you want (see Selecting Recipients for Job Notification on page 492). 10. Click Run now. 11. Write this same media label on an external label fixed to the outside of the physical media. The job will be submitted as a Run now job, unless you submitted the job on hold. You can monitor the Label media operation from the Job Monitor. You cannot cancel a Label media operation after it has started; however, you can use Cancel to stop a queued Label media operation. See also: Renaming Media Labels on page 202
176
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 media 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 the media.
To eject media from a drive: 1. On the navigation bar, click Devices. 2. Expand the server icon, and then click Stand-alone Drives. 3. Select the drive. 4. Under Drive Tasks in the task pane, select Eject media. 5. Select the appropriate options as follows:
Managing Devices
Eject media options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
6. If you want a person or group to be notified when the job completes, on the Properties pane, under Settings, click Notification, and select the options you want (see Selecting Recipients for Job Notification on page 492). 7. Click Run Now. The job will be submitted as a Run now job, unless you submitted the job on hold.
177
Setting Up Cleaning Jobs for Robotic Library Drives

You can submit once-only cleaning jobs for robotic library drives, or set up scheduled cleaning jobs. This option is not available for stand-alone drives. Before submitting a cleaning job, you must define a cleaning slot that contains the cleaning tape.
To define a cleaning slot: 1. On the navigation bar, click Devices. 2. Click Robotic Libraries, and then click the robotic library for which you are setting up the cleaning. 3. Click Slots to display the librarys slots in the right pane. 4. Select the slot that contains the cleaning tape. 5. Under General Tasks in the task bar, select Properties. 6. Select the Cleaning Slot option 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 set up a cleaning job: 1. On the navigation bar, click Devices. 2. Click Robotic Libraries, and then click the robotic library containing the drive. 3. Select the drive. 4. Under Drive Tasks in the task pane, select Clean.
178

Clean Robotic Library Drive options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
Managing Devices
7. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). You can monitor the cleaning job through the Job Monitor. You can view cleaning statistics for the drive by right-clicking the drive and selecting Properties. For more information, see Viewing and Using Drive Properties and Statistics on page 116.
179
Importing Media
Backup Exec fully supports robotic libraries with portals through its Import and Export utility jobs. It is important to create Import and Export jobs when changing media in your robotic library so that the Backup Exec database is updated. You can select any number of slots to import and export. When you use the Import utility, the slots you highlighted are checked for media. If media is present, 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. 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.
To import media in the robotic library: 1. On the navigation bar, click Devices. 2. Select the robotic library. 3. Click Slots. 4. On the results pane, select the slots you want to import media to. 5. Under Media Tasks in the task pane, select Import media. 6. Select the appropriate options as follows:
Import options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
180
7. If you want Backup Exec to inventory the media after the job completes, double-click Settings, click Options and select the following:
Auto-inventory option Item Auto-inventory after import is completed Description Select this option to have Backup Exec automatically create an inventory job to run after the import job completes.
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 Selecting Recipients for Job Notification on page 492). 9. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). You can monitor the import job through the Job Monitor.
Managing Devices
Exporting Media
The Import media and Export media utilities allow Backup Exec to fully support robotic libraries with portals. When you use the Export media utility 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, 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.
To export media: 1. On the navigation bar, click Devices. 2. Select the robotic library. 3. Click Slots. 4. On the results pane, select the slots you want to export media from. 5. Under Media Tasks in the task pane, select Export media.
181

Export media options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
7. If you want a person or group to be notified when the job completes, on the Properties pane, under Settings, click Notification and select the options you want (see Selecting Recipients for Job Notification on page 492). 8. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). You can monitor the export job through the Job Monitor.
Locking the Robotic Library
To create a job to lock the robotic librarys front panel: 1. On the navigation bar, click Devices. 2. Select the robotic library. 3. Under Robotic Library Tasks in the task pane, select Lock.
182

Lock options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
Managing Devices
6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). You can monitor the lock job through the Job Monitor.
Unlocking the Robotic Library
To create a job to unlock the robotic librarys front panel: 1. On the navigation bar, click Devices. 2. Select the robotic library. 3. Under Robotic Library Tasks in the task pane, select unlock.
183

Unlock options Item Job name Job priority Description Type a name for the job or accept the default name. Select the priority for the job. Available options are: Lowest Low Medium High Highest
5. If you want a person or group to be notified when the job completes, on the Properties pane, under Settings, click Notification and select the options you want (see Selecting Recipients for Job Notification on page 492). 6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). You can monitor the unlock job through the Job Monitor.
184
Managing Media
With Backup Execs media management tools you can:

Protect data from being overwritten. Set up media rotation strategies. Track the location of media. Label media automatically. Read and track media labels with bar codes. Collect and report media statistics.
On the navigation bar, click Media to view all the media used in Backup Exec, view how the media is organized into media pools, media sets, and media vaults, and view media properties.
Media Overwrite Protection

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. At any given time, Backup Exec is aware of all media that is loaded into attached storage devices, media that is offline, and media that has been placed in media vaults. Each media has a status that allows Backup Exec to identify which media can be written to and which media is overwrite-protected. 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 trade-off between the longevity of stored backup data and the cost of more media is controlled in Backup Exec by restrictions placed on data that is written to media. A restriction is placed on how long new jobs can be written to the media after the first job has been written (the append period), and another restriction is placed on how long the data is preserved after it is written (the overwrite protection period).
Media Management
185
These two restrictions, the append period and the overwrite protection period, combine to form a policy that can be applied to groups of media. These policies are called media sets, which are containers for media that have the same append period and the same overwrite protection period. The append period and overwrite protection period are attributes of the container.
Media Set
Append Period 5 Days
Overwrite Protection Period 30 Days
The append period is the amount of time that data can be appended (added) to a media. The append period is measured from the time the media was first allocated (assigned) to the media set. It can be specified in hours, days, weeks, or years. The overwrite protection period is the amount of time that media is protected from being overwritten. It can be specified in hours, days, weeks, or years. The overwrite protection period is measured from the time when the last append backup job completed. When the overwrite protection period is over, the media becomes recyclable and can be overwritten.
186
The Append Period begins when the media is allocated to a Media Set.
APPEND_PERIOD
TIME
OVERWRITE_PROTECTION_PERIOD
The Overwrite Protection Period begins each time data is appended 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. The media cannot be overwritten by another job during this interval. (However, you could erase the media or move it to a scratch pool.)
TIME
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 Protection Period expires.
Media Management
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 appended to a media, the time remaining in the overwrite protection period is reset and the countdown restarted.
Chapter 5, Managing Media
187
Time in days
Append period = 5 days
Time in days
Time in days
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Normal Bkup
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Normal Bkup Normal Bkup 1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Normal Bkup Normal Bkup 1 Normal Bkup 1 2 Normal Bkup 1 2 3 Normal Bkup 1 2 3 4
Protection Period 14 Days
The media can be overwritten at this time
17 18 19 20 The media can be overwritten at this time
Fifth Day
The media can be overwritten at this time
First Day
Second 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 you create a media set named Weekly with an overwrite protection period of seven days, and an append period of 0, and you schedule a full backup job to run each Friday at 9 p.m. When it is time for the full backup to run at 9 p.m. the following Friday, the job cannot run because the first backup job that ran the previous Friday did not complete until 10:10 p.m. Therefore, 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 take into account the amount of time a job may run. For this example, the scheduled job recurring at 9 p.m. can run if the overwrite protection period is set to 6 days instead of 7 days.
188
Default Media Set

When Backup Exec is installed, three important defaults associated with overwrite protection of media are established:

A media set named Media Set 1 is created. The append and overwrite protection periods for Media Set 1 are set to Infinite. All backup jobs you create are targeted to Media Set 1, unless you change the target during the First Time Startup Wizard.
By using these defaults, you can keep all of your backup data safe from overwriting forever (unless you erase, label, or format the media, or move it to Scratch Media). You will eventually run out of overwritable media unless you continually introduce scratch media into Backup Exec. To ensure that Backup Exec has media available, you can:
Create new media sets with append and overwrite protection periods set to intervals of time that accommodate your needs (such as weekly, monthly, etc.) and then assign jobs to these media sets. When the overwrite protection period expires, the media become recyclable and Backup Exec can use them for other overwrite jobs. Change the append and overwrite protection periods of Media Set 1 to finite periods. The danger with changing the overwrite protection period in Media Set 1 is that if you continue to use Media Set 1 as the default destination media set for all backup jobs, your data may not be protected as long as you need it to be.
The media for many jobs can be targeted to the same media set. Allocated media are media that belong to a media set. As long as the append and overwrite protection periods are current, the media are allocated to that media set. Backup Exec automatically allocates media. When the overwrite protection period expires, the media become recyclable. The media are still displayed as being in that media set, but with a status of recyclable. You do not need to move recyclable media to or from a media set; Backup Exec can overwrite the recyclable media in any media set whenever more media are needed for other jobs. See also: Creating Media Sets on page 227 Deleting a Media Set on page 229 Renaming a Media Set on page 230 Editing and Viewing Media Set Properties on page 230
Media Management
189
Media Overwrite Protection Levels

With the media overwrite protection levels, you choose the types of media that you want to be available for overwrite backup jobs. Although the terms are similar, the media overwrite protection levels and the media overwrite protection period are different. The media overwrite protection levels are global settings that designate groups of media as overwritable, whereas the media overwrite protection period is a time interval that changes from one media set to another. The media overwrite protection levels are:

Full. Allows you to overwrite scratch (media that contains data you are willing to discard) and recyclable media (media with an expired overwrite protection period). Partial. Allows you to overwrite imported media, which is media that was created by another installation of Backup Exec or some other backup product. You can also overwrite scratch media with the Partial protection level. None. Allows you to overwrite all media, including those that have current overwrite protection periods (allocated media).
Caution The None option is not recommended because it does not protect data from being
overwritten.
Section 1 in the figure Media Overwrite Protection on page 194 illustrates the Media Overwrite Protection level. See also: Setting Default Media Options on page 203
Media Categories
Backup Exec recognizes media that is inserted into storage devices and categorizes it as:
All Media. All media that has been introduced into Backup Exec. Any media that is available for overwriting in backup operations, such as scratch or recyclable media, displays in blue. When you click the All Media icon, the Results pane displays properties for the media in Backup Exec. For more information, see Viewing Media Information on page 92. System Media. All media that has been introduced into Backup Exec, except those media that have been allocated to a media set. System Media includes Scratch, Retired, and Imported Media. Scratch media displays in blue in the Media and Devices views. Scratch Media. Media that do not belong to a media set and can be overwritten, including:
190
New or blank media. Media that you have moved from another group, such as a media set or Imported Media. Erased media.
Retired Media. Media that you have taken out of service, usually because of an excessive number of errors. After a media has been categorized as retired, it is not selected for use in a media set by Backup Exec. It is still available for restore operations, if it has not been damaged. 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.
Imported Media. Media created by a product other than this installation of Backup Exec. By default, Imported media have an overwrite protection period of Infinite, but can still be overwritten if the Media Overwrite Protection Level is set to Partial or None. You can overwrite imported media using several methods. Data can be restored from imported media until that media is overwritten. Other media pools that are contained in Imported Media are: Backup Exec and Windows NT Backup Media. Media from another installation of Backup Exec. Backup Exec Archive Media. Media that was used for archive jobs. Foreign Media. Media from a product other than Backup Exec.
Media Management
Media Sets. Media sets are groups of media that have the same overwrite protection period and append period. The overwrite protection period is the length of time that data is retained on a specific media before becoming available for overwriting. The append period is the length of time that data can be added to a media. You can create different media sets, each with different data overwrite protection and append periods. When a backup job is created, you target it to a specific media set that defines the particular data overwrite protection and append periods you want applied to the backup job. Use media sets to set up media rotation strategies. Media sets include: Allocated media. Media that belong to a media set. Allocated media are always displayed in the allocated media set, even after the data overwrite protection date expires. Recyclable media. Media that are allocated to a media set, but have expired overwrite protection periods. You can move recyclable media to Scratch Media, or you can let it remain in the media set list. When a backup job runs, by default Backup Exec uses scratch media first, and then selected recyclable media that is in the targeted media set for
191
overwriting if no scratch media are available. To change this default, on the Tools menu, click Options, and then under Settings, click Media Management. Recyclable media, along with scratch media, display in blue in the Media and Devices views.
Media Overwrite Options

Media overwrite options set the order in which Backup Exec searches for overwritable media. When Backup Exec searches for overwritable media for a backup job, it searches for either scratch media or media that has an expired overwrite protection period. You are prompted to select the type of media that you want Backup Exec to use first:
Overwrite scratch media before overwriting recyclable media contained in the targeted media set. 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.
Note In a drive pool, Backup Exec selects the oldest recyclable media in all of the drives in the drive 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. See also: Setting Default Media Options on page 203
192
How Backup Exec Searches for Overwritable Media

The following table describes the order in which Backup Exec searches for media to use for an overwrite job, depending on the combination of the overwrite protection level and the media overwrite option you select.
How Backup Exec searches for overwritable media Overwrite protection level and overwrite option: Full + Overwrite scratch media first Note This combination provides the most protection against overwriting media. Full + Overwrite recyclable media first 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
Partial + Overwrite recyclable media first
1. Recyclable media in the targeted media set 2. Scratch media 3. Recyclable media in any media set 4. Imported media
Media Management
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
None - No overwrite protection + overwrite recyclable media first Caution This option is not recommended because it does not protect data from being overwritten.
193
Media Overwrite Protection Media Overwrite Protection
1 1 1 2
Media Overwrite Protection Level
None
Partial
Full
Media Overwrite Options 2

Recyclable Media
(current user media sets)
Scratch Media
Media Overwrite Option can reverse these, causing the Scratch media set to be examined second rather than first.
Scratch Media
Recyclable Media
(current user media sets)
Recyclable Media
(other media sets)
Recyclable Media
(other media sets))
Imported Media
Imported 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).
Allocated Media
Allocated Media
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. See also Media Overwrite Options on page 192
194
Media Append Options

When you set up an append backup job, you can determine how Backup Exec should handle the job. The following append options are located on the Device and Media section of the Backup Job Properties dialog box.
Append to media, overwrite if no appendable media is available. When you are performing an append backup operation and the backup job is set to this option, Backup Exec searches for available media as follows: 1. Searches for appendable media in the Media set that is targeted in the backup operation. 2. If no appendable media can be found, Backup Exec changes the backup operation to overwrite and continues searching for overwritable media as outlined in How Backup Exec Searches for Overwritable Media on page 193.
Caution 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. If the media in the drive is not overwritable, a message prompts you to insert overwritable media.
Append to media, terminate job if no appendable media is available. When you are performing an append backup operation and the backup job is set to this option, Backup Exec searches for available media as follows: 1. Searches for appendable media in the media set targeted in the backup operation. 2. If no appendable media is found, the backup operation is terminated.
Media Management
See also: Creating a Backup Job on page 235
Overwriting Allocated or Imported Media

Backup Exec protects allocated and imported media from being overwritten when full or partial overwrite protection is used. However, if necessary, you can allow allocated and imported media to be overwritten by Backup Exec before the data overwrite protection period expires, and without setting the media overwrite protection level to None. Several methods are available:

Move the media to Scratch Media. The media is overwritten when it is selected for an overwrite job. Erase the media. Erased media is automatically recognized as scratch media and will be overwritten immediately.
195
Media Labeling
Label the media. The Label Media operation immediately writes a new media label on the media, which destroys any data contained on the media. Format the media. Formatting destroys any data contained on the media. Change the overwrite protection period for the media set so that it is expired. Select the media set, and then under General Tasks, click Properties.
See also: Deleting Media on page 218 Editing and Viewing Media Set Properties on page 230 Media Overwrite Options on page 192
Removing Damaged Media

Media that meets or exceeds the discard thresholds determined by the media manufacturer should be moved to Retired Media. 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. Move 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. Media can only be deleted from Backup Exec when it is part of the Retired Media set. See also: Deleting Media on page 218 Viewing Media Statistical Properties on page 223 Media Set Report on page 523
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.
Media Labeling
You can allow the media label to be assigned automatically by Backup Exec, or you can specify a label prefix and number to be assigned for a type of media. For example, you can specify that all 4mm media that are entered for the first time into this installation of Backup Exec are labeled with a prefix of ACCT, and with numbering starting from 1000. You can specify another media type to be labeled with a prefix of FIN, and with numbering starting at 10,000. Customizing labels in this manner can help you recognize and organize media. Another type of media label used by Backup Exec is the media ID, which is a unique label assigned by Backup Exec to individual media used in Backup Exec. The media ID is used internally by Backup Exec in order to keep statistics on each media. Because the media label or bar code label for media can be changed, Backup Exec must use the media ID, which cannot be changed or erased, to preserve continuity in record keeping for each individual media. The media ID has no effect on the media label, or on your ability to rename, label, or erase media. At times, you may need to use the media ID to distinguish media that have duplicate media labels. Duplicate labels can be automatically generated in instances when Backup Exec is reinstalled or media from another Backup Exec installation is used. Use the media ID to distinguish between duplicate labels. You can view the media ID in a 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. Three methods are available in Backup Exec to change a media label:

Label Media operation. Writes a new media label on the media. This write operation destroys any data on the media. This option is available on the Devices view. Rename operation. Changes the name of the media in the display, but does not write the new label to the media until an overwrite operation occurs. The data on the media is viable until the media is overwritten. Edit the label in the 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.
Media Management
See also: Setting Default Media Options on page 203 Labeling Media on page 174 Bar Code Labeling on page 198 Renaming Media Labels on page 202 Viewing General Media Properties on page 220
197
Media Labeling
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. See also: Viewing General Media Properties on page 220
Bar Code Labeling

If there is a bar code label on the physical cartridge, and the cartridge is in a robotic library that has a bar code reader, the bar code label automatically becomes the media label. You can change the media label in Backup Exec, but as long as the media has a bar code label that can be read, the bar code label takes precedence over the media label. To use the media label you entered using Backup Exec, you must remove the physical bar code label from the media cartridge, or use the media in a device without a bar code reader. Example Robotic Library 1 has bar code support. During a backup operation, Backup Exec requests a new or overwritable media for the operation. A new media with the bar code label 'ABCD' is inserted in the robotic library magazine and the bar code reader scans the bar code ID on the media label. Backup Exec selects this media for the operation and detects that a bar code label has been assigned to the media. Backup Exec automatically uses the bar code label and continues the operation. When you change magazines or insert new media in a magazine, bar code readers allow you to quickly update slot information by right-clicking the slot (or slots) and selecting Scan. See also: Media Labeling on page 196
198
Media Labeling
Bar Code Labeling in Mixed Media Libraries

If you are using a robotic library that uses different types of drives and you have bar code support for that library, you can set up Backup Exec to identify which media type can be used in which drive type. You set up a bar code label with a prefix or a suffix that corresponds to a certain type of media. When Backup Exec reads that bar code label, 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. You can add both a prefix and a suffix or just one of them. After setting up bar code rules, you must set up two more items 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. To set this up, see Viewing and Specifying a Drives Media Types on page 130.
To set up a bar code label rule: 1. On the Tools menu, click Options. 2. In the Properties pane, under Settings, click Bar Code Rules.
Media Management
199
Media Labeling Bar Code Rules
3. Click Add.
Add Bar Code Rule
200
Media Labeling

Add Bar Code Rule dialog box Item Select a Media Type Vendor Description Select the media for which you want to add a bar code rule.
Type the name of this librarys manufacturer. You can find the name of the library manufacturer on the librarys property page. This is an optional field. 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, do not type anything in this field. This field is not case-sensitive. Type a code to be placed before the bar code. This code 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. This code 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.
Barcode Prefix
Barcode Suffix
5. Click OK to save the bar code label rule for the media. 6. Verify that bar code rules are enabled for the robotic library. The bar code rules do not go into effect until you enable them for the robotic library. For more information, see Viewing Robotic Library Configuration Properties on page 136.
Media Management
To change a bar code rule: 1. On the Tools menu, click Options. 2. In the Properties pane, under Settings, click Bar Code Rules. 3. Click Modify. 4. Change the options as needed. 5. Click OK to save the changes. 6. Click OK.
201
Media Labeling
To delete a bar code rule: 1. On the Tools menu, click Options. 2. In the Properties Pane, under Settings, click Bar Code Rules. 3. Select a bar code rule to delete. 4. Click Delete. 5. Click Yes to verify that you want to delete the rule. 6. Click OK.
Renaming Media Labels

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 medias 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 a media label: 1. Do one of the following: If the media is in a drive, then from the navigation bar, click Devices, and then click that drive 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. Select the media you want to rename. 3. Under General Tasks in the task pane, click Rename.
202
Setting Default Media Options Rename Media Label dialog box
4. In Name, type a new media label. 5. Click OK. 6. Write this media label on an external label fixed to the outside of the physical media. See also: Viewing General Media Properties on page 220
Setting Default Media Options

This procedure explains how to set options for the media overwrite protection levels, the media overwrite options, the default media labeling, and the default location for Backup-to-Disk Folders.
To set media options: 1. On the Tools menu, click Options. 2. On the Properties pane, under Settings, click Media Management.
Media Management
203
Setting Default Media Options Media Options - Set Application Defaults

Media Options - Set Application Defaults Item Description
Media overwrite protection level Full - protect allocated and imported media Select this option to protect media in media sets and imported media from being overwritten. This is the safest option to choose because the media being protected cannot be overwritten until: The overwrite protection period for the media expires. You move media that belongs to an active media set to Scratch Media. You erase, format, or label the media. You move media from Imported Media to Scratch Media.
204
Setting Default Media Options Media Options - Set Application Defaults (continued) Item Partial - protect only allocated media Description 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 imported media None Caution This option is not recommended because it does not protect data from being overwritten. Select this option to be prompted before Backup Exec overwrites imported media when Partial has been selected.
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 drive, and the media overwrite protection level is set to None, the media in that drive is overwritten.
Prompt before If you selected None (no overwrite protection), it is highly overwriting allocated or recommended that you select this option to be prompted imported media before overwriting allocated or imported media.
Media Management
205
Setting Default Media Options Media Options - Set Application Defaults (continued) Item Media overwrite options 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. 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). See How Backup Exec searches for overwritable media on page 193. 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 193. 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 label configuration Media type Select the type of media for which you want to create default labels. 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. Description
206
Setting Default Media Options Media Options - Set Application Defaults (continued) Item Prefix Description Displays the current default prefix for the selected cartridge type. To specify a new prefix on the label, type from one to eight alpha-numeric characters. 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.
Next value
Media Management
207
Setting Default Media Options Media Options - Set Application Defaults (continued) Item Backup-to-Disk default folder location Description Type the default path for new backup folders. This default path appears in the New Backup-to-Disk Folder dialog box where you add a new backup folder. For more information, see Using Backup-to-Disk Folders and Files on page 143. When making selections for backups you are targeting to a backup folder, avoid including that backup folder in the selections for the job. For example, if you create a new backup folder in c:\Backup Folders and then select the entire c:\ volume for backup, make sure you exclude c:\Backup Folders from the selection list. When adding backup folders, make sure there is sufficient space on the disk for the data you are backing up. Backups that exceed the size of available disk space will fail.
4. Click OK. See also: Media Overwrite Options on page 192 Media Append Options on page 195 Media Labeling on page 196
208
Media Location
Media Location
Backup Exec helps you track the location of your media. There are three categories available for tracking media:
Online location. The online location lists media that reside in a storage device, robotic library slot, or Backup-to-Disk folder. The online location is defined by Backup Exec, so you cannot delete or rename it. In addition, you cannot add media to the online location.
Note If you move media from an online location, its overwrite protection period and append period remain in effect.
Offline location. The offline location displays all media that are onsite but are not in drives 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, you must run an inventory of the devices or slot, or you must 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 user-defined 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 create as many user-defined media vaults as necessary.
Media Management
See also: Finding Media in a Location or Vault on page 210 Renaming a User-defined Media Vault on page 211 Adding Media to the Offline Location or a User-Defined Vault on page 211 Moving Media by Dragging and Dropping on page 212 Deleting a User-defined Media Vault on page 213 Media Vault Contents Report on page 524
209
Media Location
Creating User-defined Media Vaults

Create media vaults to track media stored in specific sites.
To create a user-defined media vault: 1. On the navigation bar, click Media. 2. Under Media Location Tasks on the task pane, click New media vault. 3. Type the name and a description of the new vault. 4. Click OK.
Finding Media in a Location or Vault

If you know the media label for a piece of media, but dont know where it is located, you can search for it using the label.
To find media: 1. On the navigation bar, click Media. 2. On the Media selections pane, click Media Location. 3. Under Media Location Tasks on the task pane, click Find media. 4. Type the name from the media label of the media you want to find. 5. Click OK. Backup Exec highlights the location of the media and displays its properties in the preview pane. Note If you are using BEWAC, the preview pane is not available.
210
Media Location
Renaming a User-defined Media Vault

You can rename a user-defined media vault at any time. You cannot rename the system-defined online and offline media vaults.
To rename a user-defined media vault: 1. On the navigation bar, click Media. 2. On the Media selections pane, click the media vault you want to rename. 3. Under General Tasks in the task pane, click Rename. 4. Type the new name. 5. Click OK.
Adding Media to the Offline Location or a User-Defined Vault

You can add media to the offline location or a user-defined vault. You cannot add media to the online vault. When you add media to a different location or vault, Backup Exec removes the media from the original location or vault.
To add media to the offline location or a user-defined media vault: 1. On the navigation bar, click Media. 2. In the Media selections pane, select the media location or vault to which you want to add media. 3. Under Media Location Tasks in the task pane, click Add media to selected vault. 4. Type the media label or scan the bar code label for the media you want to add to this vault. 5. Click Add. 6. Repeat steps 4 and 5 for all the media you want to add. 7. Click OK.
Media Management
211
Media Location
Moving Media by Dragging and Dropping

When you are working with media in a location, you cannot move it using the media move operation that you use when you are working with media in media sets, imported media, or other media areas. To move media from a location, you drag and drop it from one location to another location. The following table lists the drag-and-drop rules for media locations and vaults: Note If you move media from an online location, its overwrite protection period and append
period remain in effect. Media Location and Vault Drag-and-Drop Rules From/To Online Location Offline Location Yes, with a warning that the media is not physically moved from the online location. No User-defined Media Vaults Pools/Sets Yes, with a No warning that the media is not physically moved from the online location. Yes No All Media
Online location No
No
Offline location User-defined vault Media Pools/Sets All Media
No
No
No
Yes
Yes
No
No
No
Yes, with a warning Yes, with a warning that the media is not physically moved from the online location.
Yes, with a warning
Yes
No
No
Yes, with a Yes warning that the media is not physically moved from the online location.
No
212
Media Location
To move media from a location or vault: 1. On the navigation bar, click Media. 2. On the Media selections pane, click the vault containing the media. 3. Select the media from the Results pane, and drag it to the new location.
Deleting a User-defined Media Vault

You can delete an empty user-defined 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 user-defined vault: 1. On the navigation bar, click Media. 2. On the Media selection pane, select the media vault you want to delete. 3. Under General Tasks in the task pane, click Delete. 4. Click Yes to delete, or, if you are deleting multiple vaults, click Yes to All to delete without prompting for each vault.
Media Management
213
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. Three of the most commonly used media rotation strategies are:

Son. Uses the same media each day to run a full backup. See Son Media Rotation Strategy on page 214. 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 215. 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 216.
Son Media Rotation Strategy

Number of media required: 1 (minimum) Overwrite protection period: last backup The Son strategy involves performing a full backup every day. Although the Son strategy is simple to administrate, 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
214
Father/Son Media Rotation Strategy

Number of media required: 6 (minimum) Overwrite protection period: Two weeks The Father/Son media rotation strategy uses a combination of full and differential or incremental backups for a two-week schedule. In the Father/Son scenario, four media are used Monday through Thursday for differential or incremental backups. The other two media containing full backups are rotated out and stored offsite every Friday.
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
Media Management
Note When this backup strategy is first implemented, you must start with a full backup. The Father/Son strategy is easy to administrate 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.
215
Grandfather Media Rotation Strategy

Number of media required: 19 (minimum) Overwrite protection period: One year The Grandfather method is one of the most common media rotation strategies. It is simple to administrate 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.
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.
216
Running the Media Rotation Wizard

Backup Execs Media Rotation wizard guides you through setting up a media rotation job. This job is based on a modified Grandfather/Father/Son strategy. After running the wizard, the following jobs are set up to protect the data that you select:

A full backup job to start the media rotation job. A scheduled full backup job that runs at least once a week. A scheduled differential or incremental backup job that runs on the days that the full backups do not occur.
To run the Media Rotation wizard: 1. From the Tools menu, point to Wizards, and then select Media Rotation Wizard. Note You also can find the Media Rotation wizard on the Job Setup screen. On the navigation bar, click Job Setup. Under Backup Strategy Tasks on the task pane, click Set up media rotation. 2. Follow the on-screen prompts. See also: Backing Up Data on page 233 Media Rotation Strategies on page 214 Media Sets on page 226
Media Management
217
Media Operations
Media Operations
You can perform several types of operations on media. You can delete media from the Retired Media set, move media to a different media set, or create a new catalog for a piece of media. In addition, you can view properties for the media, including the general, management, statistical, and cleaning properties. See also: Deleting Media on page 218 Moving Media on page 219 Cataloging Media in a Drive on page 397 Viewing General Media Properties on page 220 Viewing Media Management Properties on page 222 Viewing Media Statistical Properties on page 223 Viewing Media Cleaning Properties on page 225
Deleting Media
You may want to delete media when:

You have a lot of offsite media that you do not want to recycle. You throw away damaged or old media.
Media can only be deleted from Backup Exec when it is part of 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 it must be cataloged. Note Deleting media from Backup Exec is not the same as erasing media.
To delete media: 1. On the navigation bar, click Media. 2. If the media is not already in Retired Media, you must move it there. To look at the contents of Retired Media, expand the server icon, then expand System Media, then expand Retired Media. To move media to Retired Media, drag the media to the Retired Media icon. 3. Select the media you want to delete.
218
Media Operations
4. Under General Tasks in the task pane, click Delete. If Delete is unavailable, the media is not in Retired Media. You must move the media to Retired Media before Delete is available. 5. Click Yes or Yes to All to delete the media that are displayed. See also: Removing Damaged Media on page 196
Moving Media
You may want to move media when:

Media is reported as generating too many errors and needs to be retired. You no longer want to keep the data on imported media and want to reuse the media.
When you move media to a media set, the media takes the append and overwrite protection period properties of the media set to which it was moved. Note Moving scratch or imported media to a media set is not recommended.
To move media: 1. On the navigation bar, click Media.
Media Management
2. Expand All Media to display a list of media, and then select the media you want to move. 3. You can drag the media to a media set, or under Media Tasks on the task pane, click Move.
Move Media dialog box
4. Click the Down arrow next to the Move this media to field to display the media set to which you want to move this media, and then click OK.
219
Media Operations
Viewing General Media Properties
To view media properties: 1. On the navigation bar, click Media. 2. Expand the All Media icon, and then select the media that you want to view. 3. Under General Tasks on the task pane, click Properties. The General Media Properties tab provides the following information:
General Media Properties tab Item Media Label Description 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. You can edit the media description, which is limited to 128 characters, to make it a more descriptive label. Media Type Media type and subtype (if available). Click the button next to the field to change the media type or subtype.
220
Media Operations General Media Properties tab (continued) Item Used Capacity Description 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 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. 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.
Media Management
Bytes Written
Compression Ratio (Bytes Written/Used Capacity)
221
Media Operations General Media Properties tab (continued) Item Media ID Description Internal identification number assigned by Backup Exec. You cannot change this number.
See also: Media Labeling on page 196 Creating a Test Run Job on page 307 Viewing Media Information on page 92 Viewing Media Statistical Properties on page 223 Viewing Media Cleaning Properties on page 225
Viewing Media Management Properties
To view media management properties: 1. On the navigation bar, click Media. 2. Expand the All Media icon, and then select the media that you want to view. 3. Under General Tasks in the task pane, click Properties. 4. Select the Management tab. The Media Management Properties tab provides the following information:
Media Management Properties tab Item Creation date Allocation date Description 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.
Modification date
222
Media Operations
Note In BEWAC, the servers date and time format are used instead of the clients date and time format. 5. Click OK. See also: Viewing General Media Properties on page 220 Viewing Media Cleaning Properties on page 225
Viewing Media Statistical Properties
To view media statistical properties: 1. On the navigation bar, click Media. 2. Expand the All Media icon, and then select the media that you want to view. 3. Under General Tasks in the task pane, click Properties. 4. Select the Statistics tab. The Media Statistic Properties tab provides the following information:
Media Statistic Properties tab Item Totals Total bytes written Total bytes read Total mounts Total seeks Number of bytes that have been written to this media. 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 total number of hours that this media has been in use. Description
Media Management
Total hours in use Errors
223
Media Operations Media Statistic Properties tab (continued) Item Seek errors Soft read errors Description The number of errors encountered while trying to locate data. 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. 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.
Hard read errors
Soft write errors
Hard write errors
5. Click OK. See also: Editing and Viewing Media Set Properties on page 230 Creating Media Sets on page 227
224
Media Operations
Viewing Media Cleaning Properties

You can view media cleaning properties only for cleaning media.
To view media cleaning properties: 1. On the navigation bar, click Media. 2. Expand the All Media icon, and then select the media that you want to view. 3. Under General Tasks in the task pane, click Properties. 4. Select the Cleaning tab. The Media Cleaning Properties tab provides the following information:
Media Cleaning Properties tab Item Number of cleanings Description Displays the number of cleanings performed so far by this cleaning media. Type the maximum number of times you want to use this media for cleaning. If the media contains Media Auxiliary Memory, the maximum number of cleanings displays automatically.
Maximum number of cleanings
Media Management
5. Click OK.
225
Media Sets
Media Sets
A media set is a container for media. When you create a new media set, you must set an append period and an overwrite protection period for the set. When media is placed into the media set, that media takes on the attributes of the media set. Media sets can contain allocated media and recyclable media. When you create a backup job, you must identify a media set that will receive the backed up files. You can create media sets manually or using the Media Set Wizard. See also: Creating Media Sets on page 227 Deleting a Media Set on page 229 Renaming a Media Set on page 230 Editing and Viewing Media Set Properties on page 230
Running the Media Set Wizard

The Media Set Wizard guides you through the process of creating a new media set. It explains the choices you can make. The Media Set Wizard is helpful if you are new to Backup Exec or are unfamiliar with the concepts and terminology of media sets. Before you run this wizard you should understand media overwrite protection and append periods. For an overview of these terms, see Media Overwrite Protection on page 185. If you do not need a wizard to set up a new media set, see Creating Media Sets on page 227.
To run the Media Set Wizard: 1. On the Tools menu, point to Wizards. 2. Click Media Set Wizard. 3. Follow the instructions on the screen. 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.
226
Media Sets
Creating Media Sets
To create a media set: 1. On the navigation bar, click Media. 2. Under Media Set Tasks in the task pane, click New Media Set. 3. Select the appropriate options as follows:
New Media Set General tab Item Name Creation date Description 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.
Media Management
227
Media Sets New Media Set General tab (continued) Item Media set periods Overwrite protection period 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, moved to 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. Description
4. Click OK.
228
Media Sets
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 contains media. You must move the media to another media set first. Caution Make sure that the media set to which you move the media has the appropriate overwrite protection and append periods.
To delete a media set: 1. On the navigation bar, click Media. 2. In the Media selection pane, under Media Sets, select the media set that you want to delete. 3. Under General Tasks on the task pane, click Delete. 4. Click Yes to delete the media set, or if you selected multiple media sets to delete, click Yes to All to delete all the selected media sets without further prompting. 5. If there are scheduled jobs allocated to the deleted media set, you are prompted to redirect the jobs to another media set.
Media Management
Retarget Jobs dialog box
The media set you deleted displays. 6. In the Media Set selection box, click the Down arrow to see more options, and then select the new media set to which you want to redirect the scheduled jobs. 7. Click Yes to redirect the displayed job to the selected media set, or if there are multiple scheduled jobs, click Yes to All to redirect all scheduled jobs to this media set without further prompting. The scheduled jobs are redirected.
Chapter 5, Managing Media 229
Media Sets
Renaming a Media Set

When you rename a media set, properties for any jobs that belong to that media set will still display the previous media set name. To update the media set name for these jobs, select the job from the Job Setup view and then under General Tasks on the task pane, click Properties. The media set name is updated to the new name.
To rename a media set: 1. On the navigation bar, click Media. 2. In the Media selection pane, under Media Sets, select the media set you want to rename. 3. Under General Tasks on the task pane, click Rename. 4. In the Name field, type the new name you want to assign to this media set. 5. Click OK.
Editing and Viewing Media Set Properties

You can change the overwrite protection and append periods for a media set at any time.
To edit media set properties: 1. On the navigation bar, click Media. 2. In the Media selection pane, under Media Sets, select a media set. 3. Under General Tasks on the task pane, click Properties. 4. Select the appropriate options as follows:
Media Set properties Item Name Creation Date Description Media set name. Date when the media set was created.
230
Media Sets Media Set properties (continued) Item Media Set Periods Overwrite protection period 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, 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. 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, moved to Scratch Media, or if the Media Overwrite Protection Level is set to None. Description
Media Management
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.
5. Click OK.
231
Media Sets
232
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:
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 on the backup job properties pages accessed by either clicking the Backup button or selecting New Job from the Job Setup task pane. 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 template. Set all the destination, settings, and schedule options you want to use and save them as a template. You can quickly create a job using a template by combining the template with a selection list. You can use templates for multiple jobs, and, if changes are needed to these jobs settings, you can make changes to the template rather than editing the individual jobs. 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 then create a job from a template, combining the template with the chosen selection list.
Backing Up Data
Using Backup Execs Windows Explorer interface. Select and back up files and folders from Windows Explorer without having to launch the Backup Exec Administration Console. Running a one-button backup job. Select one-button backup from the Backup Exec Assistant or the Information Desk to quickly back up the local media server. One-button backups use the default backup settings.
233
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:

A test run of a scheduled backup job to determine whether or not it is likely to complete successfully. A job that duplicates backup sets either from previously backed up data or data scheduled to be backed up. If the backup sets are to be duplicated from a scheduled job, the duplicate backup data job runs automatically after the backup job completes. Verify jobs to test the integrity of the media. Archive jobs to preserve storage space. Resource discovery jobs to find new resources that may need to be backed up on a regular basis.
Before you begin backing up data, you should develop a backup strategy that includes the method, frequency, and media rotation methods that are appropriate for your organization. You may have different strategies for different areas of the organization. You may also want to configure device and media management before creating backup jobs. You can set up Backup Exec to use physical devices, such as stand-alone drives, or virtual devices, such as backup-to-disk folders. Or, you can have Backup Exec use logical groupings of devices, such as drive pools. Specifically, you might want to perform the following tasks to help you manage storage hardware and media most effectively:

Set up drive pools for systems with more than one storage device. For more information, see Creating Drive Pools on page 97. Create media sets. For more information, see Creating Media Sets on page 227.
234
Creating a Backup Job
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. See also: Creating a Backup Job on page 235 Setting Default Backup Options on page 312 About Backup Strategies on page 336 VERITAS Backup Exec - Remote Agent on page 821

Backing up data from a server or workstation involves the creation of a backup job in which you specify the:

Source Destination Settings Frequency
Unless you specify otherwise, the backup job will use the defaults set through the Tools menu by selecting Options. You can use the Backup Wizard to have Backup Exec guide you through the creation of a backup job, but after you become familiar with Backup Exec, you will probably choose to set your options by configuring backup job properties. See also: Using the Backup Wizard on page 236 Creating a Manual Backup Job by Configuring Job Properties on page 236 Setting Default Backup Options on page 312 Specifying Backup Networks on page 323
Backing Up Data
Chapter 6, Backing Up Data
235
Using the Backup Wizard

If you are new to Backup Exec or are uncertain about how to set up a backup job, you can use the Backup Wizard. The wizard will guide you through the process of creating a backup job. While the wizard will prompt you to select some options, most of the backup job settings will be based on the defaults set through the Tools menu by selecting Options.
To launch the Backup Wizard: 1. On the navigation bar, click Job Setup. 2. Under Backup Tasks in the task pane, select New job using wizard. 3. Follow the on-screen prompts. You can monitor the backup job through the Job Monitor. See also: Creating a Manual Backup Job by Configuring Job Properties on page 236 Setting Default Backup Options on page 312 Monitoring Jobs on page 365
Creating a Manual Backup Job by Configuring Job Properties
To create a backup job for a server or workstation: 1. On the navigation bar, click Backup. 2. From the backup selections pane, select the data you want to back up (see Selecting Data to Back Up on page 259) or choose an existing selection list from the Selection list name field (see Using Selection Lists on page 267). For more information about the Selections options, see Selections Options for Backup Jobs on page 239. 3. On the Properties pane, under Destination, click Device and Media, and complete the options as described in Device and Media Options for Backup Jobs and Templates on page 241. 4. On the Properties pane, under Settings, click General and complete the options as described in General Options for Backup Jobs on page 246.
236
You can select additional configuration options for your backup job if, before selecting to run or submit the job, you select additional options on the Backup Job Properties dialog boxs Properties pane: If you want to set advanced options for the backup job, on the Properties pane, under Settings, click Advanced. Then, complete the options as described in Advanced Options for Backup Jobs on page 251. If you want to set commands to run before or after a job, on the Properties pane, under Settings, click Pre/Post Commands and complete the options as described in Pre/Post Commands for Backup or Restore Jobs on page 255. If you are using the Advanced Open File Option, on the Properties pane, under Settings, select Advanced Open File and complete the options as described in Selecting the Advanced Open File Option for a Single Backup Job on page 964. 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. If you want to change the backup network for this job, on the Properties pane, under Settings, click Network, and then set up the backup network for this job (see Changing the Backup Network for a Job on page 328). If you want Backup Exec to notify someone when the backup job completes, on the Properties pane, under Settings, click Notification (see Selecting Recipients for Job Notification on page 492).
5. 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 358), and then click Submit. Note If you are using Backup Exec Web Administration Console (BEWAC), click Next to run the job or set the scheduling options.
Backing Up Data
237
6. 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, select Options, and then clear Display the job summary dialog before creating a backup job (see Backup Exec Defaults on page 84). Note If you are using BEWAC, click Finish to run the job. If you are not satisfied with the settings you selected, click Back. However, you must reset all of the settings. BEWAC does not save the settings when you click Back. Note If a drive loses power during a backup operation, you should restart the backup job using a different tape. You can restore the data written to the tape up to the point of the power loss, but you should not reuse the tape for subsequent backup operations. See also: Using the Backup Wizard on page 236 Selecting Data to Back Up on page 259 Setting Default Backup Options on page 312 Creating a New Backup Template on page 276 Creating a New Backup Job from a Template on page 283
238
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. You can also choose how the data will appear in this dialog box.
Selections options for a backup job
Options on this dialog box include:

Selections options for backup job Item Selection list name Description If you are creating a job using an existing selection list, select the selection list you want to use (see Using Selection Lists on page 267). Otherwise, use the default Selection list name, which creates a new selection list using this name. Enter a description for the selection list.
Backing Up Data
Selection list description Load Selections from Existing List
Click this button if you want to use a previously created selection list or merge existing selection lists (see Using Selection Lists on page 267).
239
Creating a Backup Job Selections options for backup job (continued) Item View Format Graphical Show file details Select this option to view selections in a directory tree view. Select this option to display details about the files available for selecting. Select this option 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 (see Including or Excluding Files for Backup Using Advanced File Selection on page 262). Select this option if you want to select the contents of all the subfolders when a directory is selected. Description
Text Advanced
Include subdirectories
See also: Selecting Data to Back Up on page 259 Changing the Order for Processing Backup Selections on page 265 Changing Logon Accounts for Resources on page 266 Including or Excluding Files for Backup Using Advanced File Selection on page 262 Creating Selection Lists on page 267 Setting Up User-defined Selections on page 275
240
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.
Device and Media options for backup job
Backing Up Data
241

Device and Media options for backup job Item Device 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 Using Backup-to-Disk Folders and Files on page 143). If the size of a backup job exceeds the amount of free space on the disk where the backup folder is located, the job fails. Before you back up data to a disk, verify that there is sufficient free space on the destination disk. To maximize the amount of data that you can store on a disk, use the software compression option. If a backup job fails due to insufficient disk space, the backup folder goes offline. To complete the backup job, you must create more free space on the disk, and then pause and resume the folder. You can create more disk space by: Moving the backup files to another disk or backing up the files to a tape. Changing the location of the backup folder. Erasing the backup files. Overwriting the existing backup files. If you are unable to create more free space and cannot continue the backup job, you can restore the data that was backed up prior to the failure. Note 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.
242
Creating a Backup Job Device and Media options for backup job (continued) Item Media set Description Select the media set for the backup (see Editing and Viewing Media Set Properties on page 230). 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. For more information, see Setting Default Media Options on page 203. If you selected one of the append options, the backup will be added to an appendable media (if one exists). Family name Specify a name for the new or overwritable media. This name is used to identify the media in the Restore Selections dialog boxes. The family name defaults to Media created date time. To customize the family name, you can use any combination of the following variables in this field: %s - includes the media server name %j - includes the job name %d - includes the date the media was created %t - includes the time the media was created
Backing Up Data
243
Creating a Backup Job Device and Media options for backup job (continued) Item When this job begins Overwrite media Select this option to place this backup on an overwritable media. Make sure that appropriate media is in the stand-alone drive or drive pool you select in the Device field in this dialog box. The media in the drive is overwritten if the media is scratch or recyclable (its overwrite protection period has expired). If allocated or imported media are in the drive, they may also be overwritten depending on the Media Overwrite Protection Level that is set. For more information, see Setting Default Media Options on page 203. Depending on your configuration, overwritable media is selected from scratch media or recyclable media. For more information, see Media Overwrite Options on page 192. If the media in the drive is not overwritable, an alert appears requesting that you insert overwritable media. Append to media, Select this option to append this backup to the media set listed in the overwrite if no appendable Media Set field in this dialog box. The backup set is appended if an media is available appendable media is available in the selected media set; if not, an overwritable media is used and added to the media set. Note If an append job fills a media, the job continues on another piece of overwritable media. If the media in the drive is not overwritable, an alert appears requesting that you insert overwritable 0media. Append to media, terminate job if no appendable media is available Eject media after job completes Select this option to append this backup to the media set listed in the Media Set field in this dialog box. The backup set is appended if an appendable media is available in the selected media set; if not, the job is terminated. Select this option to have Backup Exec automatically eject the media in the drive when the operation completes. Description
Write checksums to media Select this option if checksums are to be calculated for each data stream written to tape, and then written in a separate stream immediately following the data stream. If this option is not selected, backup performance may be improved, but there will be no way to verify the integrity of the data on the tape.
244
Creating a Backup Job Device and Media options for backup job (continued) Item Retension media before backup Description 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.
Media Protection Password protect media Select this option if you are overwriting the media and you want to protect it. When the Enter Password dialog box appears, enter a media password. When a password-protected media is taken to another location, such as another media server, the password is required to catalog the tape. Note Password protected media can be erased without requiring the password. Change password Click this button to change the password for the media.
Backing Up Data
245
General Options for Backup Jobs

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.
General settings options for backup job
246

General settings options Item Job name Description Enter the name for this backup job, or accept the default name that appears. The job name must be unique. Select the priority level for this job. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Your choices are: Highest High Medium Low Lowest Backup set description Type a description of the information you are backing up.
Job priority
Backing Up Data
247
Creating a Backup Job General settings options (continued) Item Backup method for files Description Select a backup method. Your choices are: FULL - Back Up Files - Reset Archive Bit. Includes all of the selected data on a volume and resets the archive bit to indicate that the files have been backed up. COPY - Back Up Files. Includes all selected data, and does not affect any media rotation scheme because the archive bit is not reset. DIFFERENTIAL - Changed Files. Includes all files that have changed (based on the archive bit) since the last full backup, and does not affect any media rotation scheme because the archive bit is not reset. INCREMENTAL - Changed Files - 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. FULL - Back Up Files - Allow incrementals and differentials using modified time. Includes all of the selected data on a volume and allows the use of incrementals and differentials using the modified date and time stamp. DIFFERENTIAL - Using modified time. Includes all files since the last full backup using the files last modified date and time stamp. INCREMENTAL - 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. DAILY - Files that Changed Today. Backs up all files that were created or modified today. WORKING SET - All files last accessed in (x) days. Includes all files that were created or modified since the last full or incremental backup. 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. ARCHIVE - Delete files after successful copy backup. Backs up the selected data, verifies the media, and then deletes the data from the volume. For data to be deleted, rights to delete a file must be granted; otherwise data will be backed up, but not deleted. Note Backup Exec does not delete data from Backup Exec Agent workstations when using the archive feature. For more information, see Understanding Backup Methods and Their Advantages on page 340. 248 Administrators Guide
Creating a Backup Job General settings options (continued) Item Files accessed in x days Description If you selected the working set backup method in the Backup method for files field, use this field to specify the number of days for which to include accessed files. Note VERITAS 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 Windows Change Select this option if you want to use Windows NTFS Change Journal if available 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 Allows incrementals and differentials using modified time, DIFFERENTIAL - Using modified time or INCREMENTAL - Using modified time. 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. 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.
Verify after backup completes
Backing Up Data
249
Creating a Backup Job General settings options (continued) Item Compression type 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.
See also: Creating a Manual Backup Job by Configuring Job Properties on page 236
250
Advanced Options for Backup Jobs

To set Advanced options, such as open file options, for backup jobs or backup job templates, on the Properties pane, under Settings, click Advanced.
Advanced options for backup job
Backing Up Data
251
Advanced options for backup jobs include:

Advanced options for backup job Item Enable single instance backup for NTFS Description This option is only available if single instance store is being used. This option ensures that only one instance of a file for NTFS volumes will be backed up regardless of the number of single instance store (SIS) links that point to it.
Caution If the backup job does not run to completion, the file data may not be included in the backup set. Rerun the backup until it is successfully completed. If the incremental backup method was used, running the job again will not back up the same files. You must run a full or copy backup to ensure that all files are backed up completely. If the 'incremental - using modified time' backup method was used, running the same backup job to completion will back up the files correctly.
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 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.
252
Creating a Backup Job Advanced options for backup job (continued) Item Back up data in Remote Storage 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. Note This option should not be selected if the device used for secondary storage and backups contains only one drive because Remote Storage and Backup Exec will compete for use of the drive. Set Remote Agent priority This option allows you to select the number of CPU cycles the media server will use to maintain optimal server performance while Remote Agent backups are running. The higher the priority, the more the protected servers CPU processing power is used during backup operations. Note Allocating fewer CPU cycles to a backup job may result in slower backup performance. This field contains the following options: Normal Priority. Select this option to allocate the default number of CPU cycles the protected server will use during a Remote Agent backup. Below Normal Priority. Select this option to allocate fewer server CPU cycles to the backup job. Lowest Priority. Select this option to allocate the fewest number of CPU cycles to the backup job.
Backing Up Data
253
Creating a Backup Job Advanced options for backup job (continued) Item Description
Open file backup when Advanced Open File Option is not used Never Select this option to have Backup Exec skip open files if they are encountered during the backup operation. A listing of skipped files appears in the job log for the backup.
If closed within x seconds Select this option to have Backup Exec wait the specified time interval for files to close before skipping the open file and continuing the backup operation. If the file does not close during the specified interval, it is skipped. A listing of skipped files appears in the job log for the backup. Note If multiple files are open, Backup Exec waits the specified time interval for each file; depending on the number of open files, this may significantly increase the backup time. With a lock Select this option to have Backup Exec attempt to open files that are in use. If Backup Exec is able to open a file, the file is locked while it is being backed up to prevent other processes from writing to it. Backing up open files is not as effective as closing applications and allowing the files to be backed up in a consistent state. 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.
Without a lock
Note To back up the Removable Storage database in the \Ntmsdata subdirectory, the WMI repository in the wbem\Repository subdirectory, and the Terminal Services database in the default \LServer subdirectory, select the <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. See also: Creating a Manual Backup Job by Configuring Job Properties on page 236 Setting Advanced Open File Option as the Default Setting for All Backup Jobs on page 966
Pre/Post Commands for Backup or Restore Jobs

To set commands to run before or after a job, on the Properties pane of the Backup Job Properties dialog box, the Restore Job Properties dialog box, or the New Backup Job Template dialog box, under Settings, click Pre/Post Commands. You can run commands before or after a backup or restore job, and set conditions for these commands:

Run the backup or restore job only if the pre-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 backup or restore 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 does 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 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-job command fails. Additionally, if Backup Exec is configured to check the return codes of the pre- and post-job commands, and the post-job command returns a non-zero code, the job log reports that the post-job command failed. If you also selected to run the job only if the pre-job command is successful, and both the pre-job command and the job ran successfully, Backup Exec will mark the job as failed if the post-job command fails. For example, if the pre-job command runs successfully and shuts down the database and the backup 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 backed up, the pre- and post-commands are run and completed for each server before processing begins on the next selected server.
Backing Up Data
255
Creating a Backup Job Pre-job and post-job command options
Options for this dialog box include:

Pre- and post-job command options Item Description
Pre-job and post-job commands Pre-job command Specify a command to be run on the specified server before the backup or restore job is run. Use local paths, and make sure the paths exist on each server and are correct. Note Commands that require user interaction, such as prompts, are not supported. Post-job command Specify a command to be run on the specified server after the backup or restore job has run. Use local paths, and make sure the paths exist on each server and are correct. Note Commands that require user interaction, such as prompts, are not supported.
256
Creating a Backup Job Pre- and post-job command options (continued) Item Run job only if pre-job command is successful Description Select this option to run the backup or restore job only if the pre-job command is successful. If the pre-job 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-job 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, it is interpreted by Backup Exec to mean that the pre-job command did not run successfully. The job is not run and the job status is marked as Failed. Run post-job command Select this option to run the post-job command only if the pre-job only if pre-job command is command is successful. successful If it is critical that the post-job command does not run if the pre-job 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-job command, it is interpreted by Backup Exec to mean that the pre-job command did not run successfully. The post-job command does not run. If you also select Run job only if pre-job command is successful, and both the pre-job command and the job are successful, but the post-job command returns a non-zero code, the job log reports both the job and the post-job command as failed. Run post-job command even if job fails Select this option if it is critical to run the post-job command regardless of whether 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-job command returns a non-zero code, the job log reports the post-job command as failed.
Backing Up Data
257
Creating a Backup Job Pre- and post-job command options (continued) Item Allow pre- and post-job commands to be successful only if completed with a return code of zero Description Select this option to allow Backup Exec to check the return codes of the pre- and post-job commands to determine if they 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 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-job commands. If this option is not selected, the success of the pre- and post-job commands is not determined based on the return code. Cancel command if not completed within x minutes Run these commands On this media server Select this option to run the pre- and post-job commands on this media server only. Select the number of minutes Backup Exec should wait before canceling a pre-job or post-job command that did not complete. The default time-out is 30 minutes.
On each server backed up Select this option to run the pre- and post-job commands one time on each server backed up. The pre- and post-job 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.
See also: Creating a Manual Backup Job by Configuring Job Properties on page 236 Setting Default Backup Options on page 312 Setting Default Pre/Post Commands on page 319
258
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 Backup Exec database System State Network shares
Workstation agents User-defined selections
The Local Selections include:

Local Drives. Includes hard drives as well as CD-ROM drives physically residing on the media server. Backup Exec database. Includes job, schedule, job history, notification, alerts, device, media, and catalog indexes data for Backup Exec. System State. This collection of system-specific data is selected for backup whenever the Local Selections icon is selected. Backing up System State is recommended; however, you can clear the check box next to System State if you do not want to back it up with the Local Selections. When you double-click the icon for System State, the resources that comprise it appear to the right of it. If a resource is not installed on the computer, then it is not listed. You cannot select or expand the System State resources individually. They are backed up and restored only as a collection, never individually. You can only perform a full backup on System State. However, if you select other items at the same time, you can perform other backup methods on those items. You can back up System State remotely on other computers if Backup Exec Remote Agent is installed on the remote computer. For more information about System State, refer to your Microsoft Windows 2000 or .NET documentation.
Backing Up Data
Utility Partition. Includes the utility partitions 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
259
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. You can only perform a full backup of utility partitions. However, if you select other items at the same time, you can perform other backup methods on those items. You can back up utility partitions remotely on other computers The Remote Selections include:

Network Shares. Includes Microsoft Windows systems protected by the Remote Agent for Windows Servers. Workstation Agents. The Backup Exec Workstation Agents protect workstations running Windows 98/Me, Macintosh, and UNIX. The Novell SMS devices appear only when the Client (or Gateway) Services for NetWare service is enabled or Novell NetWare Client 32 is installed. If an agent workstation is password-protected, you must enter a password to access the agents published data. If some or all of the computers shared directories cannot be selected, a gray check box appears next to the agent. If this occurs, only the agent computers that Backup Exec scanned successfully are selected for backup. Review your security and attachment rights to the computers that are not selected. You cannot restore or archive workstation agent shares that are published as read-only. Valid logon accounts are required to access the systems. User-defined Selections. Lists shortcuts to servers or shares that were created and saved as user-defined selections. Use this feature to quickly access shares that have a very long path or that are offline when you are setting up a backup job.
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. 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.
260
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. To select data, select the check box next to the drive or directory you want to back up. The check box and check mark displayed are described in the following.
Data selection descriptions 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.
A shaded check box means the item cannot be selected, but items below this item may be selectable.
See also: Protecting Windows.NET Systems on page 333 Backing Up NetWare Network Volumes on page 335
About Selecting Distributed File System (Dfs) Links for Backup

To back up Microsofts Distributed File System (Dfs), select the Dfs links on the Dfs server. 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. See also: Setting Up User-defined Selections on page 275 Restoring Distributed File System (Dfs) Links on page 424
Chapter 6, Backing Up Data 261
Backing Up Data
Including or Excluding Files for Backup Using Advanced File Selection

Advanced file selection allows you to quickly select or de-select files for backup and archive operations by specifying file attributes. With this feature you can:

Include or exclude files by filename attributes. For example, you can select only files with .txt extensions, or exclude files with .exe extensions from a backup. Select only files that fall within a specified date range. For example, you can select files that were created or modified during the month of December. Specify files that have not been accessed in a specified number of days. For example, you can select files that have not been accessed in 30 days from your My Documents folder for an archive operation.
To select files using Advanced File Selection: 1. On the navigation bar, click Backup. 2. Select the resource that contains the files you want to include or exclude from the backup. 3. Select the path or file that contains the files you want to include or exclude. 4. Click Advanced.
Advanced File Selection dialog box
262
5. Select the appropriate options as follows: Note 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.
Advanced File Selection options Field Drives Description 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.
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 a single asterisk (*) to represent any number of characters before the next backslash. Use a double asterisk (**) to represent any number of characters, irrespective of any backslashes. For example, on your C: drive you have a My Documents folder that contains a subfolder called Work Files. There are three Work Files subfolders called 1999, 2000, and 2001. Each one of those subfolders has a subfolder called Personnel. If you type the path as \My Documents\**\Personnel, the backup will include or exclude: C:\My Documents\Work Files\2001\Personnel C:\My Documents\Work Files\2000\Personnel C:\My Documents\Work Files\1999\Personnel In addition, every subfolder below the ** wildcard is included or excluded. However, the only files from the subfolders that are included or excluded are those that match the file name you type in the File field. So in the example above, every subfolder of C:\My Documents is included in or excluded from the backup, and only the files that match the file name you type in the File field are included or excluded. After you type the path, type the file name in the File field.
Backing Up Data
263
Selecting Data to Back Up Advanced File Selection options (continued) Field File Description 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 a single asterisk (*) to represent any number of characters. For example, to include all files with the .exe extension, type *.exe. You can use more than one asterisk if you know that a file name has certain letters in it, but not the exact file name. For example, to include or exclude any file that has the name Sam in it, type *Sam*.*. The default entry is *.*, which means every file name with every extension is selected. After you type the file name, indicate whether you want to include or exclude it. Type Include Exclude Selection Criteria Include subdirectories 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. 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. 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. (Default) Select this option to include the files in the job. Select this option to exclude the files from the job.
Only modified Files
Only read-only Files Files dated
Files not accessed in x days
264
6. After completing your selections, click OK. 7. Submit the operation using the same procedures as required for other backups. For more information, see Creating a Manual Backup Job by Configuring Job Properties on page 236.
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.
1. On the navigation bar, click Backup. 2. Select the data you want to back up. 3. On the Properties pane, under Source, click Resource Order. 4. Select an item you want to move. 5. Then, 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. 6. Process the backup job (see Creating a Manual Backup Job by Configuring Job Properties on page 236).
Backing Up Data
265
Changing Logon Accounts for Resources

A logon account enables Backup Exec to access resources for backup.
To change a logon account for a resource: 1. On the navigation bar, click Backup. 2. Select the data you want to back up. 3. On the Properties pane, under Source, click Resource Credentials. 4. Select the resource whose logon account you want to edit. 5. Click Change. 6. Select the Backup Exec logon account you want to use for this backup selection, or click New and create a new Backup Exec logon account (see Creating a Backup Exec Logon Account on page 350). 7. Click OK.
266
Using Selection Lists

Selection lists provide a quick and easy way of selecting files that you back up often. After you choose devices, directories and files, you can save the selections as a selection list that you can use in regularly scheduled operations or once-only operations. Selection lists, which define what is to be backed up, are also automatically created when you create a backup. You can combine a selection list with a template and quickly create a backup job. See also: Creating Selection Lists on page 267 Using Selection Lists to Create a Backup Job on page 270 Deleting Selection Lists on page 272 Editing Selection Lists on page 273 About the Excludes Selection List on page 273
Creating Selection Lists

Backup selection lists contain selections from the Backup Job Properties - Source dialog box. Restore and verify selection lists contain selections from the Restore Job Properties Source dialog box. The following steps explain the creation of a backup selection list.
To create a backup selection list: 1. On the navigation bar, click Job Setup. 2. Under Backup Tasks in the task pane, select New selection list.
Backing Up Data
267
Using Selection Lists Selections options for new selection list
3. Select the resources you want to back up from the backup selections pane. For more information about selecting data, see Selecting Data to Back Up on page 259. 4. Select the appropriate options as follows:
Selections options for selection list Item Selection list name Selection list description Load Selections from Existing List Description Enter the name of this selection list. Enter a description for this selection list.
Click this button if you want to load an existing selection list or merge multiple selection lists (see Merging and Replacing Selection Lists on page 271).
View format Graphical Select this option to view selections in a directory tree view.
268
Using Selection Lists Selections options for selection list (continued) Item Show file details Description Select this option to display details about the files available for selecting. Select this option 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 (see Including or Excluding Files for Backup Using Advanced File Selection on page 262).
Text Advanced
Include subdirectories Select this option if you want to select the contents of all the subfolders when a directory is selected.
5. Click OK. See also: Using Selection Lists on page 267 Using Selection Lists to Create a Backup Job on page 270 Deleting Selection Lists on page 272 Editing Selection Lists on page 273 About the Excludes Selection List on page 273
Backing Up Data
269
Using Selection Lists to Create a Backup Job
To use selection lists to create a backup job: 1. On the navigation bar, click Backup. 2. Click Load Selections from Existing List.
Load Selections from Existing List
3. Click the check box next each selection list you want to use for this backup. You can select multiple selection lists. A merged selection list will then be created and used for the job. The merged selection list will be saved separately and can be used for other jobs.
270
4. Submit the operation using the same procedures required for other backup operations (see Creating a Manual Backup Job by Configuring Job Properties on page 236). You can combine selection lists with a template to quickly create a new backup job. See also: Using Selection Lists on page 267 Creating Selection Lists on page 267 Deleting Selection Lists on page 272 Editing Selection Lists on page 273 About the Excludes Selection List on page 273 Creating a New Backup Job from a Template on page 283
Merging and Replacing Selection Lists

You can create a new selection list by merging two or more existing lists with new selections. Merging of selection lists can be done when creating a job (see Using Selection Lists to Create a Backup Job on page 270) or by selecting the New selection list option. You can also replace selections in the tree with other selection lists.
To merge or replace selection lists: 1. On the navigation bar, click Job Setup. 2. Under Backup Tasks in the task pane, select New selection list. 3. To merge with an existing selection list: a. On the New Backup Selection List dialog box, select resources to include in the selection list. b. Click Load Existing Selection List. c. On the Use Selections dialog box, select the selection lists you want to merge with the previously selected items. d. Click Merge.
Backing Up Data
271
4. To replace selections with an existing selection list: a. Click Load Existing Selection List. b. On the Use Selections dialog box, select the selection lists you want to replace with the previously selected. c. Click Replace. 5. Click OK. 6. Complete the other options on the New Backup Selection List dialog box as described in Selections options for selection list on page 268. 7. Click OK.
Deleting Selection Lists
To delete a selection list you are no longer using: 1. On the Edit menu, click Delete Selection List. The Delete Selections dialog appears. The available selection lists are listed in this window. 2. Click the selection list you want to delete, and then click Delete. 3. Click Yes to delete the Selection List; 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. See also: Using Selection Lists on page 267 Creating Selection Lists on page 267 Using Selection Lists to Create a Backup Job on page 270 Editing Selection Lists on page 273 About the Excludes Selection List on page 273
272
Editing Selection Lists

Editing a selection list affects all jobs using that selection list. If you want to only edit selections for a specific job, edit the job rather than the selection list.
To edit a selection list: 1. On the navigation bar, click Job Setup. 2. On the Backup Selection Lists pane, select the selection list you want to edit. 3. Under General Tasks in the task pane, click Properties. 4. If the selection list is being used by jobs, you will be prompted to click Yes to continue. 5. Make the changes you want to Selections, Resource Order, and Resource Credentials. 6. Click OK. See also: Using Selection Lists on page 267 Creating Selection Lists on page 267 Using Selection Lists to Create a Backup Job on page 270 Deleting Selection Lists on page 272 About the Excludes Selection List on page 273
About the Excludes Selection List

The Excludes Selection List provides an easy way for you to specify directories and/or files that you never want to back up. For example, you may have many temporary (*.tmp) files residing on your local disk. By adding them to the Excludes Selection List, these files are not backed up or archived. You can delete the Excludes Selection List. However, if you want to create a new Excludes Selection List, use Excludes as the Selection List name.
Backing Up Data
273
To edit the Excludes list: 1. On the Edit menu, click Edit Selection List.
Edit Selection List dialog box
The Name and Type, such as backup or restore, of each selection list appears. 2. Choose Excludes from the Selection lists. 3. Click Edit. 4. If the Excludes list has been previously edited, you can select the Selection rule you want to edit and click Edit (see Including or Excluding Files for Backup Using Advanced File Selection on page 262), or select the Selection rule you want to remove and click Delete. 5. If this is the first time the Excludes list is being edited, click Insert (see Including or Excluding Files for Backup Using Advanced File Selection on page 262). 6. Click OK to save your changes and exit the Edit Selection List window. See also: Deleting Selection Lists on page 272 Creating Selection Lists on page 267
274
Setting Up User-defined Selections
Setting Up User-defined Selections

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 are setting up a backup job. You can set up direct access to a share by entering its UNC name, IP address, or machine name. A share may be unavailable because the network resources used to locate the machine are offline, even though the machine may still be running and available. In some cases this happens because the machine is on the internet and accessible from within the companys private network, but cannot be located using just its name or normal browsing methods.
To add a user-defined selection: 1. On the navigation bar, click Backup. 2. On the backup selections pane, expand Remote Selections. 3. Right-click User-defined Selections, and then click User-defined Selections. 4. In the UNC Name field, type the server name and volume name Example: \\Production\graphics Note TCP/IP addresses can also be provided for user-defined selections. For example: \\10.0.0.0. Or you can use the computer name. 5. Click Add. The share appears in the Selections defined section of the dialog box. Repeat steps 4-5 to add additional user-defined selections. 6. When you are finished adding selections, click Close. The selections that you specified can be selected for backup operations from the User-defined Selections node. See also: Using Selection Lists on page 267 Creating Selection Lists on page 267 Using Selection Lists to Create a Backup Job on page 270 Deleting Selection Lists on page 272 Editing Selection Lists on page 273 About the Excludes Selection List on page 273
Backing Up Data
275
Using Backup Job Templates

Templates are job attributes that define how and when Backup Exec processes a job. Templates specify the device, settings, and schedule options to use, but do not include the resource selections to be used for the backup job. Templates are useful when you want to create new backup jobs that use the same settings. For example, you may want to define your backup strategy (see About Backup Strategies on page 336) that includes the media rotation methods. You can reflect this strategy once in your template definition, and then reuse the template for all resources being protected by the media server. Using templates offers another advantage when changes in the settings need to be made to multiple jobs. Rather than editing all jobs that use the same template, you can edit the template. Backup Exec then applies the template change to all jobs using that template during the next job processing interval.
Creating a New Backup Template
To create a new backup template: 1. On the navigation bar, click Job Setup. 2. Under Backup Tasks in the task pane, select New job template.
Device and Media options for new template
276
3. Set up the Device and Media options for this template. See Device and Media options for backup job on page 242 for detailed information about these options. 4. On the Properties pane, under Settings, click General and select options as described in General Options for Backup Job Templates on page 278. 5. Additional options can be set by selecting on the Properties pane additional Settings options, such as Advanced (see Advanced Options for Backup Jobs on page 251) and Pre/Post Commands (see Pre/Post Commands for Backup or Restore Jobs on page 255). 6. On the Properties pane, under Frequency, click Schedule to set the schedule options for this template (see Scheduling Jobs on page 358). 7. Click OK. See also: Creating a Manual Backup Job by Configuring Job Properties on page 236 Using Selection Lists to Create a Backup Job on page 270
Backing Up Data
277
General Options for Backup Job Templates

General options for backup job templates include the template name and backup method. These options are set on the New Backup Job Template dialog box. To set these options, on the Properties pane, under Settings, click General.
New Backup Job Template General options
General options for backup job templates include:

General settings options for new backup job template Item Template name Backup set description Description Type the name for this backup job template. Type a description of the information you are backing up.
278
Using Backup Job Templates General settings options for new backup job template (continued) Item Backup method for files Description Select a backup method. Your choices are: FULL - Back Up Files - Reset Archive Bit. Includes all of the selected data on a volume and resets the archive bit to indicate that the files have been backed up. COPY - Back Up Files. Includes all selected data, and does not affect any media rotation scheme because the archive bit is not reset. DIFFERENTIAL - Changed Files. Includes all files since the last full backup. INCREMENTAL - Changed Files - Reset Archive Bit. Includes only the files that have changed since the last full or incremental backup and resets the archive bit to indicate that the files have been backed up. FULL - Back Up Files - Allow incrementals and differentials using modified time. Includes all of the selected data on a volume and allows the use of incrementals and differentials using the modified date and time stamp. DIFFERENTIAL - Using modified time. Includes all files since last full backup using the files last modified date and time stamp. INCREMENTAL - Using modified time. Includes all files since the last full or incremental backup using the files last modified date and time stamp. DAILY - Files that Changed Today. Backs up all files with todays date. WORKING SET - All files last accessed in (x) days. Includes all files that were created or modified since the last full or incremental backup. 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. ARCHIVE - Delete files after successful copy backup. Backs up the selected data, verifies the media, and then deletes the data from the volume. For data to be deleted, rights to delete a file must be granted; otherwise data will be backed up, but not deleted. Note Backup Exec does not delete data from Backup Exec Agent workstations when using the archive feature. For more information, see Understanding Backup Methods and Their Advantages on page 340.
Backing Up Data
279
Using Backup Job Templates General settings options for new backup job template (continued) Item Files accessed in x days Description If you selected the working set backup method in the Backup method for files field, use this field to specify the number of days for which to include accessed files. Note VERITAS 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 Windows Change Select this option if you want to use Windows NTFS Change Journal to determine which files have been modified since the Journal if available
last full backup. This option can only be used with NTFS volumes and only when the backup method selected is FULL - Back Up Files - Allows incrementals and differentials using modified time, DIFFERENTIAL - Using modified time or INCREMENTAL - Using modified time.
Preserve tree on archive Select this option to retain the directory structure of the files backed up in an archive job. 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.
Verify after backup completes
280
Using Backup Job Templates General settings options for new backup job template (continued) Item Compression type 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.
Backing Up Data
281
Editing a Backup Job Template

You can quickly update the settings for all jobs that use the same template by editing the template rather than the individual jobs.
To edit a job template: 1. On the navigation bar, click Job Setup. 2. On the Backup Job Templates pane, select the template you want to edit. 3. Under General Tasks in the task pane, select Properties. 4. Make the changes you want, and then click OK. See also: Creating a New Backup Template on page 276
Creating a Copy of a Backup Job Template

You can make a copy of an existing backup job template. You may want to make a copy if you want to create a new template that uses most of the properties of an existing template. For example, if you want to create both full and differential backup jobs for resources and all other job settings will be identical, you can create a template using the full backup method and copy the template, you can then make changes to the copy through the templates Properties (see Editing a Backup Job Template on page 282).
To make a copy of a template: 1. On the navigation bar, click Job Setup. 2. In the Backup Job Templates pane, select the template you want to copy. 3. Under Backup Tasks in the task pane, select Copy template. 4. Enter the name of the new template, and then click OK.
282
Creating a New Backup Job from a Template

Before you can create a backup job from a template, you must have a template with your specifications for the backup job and a selection list that contains the data you want to back up. If you do not have a template set up, see Creating a New Backup Template on page 276. If you do not have a selection list set up, see Creating Selection Lists on page 267. If you want to notify a person when the backup job completes, you must also have this person set up in a recipient list. 1. On the navigation bar, click Job Setup. 2. Under Backup Tasks, click New job from template.
Template options for new job from template
Backing Up Data
3. Select the template you want to use for this backup job. If you want to create a new template for this backup job, click New. Then, refer to Creating a New Backup Template on page 276. 4. On the Properties pane, under Source, click Backup Selection Lists. 5. Choose the selection list you want to use for this backup job. If you want to create a new selection list for this backup job, click New. Then refer to Creating Selection Lists on page 267.
6. On the Properties pane, under Settings, click General and set general options for this job as described in General Options for New Job from Template on page 284. 7. If you want Backup Exec to notify someone when the backup job completes, on the Properties pane, under Settings, click Notification (see Selecting Recipients for Job Notification on page 492). 8. Click Run Now. The backup job is submitted according to the schedule options you set in the profile.
General Options for New Job from Template

Most options for a backup job created from a template are set when creating the backup job template. However, you can set some general options, such as the job name, from the Backup Job Properties dialog box by selecting on the Properties pane, under Settings, General.
General options for new job from template
284
General options for a job created from a backup job template include:
General options for new job from template Item Job name Job priority Description Enter a unique name for the 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 choices are: Highest High Medium Low Lowest Submit job on hold Enable automatic cancellation feature Select this option if you want to submit the job on hold. Select this item if you want Backup Exec to automatically cancel the backup job if it does not complete within a specific amount of time after the scheduled start time. Then, in the Cancel job if not completed within fields, select the amount of time you want Backup Exec to wait before canceling the job. Indicate the number of minutes or hours you want Backup Exec to wait before it cancels the backup job.
Cancel job if not completed within x
Backing Up Data
285
Using Backup Execs Windows Explorer Interface
Reapplying a Template to Jobs

If you edit a backup job that was created using a backup job template, you receive a warning that editing the job will break the jobs association with the template. After editing the job, you should then reapply the template.
To reapply the template to a backup job: 1. On the navigation bar, click Job Setup. 2. From the Backup Job Templates pane, select the template you want to reapply. 3. Under Backup Tasks in the task pane, select Reapply Templates to Jobs. 4. A warning message displays the jobs that will be affected. 5. Click Yes.

Backup Execs Windows Explorer interface allows you to select and back up files from Windows Explorer. Backup Execs administration console does not have to be running to create and submit backup jobs from Windows Explorer; however, Backup Exec services must be running on the server. The Windows Explorer interface can be used on the Backup Exec server and any computer running the Backup Exec Remote Administrator (see Installing the Backup Exec Remote Administrator on page 67). Backup Execs Windows Explorer interface cannot be used to back up databases, such as Microsoft SQL or Exchange server. To back up a database, use the appropriate Backup Exec agent. For more information, see Backup Exec Options on page 36.
To set up Backup Exec to create backups from Windows Explorer: 1. On the Tools menu, click Options. 2. On the Properties pane, under Settings, click Preferences. 3. Select Enable backup from Windows Explorer.
286
4. Click OK. The Back up with Backup Exec option will now appear on the Windows Explorer shortcut menu. See also: Backup Exec Defaults on page 84 Submitting a Backup Job from Windows Explorer on page 290 Archiving Data on page 293
Specifying or Changing Backup Settings for Windows Explorer

The first time you submit a backup job using the Backup Exec Windows Explorer interface, you must specify logon information for the media server and enter a backup device name. The Backup Settings dialog box allows you to save the settings, which are used for subsequent backup jobs submitted from Windows Explorer. If you do not save the settings, you need to enter the logon information and the backup device name each time you submit a backup job from Windows Explorer.
To specify or change settings for a backup job from Windows Explorer: 1. From Windows Explorer, right-click any file or folder. 2. Select Back up with Backup Exec from the shortcut menu. Note If you have already specified and saved backup job settings, the Backup dialog box appears. You can change backup job settings from the Backup dialog box. For more information, see Submitting a Backup Job from Windows Explorer on page 290.
Backing Up Data
287
Using Backup Execs Windows Explorer Interface Backup Settings dialog box

Backup Settings options Name Server Name Description Type the name of the media server on which Backup Exec is installed.
Remote Server Login User Name View or change the user name. The default is the name of the user currently logged on to the machine. You can enter a different user or administrator. Note If you are logged on as part of a workgroup, the user domain is your local machine name. Password Type the password for the user.
288
Using Backup Execs Windows Explorer Interface Backup Settings options (continued) Name Backup Options Job Name View or change the job name. The utility generates a unique name for the backup job in the format: Backup <local machine name><numeric ID>. If the job name exceeds 25 characters, the utility truncates the local machine name. For example: For a backup run on a machine named ADMN-30PAYROLL, the utility could generate the job name Backup ADMN-30P 960576233. If you change the default job name, you must ensure it is a unique job name. Device Name Type the name of the backup device. Description
Include subdirectories in Select this option to include all subfolders within the selected backup folders in the backup job. Save Settings Select this option to save the backup settings as defaults for subsequent backup jobs. Note You must submit a backup job to save the settings in the Registry. Clear this option if you want to change the settings for a single backup job but keep the defaults saved in the Registry. Job Status View the status of a job, confirmation and error messages, and the job ID.
4. Click Submit Job. See also: Archiving Data on page 293
Backing Up Data
289
Submitting a Backup Job from Windows Explorer

After you have enabled Backup Exec to use the Windows Explorer interface and specified the backup settings, you can submit backup jobs from Windows Explorer.
To submit a backup job from Windows Explorer: 1. From Windows Explorer, select the files or folders you want to back up. 2. Right-click the selected files or folders and select Back up with Backup Exec from the shortcut menu.
Selecting Back up with Backup Exec from Windows Explorer
Note If you have not yet saved backup job settings, the Backup Settings dialog box appears. You must specify settings before submitting a backup job. For more information, see Specifying or Changing Backup Settings for Windows Explorer on page 287.
290
Using Backup Execs Windows Explorer Interface Backup dialog box

Backup options Name Job Name Description View or change the job name. The utility generates a unique name for the backup job in the format: Backup local machine name numeric ID. If the job name exceeds 25 characters, the utility truncates the local machine name. For example: For a backup run on a machine named ADMN-30PAYROLL, the utility could generate the job name Backup ADMN-30P 960576233. If you change the default job name, you must ensure it is a unique job name. Include Subdirectories in Select this option to include all subfolders within the selected Backup folders in the backup job. Job Status View the status of a job, confirmation and error messages, and the job ID.
Note The backup job defaults to the options set in the Backup tab. For more information, see Setting Default Backup Options on page 312.
Backing Up Data
291
Running a One-button Backup Job
4. Click Submit Job. 5. Click Close Dialog after the backup job has been submitted and confirmed. Note To submit another backup job, you must close the Backup dialog box. See also: Specifying or Changing Backup Settings for Windows Explorer on page 287 Submitting a Backup Job from Windows Explorer on page 290
Running a One-button Backup Job

One-button backup quickly backs up the local media server using the backup defaults. With one-button backup, you cannot select data or set options for the backup. After you select one-button backup, the backup job is submitted immediately using your default logon account and the default backup selections and settings. You can back up the following with one-button backup:

Local drives that do not use removable media Lotus Domino resources Windows NT System State Windows NT Utility Partition Windows NT Shadow Copy Device Microsoft SQL Server databases Microsoft Sharepoint Portal Server Microsoft Exchange 5.5 Directory Microsoft Exchange 5.5 and 2000 Information Store Microsoft Exchange 2000 Key Management Service (KMS) and Site Replication Service (SRS)
You cannot back up the following types of data with one-button backup:

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:)
292
Archiving Data
To run a one-button backup job: 1. On the navigation bar, click Overview. Note You can also run a one-button backup job from the Backup Exec Assistant. To activate the Backup Exec Assistant, on the Tools menu, select Backup Exec Assistant. 2. On the Properties pane, under Views, select Information desk. 3. On the Information Desk, under Getting Started, click Back up this media server now with One-button backup. Backup Exec submits the job to the job queue.
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. Note For data to be deleted, rights to delete a file must be granted; otherwise data will be backed up, but not deleted. Backup Exec does not delete data from Backup Exec Agent workstations when using the archive feature. During an archive job, Backup Exec automatically performs a verify operation after the data is backed up. If the verify operation fails, the archive job stops and you are notified. If you get a verification failure, investigate the problem by viewing the job log, try to correct the problem, and then retry the archive operation. After the data is backed up and verified, Backup Exec automatically deletes the data included in the archive job. The job log contains a list of the data that was deleted.
Backing Up Data
293
Archiving Data
Archiving Data Using Disk Grooming

The archive operation can be used to perform disk grooming, which uses Windows last access date to move obsolete files from the server to media. Note The NTFS file system supports the last access date capability as does the VFAT file system under Windows NT. However, files accessed while the VFAT file system is used under DOS are not selected.
To perform an archive operation: 1. On the navigation bar, click Backup. 2. Click Advanced. 3. For each resource you want to archive: a. On Drives selections, select the resource. b. Click Files not accessed in x days. Then, type or select the number of days (up to 999) to use as the criteria for selecting files. At this time, you may specify other criteria for data you want to include in the operation. For example, type *.doc in the File field to groom all of your document files not accessed in the number of days specified in the Files not accessed in x days field. c. Click OK. 4. On the Properties pane, under Settings, click General, and then select Archive as the backup method. 5. Complete the backup job options following the procedures described in Creating a Manual Backup Job by Configuring Job Properties on page 236. See also: Including or Excluding Files for Backup Using Advanced File Selection on page 262 Archive Backups on page 344
294
Using Resource Discovery to Search for New Resources

Backup Execs Resource Discovery feature allows detection of new backup resources within a Windows domain. Using this feature, you can create and schedule a job that searches for new server volumes or databases. You can specify which types of resources to include in the search, and can have Backup Exec send a notification when a new resource is discovered. Using the discovered resources identified in the job log, you can then create a backup job to ensure that the new resource is protected.
To create a resource discovery job: 1. On the navigation bar, click Job Setup. 2. Under Backup Strategy Tasks in the task pane, select New job to automatically discover resources.
Target options for resource discovery job
Backing Up Data
3. Select the domain you want Backup Exec to search for new resources. 4. 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.
295
Note If you are using BEWAC, you can only choose a pre-defined logon account. You cannot create or edit a logon account. 5. If you want to exclude computers from the search, see Excluding Computers from a Resource Search on page 299. 6. On the Properties pane, under Settings, click General and complete the options described in General Options for Resource Discovery Job on page 297. 7. On the Properties pane, under Settings, click Resources and complete the options described in Resources Options for a Resource Discovery Job on page 298. 8. If you want Backup Exec to notify someone when this job completes, on the Properties pane, under Settings, click Notification (see Selecting Recipients for Job Notification on page 492). 9. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358).
296
General Options for Resource Discovery Job

General options for a resource discovery job can be set through the Resource Discover Job dialog box. To set the options, on the Properties pane, under Settings, click General.
General settings for resource discovery job

General settings options for resource discovery job Item Job name Job priority Description Enter the name for this job.
Backing Up Data
Select the priority level for this job. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Your choices are: Highest High Medium Low Lowest
297
Resources Options for a Resource Discovery Job

You can specify types of resources to discover and set some notification options through the Resources options dialog box. To set resource options, from the Resource Discovery Job dialog box, on the Properties pane, under Settings, click Resources.
Resources options for resource discovery job

Resources options for resource discovery job Item Description
Select the types of resources to automatically discover Network administrative shares Network user shares Select this option if you want Backup Exec to search for new administrative network shares or volumes. Select this option if you want Backup Exec to search for new user-defined shares. Select this option if you want Backup Exec to search for new Microsoft SQL databases.
Microsoft SQL databases
298
Using Resource Discovery to Search for New Resources Resources options for resource discovery job (continued) Item Microsoft Exchange servers Description 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. Select this option if you want Backup Exec to search for new Lotus Domino databases. Select this option if you want Backup Exec to search for new System State resources.
Lotus Domino databases System State
When new resources are discovered: Send separate notification for each new resource found Send one notification for all new resources found Include previously discovered resources when sending notification Select this option if you want Backup Exec to send separate notifications when each new resource is found.
Select this option if you want Backup Exec to send out a single notification for all new resources found.
Select this option if you want Backup Exec to send a notification that includes all resources previously found during resource discovery jobs.
Excluding Computers from a Resource Search

When creating a resource discovery job, you can select to exclude one or more computers in the domain from the resource search.
To exclude computers from the resource search: 1. After selecting the domains for Backup Exec to search for new resources (see Using Resource Discovery to Search for New Resources on page 295), on the Properties pane, under Target, click Exclude. 2. In the Domain field, select the domain that contains the servers you want to exclude. 3. From the list below the Domain field, select the server you want to exclude, and then click Exclude.
Backing Up Data
299
Duplicating Backed Up Data
To select consecutive servers, click the first item, press and hold <Shift>, and then click the last item. To select servers that are not consecutive, press and hold <Ctrl>, and then click each item. Note Alternatively, you can type the name of the server in the Servers excluded field, and then click Add. To exclude multiple servers at one time, type a space between the name of each server. Tip To remove a server from the list of excluded servers, select it and then click Include to return it to the list of included servers. You can also select multiple servers simultaneously.
4. Continue creating the resource discovery job.

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 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.
To duplicate backup data: 1. From the navigation bar, click Job Setup. 2. Under Backup Tasks, select New job to duplicate backup data. 3. If you want to copy existing backup sets to another destination: a. Select Duplicate existing backup sets, and then click OK. b. Select the backup sets you want to copy.
300
4. If you want to duplicate backup sets created when a scheduled backup job runs: a. Select Duplicate backup sets following a job, and then click OK. b. Select the scheduled backup job to be used as the source. 5. On the Properties pane, under Destination, select Device and Media, and complete these options as described in Device and Media Options for Backup Jobs and Templates on page 241. 6. On the Properties pane, under Settings, click General, and complete these options as described in General Options for a Duplicate Job on page 302. 7. On the Properties pane, under Settings, click Advanced, and complete these options as described in Advanced Options for a Duplicate Job on page 303. 8. If you want Backup Exec to notify someone when the backup job completes, on the Properties pane, under Settings, click Notification (see Selecting Recipients for Job Notification on page 492). 9. 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. 10. 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 358).
Backing Up Data
301
General Options for a Duplicate Job

General options for duplicate job
General options for a duplicate job include:

General settings for New Duplicate Job Item Job name Job priority Description 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 choices are: Highest High Medium Low Lowest Backup set description Type a description of the information you are backing up.
302
Duplicating Backed Up Data General settings (continued)for New Duplicate Job (continued) Item Description
Preferred source device Select the device used as the destination device for the original backup job.
Advanced Options for a Duplicate Job

Advanced options for a duplicate job
Advanced options that can be set for a duplicate job include:

Advanced options for duplicate job Item Verify after backup completes Description 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.
Backing Up Data
303
Duplicating Backed Up Data Advanced options for duplicate job (continued) Item Compression type 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.
304
Verifying a Backup
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 the Write checksums to media option is selected as a default backup option, checksums are calculated for each data stream written to tape, and then written in a separate stream immediately following the data stream. If this option is not selected, backup performance may be improved, but there will be no way to verify the integrity of the data on the tape. Performing a verify operation when there are no checksums written for the set only verifies that the set can be read without getting a translation error. If you perform a verify operation and files fail to verify, the media may be bad. Details about files that failed to verify are provided in the job log, which can be viewed from the Job Monitor.
To create a verify job: 1. On the navigation bar, click Job Setup. 2. Under Backup Tasks in the task pane, select New job to verify backup data. 3. Select the media you want to verify. Note The default view is the Resource view, which lists data by the device from which it was backed up. The Media view lists the data that is contained on a piece of media. To switch views, under View by, select the view you want to use. In addition, you can set Backup Exec to display the selections in a graphic format or a text format. To switch the format, select either Graphical or Text from the View format section. 4. On the Properties pane, under Destination, click Device. 5. Select the device that contains the media you want to verify. 6. On the Properties pane, under Settings, click General. 7. Select the appropriate options as follows:
General Verify dialog box Item Job Name Description Type a name that describes the data you are verifying.
Backing Up Data
305
Verifying a Backup General Verify dialog box Job priority Select the priority level for this job. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Your choices are: Highest High Medium Low Lowest
8. If you want Backup Exec to notify someone when the backup job completes, on the Properties pane, under Settings, click Notification (see Selecting Recipients for Job Notification on page 492). 9. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). After verification has completed, you can check the results in the job log. See also: Setting Default Backup Options on page 312 Verify after backup completes on page 303
306
Creating a Test Run Job

The Backup Exec test run option determines if a scheduled backup will complete successfully. When you run a test job, you can monitor the job just as you would a normal backup job, but no data is backed up. During the test run, the tape capacity, credentials, and media are checked. If there is an error, the job will continue to run and the error will appear in the job log. Notification can also be sent to a designated recipient. During a test run job, the following may cause a job to fail:

The logon credentials are incorrect. Insufficient media is available. Media is not in the drive. There is no overwritable media for an overwrite job. There is no appendable media for an append job.
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.
To create a test run of a job: 1. On the navigation bar, click Job Setup. 2. In the Jobs pane, select the job for which you want to create a test run. 3. Under General Tasks, click Test Run. 4. Select General options as described in General Options for Test Run Jobs on page 308. 5. If you want Backup Exec to notify a recipient when the backup job completes, on the Properties pane, under Settings, click Notification (see Selecting Recipients for Job Notification on page 492). 6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). See also: Viewing General Media Properties on page 220 Creating a Manual Backup Job by Configuring Job Properties on page 236 Test Run Results Report on page 528
Backing Up Data
307
General Options for Test Run Jobs

General settings options for test run job
General options for a test run job include:

General settings options for test run job Item Job name Credentials check Description 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.
Media capacity check to Select this check box to test if there is enough available capacity on the complete individual job media to complete the job. Note During the test run job, the number of scheduled jobs in the queue is not checked; therefore, jobs that are scheduled before the test run job may use the media that was available when the test run job was performed. Media check Select this check box to test whether the media is online and overwritable.
308
Creating a Test Run Job General settings options for test run job (continued) Item Description
Method for determining job size Use previous job history, if available Select this option to use past job histories to determine whether there is enough media available to run the scheduled backup job. Checking the previous job history is faster than performing a pre-scan. 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.
Perform Pre-scan
Upon any failure, place the scheduled job on hold Run at priority
Select the priority level for the test job. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Your choices are: Highest High Medium Low Lowest
See also: Viewing General Media Properties on page 220 Creating a Manual Backup Job by Configuring Job Properties on page 236 Test Run Results Report on page 528
Backing Up Data
309
Setting Test Run Default Options
To set test run default options: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Test Run.
Test Run default options
310

Default options for test run jobs Item Check credentials Description 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. Note During the test run job, the number of scheduled jobs in the queue is not checked; therefore, jobs that are scheduled before the test run job may use the media that was available when the test run job was performed. Check media availability 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. 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.
Check media capacity to complete job
Perform Pre-scan
Place the job on hold if Select this option to have the scheduled job placed on hold if any any failure occurs failures are detected during the test run.
4. Click OK.
Backing Up Data
311
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 configure backup options: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Backup.
Default backup options
312
3.
Select the appropriate options as follows:

Backup default options Item Backup method for files Definition Select the default Backup method. FULL - Back Up Files - Reset Archive Bit is the typical selection for this field. For more information about backup methods, see Understanding Backup Methods and Their Advantages on page 340. When the Working Set backup method is selected, use this field to specify the number of days for which to include accessed files.
Files accessed in x days
Backing Up Data
313
Setting Default Backup Options Backup default options (continued) Item Media overwrite protection Definition Select one of the following media overwrite options: Overwrite media. Select this option to place this backup on an overwritable media. Make sure that appropriate media is in the stand-alone drive or drive pool you select in the Device field in this dialog box. The media in the drive is overwritten if the media is scratch or recyclable (its overwrite protection period has expired). If allocated or imported media are in the drive, they may also be overwritten depending on the Media Overwrite Protection Level that is set. For more information, see Media Overwrite Protection Levels on page 190. 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 Options - Set Application Defaults Preferences on page 85). The backup set is appended if an appendable media is available in the selected media set; if not, an overwritable media is used and added to the media set. If an append job fills a media, the job continues on another piece of overwritable media. Depending on your configuration, overwritable media is selected from Scratch media or Recyclable media. For more information, see Media Overwrite Options on page 192. 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 Options - Set Application Defaults Preferences on page 85). The backup set is appended if an appendable media is available in the selected media set; if not, the job is terminated.
314
Setting Default Backup Options Backup default options (continued) Item Compression type Definition Select one of the following compression types: None. Select this option to copy the data to the media in its original form (uncompressed). Note Using some form of data compression can help expedite backups and preserve storage media space. Software. Select this option to use STAC software data compression, which compresses the data before it is sent to the storage device. Hardware [if available, otherwise none]. Select this option to use hardware data compression (if the storage device supports it). If the drive does not feature data compression, the data is backed up uncompressed. Hardware [if available, otherwise software]. Select this option to use hardware data compression (if the storage device supports it). If the drive does not feature hardware data compression, STAC software compression is used. Verify after backup Select this option if you want backups to be verified after they are completed. Verify operations make sure the media can be read once the backup has been completed. Verifying all backups is recommended. Select this option if checksums are to be calculated for each data stream written to tape, and then written in a separate stream immediately following the data stream. If this option is not selected, backup performance may be improved, but there is no way to verify the integrity of the data on the tape; Backup Exec can only verify that the data can be read from the device.
Write checksums to media
Backing Up Data
315
Setting Default Backup Options Backup default options (continued) Item Back up files and directories by following junction points Definition Select this check box to back up the information for the junction points and the files and directories to which they are linked. If this check box is not selected, then only the information for the junction points is backed up; the files and directories to which they are linked are not backed up. Note Since Mounted Drives that do not have a drive letter assigned to them cannot be selected, the files and directories to which they are linked are backed up regardless of whether this option is selected. If this option is selected and the actual files and directories to which the junction points are linked are also included in the backup selections, then the files and directories are backed up twice; once during the full file and directory backup, and again via the junction point. WARNING: If a junction point is linked to a location that encompasses it, then recursion (a situation where data is backed up repeatedly) will occur, resulting in an error and job failure. For example, if c:\junctionpoint is linked to c:\, recursion will occur when attempting to back up c:\junctionpoint, and the backup job will fail. 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. Note This option should not be selected if the device used for secondary storage and backups contains only one drive because Remote Storage and Backup Exec will compete for use of the drive.
316
Setting Default Backup Options Backup default options (continued) Item Use Change Journal if available Definition 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
- Allow incrementals and differentials using modified time, DIFFERENTIAL - Using modified time or INCREMENTAL - Using modified time.
Enable single instance backup for NTFS volumes Select this option if you want Backup Exec to protect Single Instance Store (SIS) volumes. SIS, which is used by Remote Installation Services to save disk space, maintains a single physical copy of all identical files on a specified volume. If SIS finds an identical file on the volume, a copy of the original file is placed in the SIS and a link is made to the actual physical location. By selecting this option, Backup Exec will back up the physical file one time, no matter how many links have been created.
Caution If the backup job does not run to completion, the file data may not be included in the backup set. Rerun the backup until it is successfully completed. If the incremental backup method was used, running the job again will not back up the same files. You must run a full or copy backup to ensure that all files are backed up completely. If the incremental - using modified time backup method was used, running the same backup job to completion will back up the files correctly.
Backing Up Data
317
Setting Default Backup Options Backup default options (continued) Item Definition
Open file backup when Advanced Open File Option is not used 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. Note If multiple files are open, Backup Exec waits the specified time interval for each file; depending on the number of open files, this may significantly increase the backup time. With a lock Select this option to have Backup Exec attempt to open files that are in use. If Backup Exec is able to open a file, the file is locked while it is being backed up to prevent other processes from writing to it. Backing up open files is not as effective as closing applications and allowing the files to be backed up in a consistent state. Select this option to have Backup Exec attempt to open an in use. If Backup Exec is able to open the file, the file is NOT locked while it is being backed up. This allows other applications to write data to the file during the backup operation. WARNING: This option allows files to be backed up that contain inconsistent data and possibly corrupt data. For information about the Advanced Open File Option, see VERITAS Backup Exec for Windows Servers - Advanced Open File Option on page 955.
If closed within x seconds
Without a lock
318
Setting Default Pre/Post Commands

You can set defaults for the commands you want to run before or after all backup and restore jobs. If the default options are not appropriate for a particular job, you can override the default options when you create the job. Conditions that you can set for these commands include:

Run the backup or restore job only if the pre-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 backup or restore 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 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-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 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-job command fails. Additionally, if Backup Exec is configured to check the return codes of the pre- and post-job commands, and the post-job command returns a non-zero code, the job log reports that the post-job command failed. If you also selected to run the job only if the pre-job command is successful, and both the pre-job command and the job ran successfully, Backup Exec will mark the job as failed if the post-job command fails. For example, if the pre-job command runs successfully and shuts down the database and the backup 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 backed up, the pre- and post-commands are run and completed for each server before processing begins on the next selected server.
Backing Up Data
To set pre/post command options: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Pre/Post Commands.
319

Pre-job and Post-job options Item Description
Pre-job and post-job commands Run job only if pre-job command is successful Select this option to run the backup or restore job only if the pre-job command is successful. If the pre-job command fails, the job does not run, and is marked as failed. If it is critical that the job not run if the pre-job 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, it is interpreted by Backup Exec to mean that the pre-job command did not run successfully. The job is not run and the job status is marked as Failed.
320
Setting Default Pre/Post Commands Pre-job and Post-job options (continued) Item Run post-job command only if pre-job command is successful Description Select this option to run the post-job command only if the pre-job command is successful. If it is critical that the post-job command fail if the pre-job 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-job command, it is interpreted by Backup Exec to mean that the pre-job command did not run successfully. The post-job command is not run. If you also select Run job only if pre-job command is successful, and both the pre-job command and the job are successful, but the post-job command returns a non-zero code, the job log reports both the job and the post-job command as failed. Run post-job command even if job fails Select this option if it is critical to run the post-job command regardless if the job is successful or not. If you also select Allow pre- and post job commands to be successful only if completed with a return code of zero and the post-job command returns a non-zero code, the job log reports the post-job command as failed. Allow pre- and post-job 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-job commands to determine if they completed successfully. An exit code of zero returned to the operating system by the preor post-job 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-job commands. If this option is not selected, the success of the pre- and post-job commands is not determined based on the return code. Cancel command if not completed within x minutes Run these commands On this media server Select this option to run the pre- and post-job commands on this media server only. Select the number of minutes Backup Exec should wait before canceling a pre-job or post-job command that did not complete. The default time-out is 30 minutes.
Backing Up Data
321
Setting Default Pre/Post Commands Pre-job and Post-job options (continued) Item On each server backed up Description Select this option to run the pre- and post-job commands one time on each server backed up. The pre- and post-job 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.
4. Click OK. See also: Pre/Post Commands for Backup or Restore Jobs on page 255
322
Specifying Backup Networks

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 media server and the remote computer are located on the specified local network. If both the media server and the remote computer are on the backup network, then the backup operation is performed. If the media server or the remote computer is not on the specified local network, the job fails. However, you can set up Backup Exec to use any available network to back up remote computers that are not connected to the backup network. The following diagram shows an example of a basic backup network configuration.
Example of backup network
IP address: 128.10.0.1 Backup Exec media server
backup network network ID: 128.10.0.0 subnet mask: 255.255.0.0 router A IP address: 128.10.0.2 IP address: 128.20.0.2 IP address: 128.10.0.3 IP address: 128.20.0.3 router B
Backing Up Data
database server running Remote Agent 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
323
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. See also: Using Backup Exec with Firewalls on page 331 Browsing Systems Through a Firewall on page 332
324
Specifying the Default Backup Network

You can specify a network to be used as the default for every Backup Exec job. Before configuring the feature, test for network connectivity between the media server and the remote computers. Note The remote computers that you want to back up must have the most current version of Backup Exec Remote Agent installed.
To set the default backup network: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Network.
Network options dialog box
Backing Up Data
325

Network Options - Set Application Defaults Item Enable selection of default shares Enable selection of user selections Default Network 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. The list includes all available network interface cards on the media server. Displays the IP address of the network interface card you selected for the backup network. Displays the 32-bit number that determines the subnet to which the network interface card belongs. Displays the base network that Backup Exec calculated based on the IP address and the subnet mask of the network interface card you selected. This is the network that will be used to perform remote backups and restores. For Windows 2000 and later operating systems, this field displays the Media Access Control (MAC) address for the network identification card you selected. For Windows NT 4 and earlier operating systems, this field lists the service entry name. 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 Description Select this option to enable selection of Windows default shares.
Select this option to enable selection of Windows user shares.
IP address
Subnet mask
Network ID
Physical address
Use any available network route for remote agents not bound to the above Network ID
326
Specifying Backup Networks Network Options - Set Application Defaults (continued) Item Enable agents using TCP/IP protocol Description Select this option to use the TCP/IP network protocol to communicate with other devices on the network. If you select this option, make sure that all agent workstations are configured to advertise their IP addresses directly to the media server. To set up this protocol, refer to your Windows documentation. Enable agents using NetWare IPX/SPX protocol Select this option to use the IPX/SPX network protocol to communicate with other devices on the network. If you are using Backup Exec Agents that communicate using SPX, you should ensure that you are using a consistent IPX frame type on your network. If you do not, and Backup Exec is using a different IPX frame type than the workstations running the Backup Exec Agent software, all SPX packets must be routed through a server that can translate the packets. This generates excessive network traffic and, if the router does not properly handle large SPX packets, some packets may be lost. One symptom of this problem is a backup that times-out with a Device not responding error message. Please note that the Auto-Detect frame type will not work if there are any combinations of 802.2 and 802.3 on the network. To set up this protocol, refer to your Windows documentation. Enable Media Server TCP Select this option if you want to allow the media server to use a dynamic port range range of ports for communications, and then enter the port range. If the first port 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. VERITAS recommends using a range of 50 allocated ports for the media server if using Backup Exec with a firewall (Using Backup Exec with Firewalls on page 331).
Backing Up Data
327
Specifying Backup Networks Network Options - Set Application Defaults (continued) Item Enable Remote Agent TCP dynamic port range Description 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 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. VERITAS recommends using a range of 25 allocated ports for the remote systems if using Backup Exec with a firewall (Using Backup Exec with Firewalls on page 331).
See also: Changing the Backup Network for a Job on page 328 Specifying the Restore Network on page 444
Changing the Backup Network 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.
To change the backup network for a backup job: 1. On the navigation bar, click Backup. 2. Set up the backup job as usual by selecting data and setting General and Advanced options (see Creating a Manual Backup Job by Configuring Job Properties on page 236).
328
3. On the Properties pane, under Settings, click Network.

Network options for backup job

Network Backup Job Properties Item Network Interface Description 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. Displays the IP address of the network you selected as the backup network. Displays the 32-bit number that determines the subnet to which the network interface card belongs. Displays the network identification or subnet address that Backup Exec calculated based on the network you selected as the backup network.
Backing Up Data
IP address
Subnet mask
Network ID
329
Specifying Backup Networks Network Backup Job Properties (continued) Item Physical address Description For Windows 2000 and later operating systems, this field displays the Media Access Control (MAC) address for the network card you selected. For Windows NT 4 and earlier operating systems, this field lists the service entry name. 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.
5. If you want Backup Exec to notify someone when the backup job completes, on the Properties pane, under Settings, click Notification (see Selecting Recipients for Job Notification on page 492). 6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). See also: Specifying Backup Networks on page 323 Specifying the Default Backup Network on page 325 Creating a Manual Backup Job by Configuring Job Properties on page 236
330
Using Backup Exec with Firewalls

In firewall environments, Backup Exec provides the following advantages:

The number of ports used for receiving incoming 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. VERITAS 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. The firewall must have a static Network Address Translation (NAT) configuration for these two-way communications to work. When a media server makes a connection with a remote system, the initial connection will be initiated on 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 as specified in the Enable media server TCP dynamic port range. Additional connections from the media server to the Remote Agent will be initiated on an available port selected in the Enable remote agent TCP dynamic port range option, and the media server side of these connections will be bound to an available port as specified in the Enable media server TCP dynamic port range option. Communication between the media server and the Remote Agent for Windows Servers will usually require 2 ports on the media server side and up to 2 ports on the remote agent side per 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:
Backing Up Data
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, VERITAS recommends using a range of 50 allocated ports for the media server (see Enable Media Server TCP dynamic port range on page 327), and 25 allocated ports for the remote systems (see Enable Remote Agent TCP dynamic port range on page 328). For optimum reliability, port ranges should not overlap. Note The number of dynamic ports used by the media server and 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 defaults dialog box. Because the backup communications between the media server and the remote agent for Windows servers will usually require multiple two-way connections on different port numbers, you must configure your firewall to support this type of communications. Note Firewalls using a many to one Network Address Translation (NAT), or Circuit-level Gateways, may not accept incoming connections destined for a private address behind the firewall. As a result, firewalls utilizing this technology may not be compatible with Backup Exec for Windows Servers firewall backup methods. You can make NAT work with port forwarding or putting Backup Exec on a DMZ host. Please refer to your firewall documentation for more information on these and other configurations.
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 view devices in firewall environments: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Network.
332
Protecting Windows.NET Systems
3. Verify that a dynamic range of ports has been set for the media server and remote agent and that the firewall is configured to pass these port ranges. 4. Click OK. 5. On the navigation bar, click Backup. 6. On the backup selections pane, expand Remote Selections. 7. Right-click User-defined Selection. 8. From the shortcut menu, click User-defined Selections. 9. In UNC Name, after \\, type the name or IP address of the remote system, and then click Add. 10. Click Close. Under User-defined Selections, you can now select the data to be protected, providing a valid user name and password if prompted, and create a backup job to protect this data by following the procedures described in Creating a Manual Backup Job by Configuring Job Properties on page 236.
Protecting Windows.NET Systems

Windows.NET systems use Shadow Copy technology, which provides a copy of a volume when a backup is initiated. With Shadow Copy, a system can be backed up while applications and services are running, eliminating the need to shut down applications to ensure a successful volume backup. Microsofts Volume Snapshot Services (VSS) enables third party vendors to create snapshot plug-ins, or writers, for use with this shadow copy technology. VSS is always used for Shadow Copy Components. Writers, which are applications that store persistent information on disk and participate in shadow copy technology, appear as Shadow Copy Components. Shadow Copy Components are listed as resources in the backup and restore selections. When expanded, the Shadow Copy Components include Service State, which corresponds to application services that have writers. These services can be operating system related, such as Windows Management Instrumentation, or they can be services for third party applications, such as Microsoft SQL. Some writers, such as Microsoft SQL writers, will not appear as resources unless you have installed the Backup Exec Agents for the application or database. Some writers are greyed out in the selection list because VERITAS has not tested Backup Execs compatibility with those writers. The writers that are greyed out will not be backed up.
Backing Up Data
Backing Up Utility Partitions
To protect your Windows.NET systems, you must select all shadow copy components, your system state, and system drive for backup. You can only perform a full backup on the shadow copy components and system state. For more information about shadow copy technology, refer to your Microsoft documentation. See also: Snapshot Support on page 956
Backing Up Utility Partitions

Backup Exec allows backing up and restoring of utility partitions. Utility partitions are usually small partitions installed on the disk by OEM vendors like Dell, Compaq, Hewlett-Packard, and IBM. These utility partitions contain system diagnostic and configuration utilities. If utility partitions are on a system, the Utility Partition node appears as a resource in backup selections.
Backing up Utility Partitions
You must have Administrator rights to browse and backup utility partitions. If there are no utility partitions on the system, this resource is unavailable for backup. You can only perform a full backup of utility partitions. You can select individual utility partition resources, which appear as Utility Partition On Disk disk_number (such as Utility Partition On Disk 0) when the Utility Partition node is expanded. VERITAS recommends backing up utility partitions when a full system backup is performed, such as during disaster recovery preparation. See also: Restoring Utility Partitions on page 423 Disaster Preparation and Recovery on page 531
334
Backing Up NetWare Network Volumes
Backing Up NetWare Network Volumes

In order to see NetWare volumes in your backup selections pane, you must have the Client (or Gateway) Services for NetWare service or NetWare Client 32 enabled on the media server. In addition, you may need to use a fully distinguished logon for some NetWare servers you are working with. If you want to back up NetWare Network Volumes, expand Novell Storage Management Services to select files. When you use the Novell Storage Management Services node, the backed up data includes standard file data and additional special data such as Access Control Lists, disk quotas, Macintosh-specific data, partition information, and security data. This additional information is needed to fully restore NetWare.
Novell Storage Management Services
Backing Up Data
Note If you use Backup Exec on an IntraNetWare client, there is no NDS node when browsing for a server using Network Neighborhood. While looking at the backup selections pane, you may notice a selection called NetWare or Compatible Networks. Although you can select NetWare files to back up from this node, VERITAS does not recommend that you use it. When you select files from the NetWare or Compatible Networks node, only the standard files are backed up. Special files, such as security, bindery, and ACL, are not included in the backups.
335
About Backup Strategies
In addition, VERITAS recommends that you use the Backup Exec Remote Agent for NetWare. Because the Remote Agent for NetWare 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 all data and special files on resources for a remote NetWare server for backup until a Remote Agent has been installed. See also: About Backing Up NetWare Servers on page 1228 Default Settings for the Remote Agent for NetWare on page 1235

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. See also: Media Rotation Strategies on page 214 Using Backup Job Templates on page 276
336
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.
Backing Up Data
337
How long does the data need to be stored? The amount of time the data needs to be stored is directly related to the media rotation scheme you use. For example, if you use one media and back up every day, your backups will never be more than a day old. Since storage media is relatively inexpensive when compared to the value of your data, it is a good idea to periodically back up your system on media not used in the media rotation scheme and store it permanently. Some administrators may choose to do this every week, while others may choose to store only one permanent backup per month. The threat of viruses is an issue also. Some viruses take effect immediately, while others may take days or weeks to cause noticeable damage. Because of this, you should have at least the following backups available to restore at any time:

3 daily backups (for example, Monday, Tuesday, Wednesday). A one-week-old full backup. A one-month-old full backup.
Having these backups available should allow you to restore your system prior to when it became infected. Which devices am I backing up? Since Backup Exec can back up servers, workstations, and agents, you should consider which devices you want to protect. You will need to coordinate times that are suitable to back up different devices. 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 devices or a job for each device. Here are some of the advantages and disadvantages of each method.
One job per device: Advantages: If a job fails, you know immediately which device was not backed up. If a device is turned off or moved, backups of other devices are not affected. When devices are added to the network you can simply set up new jobs for each device.
Disadvantages: You have more jobs to keep track of (for example, reviewing job histories, and so forth).
338
Multiple devices per job: Advantages: 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.
Disadvantages: If any of the devices in the job are not available during the backup, the job results in an abnormal completion status.
Backing Up Data
339
Understanding Backup Methods and Their Advantages

Before you can develop your media rotation strategy, you will need to decide whether you want to perform only full backups or use a strategy that includes Full backups and one of the modified backup methods (differential, incremental or working set backups). The backup methods used by Backup Exec are:

Full Differential Incremental Copy Daily Working set Archive
There are advantages and disadvantages to each backup method.
Full Backups
Full backups include all of the data on a volume and use the full backup method (so Backup Exec detects the device as having been backed up). Backup Exec allows you to select to use either archive bit or modified time to determine if a file has been backed up. The advantages and disadvantages described in this section pertain to either type of full backup.
Advantages 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.
Disadvantages 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).
340
Note You will need to perform a full backup of your server (including the Windows NT Registry) to establish a baseline for disaster recovery. See also: Understanding the Archive Bit and Backup Methods on page 344 Understanding Modified Time and Backup Methods on page 345
Differential Backups
Differential backups include backing up all files that have changed since the last full 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 - Backs Up Files - Reset Archive Bit and want to run differential backups, you must use the DIFFERENTIAL - Changed Files method. If you select to use the FULL - Backs Up Files - Allows incrementals and differentials using modified time, you must use the DIFFERENTIAL - Using modified time method. The advantages and disadvantages described in this section pertain to either type of differential backup.
Advantages 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.
Disadvantage Redundant backups - All of the files created or modified since the last incremental backup are included; thus creating redundant backups.
Backing Up Data
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.
341
Incremental Backups
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 - Backs Up Files - Reset Archive Bit and want to run incremental backups, you must use the INCREMENTAL - Changed Files method. If you select to use the FULL Backs Up Files - Allows incrementals and differentials using modified time, you must use the INCREMENTAL - Using modified time method. The advantages and disadvantages described in this section pertain to either type of differential backup.
Advantages 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.
Disadvantage 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.
Copy Backups
Copy backups 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.
Daily Backups
Daily Backups may be performed in addition to the media rotation scheme selected. The Daily Backup method backs up all files with todays date (created or changed today). The Daily Backup method does not affect the files backup status because the archive bit is not reset.
342
Working set Backups

The working set backup option allows you to back up data that has been created and modified since the last full or incremental backup, and to specify to include data that has been accessed in the last x days. This option is similar to a differential backup, in which files that have been created or changed since the volumes 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.
Advantages: 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.
Disadvantages: Along with all files accessed in the specified time, all of the files created or modified since the last full or incremental backup are included on each media, thus creating redundant working set backups.
Backing Up Data
This option 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.
343
Archive Backups
The archive backup option 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. 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.
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 backup methods FULL - Back Up Files - Reset Archive Bit, DIFFERENTIAL Changed Files, and INCREMENTAL - Changed Files - Reset Archive Bit, can affect the archive bit. Whenever a file has been backed up using either the FULL - Back Up Files - 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: Fred wants to implement a backup strategy for the office fileserver. Fred knows that all backup strategies begin with a full backup (backup of an entire device using the full backup method), so he creates a Selection List (see Creating Selection Lists on page 267) for his server and submits the job to run at the end of the day on Friday.
344
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 - Allow incrementals and differentials 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. 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.
Backing Up Data
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 use 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. See also: Using Selection Lists on page 267
345
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.
346
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:

Configure logon accounts Schedule jobs Monitor Jobs Configure error-handling rules Configure Database Maintenance Connect to ExecView
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 easily 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.
347
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. See also: Creating a Backup Exec Logon Account on page 350
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 before 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.
348
Note For more information on using Backup Exec logon accounts with Exchange mailbox and SQL backups, see Using Backup Exec Logon Accounts for SQL 2000 Resources on page 978 and Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069.
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.
See also: Changing Your Default Backup Exec Logon Account on page 355
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 or you can delete it. However, if you delete the SLA, the jobs in which it is used may fail. If the SLA is deleted, you can re-create it using the Logon Account Management dialog box. The SLA is used for the following tasks and jobs:

Jobs migrated from a previous version of Backup Exec Windows Explorer interface jobs One-button backup jobs (if a default Backup Exec logon account does not exist for the user running the job) Duplicate backup data jobs
Chapter 7, Administrating Backup Exec
349
Command Line Applet Backup Exec R/3 Agent
See also: Creating a New Backup Exec System Logon Account on page 355
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 can not be modified.
To launch the Logon Account Wizard:
On the Tools menu, point to Wizards, and then click Logon Account Wizard. The wizard will guide you through the process of creating a Backup Exec logon account.
350
To create a new Backup Exec logon account using the Logon Account Management dialog: 1. On the Network menu, click Logon Accounts.
Logon Account Management dialog box
2. Click New. 3. Enter the appropriate options as follows:

Add Logon Credentials dialog box Item User name Description Enter 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. Enter 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-enter the password for confirmation. The password must match the password you typed in the Password field.
Password
Confirm password
351
Configuring Logon Accounts Add Logon Credentials dialog box (continued) Item Description Description Enter the unique name for the Backup Exec logon account. The user name is automatically added if you do not enter information into the field. Enter any comments to describe how the Backup Exec logon account will be used. Select this check box to enable the Backup Exec logon account to be used only by the owner of the logon account and those who know the password. If this is not selected, the Backup Exec logon account will be a common account. Common accounts are shared accounts that can be accessed by all users. Select this check box to make this your default Backup Exec logon account used to browse, make selections, or restore data on your local and remote resources.
Notes
This is a restricted logon account
This is my default logon account
4. Click OK to create the Backup Exec logon account. See also: Deleting a Backup Exec Logon Account on page 354 Replacing a Backup Exec Logon Account on page 353
Editing a Backup Exec Logon Account

When you edit a Backup Exec logon account, the changes will automatically be 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) Description Password User name Notes
352
To edit a Backup Exec logon account: 1. On the Network menu, click Logon Accounts. The Logon Account Management dialog box appears. 2. Select the Backup Exec logon account you want to change, and then click Edit. If you are not logged on to Backup Exec with the same user name as the Backup Exec logon account owner, you must provide the password before you can edit the account. 3. Modify the Backup Exec logon account properties as needed. 4. To change the password for the Backup Exec logon account: a. Click Change password. b. In Password, type a new password. c. In Confirm, re-type the password. d. Click OK. 5. Click OK.
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 with another Backup Exec logon account: 1. On the Network menu, click Logon Accounts. The Logon Account Management dialog box appears. 2. Select the Backup Exec logon account you want to replace, and then click Replace. The Replace Logon Account dialog box appears.
353
3. Select the Backup Exec logon account with which you want to replace the selected Backup Exec logon account. If the Backup Exec logon account is restricted and you are not logged on to Backup Exec with the same user name of the Backup Exec logon account owner, you must provide the password before you can edit the account. 4. Click OK.
Deleting a Backup Exec Logon Account

You cannot delete a Backup Exec logon account when it is:

Being referenced by a job. Owned by a user who is logged on to the media server. Set as the default Backup Exec logon account of a user who is logged on to the media server.
You can delete a Backup Exec logon account when the owner is logged off and all users who have it set as their default logon account are logged off.
To delete a Backup Exec logon account: 1. On the Network menu, click Logon Accounts. The Logon Account Management dialog box appears. 2. Select the Backup Exec logon account you want to delete, and then click Delete. 3. Click Yes to confirm the deletion. The Backup Exec logon account is removed from the Backup Exec logon account list.
354
Changing Your Default Backup Exec Logon Account

You can change your default Backup Exec logon account that enables you to browse, make selections, or restore data. To change your default Backup Exec logon account, you must edit the properties for the Backup Exec logon account that you want to use as the new default Backup Exec logon account.
To change your default Backup Exec logon account: 1. On the Network menu, click Logon Accounts. The Logon Account Management dialog box appears. 2. Select the Backup Exec logon account you want to use as your default Backup Exec logon account, and then click Edit. 3. Select This is my default logon account check box. 4. Click OK.
Creating a New Backup Exec System Logon Account

The Backup Exec System Logon Account enables you to perform several operations, such as one-button backup, copy jobs, and Windows Explorer interface jobs. It is also used with Backup Exec R/3 Agent and Command Line Applet. If you delete the Backup Exec System Logon Account, you should create a new one that enables you to perform the specified operations and use the agent and applet.
To create a new Backup Exec System Logon Account: 1. On the Network menu, click Logon Accounts. The Logon Account Management dialog box appears. 2. Click System Account. The Edit Logon Credentials dialog box appears.
355
3. Enter the appropriate options as follows:

Edit Logon Credentials dialog box Item User name Description Enter 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. Enables you to enter 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. Enter any comments to describe how the Backup Exec logon account will be used. Select this check box to enable the Backup Exec logon account to be used only by the owner of the Backup Exec logon account and those who know the password. If this is not selected, the Backup Exec logon account will be a common account. Common accounts are shared accounts that can be accessed by all users. Select this check box to make this your default account used to browse, make selections, or restore data on your local and remote resources.
Change password
Notes
This is a restricted logon account
This is my default logon account
4. Click OK to create the system logon account.
Viewing and Clearing the Audit Log

You can view the audit log to determine when changes were made to Backup Exec logon accounts. The audit log displays the date and time the change was made, the user that made the change, and Backup Exec logon account that was changed. The audit log entries can be viewed, but not edited; however, you can clear all the entries in the log.
To view or clear the audit log: 1. On the Network menu, click Logon Accounts. The Logon Account Management dialog box appears.
356
2. Click Audit Log.
The Logon Account Audit Log dialog box provides the following information:
Alerts Audit Log Item Date/Time Description The date and time the change was made to the Backup Exec logon account. The user ID that made the change to the Backup Exec logon account. The name of the Backup Exec logon account to which the change was made.
User Name Message
3. Click Refresh to update the audit log with new entries. 4. Click Clear to remove all entries from the audit log. 5. Click Close.
357
Scheduling Jobs
Scheduling Jobs
The schedule option enables you to configure the time and the frequency you want to run jobs. You can configure a schedule for all types of jobs such as backup, restore, inventory, new catalog, etc. During the job setup, you can choose to run jobs immediately, run once on a specific day and time, or run according to a schedule.
To configure a schedule for a job: 1. Determine the type of job you want to schedule. The job dialog box appears that enables you to select properties for the job. 2. On the Properties pane, under Frequency, click Schedule.
Schedule Time and Frequency dialog box
358
Scheduling Jobs
3. Select one of the following schedule options: Click Run now to run the job immediately. Click 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. Click Run according to schedule to configure a schedule for a recurring job, and then click Edit Schedule Details to configure the schedule. For more information, see Editing the Job Schedule on page 360.
4. Click View Schedule Summary to verify your schedule. The Summary dialog box displays the Effective Date, Time Window, Restart Interval, and a calendar. The calendar displays a six month period with the selected scheduled run dates in bold. 5. Click 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. 6. Click Enable automatic cancellation, and then type the number of hours or minutes in the Cancel job if not completed within option. This option enables you 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 is queued, not when the job begins. 7. You can start the job after configuring the schedule or select other options from the Properties pane. Note If you are using Backup Exec for Web Administration Console (BEWAC), click Next when you are ready to submit the job to the job queue. Click Finish to run the job after you view the job summary. If you are not satisfied with the settings you selected, click Back. However, you must reset all of the settings. BEWAC does not save the settings when you click Back. See also: Backing Up Data on page 233 Monitoring Jobs on page 365 Configuring Default Schedule Options on page 363
Configuring Holiday Scheduling for Jobs on page 364
359
Scheduling Jobs
Editing the Job Schedule

You can select the time and frequency you want to run a recurring job. When you select the Run according to schedule option, and then click Edit Schedule Details, you must configure the schedule for the recurring job.
Schedule options
There are two types of options for configuring a schedule: General Options and Run Day Options. General options enable you to determine the date the schedule goes into effect, the time the job can begin, and the time it can restart during the run day, and the date when the schedule goes into effect. The selected options apply each day the job is scheduled to run. Run day options enable you to select the days on which a job can run. Run days consist of specific dates, a recurring pattern of days, or both. You can also exclude specific dates from a schedule.
360
Scheduling Jobs
To edit schedule details for a job: 1. Under General Options or Run Day Options in the tree pane, select the appropriate options as follows:
Schedule Options Item General Options Effective Date Select this option to specify a date when the schedule begins. On the right pane, select the Make the schedule go into effect check box, and then enter the date. Time Window Select this option to specify the time window on any scheduled run day during which the job can begin. On the right pane, select both the earliest and the latest time the job can start. A job can run any time between 11:00:00PM and 10:59:59 PM. The time window does not extend beyond 24 hours, or more specifically, beyond 23 hours, 59 minutes, and 59 seconds. For example, you cannot set a time window starting at 3:00 AM and ending at 5:00 AM the following day. Restart Time Interval Select this option to specify a time period during which the job can be restarted on the run day. On the right pane, select the Restart task every check box, and then enter the repeat interval in hours, minutes, and second. Run Day Options Week Days Select this option to schedule the job for specific days of the week, weeks of each month, or days on specific weeks of the month. On the right pane, select a check box to specify the day that the job is scheduled to run. You can click Select All to select all the days, and then click specific days to clear them. To select an entire column or row, click the heading. Day Interval Select this option to schedule a task to run every selected number of days starting from a particular date. By default, the date from which the interval is calculated is the current date. On the right pane, select the Every x days check box, and enter the number of days for the interval. To change the calculated date, in the calculated from option, enter a new date. Description
361
Scheduling Jobs Schedule Options (continued) Item Days of the Month Description Select this option to schedule a task to run on specific days of each month. On the right pane, select the day or days you want the task to run. You can also select Last to schedule a task to run on the last day of the month, regardless of the actual date the month ends. Specific Dates Select this option to schedule specific dates for a task. On the right pane, select the dates you want from the calendar, and then click << to move that date to the Include list. To delete a date from the Include list, select the date and click Delete. Exclude Dates Select this option to exclude specific dates, such as holidays, from a run schedule. On the right pane, select the dates you want to exclude from the calendar, and then click << to move that date to the Exclude list. To delete a date from the Exclude list, select the date and click Delete. Summary Enables you to verify your schedule. The dialog box includes the Effective Date, Time Window, Restart Interval, and a calendar. The calendar displays a six month period with the selected scheduled run dates in bold.
2. Click OK to return to the Schedule dialog box. 3. You can start the job after editing the schedule or select other options from the Properties pane. See also: Configuring Holiday Scheduling for Jobs on page 364
362
Scheduling Jobs
Configuring Default Schedule Options

You can configure default scheduling parameters for all new jobs 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 for all new jobs that run according to a schedule: 1. On the Tools menu, click Options. The Options - Set Application Defaults dialog box appears. 2. On the Properties pane, under Job Defaults, click Schedule. 3. Click Edit Schedule Details and then select the appropriate options. For more information, see Schedule Options on page 361. 4. Click OK to return to the Schedule dialog box. 5. Click View Schedule Summary to verify your schedule. The Summary dialog box displays the Effective Date, Time Window, Restart Interval, and a calendar. The calendar displays a six month period with the selected scheduled run dates in bold. 6. Click Enable automatic cancellation, and then type the number of hours or minutes in the Cancel job if not completed within option. This option enables you 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 when the job is scheduled to begin. 7. Click OK to save the options or select other options from the Properties pane. See also: Backup Exec Defaults on page 84
363
Scheduling Jobs
Configuring Holiday Scheduling for Jobs

You can edit the job properties to prevent a job from running on holidays.
To configure holiday scheduling for an existing job: 1. On the navigation bar, click Job Setup. 2. On the Jobs pane, select the job for which you want to configure holiday scheduling. 3. Under General Tasks in the task pane, click Properties. The Properties dialog box for the job appears. 4. On the Properties pane, under Frequency, click Schedule. 5. Click Edit Schedule Details to edit the schedule. 6. Under Run Day Options in the tree pane, click Exclude Dates. 7. On the calendar, click the date of the holiday you want to exclude, and then click << to move the date to the Exclude list. 8. Click OK to return to the Schedule dialog box. The job will resume on the next scheduled day. 9. You can start the job after configuring the schedule or select other options from the Properties pane.
364
Monitoring Jobs
Monitoring Jobs
Backup Execs Job Monitor enables you to monitor and perform tasks on active, scheduled, or completed jobs that have been submitted for processing. The Job Monitor has two views for jobs: Jobs list and Job Calendar. You can select filters to limit the type of jobs you want to appear in each view. The Jobs list view displays active and scheduled jobs in the Current Jobs pane and successful, completed, failed, and canceled jobs in the Job History pane. The Job Calendar view displays scheduled, active, and completed jobs in either a day, week, or monthly view.
Viewing and Filtering Jobs in the Job List View

The Jobs list view displays active, scheduled and job history jobs in the Current Jobs and Job History panes. You can select filters to limit the jobs that appear in each pane.
To view jobs in the Jobs list view:
On the navigation bar, click Job Monitor and then under Views in the task pane, click Jobs list.
365
Monitoring Jobs Jobs list view
The information that appears for each job includes the following: State Job Name Device Name Job Type Job Status Priority Percent Complete Start Time Elapsed Time Byte Count
366
Monitoring Jobs
To set View Filters for Current Jobs and Job History: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list. 3. Under Current Job View Filters or Job History View Filters, select or clear the appropriate filters as follows:
Jobs List View Filters Item Description
Current Job View Filters Show active jobs Show scheduled jobs Job History View Filters Show successful jobs Show completed jobs with exceptions Show failed jobs Lists all jobs that completed without errors. Lists jobs that completed, but may contain one or more minor errors. Lists jobs currently processing or in the job queue. Lists the next occurrence for a job.
Lists jobs that were processed, but one or more significant errors occurred. Lists jobs that were terminated as the operation was running. Lists all the jobs that were processed in the last 24 hours. Lists all the jobs that were processed in the last 7 days. Lists all jobs that were processed.
Show canceled jobs Show last 24 hours Show last 7 days Show all
See also: Viewing and Changing Active Job Status on page 370 Viewing and Modifying Scheduled Jobs on page 374 Viewing Completed Jobs on page 378
367
Monitoring Jobs
Viewing and Filtering Jobs in the Calendar View

The Job Calendar displays active, scheduled and completed jobs in a day, week, or month view, sorted by the start time. You can also select filters to limit the jobs that appear in each view.
To view jobs in the Calendar view: 1. On the navigation bar, click Job Monitor and then under Views in the task pane, click Calendar. Note Icons at the top of the Job Calendar enable you to select calendar views, navigation, and display filters without using the task pane.
Calendar view
368
Monitoring Jobs
2. Under Calendar Views, select the appropriate view for the jobs as follows:
Calendar Views Item Day Description Lists all the jobs and information about each job for the selected day. You can view jobs for a different day by selecting a day from the calendars that appear. Click the arrows at the top of the calendars to view the previous or subsequent months. Lists all the jobs for the selected week. For recurring jobs, only the next 24 occurrences for the job are listed for a day. You can view previous or subsequent weeks using the scroll bar. Lists all the jobs for the selected month. You can view previous or subsequent weeks using the scroll bar.
Week
Month
3. If the current day is not selected for a calendar view, under Navigation, click Go To Today. The current day appears in the view.
To set View Filters and Display Filters for the Job Calendar: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Calendar. 3. Under View Filters or Display Filters, select or clear the appropriate filters as follows:
Job Calendar View Filters Item View Filters Show active jobs Show scheduled jobs Show scheduled job recurrences Show successful jobs Lists jobs currently processing or in the job queue. Lists the next occurrence for a job. Lists all occurrences of a recurring job. If the Show scheduled jobs filter is clear, this filter cannot be selected. Lists all jobs that completed without errors. Description
369
Monitoring Jobs Job Calendar View Filters (continued) Item Show completed jobs with exceptions Show failed jobs Description Lists jobs that completed, but may contain one or more minor errors.
Lists jobs that were processed, but one or more significant errors occurred. Lists jobs that were terminated as the operation was running.
Show canceled jobs Display Filters Show job state icon Show job time
Displays the job status icon for the jobs. Displays the time jobs are scheduled to run.
See also: Viewing and Changing Active Job Status on page 370 Viewing and Modifying Scheduled Jobs on page 374 Viewing Completed Jobs on page 378
Viewing and Changing Active Job Status

You can view properties and change the status of active jobs that are submitted for processing in the Jobs list or Calendar view in the Job Monitor. If you select the Calendar view and the job is not displayed, click the arrow that appears above the listed jobs to display all the jobs for the selected day.
To view active job properties: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar.
370
Monitoring Jobs
3. Select the active job you want to view from the Current Jobs pane or the Job Calendar, and then under General Tasks in the task pane, click Properties. 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 being processed. For more information on the job history, see Viewing Completed Jobs on page 378. The Job Activity tab provides the following information:
Job Activity dialog box Item Job Name Job log Description The job name entered during job configuration. The filename of the job log. The job log cannot be viewed until the job has completed and is located in Program Files\VERITAS\Backup Exec\NT\Data. The status of the operation. Possible statuses for an active job include: Running. The operation is underway. Queued. The job has been initiated, but Backup Exec is actively looking for a suitable drive or media, waiting for the Open File Option to initialize, or waiting for a pre- or post-job command to complete. Cancel Pending. The job has been canceled, but Backup Exec cannot process the request immediately. This status is displayed until the job is actually canceled. The job is then displayed in Job History with a status of Canceled. Loading Media. The media is being loaded and positioned on the target device, or the job is waiting for the Open File Option to initialize. Pre-processing. Backup Exec is calculating the amount of data that will be backed up. Media Request. The job requires additional media because the media is full or there is no available media in the device. Device Paused. The device that the job was sent to is paused. Server Paused. The Backup Exec server is paused.
Status
Operation
The type of operation currently in progress (Archive, Backup, Catalog, Restore, Verify, Backup Scan and etc.). The media server processing the job. 371
Server name Chapter 7, Administrating Backup Exec
Monitoring Jobs Job Activity dialog box (continued) Item Device name Source Description The name of the storage device processing the job. The media or share being processed. The icon field to the left of the field name displays either: A disk drive icon when a backup or archive operation is running, or A tape drive icon when a restore or verify operation is running. Destination Where the data is being written. The icon field to the left of the field name displays either: A tape device icon when a backup operation is running, or A disk drive icon when a restore operation is running. Current Directory Name of the current directory being processed. The icon field to the left of the field displays either: A folder if the active job is a backup or restore operation No icon, if the active job is not a backup or restore operation, but a job such as an Erase or Format operation. Current File Name of the current file being processed. The icon field to the left of the field name displays either: A page, if the active job is a backup or restore operation No icon, if the active job is not a backup or restore operation, but a job such as an Erase or Format operation. Statistics Directories Files Skipped Files Corrupt Files Files in use Rate Bytes 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. Amount of data backed up per minute. Number of bytes processed.
372
Monitoring Jobs Job Activity dialog box (continued) Item Start Time Elapsed Time Percent complete Description 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, select Display progress indicators for backup jobs in Preferences in the Tools - Options menu. The total number of bytes for the backup job estimated during a prescan. To display this option, select Display progress indicators for backup jobs in Preferences in the Tools - Options menu. The estimated time it will take for the job to complete. To display this option, select Display progress indicators for backup jobs in Preferences in the Tools - Options menu. Cancels 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. Prints the Job Activity information. You must have a printer attached to your system and configured in order to print the report.
Estimated total bytes
Estimated time remaining
Cancel Job
Print
To cancel an active job: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar. 3. Select the active job from the Current Jobs pane or the Job Calendar, and then under Active Job Tasks in the task pane, click Cancel. Confirm the cancellation of the job. If the job is scheduled, it will run again at the next scheduled time. You can select multiple jobs in the Jobs 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 Cancel on more than one job at a time, as long as the jobs are of similar type.
373
Monitoring Jobs
To place all scheduled occurrences of an active job on hold: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar. 3. Select the active job from the Current Jobs pane or the Job Calendar, and then under Active Job Tasks in the task pane, click Hold Schedule. The active job continues and all scheduled occurrences of the job are placed on hold. To remove the hold on future jobs, click Hold Schedule again. You can select multiple jobs in the Jobs 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 Hold Schedule on more than one job at a time, as long as the jobs are of similar type. See also: Viewing Completed Jobs on page 378
Viewing and Modifying Scheduled Jobs

You can modify scheduled jobs submitted for processing using the Jobs list or Calendar view in the Job Monitor. The Calendar view also enables you to schedule a new job. The Jobs list view displays a single occurrence of a scheduled job in the Current Jobs pane. The Calendar view can display a single occurrence or all occurrences of a scheduled job depending on the View Filters selected. If you select the Calendar view and the job is not displayed, click the arrow that appears above the listed jobs to display all the jobs for the selected day. You can select multiple jobs in the Jobs 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 Test Run or Delete on more than one job at a time, as long as the jobs are of similar type.
Running a Scheduled Job Immediately

You can run a scheduled job immediately and the job will also run on the next scheduled occurrence. 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar.
374
Monitoring Jobs
3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then under Scheduled Job Tasks in the task pane, click Run now. The scheduled job is submitted to the job queue for processing.
Placing a Scheduled Job on Hold

You can place a scheduled job on hold to prevent the job from running. The scheduled job will not run until you change the jobs hold status. 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar. 3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then under Scheduled Job Tasks in the task pane, click Hold Schedule. The scheduled job is placed on hold. To remove the hold and run the job according to the schedule, click Hold Schedule again. You can select multiple jobs in the Jobs 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 Hold Schedule on more than one job at a time, as long as the jobs are of similar type.
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. 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar.
375
Monitoring Jobs
3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then under Scheduled Job Tasks in the task pane, click the priority you want to select for the job. Priorities include: Highest priority High priority Medium priority Low priority Lowest priority
The priority is changed for all occurrences of the scheduled job. You can select multiple jobs in the Jobs 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 setting priorities on more than one job at a time, as long as the jobs are of similar type.
Running a Test Job for a Scheduled Job

The test run option determines if a scheduled backup will complete successfully. During the test run, the tape capacity, credentials, and media are checked. If the test job determines there is a problem, the job will continue to run and the problem will appear in the job log.
To run a test job for a scheduled job: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar. 3. Select the active job from the Current Jobs pane or the Job Calendar, and then under Scheduled Job Tasks in the task pane, click Run test job. You can select multiple jobs in the Jobs 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 Test Run on more than one job at a time, as long as the jobs are of similar type. 4. Enter test run properties for the job. For more information, see General settings options for test run job on page 308.
376
Monitoring Jobs
5. On the Properties pane, under Settings, click Notification and enter notification information for the items. For more information, see Selecting Recipients for Job Notification on page 492. 6. On the Properties pane, under Frequency, click Schedule and then click Submit job on hold if you want to submit the job with an on-hold status. Select this option if you want to submit the job, but do not want the job to run until you change the jobs hold status. 7. Click Run Now to submit the test run job.
Deleting Scheduled Jobs

Deleting a scheduled job from the Job Monitor removes a single job occurrence or all occurrences of the scheduled job.
To delete a scheduled job: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar. 3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then under Scheduled Job Tasks in the task pane, click Delete. You can select multiple jobs in the Jobs 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. 4. After clicking Delete, you are prompted to delete backup selection lists that are no longer in use by any other jobs. Click Yes to all to delete all of the unused backup selection lists, or click No to all to leave the backup selection lists intact. To delete selection lists later, on the Edit menu, click Delete Selection Lists. 5. Confirm the deletion of the scheduled job. If you are deleting the job from the Jobs list view, all occurrences of the job will be deleted. If you are deleting the job from the Calendar view, you can delete a single days occurrences or all occurrences of the job.
377
Monitoring Jobs
Viewing Completed Jobs

You can view detailed job-related properties for each job that has been processed. 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.
To view completed job properties: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar. 3. Select the completed job you want to view from the Job History pane or the Job Calendar, and then under General Tasks in the task pane, click Properties. The Job History dialog box appears. Click Expand All to view all the information contained in the topics. Click Collapse All to hide the information in the topics. The Job History tab provides the following job summary and set detail information:
Job History Item Job name Job type Description The job name entered during job configuration. The type of operation that was performed (Archive, Backup, Catalog, Restore, Verify). The status of the operation. The filename and location of the job log. The media server that processed the job. The selection list processed in the job. The name of the device that processed the job. The name of the device selected during job configuration. The name of the media set that processed the job.
Job status Job log Server name Selection list name Device Name Target name Media set name Job Summary Original start time
Time the job was submitted for processing.
378
Monitoring Jobs Job History (continued) Item Job started Job ended Files Directories Skipped files Corrupt files Files in use Byte count Rate Set Detail Information Set type The type of operation that was performed on the media set (Archive, Backup, Catalog, Restore, Verify). The status of the operation. The job name entered during job configuration. The name of the resource accessed during the operation. The Backup Exec logon account used to access the resource. Displays if an agent was used during the operation. Displays if the Advanced Open File Option was used during the operation. Displays if the Intelligent image Option was used during the operation. Description Time the operation started. Length of time the operation took. 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. Number of bytes processed. Number of megabytes processed per minute.
Set status Set description Resource name Logon account Agent used Advanced Open File Option used Image used
Start time End time
Time the operation started. Length of time the operation took.
379
Monitoring Jobs Job History (continued) Item Files Directories Skipped Files Corrupt files Files in use Byte count Rate Media used Description 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. Number of bytes processed. Number of megabytes processed per minute. Name of the media used during the operation. If the job does not require additional media, this option will not display. Lists the name of the file that was skipped. If the job does not contain a skipped file, this option will not display. Lists the name of the file in use. If the job does not encounter a file in use, this option will not display. Lists the name of the corrupt file. If the job does not contain a corrupt file, this option will not display.
File was skipped
File is in use
File is corrupt
4. Click Job Log to view detailed information about the job. The job log is in an HTML format. Click Expand All to view all the information in the topics or Collapse All to hide the information in the topics. The Job Log tab provides the following information:
Job Log Item Job Information Description Displays the job server, job name, job start date and time, job type, and job log name. Displays the robotic library name, drive name, slot number, media label, media ID, media overwrite protection and append date and time, and the targeted media set.
Device and Media Information
380
Monitoring Jobs Job Log (continued) Item Job Operation Description Displays the options selected during job configuration and agents used during job processing.
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. Errors Displays a detailed description of the errors encountered during job processing. The error section is red in the job log. Displays a detailed description of the minor errors encountered during job processing. The exceptions section is orange in the job log.
Exceptions
5. 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. 6. Click OK. See also: Understanding Job Log Status on page 382 Configuring Default Job Log Options on page 384
Deleting Completed Jobs

You can delete a job from the Job Monitor, or have Backup Exec automatically delete the job history using database maintenance. If you delete a job, it is completely removed from the system and cannot be recovered.
To delete a completed job: 1. On the navigation bar, click Job Monitor. 2. Under Views in the task pane, click Jobs list or Calendar.
381
Monitoring Jobs
3. Select the job you want to delete from the Job History pane or the Job Calendar, and then under General Tasks in the task pane, click Delete. You can select multiple jobs in the Jobs 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. 4. After clicking Delete, you are prompted to delete backup selection lists that are no longer in use by any other jobs. Click Yes to all to delete all of the unused backup selection lists, or click No to all to leave the backup selection list intact. To delete selection lists later, on the Edit menu, click Delete Selection Lists. 5. Confirm the deletion of the job history and associated job log. See also: Configuring Database Maintenance on page 389
Understanding Job Log Status

Backup Exec includes seven possible job completion statuses for jobs that were processed. Job statuses include the following:

Successful. The job completed without errors. Completed with exceptions. The job completed, but a file in use, skipped, or corrupted file was encountered during the operation. Failed over. The job ran in a cluster environment and was active on one machine and then the cluster performed a failover and the job was restarted on another server in the cluster. There are two separate sets of job history when a job is failed over. The first job history will have the Failed over status and the second job history will have the status that is appropriate for the completed job. Resumed. The status is the same as the failed over status, however the Apply CheckPoint Restart option was selected. Canceled. The administrator terminated the operation as it was running. Canceled, timed out. The Enable automatic cancellation feature in the Frequency Schedule property was enabled and the job was not completed within the specified timeframe.
382
Monitoring Jobs
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 you get a job failure occurred due to a lost connection during job processing, you could choose to resubmit the job when the connection becomes intact.
Note If a drive loses power during a backup operation, you should restart the backup job using a different tape. You can restore the data written to the tape up to the point of the power loss, but you should not reuse the tape for subsequent backup operations. A failed job will have an error message in the Errors section of the job log. The most common errors are searchable in the VERITAS Online Knowledge Base at www.support.veritas.com Some reasons a job may fail are: Devices specified by the job were not available when the job was run. Errors were found with the logon information associated with the job. There was a problem with the storage device when the job was run. The job information was corrupted. The user turned off the workstation.
383
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. 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. On the Tools menu, click Options. The Options - Set Application Defaults dialog box appears. 2. On the Properties pane, under Job Defaults, click Job Logs. 3. Select the appropriate options as follows:
Job Log default options Item Description
Information to include in log Summary information only Select this option to include the job name, job type, job log name, media server name, storage device, the starting date and time, any errors encountered, ending date and time, and 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 Select this option to include summary information and a list of all processed subdirectories.
Summary information, Select this option to include Summary information, processed directories, and files subdirectories, and a list of all the filenames that were processed. processed Summary information, Select this option to include Summary information, processed directories, files and subdirectories, a list of all the filenames and their attributes. file details Selecting this option increases the job log sizes significantly. Job log file base Enter the prefix to be used for the job logs that are processed.
See also: Backup Exec Defaults on page 84
384
Monitoring Jobs
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: bemcmd -o31 -f"<pathname\job log filename>" For example, to display the job log C:\program files\Backup Exec\NT\Data\bex00001.xml in text format to the command prompt, you would type: bemcmd -o31 -f"C:\program files\Backup Exec\NT\Data\bex00001.xml" To redirect the job log to a file, you would type: bemcmd -o31 -f"C:\program files\Backup Exec\NT\Data\bex00001.xml" > bex00001.txt See also: VERITAS Backup Exec Command Line Applet on page 591
385
Error-Handling Rules
Backup Exec has predefined error-handling rules that determine how job errors are handled. They apply to all backup jobs and are defined based on the cause of the failure. The rules can be configured to automatically perform operations such as retry, pause, or cancel a job after a failure occurs. If Backup Exec is running in a cluster environment, you can also configure the cluster failover error-handling rule. However, the rule only appears if the server on which Backup Exec is installed is in a cluster environment. 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 option is dependent on the error-handling rule, so if you disable the rule, the option will automatically be disabled to match the rules setting. Error-handling rules are disabled by default, except for cluster failover, which is enabled by default. Error-handling rules can be enabled or disabled for jobs that result in one of the following types of errors:

Resource Errors Server Errors Job Cancellation Job Errors System Errors Network Errors Backup Device Errors Security Errors Backup Media Errors Other Errors (errors that are not in any of the previous categories) Cluster Failover
See also: Enabling or Disabling Checkpoint Restart on page 747
386
Configuring Error-Handling Rules

You can configure error-handling rules for jobs in which the final status, error category, and error code match a defined rule. The settings for error-handling rules enable you to rename the error-handling rule, activate the rule, and retry, pause, or cancel the job. Note If Backup Exec is running in a cluster environment, the cluster failover error-handling rule appears. You can only enable or disable the rule, there are no additional options you can configure.
To configure an error-handling rule: 1. On the Tools menu, click Configure Error-Handling Rules. The Error-Handling Rules dialog box appears. Each rule displays the Name, Job Status, Error Category, and Enabled status. 2. Select the error-handling rule you want to configure, and then click Settings. 3. Complete the items in the Error-Handling Rule Settings dialog box as follows:
Error-Handling Rule Settings Item Name Final Job Status Description The title of the error-handling rule. The status for the job that will activate the rule. The job status can be viewed, but not modified. Available statuses include: Error Canceled Failed
387
Error-Handling Rules Error-Handling Rule Settings (continued) Item Error Category Description The category of error for which the rule will be applied. The error category can be viewed, but not modified. Available error categories include: Backup Device Backup Media Job Network Other Resource Security Server System Enabled Retry Options Retry Job Maximum retries Select this check box to enable Backup Exec to retry the job. Enter the number of times you want to retry the job. 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. Select this check box to enable the error-handling rule.
Retry Interval
Final Job Disposition Pause job until error condition has been manually cleared Select this option to place the job on hold until you can manually clear the error. After you clear the error, you must remove the hold for the job.
Cancel job and Select this option to cancel the current job after the selected number reschedule for its next of retry options has been met. After the job is canceled, it will run at scheduled service the next scheduled time. Notes Enter information for the error-handling rule.
388
Configuring Database Maintenance

The Database Maintenance option enables you to manage the Backup Exec database. The Backup Exec database maintains a record of files and data you have configured such as templates, catalogs, and etc. 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 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.
To configure database maintenance: 1. On the Tools menu, click Options. 2. On the Properties pane, under Settings, click Database Maintenance.
389

Database Maintenance options Item Descriptions
Enable Backup Exec Select this check box to activate the database maintenance process. database maintenance Last time maintenance The date and time the last database maintenance was performed. was performed Perform database maintenance at Delete expired data Delete expired data Select this check box to activate the deletion of expired job history, job logs, alert history, and reports from the Backup Exec database after the specified number of days have passed. Enter the time you want to perform database maintenance. All the maintenance will occur once a day at the time you specify.
Number of days to keep data before deleting it from the Backup Exec database Job history 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. Select this check box to check the logical and physical consistency of the data in the database. Note The option is not enabled by default, but it is recommended that you run a consistency check periodically at a time when there is minimal activity from Backup Exec.
Job logs
Alert history
Reports
Perform database consistency check
390
Using ExecView in Backup Exec Database Maintenance options (continued) Item Descriptions
Optimize database size Select this check box to reorganize fragmented pages and decrease the size of the physical database to 10 percent above what is actually used. 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. For more information, see Recover a Media Server Database on page 813.
4. Click OK.
Using ExecView in Backup Exec

ExecView is a web-based monitoring tool that includes a user interface called the ExecView Console. ExecView provides a single management console for locally or remotely monitoring and managing devices, jobs, and alerts for your Backup Exec media servers. The ExecView Console can be launched on Windows servers from Internet ExplorerTM. The ExecView Communication Module (ECM) is installed on your media servers and sends information about your media servers to a database on the ExecView Information Server (EIS), a web server that resides on Windows servers. From the ExecView Console, you can monitor your media servers, devices attached to those servers, jobs, and alerts.
391
Your ExecView Console, EIS, and ECM can run on three separate systems or you can have any combination of these components residing on the same system. For example, your ExecView Console and EIS can reside on the same Windows server.
ExecView Components in Common Scenario
ExecView Console Windows servers
ExecView Information Server Windows server
ExecView Communication Module (Backup Exec Servers) Windows servers or NetWare 4.2 and later
You can have multiple EIS and multiple media servers reporting through the same ExecView Console, but the console can only report information about devices, jobs, and alerts from one EIS at a time. To monitor media servers from ExecView, you must first create a profile for the EIS, and then create a server group, a group of media servers that report to the EIS. Placing servers into groups allows you to:

Control the size of the display in ExecView. Monitor your enterprise network more efficiently.
Servers can be grouped by any category, such as department or function, and can belong to multiple server groups. You can create as many groups as you need, and each group can contain as many servers as necessary.
392
A user can set preferences for how many scheduled and completed jobs are displayed for each server, whether the time displayed on the ExecView Consoles screens will be the local systems time or the media server time, and set the refresh rate for the ExecView Console. If multiple profiles are created, each profile can have different user preferences set. You can log into to multiple ExecView Consoles using different profiles; however, each ExecView Console only allows one user (profile) to be logged on at a time. For more information about ExecView, see the ExecView documentation in the ExecView\language\Docs directory on the Backup Exec CD.
Configuring ExecView
You can configure ExecView connection settings and then save them in Backup Exec. You can also edit the settings at any time using the configuration method. Configuring the connection settings enables you to quickly launch the ExecView console through Backup Exec.
To configure ExecView connection settings: 1. On the Tools menu, point to ExecView, and then click Connection Settings. The ExecView Information Server Settings dialog box appears. 2. Enter the appropriate options as follows:
ExecView Information Server Settings dialog box Item Name of remote host machine on which the ExecView Information Server (EIS) is running Description Enter the host machine on which the ExecView Information Server (EIS) runs. EIS is a web server that resides on a Windows system. It is the central server that the ExecView Communication Module (ECM) communicates with and sends data to.
Port number on which Enter the port number on which the EIS listens for console the EIS web server is connections. The console communicates with the EIS using http listening protocol on this port.
3. Click OK.
393
To launch the ExecView console:
On the Tools menu, point to ExecView, and then click ExecView Console.
If the ExecView Information Server settings are configured, the ExecView Console is launched. If the settings are not configured, you must enter the ExecView Information Server settings using the steps in the previous procedure.
394
Restoring Data
Restoring Data
The restore operation allows you to 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 (in a disaster situation) an entire system will need to be restored. Backup Exec offers several convenient methods for finding the files you need to restore:
Resource view. The resource view lists backed up data by the resource from which it was backed up. This feature is useful for finding files that were located on a certain server or workstation. Media view. The media view lists the data that is contained on a piece of media. This feature is useful for viewing the contents of a tape that was backed up from another media server. Advanced file selection. The Advanced File Selection feature allows you to specify file and date attributes for the data you want to restore. Search catalogs. The Search Catalogs feature makes it easy to find files that you want to restore, or to make sure that you have backups of certain files. This feature also allows you to see all cataloged, backed up versions of a file, so you can restore earlier versions if needed.
You can select options that you want to use for most restore operations. Backup Exec will use these default options unless you override these options when setting up a specific restore job.
395
Restore Operations and the Catalog
When creating your restore jobs, you can:

Restore data to the system from which it was originally backed up or redirect the restore to another system. Specify if the restore job should begin processing immediately or schedule it to run at a future time. Specify which local network is to be used for restoring data, ensuring that other connected critical networks are not affected by this Backup Exec operation.
See also: Using the Resource View on page 428 Using the Media View on page 428 Selecting Data to Restore on page 428 Using Advanced File Selection to Restore on page 430

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 operation performed on it before files can be selected to restore. See also: Cataloging Media in a Drive on page 397 Setting Catalog Defaults on page 399 Catalog Levels on page 402
396
Restoring Data
Cataloging Media in a Drive

Use Catalog to log the contents of a media created by a product other than this installation of Backup Exec (imported media), or to create a new catalog on the local hard drive if the catalog for the media no longer exists. Media must have a catalog before data can be restored from it or verified. You can also catalog backup-to-disk files. If the media is being used by this system for the first time, you may need to inventory the media first (see Inventorying Media in Devices on page 165).
To catalog media: 1. On the navigation bar, click Devices. 2. Select the device containing the media to be cataloged, and then select the media you want to catalog. 3. Under Media Tasks in the task pane, select New catalog. 4. Select the Device options as described in Device Options for Catalog Jobs on page 398. 5. On the Properties pane, under Settings, click General, and select the options as described in General Options for a Catalog Jobs on page 399. 6. 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 Selecting Recipients for Job Notification on page 492). 7. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). The catalog operation can be monitored or canceled through the Job Monitor. See also: Using Backup-to-Disk Folders and Files on page 143 Monitoring Jobs on page 365 Setting Catalog Defaults on page 399 Selecting Data to Restore on page 428 Canceling a Restore Operation on page 446
Chapter 8, Restoring Data
397
Device Options for Catalog Jobs

When you select to create a catalog job, the first options that appear are the Device options.
Catalog Job Properties dialog boxThese options include:
Device options for catalog job Item Device Password Description Select the device on which this job will run. If this media is password protected and being cataloged by this system for the first time, enter the password. If this media is password protected and being cataloged by this system for the first time, re-enter the password.
Confirm Password
398
Restoring Data
General Options for a Catalog Jobs

General options for a catalog job include:
General settings options for job Item Job name Job priority Description Enter 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. Your choices are: Highest High Medium Low Lowest
Setting Catalog Defaults
To configure catalog defaults: 1. On the Tools menu, select Options. 2. On the Properties pane, under Settings, click Catalog.
399
Restore Operations and the Catalog Default catalog options

Default catalog options Item Description
Use storage media-based Select this option to allow Backup Exec to read the catalog catalogs information from the media. Media-based catalogs allow quick cataloging of tapes that are not included in the disk-based catalog (for example, media that was written by another installation of Backup Exec). This feature allows tapes 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.
400
Restoring Data
Restore Operations and the Catalog Default catalog options (continued) Item Description
Truncate catalogs after x Select this option to retain only the header information and to days remove all file and directory details after the specified number of days. 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.
Note The last access date is not reset when catalogs are truncated. Therefore, if you select to have catalogs truncated after 20 days and then select Remove unused catalogs after 30 days, the catalogs will be truncated on the 20th day. On the 30th day, unless the catalogs have been accessed, they will be removed.
Remove unused catalogs This enables Backup Exec to automatically delete disk-stored after x days catalogs that have not been accessed in the specified number of days. Enabling this feature can help manage disk space used by catalogs; however, after removing catalog information for media, the media must then be re-cataloged before data can be selected from it for a restore operation. The access date for disk-stored catalogs is updated each time data is restored from, or appended to the media. Current path The path where the catalog files are located. This path defaults to \Catalogs in the \Backup Exec\NT directory. Select a volume where the catalog files are 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.
Catalog drive
Catalog path
4. Click OK. See also: Restore Operations and the Catalog on page 396 Catalog Levels on page 402
401
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 within the Backup Exec system as show in the Media view and within Restore selections:
Media catalog levels Item Fully Cataloged Media Description With fully-cataloged media, you can: View information on all the directories and files contained in each backup set. Search for files to restore. Use the file versioning feature.
Truncated Cataloged Media
Truncated cataloged media lists only backup set information. No files or file attributes can be viewed. This version of Backup Exec writes only full catalogs. However, truncated cataloged media that was migrated from earlier versions of Backup Exec, but not cataloged by this version, will appear as truncated cataloged media. Truncated cataloged media will not allow you to make restore selections. You must catalog the media to view and select files to restore. There is no catalog information for the media. You must catalog the media to view and select files to restore.
Uncataloged Media
See also: Setting Catalog Defaults on page 399 Restore Operations and the Catalog on page 396
402
Restoring Data
Restoring Data to a Server or Workstation

Restoring data to a server or workstation involves the creating of a restore job in which you specify:

Source Destination Settings Frequency
Unless you specify otherwise, the restore job will use the default options set through the Tools menu. You can use the Restore Wizard to have Backup Exec guide you through the creation of a restore job, but after you become familiar with Backup Exec, you will probably choose to set your options by configuring restore job properties. See also: Setting Restore Defaults on page 441
Using the Restore Wizard
To launch the Restore Wizard: 1. From the navigation bar, click Job Setup. 2. Under Restore Tasks in the task pane, select New job using wizard. 3. Follow the on-screen prompts.
403
Creating a Manual Restore Job by Configuring Job Properties
To restore data to a server or workstation: 1. On the navigation bar, click Restore. 2. Select the data to be restored (see Selecting Data to Restore on page 428), and complete other Selections options as described in Selections Options for Restore Jobs on page 407. Note To protect remote resources, you must install the Backup Exec Remote Agent for Windows Servers on the remote computer. 3. On the Properties pane, under Destination, click Device. 4. Select the device containing the data being restored. 5. On the Properties pane, under Settings, click General, and select the options as described in General Options for Restore Jobs on page 409. You can select additional configuration options for the restore job before selecting to run or schedule the job. Select additional options on the Restore Job Properties dialog boxs Properties pane: If you want to redirect this job to another system other than the one from which the data was backed up, on the Properties pane, under Destination, click one of the following (see Redirecting a Restore Operation on page 436): File Redirection. Select this option to redirect file sets. SQL Redirection. Select this option to redirect SQL Server sets to another SQL server. Exchange Redirection. Select this option to redirect Exchange sets to another Exchange server. Sharepoint Redirection. Select this option to redirect Sharepoint Portal Server sets to another Sharepoint server.
404
Restoring Data
If you want to set advanced options for the restore job, on the Properties pane, under Settings, click Advanced. Then, complete the options as described in Advanced Options for Restore Jobs on page 412. If you want to set commands to run before or after the job, on the Properties pane, under Settings, click Pre/Post Commands and complete the options as described in Pre/Post Commands for Restore Jobs on page 416. If you are restoring other platform types or database agents, such as SQL, Exchange, or NetWare, select the platform type from the Properties pane, under Settings, and then refer to the chapter or appendix for that item for instructions on completing the options. If you want to specify a local network to be used for this restore job, on the Properties pane, click Network, and then enter the network information (see Specifying the Restore Network on page 444). If you want Backup Exec to notify recipients when this job completes, on the Properties pane, under Settings, click Notification, and then select each recipient to be notified when the job completes (see Configuring E-mail and Pager Notification Methods on page 467).
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. 6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358).
405
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. Caution When restoring System State, you must reboot your system before performing subsequent restore operations. Note Depending on your file system environment, byte counts for restored data may not match the byte count recorded when the data was backed up. This is normal and does not mean that files were excluded in the restore operation. For more information, see Restore Questions on page 566. See also: Selecting Data to Restore on page 428 VERITAS Backup Exec - Remote Agent on page 821 Redirecting a Restore Operation on page 436 Redirecting Restores for SQL 2000 on page 1009 Restoring Exchange 2000 on page 1088 Restore Options for Exchange 5.5 on page 1119 Restoring NetWare Servers on page 1233 Restore Options for Lotus Domino Databases on page 1192 Viewing Completed Jobs on page 378 Restoring File Permissions on page 420
406
Restoring Data
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.
Restore Selections

Selections options for restore job Item Selection list 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. Click this button if you want to use a previously created selection list or merge existing selection lists.
Load Selections from Existing List
407
Restoring Data to a Server or Workstation Selections options for restore job (continued) Item View Format Graphical Show file details Select this option to view selections in a directory tree view. Select this option to display details about the files available for selecting. Select this option 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 restoring (see Using Advanced File Selection to Restore on page 430). Select this option if you want to select the contents of all the subfolders when a directory is selected. Description
Text Advanced
408
Restoring Data
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.
General settings options for restore job

General settings options for restore job Item Job name Description Enter a name that describes the data that you are restoring. This is the name that is used to identify this operation in the job schedule.
409
Restoring Data to a Server or Workstation General settings options for restore job (continued) Item Job priority Description Select the priority level for this job. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Your choices are: Highest High Medium Low Lowest Restoring existing files Restore over existing files Select this option to have Backup Exec overwrite files on the target resource that have the same name as files that are being restored. Use this option only when you are sure that you want to restore an older version of a file. Skip if file exists Select this option to prevent Backup Exec from overwriting files on the target disk with files that have the same names that are included in the restore operation.
Skip if existing file is more Select this option to prevent Backup Exec from restoring over files recent that exist on the target resource if they are more recent than the files included in the restore operation. This option is useful if you are rebuilding a system. For example, after installing the operating system on a crashed computer, you could restore a previous full backup of the system without worrying about overwriting later versions of operating system files. Restore corrupt files Select this option only if you do not wish 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. In the unlikely event that the automatic exclusion of corrupt files cannot be accomplished, you may manually exclude corrupt files in the Restore selections window and run the job with the Restore Corrupt File option enabled.
410
Restoring Data
Restoring Data to a Server or Workstation General settings options for restore job (continued) Item Restore security Description Check this box to restore file-level security information on NTFS partitions, if it exists in the data you selected. (This option is on by default.) 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 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.
Preserve tree
See also: Creating a Manual Restore Job by Configuring Job Properties on page 404
411
Advanced Options for Restore Jobs

To set Advanced options for restore jobs, on the Properties pane, under Settings, click Advanced.
Advanced restore options

Advanced options for restore Item Restore Removable Storage data Function 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 allows applications to access and share the same media resources.
412
Restoring Data
Restoring Data to a Server or Workstation Advanced options for restore (continued) Item Restore disk quota data Function 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 a 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 Select this check box to restore the Terminal Services database. The database 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 Restoring Data To Clusters on page 767. 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. If 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. Any changes made to the cluster quorum after the last backup will be lost. This option is only available if Restore Cluster Quorum is also selected.
Force the recovery of the cluster quorum even if other nodes are online and/or disk signatures do not match.
413
Restoring Data to a Server or Workstation Advanced options for restore (continued) Item 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. Function 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 replica 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. Restore Windows NT 4.0 registry Merge the existing hardware configuration and registry services with the data to be restored Overwrite the existing hardware configuration and registry services with the data to be restored Junction Points Restore junction points, directories, and files from backup media When this option is selected, the information for the junction points and the files and directories to which they are linked is restored. Selecting this option overwrites existing junction points on your system. Note If a junction point was originally backed up without the Back up files and directories by following junction points check box selected (see Back up files and directories by following junction points on page 316), 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. Select this check box to restore registry information if it exists in the data you selected (applies to Windows NT v4.0 only). Select this option if you want to merge the existing hardware and registry services with the data you selected to be restored. This option should only be used for restoring System State or the NT Registry. 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 or the NT Registry and there have been no hardware changes.
414
Restoring Data
Restoring Data to a Server or Workstation Advanced options for restore (continued) Item Preserve existing junction points and restore files and directories from backup media Function Select this option to restore files and directories backed up from junction point links while retaining the system's current junction points. This option keeps current junction points from being overwritten with the junction point information restored from the backup media. When this option is selected and identical junction points or directory names exist on both the target system and the media, the files and directories are restored to the target system's junction point or directory. If a junction point or directory does not already exist in the same location and with the same name as the junction point to be restored, then the information for the junction point and the files and directories to which they point will be restored. Note If a junction point was originally backed up without the Back up files and directories by following junction points check box selected (see Back up files and directories by following junction points on page 316), 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.
415
Pre/Post Commands for Restore Jobs

To set up commands to run before or after a restore job, on the Properties pane, under Settings, click Pre/Post Commands. You can run commands before or after a restore job, and set conditions for these commands:

Run the job only if the pre-job command is successful Run the post-job command only if the pre-job command is successful Run the post-job command even if the job fails Allow Backup Exec to check the return codes (or exit codes) of the pre- and post-job commands to determine if the commands completed successfully. An exit code of zero returned to the operating system by the pre- or post-job command is interpreted by Backup Exec to mean the command completed successfully. A non-zero exit code is interpreted by Backup Exec to mean the command ended with an error.
If it is critical that the job not run if the pre-job command fails, then configure Backup Exec to check the return codes of the pre- and post-job commands to determine if the pre-job command failed or completed successfully. For example, if a pre-job command that shuts down a database before a restore is run fails, the database could be corrupted when the restore is run. In this situation, it is critical that the restore job fail if the pre-job command fails. Additionally, if Backup Exec is configured to check the return codes of the pre- and post-job commands, and the post-job command returns a non-zero code, the job log reports that the post-job command failed. If you also selected to run the job only if the pre-job command is successful, and both the pre-job command and the job ran successfully, Backup Exec will mark the job as failed if the post-job command fails. For example, if the pre-job command runs successfully and shuts down the database and the restore job also runs successfully, but the post-job command cannot restart the database, Backup Exec marks the job and the post-job command as failed. If you select the option On each server backed up, the pre- and post-commands are run and completed for each server before processing begins on the next selected server.
416
Restoring Data
Restoring Data to a Server or Workstation Pre/post commands options for restore job

Pre/Post Commands for restore Item Pre-job command Function Specify a command to be run on the specified server before the restore job is run. Use local paths, and make sure the paths exist on each server and are correct. Note Commands that require user interaction, such as prompts, are not supported. Post-job command Specify a command to be run on the specified server after the restore job has run. Use local paths, and make sure the paths exist on each server and are correct. Note Commands that require user interaction, such as prompts, are not supported.
417
Restoring Data to a Server or Workstation Pre/Post Commands for restore (continued) Item Run job only if pre-job command is successful Function Select this option to run the restore job only if the pre-job command is successful. If the pre-job command fails, the job does not run, and is marked as failed. If it is critical that the job not run if the pre-job 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-job command did not run successfully. The job is not run and the job status is marked as Failed. Run post-job command Select this option to run the post-job command only if the pre-job only if pre-job command is command is successful. successful If it is critical that the post-job command fail if the pre-job 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 for the pre-job command, it is interpreted by Backup Exec to mean that the pre-job command did not run successfully. The post-job command is not run. If you also select Run job only if pre-job command is successful, and both the pre-job command and the job are successful, but the post-job command returns a non-zero code, the job log reports both the job and the post-job command as failed. Run post-job command even if job fails Select this option if it is critical to run the post-job command regardless if the job is successful or not. If you also select Allow pre- and post job commands to be successful only if completed with a return code of zero and the post-job command returns a non-zero code, the job log reports the post-job command as failed.
418
Restoring Data
Restoring Data to a Server or Workstation Pre/Post Commands for restore (continued) Item Allow pre- and post-job commands to be successful only if completed with a return code of zero Function Select this option to allow Backup Exec to check the return codes of the pre- and post-job commands to determine if they 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. After checking the return codes, Backup Exec continues processing according to selections you made for running the pre- and post-job commands. If this option is not selected, the success of the pre- and post-job commands is not determined based on the return code. Cancel command if not completed within x minutes Run these commands On this media server Select this option to run the pre- and post-job commands on this media server only. Select the number of minutes Backup Exec should wait before canceling a pre-job or post-job command that did not complete. The default time-out is 30 minutes.
On each server restored to Select this option to run the pre- and post-job commands one time on each server backed up. The pre- and post-job command selections apply to each server independently. The pre- and post-job 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.
See also: Creating a Manual Restore Job by Configuring Job Properties on page 404 Setting Default Pre/Post Commands on page 319
419
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. When restoring data with the Restore Security option selected on the Restore Job Properties dialog box when on the Properties pane, under Settings, you select General, 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. 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. See also: General settings options for restore job on page 409
420
Restoring Data
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 and restored only as a collection, never individually. To restore System State data to a server that is not a domain controller, you can perform a basic restore. If the target server is currently a domain controller, start the target server in Directory Services Restore Mode before performing a restore of the System State data. 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 operation. Canceling this operation could leave the system unusable. Caution Do not redirect System State restores. System State is computer-specific, and restoring it to an alternate computer can cause severe software damage.
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. 2. To open Services, right-click on My Computer, click Manage. 3. Expand Services and Applications. 4. Click Services. 5. For each Backup Exec service listed: a. Click Properties on the shortcut menu. b. Click the Log On tab, click This account, enter a user account with local administrators rights, and then click OK. c. Right-click the service, and then click Start on the shortcut menu.
421
6. After the Backup Exec services have started, run Backup Exec and perform a restore of the System State. Caution When restoring System State, you must reboot your system before performing subsequent restore operations. Note 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, please refer to your Microsoft documentation. See also: Creating a Manual Restore Job by Configuring Job Properties on page 404 Advanced options for restore on page 412
422
Restoring Data
Restoring Utility Partitions

Utility partitions, which are usually small partitions installed on the disk by OEM vendors like Dell, Compaq, Hewlett-Packard, and IBM, can be selected for restore. These utility partitions contain system diagnostic and configuration utilities and are usually restored during disaster recovery. However, utility partitions can be selected during a normal restore job provided the following requirements are met:

Utility partitions, but not the data belonging to the partitions, must be present on the system. You must have Administrator rights to restore utility partitions. The system on which the utility partition data is being restored should be the same system from which the data was originally backed up, unless you are required to do a redirected restore (see Performing Redirected Restores of Utility Partitions on page 424). 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.
See also: Restoring Data to a Server or Workstation on page 403 Selecting Data to Restore on page 428
423
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.
See also: Redirecting a Restore Operation on page 436 Manual Disaster Recovery of Windows Computers on page 540
Restoring Distributed File System (Dfs) Links

To restore Distributed file system (Dfs) links, select the user-defined selection for the Dfs from the catalog. Only the Dfs links themselves are restored. To restore data in the Dfs links, select specific data from the catalog. Note The Dfs root must exist before the links can be restored. See also: About Selecting Distributed File System (Dfs) Links for Backup on page 261
424
Restoring Data
Restoring Media Created With Other Backup Software

Media backed up with the following software products can be read with this version of Backup Exec and restored to the system from which it was backed up (or redirected to a compatible system or resource). In addition, Backup Exec can read media backed up with products that record media in the following tape formats:

Microsoft Tape Format (MTF) SIDF ARCserve Format Stac Image Option
Backup Exec also supports restoring NetWare SMS data to non-SMS volumes. For example, data backed up with Backup Exec for NetWare or Novells SBackup can be restored to the Windows NT media server or another network share. Media from the following products can be restored with Backup Exec:

Backup Exec for Windows NT 7.3 and later (MTF) Backup Exec for NetWare 7.x, 8.x, and 9.x (MTF) Software-compressed media created with previous versions of Backup Exec, such as Backup Exec for Windows NT (5.x, 6.x and 7.x) Seagate Backup Director (SIDF) Seagate Storage Exec (SIDF) ARCserve for NetWare 4.x, 5.x and 6.x (native and embedded SMS tape format) ARCserve for Windows NT 6.x Novell SBackup (SIDF) Palindrome Backup Director for Windows NT and NetWare (SIDF) Palindrome Storage Manager for Windows NT and NetWare (SIDF)
Note Software-compressed data backed up with products other than Backup Exec for Windows NT and Windows 2000 cannot be restored.
425
Restoring ARCserve Media

Backup Exec allows you to restore data from tapes backed up with ARCserve for Windows NT v6.x, ARCserve 2000, and ARCserve for NetWare versions 4.x, 5.x, 6.x and 7.x (native and embedded SMS tape format). Note ARCserve supports the use of SMS to back up data. Data backed up using the SMS option in ARCserve 4.x and 5.x cannot be restored. However, data backed up using the SMS option in ARCserve 6.x and ARCserve 7.x can be fully restored. The following types of data cannot be restored from ARCserve tapes:

Databases (such as Microsoft SQL and Exchange Server and NetWare Directory Services) Windows NT registry Interleaved files Compressed files Encrypted files Long filenames and Extended Attributes for OS/2 files Long filenames and resource forks for Macintosh files
Note Media containing ARCserve backups can be overwritten; however, backup append operations are not supported. All Backup Exec media utility functions can be performed on ARCserve media.
426
Restoring Data
To restore data from an ARCserve tape: 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 operations with the first tape used in the ARCserve backup. 1. Inventory all the tapes included in the ARCserve backup. 2. Catalog all the tapes included in the ARCserve backup. During cataloging, Backup Exec reports file formats that it can read. Files that cannot be read do not appear in the catalogs. The media description that appears in the Backup Exec catalog comes from the session description used by ARCserve. Note 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. Note 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 Operation on page 436). See also: Inventorying Media in Devices on page 165 Cataloging Media in a Drive on page 397 Creating a Manual Restore Job by Configuring Job Properties on page 404 Redirecting a Restore Operation on page 436 Restoring Media Created With Other Backup Software on page 425
427
Selecting Data to Restore

You can view data to restore through the Resource-centric view or the Media-centric view. To change views, right-click anywhere in the middle pane of the Restore Job Properties Selections dialog box and select the view you want to use.
Using the Resource View

In the Resource view, restore selections are listed by the resource from which they were backed up.
Resource View
Local volume Network volume Backup type Backup set number
Using the Media View

The Media view allows you to view and make restore selections from all of the cataloged media in the system.
Media View Media family name 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
428
Restoring Data
Job Properties - Selections dialog box. Remember that only media cataloged or backed up at this server will be displayed in the views. If you want to restore data backed up at another installation of Backup Exec, you will need to 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. All files and directories at or below the selected directory level are included in the restore operation (if the Include Subdirectories option is selected under the Edit menu). 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 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.
See also: Restore Operations and the Catalog on page 396 Cataloging Media in a Drive on page 397 Creating a Manual Restore Job by Configuring Job Properties on page 404
429
Changing 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.
To change a logon account for a resource: 1. On the navigation bar, click Restore. 2. Select the data you want to restore. 3. On the Properties pane, under Source, click Resource Credentials. 4. Select the resource whose logon account you want to edit. 5. Click Change. 6. Select the logon account you want to use for this backup selection, or click New and create a new logon account (see Creating a Backup Exec Logon Account on page 350). 7. Click OK. See also: Creating a Manual Restore Job by Configuring Job Properties on page 404 Redirecting a Restore Operation on page 436
Using Advanced File Selection to Restore

Advanced file selection allows you to quickly select files or clear selections for restore operations by specifying file attributes. With this feature you can:

Include or exclude files by filename extensions. You could select only files with *.txt extensions, or exclude files with *.exe extensions from a restore operation. Select only files that fall within a specified date range. You could select files that were created or modified during the month of December.
To select files using Advanced File Selection: 1. On the navigation bar, click Restore. 2. Click Advanced.
430
Restoring Data
Selecting Data to Restore Advanced File Selection dialog box

Advanced Restore Selections Item Media Specification Media File Specification Backup Set Path Select the backup set for which you want to specify attributes. Enter any available directory or subdirectory. Enter the full path to the subdirectory. 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 use of a double asterisk (**) to represent any number of characters, irrespective of any backslashes. Select the media that contains the files you want to restore. Description
File
431
Selecting Data to Restore Advanced Restore Selections (continued) Item Include Subdirectories Description When this option is selected, all subdirectories (and their contents) in the path you have entered are included in (or excluded from) the operation. If you want to process only the directory listed in the Path field, leave this option unchecked.
Type Include Exclude Selection Criteria Files Dated Include or exclude the files created or modified during the specified time period. (Default) Select this option to include the files in the operation. Select this option to exclude files from the operation.
4. If you expand the view for the resource from which you included (or excluded) files, you will see check marks in the directories that contain files meeting the criteria you specified. 5. Submit the operation using the same procedures required for other restore operations. See also: Restoring Data to a Server or Workstation on page 403 Redirecting a Restore Operation on page 436
432
Restoring Data
Searching for Files to Restore

You can search the catalog to easily find files that you want to restore, or to make sure that you have backups of certain files. This feature also allows 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 operation.
To search the catalog: 1. On the Edit menu, click Search Catalogs. The Search Catalog dialog box appears. The Catalog Search box contains two tabs: the Name and Location and the Date Modified. 2. Select which method you want to use for searching catalogs: To search for a file by name and location, select the Name and Location tab and complete the options described inName and Location Options for Catalog Search on page 434. To search for files by date modified, select the Date Modified tab.
3. Click Find Now. Click Stop to halt the search, or New Search to search for another file. The Catalog Search results window appears. All of the backed up versions of the file appear in the Catalog Search window. Expand a file to view the files properties. To sort the listings by filename, size, type or date modified, click the appropriate column heading. 4. Check the version of the file you want to restore and click Restore from the toolbar. The Restore Job window opens. 5. Submit the job using the same procedures required for other restore jobs. Backup Exec will prompt you to insert the correct media if it is not already located in a drive. See also: Restoring Data to a Server or Workstation on page 403
433
Name and Location Options for Catalog Search

To display the Name & Location dialog box, on the Edit menu, click Search Catalogs.
Search Catalog dialog box

Name and Location fields Item Location Description The server and share in which to search. If you do not want to limit the search to a particular location, leave this field blank to search all locations. 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 (/). File Name The name of the file to be searched. If you do not want to limit the search to a particular file, leave this field blank to search all files. 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.
Path
Media
Find directories
434
Restoring Data
Date Modified Options for Catalog Search

To search for files by date modified, on the Search Catalogs dialog box, select the Date Modified tab.
Date Modified tab

Date Modified options Item All Files Find all files created or modified Between x/x/x and x/x/x During the previous x month(s) During the previous x day(s) Description This option allows you to search for all files. Select this option to search only for files 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. You specify the number of months. Click this option if you want to restrict the search to the previous day or days. You specify the number of days.
435
Redirecting a Restore Operation
Restore Operations and Media Libraries

For restore operations, 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 operation 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 operation in the robotic library (or other accessible storage devices), an alert is issued requesting the media necessary to complete the operation.

Backup Exec defaults to restoring data to the resource from which the data originated. By using the Restore Job Properties - Redirection dialog boxes, you can restore data to any protected server, share, or Backup Exec agent workstation.
To redirect a file set operation: 1. On the navigation bar, click Restore. 2. Select the data to be restored (see Selecting Data to Restore on page 428). 3. On the Properties pane, under Destination, click File Redirection.
436
Restoring Data
Redirecting a Restore Operation Redirect file sets

Files destination options Item Redirect file sets Description 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.
Restore to drive
437
Redirecting a Restore Operation Files destination options (continued) Item Server logon account Description 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 Configuring Logon Accounts on page 347). Click Clear to clear this field. 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. Note If you are using BEWAC, you can only choose a pre-defined logon account. You cannot create or edit a logon account.
Restore to path
Path logon account
Note Entering a name of an agent drive (Win98, Mac, UNIX) that does not appear in the Restore to drive list box causes the agent restore operation to fail. To resolve this, click Browse, and open the Remote Selections window. After Backup Exec detects the agent, the agent shares will appear in the Restore to drive list and the restore operation can be attempted again. 5. 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 (see Scheduling Jobs on page 358). See also:
Preserve tree on page 411 Using Redirected Restore to Install Domain Controllers from Media on page 439 Redirecting Restores for SQL 2000 on page 1009 Redirecting SharePoint Portal Server Restore Jobs on page 1217
Scheduling Jobs on page 358
438
Restoring Data
Using Redirected Restore to Install Domain Controllers from Media

When you want to install a new .NET 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. To decrease the installation time of a Domain Controller, you can use the Install from Media feature. With the Install from Media feature, you can 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.
To install a Domain Controller from media: 1. Perform a standard System State backup of an active .NET Server Domain Controller that is in the target domain. 2. Transport the tape to the location of the system that will be installed into the target Domain. Caution The tape is not encrypted or protected. Use caution when transporting it to the location of the target domain. 3. Inventory the drive where the tape is loaded. 4. Catalog the tape. 5. Perform a redirected restore of the System State backup to a temporary location on a volume or directory on the target system. Note 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.
439
7. Type: dcpromo /adv 8. Click OK. 9. Click Next when the Active Directory Installation Wizard appears. 10. Select Additional domain controller for an existing domain. 11. Click Next. 12. Select From these restored backup files, and then enter the temporary location to which you redirected the System State data in step 5. 13. Click Next. 14. Complete the Active Directory Installation Wizard by following the prompts on the screen. 15. Complete the Domain Controller installation. 16. Reboot the system that has the new Domain Controller. 17. Delete any remaining temporary redirected System State files. For more information, refer to your Microsoft documentation. See also: Creating a Manual Backup Job by Configuring Job Properties on page 236 Inventorying Media in Devices on page 165 Cataloging Media in a Drive on page 397 Redirecting a Restore Operation on page 436
440
Restoring Data
Setting Restore Defaults

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 operations. You can override these defaults while setting up a restore operation, if necessary.
To set application defaults for restore jobs: 1. On the Tools menu, select Options. 2. On the Properties pane, under Job Defaults, click Restore.
Default restore options
441

Restore default options Item Restore existing files 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 (or files). 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 operation. Select this option to prevent Backup Exec from restoring over files that exist on the target resource if they are more recent than the files included in the restore operation. 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. Restoring corrupt files Restore corrupt files Backup Exec will automatically exclude corrupt files from the restore process unless you select this option. Description
Skip if file exists
Skip if existing file is more recent
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. VERITAS recommends performing redirected restore of corrupt files rather than restoring to the original location.
442
Restoring Data
Setting Restore Defaults Restore default options (continued) Item Junction Points Restore junction points, When this option is selected, the information for the junction files and directories from points and the files and directories to which they are linked is backup media restored. Selecting this option overwrites existing junction points on your system. If a junction point was originally backed up without the Back up files and directories by following junction points check box selected (see Back up files and directories by following junction points on page 316), 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. Preserve existing junction points and restore files and directories from backup media Select this option to restore files and directories backed up from junction point links while retaining the system's current junction points. This option keeps current junction points from being overwritten with the junction point information restored from the backup media. When this option is selected and identical junction points or directory names exist on both the target system and the media, the files and directories are restored to the target system's junction point or directory. Note If a junction point or directory does not already exist in the same location and with the same name as the junction point to be restored, then the information for the junction point and the files and directories to which they point will be restored. If a junction point was originally backed up without the Back up files and directories by following junction points check box selected (see Back up files and directories by following junction points on page 316), 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. Description
443
Specifying the Restore Network

By default, Backup Exec will restore data using the default network information set through the Tools menu by selecting Options, and then selecting Network (see Specifying the Default Backup Network on page 325). You can, however, specify the local network to be used 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 network information for a restore job: 1. On the navigation bar, click Restore. 2. Select the data to be restored (see Selecting Data to Restore on page 428). 3. On the Properties pane, under Settings, click Network.
Restore Job Properties - Network options
444
Restoring Data

Network options for restore job Item Restore Network 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. The list includes all available network interface cards on the media server. Displays the IP address for the server. Displays the address of the network you selected as the restore network. Displays the 32-bit number that determines the subnet to which the network interface card belongs. Displays the network identification or subnet address that Backup Exec calculated based on the network you selected as the restore network. Select this option if you want Backup Exec to attempt to connect using any available network route if a connection cannot be made using the specified network. If you do not select this option, and Backup Exec cannot connect using the specified network interface, the restore job will fail. Description
IP address Subnet mask
Network ID
Physical address
5. Continue selecting options for the restore job. 6. If you want to run the job now, click Run Now. Otherwise, on the Properties pane, under Frequency, click Schedule to set the scheduling options you want to use (see Scheduling Jobs on page 358). See also: Restoring Data to a Server or Workstation on page 403 Specifying Backup Networks on page 323
445
Canceling a Restore Operation
Canceling a Restore Operation

Note 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 operation. Canceling this operation could leave the system unusable.
To cancel a restore operation: 1. On the navigation bar, click Job Monitor. 2. Under Current Job View Filters, ensure Show active jobs is selected. 3. Select the restore job you want to cancel. 4. Under Active Job Tasks in the task pane, select Cancel. 5. Select Yes when prompted to confirm the cancellation of the job. See also: Deleting Scheduled Jobs on page 377
Catalog Icon Definitions

Following are icons that can appear in the restore selections. This list can help you identify the type of data you are selecting to restore.
Backup media used for backup jobs.
Backup media is part of a multi backup media set.
A set/resource contained on the backup media.
446
Restoring Data
A set that has been partialized.
A set that contains corrupt data.
A set containing a single SQL database backup.
A set containing a SQL database that has been partialized to remove details of the set.
A set containing a SQL database that is corrupt on the backup media.
A set containing associated transaction logs for a SQL database.
A set containing associated transaction logs for a SQL database that has been partialized.
A set containing associated transaction logs for a SQL database that are corrupt on the backup media.
An Exchange Information store set.
An Exchange Information store set that has been partialized to remove details from the catalog.
An Exchange Information store set that is corrupt on the backup media.
An Exchange Information store transaction log set.
447
An Exchange Information store transaction log set that has been partialized.
An Exchange Information store transaction log set that is corrupt on the backup media.
An Exchange Directory store set.
An Exchange Directory store set that has been partialized.
An Exchange Directory store set that is corrupt on the backup media.
An Exchange Directory store transaction log set.
An Exchange Directory store transaction log set that has been partialized.
An Exchange Directory store transaction log set that is corrupt on the backup media.
An Exchange Mailbox set.
An Exchange Mailbox set that has been partialized.
An Exchange Mailbox set that is corrupt on the backup media.
An Exchange Mailbox transaction log set.
448
Restoring Data
An Exchange Mailbox transaction log set that has been partialized.
An Exchange Mailbox transaction log set that is corrupt on the backup media.
An Exchange 2000 store set.
An Exchange 2000 store set that has been partialized.
An Exchange 2000 store set that is corrupt on the backup media.
An Exchange 2000 store transaction log set.
An Exchange 2000 store transaction log set that has been partialized.
An Exchange 2000 store transaction log set that is corrupt on the backup media.
An Exchange 2000 directory store set.
An Exchange 2000 directory store set that has been partialized.
An Exchange 2000 directory store set that is corrupt on the storage media.
An Exchange 2000 directory store transaction log set.
449
An Exchange 2000 Directory store transaction log set that has been partialized.
An Exchange 2000 Directory store transaction log set that is corrupt on the storage media.
An Intelligent Image Option backup set.
An Intelligent Image Option backup set that has been partialized.
An Intelligent Image Option backup set that is corrupt on the storage media.
The backup set is incomplete because the backup job was aborted. Review the backup job logs for additional information.
The backup set is incomplete because the backup job failed. Review the backup job logs for additional information.
The Utility partition backup set is corrupt on the storage media. Review the backup job logs for additional information.
A Shadow Copy backup set.
A Shadow Copy backup set that has been partialized.
A Shadow Copy backup set that is corrupt on the backup media.
A System State backup set.
450
Restoring Data
A System State backup set that has been partialized.
A System State backup set that is corrupt on the storage media.
A Service State set.
A Service State set that has been partialized.
A Service State set that is corrupt on the backup media.
A User-defined Share backup set.
A User-defined Share backup set that has been partialized.
A User-defined Share backup set that is corrupt on the backup media.
An undefined (other) backup set.
451
452
Alerts and Notifications
Any event that occurs in Backup Exec that is important enough to present a message to the user or requires a response from the user is an alert. There are 35 alert categories that originate from system, job, media, or device sources. Each alert category may contain one or more events that can generate the alert. Each alert category is also provided with an alert type. The alert type and corresponding colored icon can help you quickly determine the severity of the alert. Backup Exec includes the following alert types:

Attention required - a green icon Errors - a red icon Warnings - a yellow icon Informational - a blue icon
The majority of Backup Exec alerts are enabled by default and automatically display. However, three alert categories are disabled by default: Backup job contains no data, Job Start and Job Success. You can modify alert categories to enable or disable the alerts when you configure alert categories, but attention required and error alerts cannot be disabled. The alert type icons that appear with the alert categories appear shaded in the Alert Categories dialog box for disabled alerts. Alerts remain active in the system until you enter a response, or you can configure the alert category property to automatically clear the alert after a specified length of time. Depending on the alert type, it may not be necessary to respond to the alert to continue with operations. After you respond to an alert, it is moved to the alert history, where the alert remains for the length of time you choose to keep it in the Backup Exec database or until you delete it. Notifications can be configured to notify recipients when alerts occur. To use notifications you must perform the following:
You must first configure the methods you want to use to notify the recipient. The methods of notification are MAPI, SMTP, or VIM (Lotus Notes) e-mail and native and alphanumeric pager configurations. Printer and Net Send notification methods do not require pre-configuration.
453
Viewing and Filtering Alerts
The second step is to configure recipients. Recipients are individuals, computer consoles, printers, or groups and can be configured to use one or more of the notification methods. The last step is assigning the recipients to alerts or jobs for notification.
See also: Responding to Active Alerts on page 459.

Alerts appear in Backup Exec when the system needs administrator attention. 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. Backup Exec has two views for alerts: Active alerts and Alert history. 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.
To view alerts in the Active alerts or Alert history pane:
On the navigation bar, click Alerts and then under Views in the task pane, click the type of alerts you want to view, either Active alerts or Alert history.
454
Viewing and Filtering Alerts Alerts view
The information that appears for each alert includes the following: Type of alert Category Message displayed by the alert Job Name Device Name Media server on which the alert occurred Source of the alert Time the alert was received
Values, properties, and alert messages for the selected alert also appear in the Active Alert or Alert History Properties pane at the bottom of the view.
Chapter 9, Alerts and Notifications
455
To set View Filters for Active alerts and Alert history: 1. On the navigation bar, click Alerts. 2. Under Views in the task pane, click the view for which you want to set filters, either Active alerts or Alert history. 3. Under View Filters in the task pane, select or clear the filters for the alerts you want to appear in the selected view. The following types of alert filters can be selected for the Active alerts and Alert history views.
Alert View Filters Item Show attention required Show errors Show warnings Show information Show system alerts Show media alerts Show device alerts Show job alerts Description Lists alerts that require a response from the user.
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.
See also: Responding to Active Alerts on page 459
456
Viewing Alert Properties
Viewing Alert Properties

Alert properties provide detailed information about each alert. In addition to the alert properties information, you can view category properties and response information, if the alert is in the alert history.
To view alert properties: 1. On the navigation bar, click Alerts. 2. Under Views in the task pane, click Active alerts or Alert history, depending on where the alert for which you want to view properties is located. 3. Select the alert from either the Active Alerts or Alert History pane. 4. Under General Tasks in the task pane, click Properties. The Alert Properties dialog box provides the following items:
Alert Properties Item Category Type Descriptions 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 Device Job Name Time alert received Name of the media server on which the alert occurred. Name of the device on which the alert occurred. The name of the job associated with the alert. Date and time the alert occurred.
457
Viewing Alert Properties Alert Properties (continued) Item Source Descriptions The cause of the alert. Alerts can originate from one of the following sources: System Job Media Device SNMP trap Identification Properties of Category Enabled Send notifications 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 VERITAS Technical Support web site for information about the Event ID. Event ID Automatically clear The alerts ID in the Windows Event Viewer. Number of hours the alert remains active with no response attempted before it is moved to the alert history. Sends the job log to the recipient configured for notification. This option can only be used for recipients that are configured for e-mail or printer notification. The SNMP message from Backup Exec regarding status and error conditions.
Send SNMP notifications Record in event log
Include job log
Response (Alert History Properties User who responded Response machine Time user responded 458 User ID that responded to the alert. Name of the computer from which the user responded. Date and time the user responded to the alert. Administrators Guide
Responding to Active Alerts Alert Properties (continued) Item User response Descriptions
The response the user entered for the alert.
5. After you view the alert properties, click OK. See also: Configuring Alert Category Properties on page 463 Configuring Recipients on page 472 Configuring SNMP Notification on page 494
Responding to Active Alerts

You can respond to active alerts and depending on the alert condition, continue or cancel the operation. By default, Backup Exec displays all enabled alerts. If you have set View Filters (see Viewing and Filtering Alerts on page 454), only those alerts that are selected appear.
To respond to an active alert: 1. On the navigation bar, click Alerts. 2. Under Views in the task pane, click Active alerts. 3. Select the alert to which you want to respond, and then under Alert Tasks in the task pane, click Respond. Note If you have more than one alert selected, click Respond OK to all to clear the selected alerts to the alert history. The alerts must have an OK response available to be automatically cleared. The alert dialog box appears. If you click Close, you will close the dialog box, but the alert remains active. To clear the alert and move it to the alert history, you must select a response such as OK, Yes, No, or Cancel from the alert dialog box.
459
Viewing the Job Log for Alerts
The alert dialog box provides the following information:

Alert Options Item Category Name Message Description The title of the alert. Describes the event that caused the alert and provides suggestions for responding to the alert. 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. Select this check box to have alerts automatically appear in the Backup Exec console when they are sent. If you do not select this option, you must respond to alerts through the Active Alerts pane. For more information, see Changing Default Preferences on page 85.
Server name Device name Job name Time Automatically display new alerts
4. Click a response for the alert. After the alert condition is resolved, the alert is moved to the Alert history.

A 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 job-related alerts from either Active alerts or Alert history, depending on where the alert is located.
To view the job log: 1. On the navigation bar, click Alerts. 2. Under Views in the task pane, click Active alerts or Alert history, depending on where the alert for which you want to view the job log is located.
460
3. Select the alert for which you want to view the job log from either the Active Alerts or Alert History pane. 4. Perform one of the following: If the alert is in Active alerts, under Alert Tasks in the task pane, click View job log. If the alert is in the Alert history, under Alert History Tasks, click View job log.
5. To print the job log, click Print. You must have a printer attached to your system and configured in order to print the log. 6. After you have finished viewing the job log, click OK. See also: Viewing Completed Jobs on page 378
461
Clearing Informational Alerts from the Active Alerts Pane
Clearing Informational Alerts from the Active Alerts Pane

Informational alerts can originate from the system, jobs, media, or devices. The alerts are set by default to move to the alert history after 24 hours; however, some informational alerts appear frequently and fill the Active alerts pane. You may want to clear these informational alerts to the Alert history pane before they are automatically moved by the system.
To clear informational alerts from the Active alerts pane: 1. On the navigation bar, click Alerts. 2. Under Views in the task pane, click Active alerts. 3. Under Alert Tasks in the task pane, click Clear all informational alerts. All the informational alerts in the Active alerts pane are cleared to the Alert history.
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 alert configuration dialog box.
To enable or disable an alert from the Active Alerts pane: 1. On the navigation bar, click Alerts. 2. Under Views in the task pane, click Active alerts. 3. On the Active Alerts pane, select the alert that you want to enable or disable. 4. Under Alert Tasks in the task pane, click Alert category enabled. The alert will be enabled or disabled, depending on the current setting. The error and attention required alert types cannot be disabled.
462
Configuring Alert Category Properties

You can configure alert categories to enable or disable alerts and determine the type of actions that will be initiated when an alert occurs. Each time you change the alert configuration, it is recorded in the audit log. You can view the audit log at any time to view the changes made to the alert category.
To view or change alert category properties: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Alert Tasks in the task pane, click Configure alert categories.
3. Under Alert Categories, click the alert for which you want to view or change properties. Tip You can change the options for more than one alert category simultaneously. To select consecutive alert categories, click the first alert, press and hold down <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.
463
4. Under Category Properties, select the appropriate options as follows:

Alert Category Properties Item Category name Enable alerts for this category Description 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. For more information, see Enabling or Disabling Alerts from the Active Alerts Pane on page 462. 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. For more information, see Configuring Recipients on page 472. Include job log with a notification to an e-mail or printer recipient Select this check box to send the job log to the recipient configured for notification. The recipient must be configured to receive e-mail or printer notifications.
Send SNMP Notifications Select this check box to enable SNMP notifications. SNMP must be installed to use this option. For more information, see Configuring SNMP Notification on page 494. 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 VERITAS Technical Support web site for information about the Event ID. Automatically clear after x hours/minutes Select this check box to enter the number of minutes or hours you want the alert to remain active before it is moved to the Alert history. For attention required alerts, you can set a default response. For more information, see Edit Server Configurations on page 801.
464
5. Click Apply to apply the properties to the alert and continue configuring additional alerts. 6. Click OK to exit the Alert Configuration dialog box. See also: Assigning Recipients to Alert Categories for Notification on page 491
Viewing and Clearing the Audit Log

You can view the audit log to determine the type of changes that were made to the category properties for alerts. The audit log displays the date and time the change was made, the user that made the change, and the information that was changed. The audit log entries can be viewed, but not edited; however, you can clear all the entries in the log.
To view or clear the audit log: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Alert Tasks in the task pane, click Configure alert categories. 3. Under Alert Categories, click Audit Log.
465
Deleting Alerts from the Alert History
The Alerts Audit Log dialog box provides the following information:
Alerts Audit Log Item Date/Time Description The date and time the change was made to the alerts category properties. The user ID that made the change to the alerts category properties. The name of the alert category to which the change was made.
User Name Message
4. Click Refresh to update the audit log with new entries. 5. Click Clear to remove all entries from the audit log. 6. Click Close.
Deleting Alerts from the Alert History

Alerts that have been responded to or automatically cleared from the system are kept in the Alert history. All alerts are displayed, except for entries that have been filtered and selected for exclusion. The alerts remain in the Alert history for the length of time you set in the database maintenance option or until you delete the alert.
To delete an alert from the Alert history: 1. On the navigation bar, click Alerts. 2. Under Views in the task pane, click Alert history. 3. Select the alert you want to delete, and then under Alert History Tasks in the task pane, click Delete. 4. Click Yes to confirm that you want to delete the alert. The alert is removed from the Backup Exec database. See also: Configuring Database Maintenance on page 389
466
Configuring E-mail and Pager Notification Methods

Backup Exec has several methods for notifying you of alerts that occur during operations. The notification methods enable you to determine the means by which a recipient will receive a notification. You can configure notification methods for SMTP, MAPI, or Lotus Notes e-mail, and native and alphanumeric pager configurations. Printer and Net Send are also methods of notification, but they do not require you to configure them before creating and configuring a recipient. Configuring the notification method is the first step in assigning recipients to alert categories for notification. After configuring the notification method, the next step is to create recipients and assign a notification method by which the recipient will be notified of an alert. The recipient can then be assigned to an alert category for notification when an alert occurs. See also: Configuring Recipients on page 472 Assigning Recipients to Alert Categories for Notification on page 491
Configuring SMTP E-Mail for Notification

You must have an SMTP-compliant e-mail system such as a POP3 mail server to receive alert notification messages using the SMTP notification method.
To configure the SMTP e-mail notification method: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure e-mail and pagers.
467
Configuring E-mail and Pager Notification Methods SMTP configuration dialog box
3. Click the SMTP Configuration tab and 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. Backup Exec will not check the server name or the e-mail address for validity. Defaults to a standard SMTP port. In most cases, the default should not have to be changed. Type the e-mail address of the user from whom the notification message will be sent. The e-mail 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.
SMTP port
Default sender
4. Click OK. See also: Configuring Recipients on page 472
468
Configuring MAPI E-Mail for Notification

You must have a MAPI-compliant e-mail system such as Microsoft Exchange to receive alert notification messages using the MAPI notification method.
To configure MAPI alert notification: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure e-mail and pagers.
MAPI configuration dialog box
3. Click the MAPI Configuration tab and select the appropriate options as follows:
MAPI Configuration dialog box Item Enable Mail server name 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 Backup Exec service account has access. For more information, see Changing Windows Security on page 44. 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.
Mailbox name to send e-mail from
469
Configuring VIM E-Mail for Notification

You must have a VIM (Lotus Notes) compliant e-mail system to receive alert notification messages using the VIM notification method.
To configure VIM alert notification: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure e-mail and pagers.
VIM configuration dialog box
3. Click the VIM Configuration tab and select the appropriate options as follows:
VIM Configuration dialog box Item Enable Notes client directory Mail password Description 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.
470
Configuring E-mail and Pager Notification Methods VIM Configuration dialog box (continued) Item Confirm mail password Description
Re-type the password that enables you to connect to the Notes client.
Configuring a Pager for Alert Notification

You can configure Backup Exec to page you with alert notification messages. You must have a modem set up on your system in order to use the pager notification method. 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure e-mail and pagers. The Notification Configuration Properties dialog box appears. 3. Click the Pager Configuration tab and select Enable to activate this alert notification method.
Pager Configuration dialog box
471
Configuring Recipients
4. Select a modem from the Select a modem for sending pages option. Only modems recognized in Windows appear in the list box. 5. 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 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 e-mail, or a pager. You must configure the notification method before you can enable it for the recipient. 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.
See also: Configuring E-mail and Pager Notification Methods on page 467 Assigning Recipients to Alert Categories for Notification on page 491
Configuring SMTP Mail for a Person Recipient

You can configure a person recipient to receive SMTP e-mail notification messages if you have configured the SMTP notification method.
To configure SMTP mail for a person recipient: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 3. Click New, click Person in the Recipient Type dialog box, and then click OK.
472
Configuring Recipients SMTP Mail dialog box
4. In the Name field, type the name of the recipient that you want to configure. 5. Click the SMTP Mail tab and select the appropriate options as follows:
SMTP Mail dialog box Item Enable Description Select this check box to activate this notification method for the recipient. Type the e-mail address of the recipient to whom the notification message will be sent. For example, john.smith@company.com. Enables you to test the notification configuration for the recipient.
Address
Test
Limit the number of notifications sent Enable Select this check box to activate the option.
473
Configuring Recipients SMTP Mail dialog box (continued) Item Notify me a maximum of x times within x minutes Description Type the total number of notifications you want sent to the recipient for all alerts generated within the specified number of minutes. After the specified number of notifications have been sent, additional notifications are not sent until the specified minutes have been reached. The maximum number of minutes that can be set is 1440, which is the number of minutes in a day. Select this check box to enter the number of minutes that must be reached before the notification limits are reset. When the time limit has been reached, the number of notifications sent is reset to zero.
Reset the notification limits after x minutes
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. 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 488.
Schedule
6. Click OK. See also: Editing Recipient Notification Methods on page 489 Editing Recipient Notification Properties on page 489 Assigning Recipients to Alert Categories for Notification on page 491
Configuring MAPI Mail for a Person Recipient

You can configure a person recipient to receive MAPI e-mail notification messages if you have configured the MAPI notification method.
To configure MAPI mail for a person recipient: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears.
474
3. Click New, click Person in the Recipient Type dialog box, and then click OK.
MAPI Mail dialog box
4. In the Name field, type the name of the recipient that you want to configure. 5. Click the MAPI Mail tab and select the appropriate options as follows:
MAPI Mail dialog box Item Enable Description Select this check box to activate this notification method for the recipient. Type the e-mail 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.
Mailbox
Test
475
Configuring Recipients MAPI Mail dialog box (continued) Item Description
Limit the number of notifications sent Enable Notify me a maximum of x times within x minutes Select this check box to activate the option. Type the total number of notifications you want sent to the recipient for all alerts generated within the specified number of minutes. After the specified number of notifications have been sent, additional notifications are not sent until the specified minutes have been reached. The maximum number of minutes that can be set is 1440, which is the number of minutes in a day. Select this check box to enter the number of minutes that must be reached before the notification limits are reset. When the time limit has been reached, the number of notifications sent is reset to zero.
Schedule
476
Configuring VIM Mail for a Person Recipient

You can configure a person recipient to receive VIM e-mail notification messages if you have configured the VIM notification method.
To configure VIM mail for a person recipient: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 3. Click New, click Person in the Recipient Type dialog box, and then click OK.
VIM Mail dialog box
4. In the Name field, type the name of the recipient that you want to configure.
477
5. Click the VIM Mail tab and select the appropriate options as follows:
VIM Mail dialog box Item Enable Description Select this check box to activate this notification method for the recipient. Type the e-mail 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.
Address
Test
Schedule
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. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 3. Click New, click Person in the Recipient Type dialog box, and then click OK.
Pager dialog box
4. In the Name field, type the name of the recipient that you want to configure.
479
5. Click the Pager tab and select the appropriate options as follows:
Pager dialog box Item Enable 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 enter a page.
Carrier Phone
Country/region name and Enter the country or region name and country code in which the code pager is located. Pager Pin Type the pager identification number provided by the paging service provider. You will have a pin if you use TAP services and in most cases, the number is the last seven digits of the pagers phone number.
Advanced Pager setup options Advanced Enables you to configure additional settings for the pager. For more information about the options, see Advanced Pager Information dialog box on page 481. Enables you to test the notification configuration for the recipient.
Test
480
Configuring Recipients Pager dialog box (continued) Item Description
Schedule
6. 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 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. Description
Retrys
Pager type Numeric 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.
Alpha-numeric
481
Configuring Recipients Advanced Pager Information dialog box (continued) Item 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. Description
Data bits, Parity, Stop bit
7. Click OK to save the settings in the Advanced Pager Information dialog box, and then click OK to save the pager configuration settings. See also: Editing Recipient Notification Methods on page 489 Editing Recipient Notification Properties on page 489 Assigning Recipients to Alert Categories for Notification on page 491
Configuring a Net Send Recipient

You can configure Net Send to send notification messages to a target computer or user.
To configure a Net Send recipient: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 3. Click New, click Net Send in the Recipient Type dialog box, and then click OK.
482
Configuring Recipients Net Send Recipient Properties dialog box

Net Send Recipient Properties dialog box Item Name Description Type the recipient for whom you are configuring the notification.
Target Computer or User Type the name of the computer or user to whom you are sending Name 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. All Computers 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.
Test
483
Configuring Recipients Net Send Recipient Properties dialog box (continued) Item Description
Schedule
484
Configuring a Printer Recipient

You can select installed printers as a notification method for recipients; however, fax printer devices are not supported by Backup Exec. Only printers that were configured using the same username and password as the Backup Exec service account can be selected.
To configure a printer recipient: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 3. Click New, click Printer in the Recipient Type dialog box, and then click OK. 4. Click Printer, and then click OK.
Printer Recipient Properties dialog box
485

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
Schedule
Configuring a Group Recipient

Groups are configured by adding recipients as group members. A group contains one or more recipients and each recipient receives the notification message. Members of the group can be a combination of individual persons, computers, printers, or other groups.
To configure a group recipient: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 3. Click New, click Group in the Recipient Type dialog box, and then click OK.
Recipient Group Properties dialog box
4. In the Group Name field, type the group for whom you are configuring the notification. 5. 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. 6. 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.
487
7. When you have completed the group, click OK. The new group can be added to other groups. See also: Editing Recipient Notification Methods on page 489 Editing Recipient Notification Properties on page 489 Assigning Recipients to Alert Categories for Notification on page 491
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. Under the Limit when notifications can be sent group box, click Enable to activate the option. 2. Click Schedule.
Availability Schedule dialog box
3. Clear the Include work days check box to exclude Monday through Friday from 8 A.M. to 6 P.M. 4. Clear the Include weeknights check box to exclude Monday through Friday from 6 P.M. to 8 A.M. 5. Clear the Include weekends check box to exclude Saturday and Sunday, 24 hours a day.
6. You can select any combination of Include work days, Include weeknights, or Include weekends, or click any single hour of the chart to select or clear that hour. 7. After selecting the days and times you want, click OK.
Editing Recipient Notification Properties

You can edit the recipient notification properties at any time and change the recipient information, such as an e-mail address, telephone number or schedule.
To edit the recipient notification properties: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 3. Select the recipient you want to edit, and then click Properties. The Recipient Properties dialog box for the type of recipient you selected appears. 4. Edit the properties for the selected recipient. You can edit any of the properties except for the recipient name in the Name field. To modify the recipient name, you must create a new recipient, and then delete the old one. 5. Click OK.
Editing Recipient Notification Methods

You can configure new notification methods or edit existing notification methods after you configure recipients.
To edit notification methods: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Assign recipients to alert categories. The Alert Notification Setup dialog box appears.
489
3. Under Recipients, click Settings. The Notification Configuration Properties dialog box appears. 4. Edit notification properties for the following types of notification methods: SMTP Configuration. See SMTP Configuration dialog box on page 468. MAPI Configuration. See MAPI Configuration dialog box on page 469. VIM Configuration. See VIM Configuration dialog box on page 470. Pager Configuration. Click Enable to activate or clear the notification method, and then select a modem from the Configured Modems list.
5. Click OK.
Removing Recipients
You can delete recipients that do not want to receive notification messages; however, the recipient is permanently removed upon deletion. If you want to keep the recipient, but do not want the recipient to receive notifications, clear the Enable check box in the recipient properties.
To remove a recipient: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Configure recipients. The Alert Notification Setup dialog box appears. 3. Select the recipient you want to delete, and then click Remove.
490
Assigning Recipients to Alert Categories for Notification
Assigning Recipients to Alert Categories for Notification

You can assign recipients to alert categories to receive notification messages. When an alert occurs, all the recipients assigned to the alert category receive the notification message. You can also clear a recipient from an alert category and edit properties for the alert categories during the alert notification setup.
To assign a recipient to an alert category: 1. On the navigation bar, click Alerts and then under Views in the task pane, click Active alerts. 2. Under Notification Tasks in the task pane, click Assign recipients to alert categories.
Alert Notification Setup dialog box
3. Under Alert Categories, select the alert category to which you want to assign recipients. 4. 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. 5. Click OK.
491
Selecting Recipients for Job Notification
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.
To modify alert category properties: 1. Under Alert Categories, select the alert category you want to modify. You can select more than one alert category and the properties you modify will be applied to all the selected alert categories. 2. Click Properties. The Alert Category Properties dialog box appears. 3. Enter property information for the alert category. 4. Click OK. See also: Configuring Alert Category Properties on page 463 Configuring E-mail and Pager Notification Methods on page 467 Configuring Recipients on page 472

When you set up a new job, you can assign recipients to be notified when the job completes. You can also 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 e-mail or printer notification.
To select recipients for notification when you set up a job: 1. Determine the type of job for which you want to configure notifications. The job dialog box appears that enables you to select properties for the job. 2. On the Properties pane, click Notification. 3. Select the recipients you want to assign to the job.
492
4. If the recipient is using an e-mail or printer notification method, click Include job log with a notification to an e-mail or printer recipient. 5. You can start the job after configuring the notifications or select other options from the Properties pane.
To configure new recipients or edit recipient properties when you set up a job: 1. Determine the type of job for which you want to configure new recipients or edit recipient properties. The job dialog box appears that enables you to select properties for the job. 2. On the Properties pane, click Notification. 3. 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.
4. Enter or edit recipient properties for the following types of recipients: Person SMTP Mail. See SMTP Mail dialog box on page 473 MAPI Mail. See MAPI Mail dialog box on page 475 VIM Mail. See VIM Mail dialog box on page 478 Pager. See Pager dialog box on page 480
Net Send. See Net Send Recipient Properties dialog box on page 483 Printer. See Printer Recipient Properties dialog box on page 486 Group. Perform the following:
a. In the Group Name field, type the group for whom you are configuring the notification. b. 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. c. 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.
493
Configuring SNMP Notification
5. Click OK. 6. You can start the job after configuring the new recipients or edit recipient properties or select other options from the Properties pane. See also: Backing Up Data on page 233

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 VERITAS 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:
Trap Type Product Start
Object ID 1302.3.1.1.9.1
String 1 Backup Exec: Application initializing Backup Exec: Application terminating
String 2
String 3
String 4
machine name product, version, revision machine name product, version, revision local or remote Operator name
Product Stop
1302.3.1.1.9.2
Job Canceled
1302.3.1.2.8.2
Backup Exec: machine name job name Job canceled by Operator Backup Exec: Job failed machine name job name
Job Failed
1302.3.1.2.8.1
detail message
Storage device 1302.3.2.5.3.3 requires human intervention 494
Backup Exec: machine name job name Storage device requires attention
detail message
Trap Type
Object ID
String 1
String 2
String 3
String 4 detail message
Robotic library 1302.3.2.4.3.3 requires human intervention Intelligent Disaster Recovery Message Intelligent Disaster Recovery Message Backup Exec system error
Backup Exec: machine name job name robotic library device requires attention machine name job name
1302.3.1.4.2.1.1 Copy to alternate path failed
detail message
1302.3.1.4.2.1.2 Backup complete, update DR disks 1302.3.1.1.9.3
machine name job name
detail message
The machine name job name application has encountered an error Information on machine name job name normal events
detail message
Backup Exec general information Job Success
1302.3.1.1.9.4
detail message
1302.3.1.2.8.3
The job succeeded
detail message
Job Success with exceptions
1302.3.1.2.8.4
The job machine name job name succeeded, but there was a problem The job has started machine name job name
detail message
Job Started
1302.3.1.2.8.5
detail message
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
detail message
Job Warning
1302.3.1.2.8.7
detail message
495
Trap Type PVL Device Error
Object ID
String 1
String 2
String 3
1302.3.1.5.1.1.1 The device has machine name job name encountered an error 1302.3.1.5.1.1.2 The device has machine name job name encountered a warning 1302.3.1.5.1.1.3 Normal device machine name job name information 1302.3.1.5.1.1.4 Device requires attention 1302.3.1.5.2.1.1 There is an error with the media machine name job name
PVL Device Warning
detail message
PVL Device Information PVL Device Intervention
detail message
detail message
PVL Media Error
detail message
PVL Media Warning
1302.3.1.5.2.1.2 There may be a machine name job name problem with the media 1302.3.1.5.2.1.3 Normal media machine name job name information 1302.3.1.5.2.1.4 Media requires machine name job name attention 1302.3.1.5.3.1.1 There is an error with the catalog machine name job name
detail message
PVL Media Information PVL Media Intervention Catalog Error
detail message
detail message
detail message
Tape Alert Error Tape Alert Warning
1302.3.1.5.4.1.1 There is a machine name job name TapeAlert error 1302.3.1.5.4.1.2 There is a TapeAlert warning 1302.3.1.5.4.1.3 Normal TapeAlert information machine name job name
detail message
detail message
Tape Alert Information
detail message
496
Trap Type Database Maintenance Error
Object ID
String 1
String 2
String 3
1302.3.2.5.5.1.1 There is a database maintenance error 1302.3.2.5.5.1.2 Normal database maintenance information 1302.3.2.5.6.1.1 There is a software update error 1302.3.2.5.6.1.2 There is a software update warning 1302.3.2.5.6.1.3 Normal software update information
Database Maintenance Information
detail message
Software Update Error
detail message
Software Update Warning
detail message
Software Update Information
detail message
Install Update 1302.3.2.5.7.1.1 There is an machine name job name Warning install warning Install Update 1302.3.2.5.7.1.2 Normal Install machine name job name Information information
detail message
detail message
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 NT: 1. From the Control Panel, click Network. 2. Select the Services tab, and then click Add. 3. Install SNMP Service. 4. From the Network Services list, select SNMP Service, and then click Properties.
497
5. Click the Traps tab. 6. For Community Name, add PUBLIC. Consult your network administrator for the proper community name to use. 7. In the Trap Destination field, add the IP address of the SNMP console. Multiple IP addresses can be added. 8. Click OK. 9. Click Close. 10. Restart the computer. When the system restarts, it sends traps to the SNMP console. By checking the console for these traps, you can verify that the SNMP system service is configured correctly. Starting and stopping the system service Backup Exec Job Engine also causes traps to be sent.
To install the SNMP system service and configure it to send traps to the SNMP console for Windows 2000 and .NET: 1. Click Start, point to Settings, point to Control Panel, and then double-click Add/Remove Programs. 2. Click Add/Remove Windows Components. 3. In Add/Remove Windows Components, select Management and Monitoring Tools, and then click Details. When selecting the component, do not select or clear its check box.
498
Adding Windows Management Instrumentation Capability
4. Select Simple Network Management Protocol, and then click OK. 5. Click Next. SNMP starts automatically after installation. You must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. If your computer is connected to a network, network policy settings might also prevent you from completing this procedure. See also: Configuring Alert Category Properties on page 463

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. Note If you are using Windows NT 4.0, you must install WMI before you install the performance counter and SNMP providers.
To install the WMI performance counter provider: 1. Insert the Backup Exec Installation CD. 2. At the command prompt, type the following: mofcomp <CD Drive Letter>:\winnt\wmi\backupexecperfmon.mof
To install the WMI SNMP provider: Note Before you install the SNMP provider included with Backup Exec, you must have the Microsoft SNMP provider installed on your system. For more information, refer to your Microsoft documentation. 1. Insert the Backup Exec Installation CD. 2. At the command prompt, type the following: mofcomp <CD Drive Letter>:\winnt\wmi\snmp\eng\bkupexecmib.mof Note To use the WMI SNMP provider you must set up SNMP notification.
499
Uninstalling WMI Providers
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
500
Reports
10
Reports
Backup Exec includes 13 standard reports that enable you to generate reports that show detailed information about your system. 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. 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. The Backup Exec Admin Plus Pack Option provides an additional 24 reports and advanced reporting capabilities such as scheduling and notification. See also: Running a Report on page 503 Running and Viewing a New Report Job on page 506 Available Reports on page 513 Advanced Reporting Capabilities on page 832
501
Viewing Reports
Viewing Reports
Reports are generated using Crystal Reports and can be viewed and printed in an HTML file format. If the Adobe Acrobat Reader is detected by Backup Exec, reports are displayed in Adobe Portable Document Format (PDF). To go to a web site to download the Adobe Acrobat Reader, on the Help menu, click Adobe Acrobat Web Site. 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:
On the navigation bar, click Reports.
The Reports pane lists the name, a description, and a category for each report. You can sort the reports in alphabetical or reverse alphabetical order by clicking Name.
Available Reports
See also: Running and Viewing a New Report Job on page 506 Viewing Report Properties on page 512 Available Reports on page 513
502
Running a Report
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 parameters available for you to select depend on the type of data that can be included in the report. After the report is generated, only the items that match the criteria appear in the report.
To run a report: 1. On the navigation bar, click Reports. 2. On the Reports pane, select the report you want to run.
Reports
3. Under Report Tasks in the task pane, click Run report now. 4. In the Filters tab, select the appropriate filter parameters for the data you want to include in the report. If filter parameters are not available for a report, you will not be able to select the parameter. Select the appropriate options as follows:
Report filters Item Media set Description Filters the report based on media set names. Media sets include all the media that is inserted into the storage device. For more information on media sets, see Media Categories on page 190. Filters the report based on job priorities. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Available priorities include: Highest High Medium Low Lowest Media server Filters the report based on media server names. The media server is the server on which Backup Exec 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. 503
Job priority
Job status Protected server
Chapter 10, Reports
Running a Report Report filters (continued) Item Vault Description Filters the report based on specific vault names. A media vault is a virtual representation of the actual physical location of media. For more information on media vaults, see Media Location on page 209.
5. Click the Ranges tab 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:
Report ranges Item Days Description Select this check box to enable the date filter.
Number of days before Type the number of days prior to the current day to begin the filter day report runs 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. Select this check box to enable the hours filter. 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. 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.
Hours Number of hours within time report
Event count Maximum number of events to include
Note Entering a value of zero for the range parameter does not limit the amount of data included in the report; this can result in an extensive report.
504
Running a Report
6. Click Run report. The report appears and displays data based on the criteria you set when you ran the report. 7. To save the report, click Save As; for a report in PDF, click the Save a Copy icon. When prompted, enter the file name and location where you want to save the report and then click Save. The report is saved in the location you specify. Backup Exec also creates a folder, with the same name as the report, in the same location in which the report is saved. The folder contains images and report pages that enable you to view the saved report. 8. 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.
Reports
Note If all the data does not print in an HTML-formatted report, you may need to edit the page setup for the report. To edit the page setup, open Microsoft Internet Explorer, and then on the File menu, click Page Setup. Under Header and Footers, delete the Header and Footer and then under Margins, set the Left and Right margins to the minimum setting that your printer will accept. 9. After you have finished viewing the report, click OK. The report will automatically be deleted. See also: Viewing Report Properties on page 512 Available Reports on page 513
Chapter 10, Reports
505
Running and Viewing a New Report Job

You can create a report job that saves the report data in the Job History. You can specify filters and ranges and select recipients for notification; however, the report is not included in the notification. Report jobs run immediately and you cannot specify a schedule. After the report is generated, you can view the completed report and job history in the Job Monitor. The report data will also be saved in the Backup Exec database. The Admin Plus Pack Option enables you to perform advanced report tasks such as scheduling a report job and including the report in a notification.
To run a new report job: 1. On the navigation bar, click Reports. 2. On the Reports pane, select the report for which you want to run a job. 3. Under Report Tasks in the task pane, click New report job.
New Report Job dialog box
4. On the Properties pane, under Settings, click General and then type the name for the job in Job name and select the Job priority. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first.
5. On the Properties pane, under Settings, click Filters, and then select the appropriate filter parameters for the data you want to include in the report. If filter parameters are not available for a report, you will not be able to view the parameters. Select the appropriate options as follows.
Report filters Item Media set Description Filters the report based on media set names. Media sets include all the media that is inserted into the storage device. For more information on media sets, see Media Categories on page 190.
Reports
Job priority
Filters the report based on job priorities. The job priority determines which job runs first. Available priorities include: Highest High Medium Low Lowest
Media server
Filters the report based on media server names. The media server is the server on which Backup Exec 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. For more information on media vaults, see Media Location on page 209.
Job status Protected server
Vault
Chapter 10, Reports
507
6. On the Properties pane, under Settings, click Ranges and select the appropriate range parameters for the data you want to include in the report. If range parameters are not available for a report, you will not be able to select the parameter. Select the appropriate options as follows
Report ranges Item Days Description Select this check box to enable the date filter.
Number of days before Type the number of days prior to the current day to begin the filter day report runs 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. Select this check box to enable the hours filter. 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. 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.
Hours Number of hours within time report
Event count Maximum number of events to include
Note Entering a value of zero for the range parameter does not limit the amount of data included in the report; this can result in an extensive report. 7. On the Properties pane, under Settings, click Notification and enter notification information for the items. For more information, see Selecting Recipients for Job Notification on page 492. When the notification is sent to the recipient, the report is not included.
508
8. On the Properties pane, under Frequency, click Schedule and then click Submit job on hold if you want to submit the job with an on-hold status. Select this option if you want to submit the job, but do not want the job to run until you change the jobs hold status. 9. Click Enable automatic cancellation, and then type the number of hours or minutes in the Cancel job if not completed within option. Select this option if you want to cancel the job if is not completed within the selected number of hours or minutes. Backup Exec starts timing the length of time the job takes to run when the job actually begins, not the scheduled time. 10. After you have completed all the items you want to set for the new report job, click Run Now. The report is submitted according to the options you selected. Note If you are using BEWAC, click Next to submit the report to the job queue. After viewing the job summary, click Finish.
Reports
To view the report in the Job History: 1. On the navigation bar, click Job Monitor. 2. On the Job History pane, select the report you want to view. 3. Under General Tasks in the task pane, click Properties. The report and job history appear and display data based on the criteria you selected when you set up the job. 4. Click Job History to view detailed information about the job or Report to view the contents of the report.
Chapter 10, Reports
509
5. 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.
Note If all the data does not print in an HTML-formatted report, you may need to edit the page setup for the report. To edit the page setup, open Microsoft Internet Explorer, and then on the File menu, click Page Setup. Under Header and Footers, delete the Header and Footer and then under Margins, set the Left and Right margins to the minimum setting that your printer will accept. 6. After you have finished viewing the report, click OK. The report is saved for the length of time you set in the database maintenance option.
To save the report to a new location: 1. On the navigation bar, click Job Monitor. 2. On the Job History pane, right-click the report you want to save. 3. Click Save As. The Save As dialog box appears. 4. 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.
510
To delete the report from Job History: 1. On the navigation bar, click Job Monitor. 2. On the Job History pane, select the report you want to delete. 3. Under General Tasks in the task pane, click Delete. 4. Confirm the job deletion. The report and associated job history are deleted. See also:
Reports
Configuring Database Maintenance on page 389 Viewing Completed Jobs on page 378 Available Reports on page 513 Advanced Reporting Capabilities on page 832
Chapter 10, Reports
511
Viewing Report Properties
Viewing Report Properties

Report properties provide detailed information about each report. The properties can be viewed, but not edited.
To view a report: 1. On the navigation bar, click Reports. 2. On the Reports pane, select the report for which you want to view properties. 3. Under Report tasks in the task pane, click Properties. The Report dialog box provides the following information:
Report Properties Item Title Description Category Description The name of the report. Describes the type of data that is included in the report. Classification for the report. Available report categories include: Media Media Vault Jobs Devices Configuration Alerts Template 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 location of the report. The size of the report. The date the report was installed on the system.
512
Available Reports
4. Click OK after you have finished viewing the properties. See also: Running a Report on page 503
Available Reports
This section provides detailed information about each report available in Backup Exec. The file name of the report, a description, and the information included in the report are listed for each report. The data included in each report will vary depending on the criteria you selected to include in the report. The following reports are included in Backup Exec:
Backup Exec Reports Report Name Active Alerts Description Lists all active alerts chronologically, displaying the most recent alerts first (see Active Alerts Report on page 515). Lists all alerts in the alert history chronologically, displaying the most recent alerts first (see Alert History Report on page 515). Lists the contents of the audit logs for selected servers for the specified time period (see Audit Log Report on page 517)
Reports
Alert History
Audit Log
Backup Sets by Media Set Lists all backup sets by media set (see Backup Sets by Media Sets Report on page 517). Configuration Settings Lists the contents of the Backup Exec system configuration parameters table (see Configuration Settings Report on page 518). Lists device usage and error summary for each selected media server (see Device Summary Report on page 519). Lists all the defined error-handling rules (see Error-Handling Rules Report on page 521). Lists all Backup Exec and other system and application event logs (see Event Logs Report on page 522). 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 523).
Device Summary
Error Handling Rules
Event Logs
Media Set
Chapter 10, Reports
513
Available Reports Backup Exec Reports (continued) Report Name Media Vault Contents Description Lists the media located in each media vault (see Media Vault Contents Report on page 524). Lists past and future operations data for user-set period (see Operations Overview Report on page 525). 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 526).
Operations Overview
Robotic Library Inventory
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 527). 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 528).
See also: Running a Report on page 503 Running and Viewing a New Report Job on page 506 Viewing Report Properties on page 512
514
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.
Active Alerts Report Item Time Media Server Job Name Device Name Category Message 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.
Reports
See also: Running a Report on page 503 Running and Viewing a New Report Job on page 506
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 Event count. Information displayed in the Active History report is described in the following table.
Alert History Report Item Time Received Description Date and time the alert occurred. Time the alert occurred.
Chapter 10, Reports
515
Available Reports Alert History Report (continued) Item Responded Responding User Job Name Media Server Category Message Description 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.
516
Available Reports
Audit Log Report

The Audit Log report lists the contents of the audit logs for the selected servers for the selected time period. You can limit the amount of data that appears in the report by entering filter parameters for the Media server option and range parameters for the Days and Event count options. Information displayed in the Audit Log report is described in the following table.
Audit Log Report Item Media Server Category Description
Reports
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. Description of the change made in Backup Exec. User that made the change.
Date Entered Message User Name
Backup Sets by Media Sets Report

The Backup Sets by Media Sets report lists all the backup sets by media set. You can limit the amount of data that appears in the report by selecting filter parameters for the Media Set option. Information displayed in the Backup Sets by Media Sets report is described in the following table.
Backup Sets by Media Sets Report Item Media Set Set Description Name of the media set on which the job ran. Sequential number for backup sets on the media.
Chapter 10, Reports
517
Available Reports Backup Sets by Media Sets Report (continued) Item Method Description Specific type of backup. For more information on backup methods, see Understanding Backup Methods and Their Advantages on page 340. Date and time the data was backed up.
Date / Time
Backup Set Description Describes the data that was backed up and the location of the data. / Source Directories Files MB Media Label Number of directories backed up. Number of files backed up. Amount of data backed up in megabytes. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label.
Configuration Settings Report

The Configuration Settings Report lists the contents of the Backup Exec system configuration parameters table. Information displayed in the Configuration Settings report is described in the following table.
Configuration Settings Report Item Parameter Name Class Description Name of the Backup Exec configuration parameter. Parameters that are associated with the Backup Exec system.
518
Available Reports Configuration Settings Report (continued) Item Value Description Value of the configuration parameter. Note The StoreMaintenanceLastrun and StoreMaintenanceRuntime parameters display the date and time in Greenwich Mean Time (GMT).
Reports
Device Summary Report

The Device Summary report lists all the devices for each selected media server. You can limit the amount of data that appears in the report by selecting filter parameters for the Media server option. Information displayed in the Device Summary report is described in the following table.
Device Summary Report Item Server Device Name 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. 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.
Drive Name Vendor/Product ID
SCSI Target State Created Cleaned
Chapter 10, Reports
519
Available Reports Device Summary Report (continued) Item Post Cleaning Totals Hours Errors MB Mounts Totals Hours Errors MB Mounts Total number of hours the device has been in use. Total number of errors occurring on the device. Total number of megabytes written to the device. Total number of mounts occurring to the device. Hours the device has been in use since the last cleaning job. Number of errors occurring since the last cleaning job. Megabytes written since the last cleaning job. Number of mounts occurring since the last cleaning job. Description
520
Available Reports
Error-Handling Rules Report

The Error-Handling Rules report lists all error-handling rules and provides details about each rule. Information displayed in the Error-Handling Rules report is described in the following table.
Error Handling Rules Report Item Error Handling Rule Name Description Description Name of the Error-Handling rule.
Reports
Information entered in the Notes section when the error-handling rule was created. Final job status that activates the rule. Possible statuses are: Error Canceled
Job Status
Error Code
The category of error for which the rule will be applied. Available error categories include: Device Job Media Network Other Resource Security Server System
Hold Device
Displays an X if this option is selected for the error-handling rule. The option holds all jobs for the device 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.
Pause Job
Retry Job
Chapter 10, Reports
521
Available Reports Error Handling Rules Report (continued) Item Maximum Retries Postpone Retries (minutes) Description Number of times the job is to be retried. Number of minutes the job is to wait before being retried.
Event Logs Report

The Event Logs report lists all Backup Exec and other system and application event logs. Information displayed in the Event Logs report is described in the following table.
Event Logs Report Item Server Number Event Date Time Source Description Description Name of the server on which the event occurred. The number assigned to the event in the Windows Event log. The type of event that occurred. Date the event occurred. Time the event occurred. The source from which the event originated. Message displayed for the event.
522
Available Reports
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. Information displayed in the Media Set report is described in the following table.
Media Set Report Item Media Set Media Label 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.
Reports
Media Type Allocated
Modified Location Totals Hours Mounts Soft Errors Hard Errors Write MB Current MB
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.
Chapter 10, Reports
523
Available Reports
Media Vault Contents Report

The Media Vault Contents report lists all the media in a specified media vault. You can limit the amount of data that appears in the report by selecting filter parameters for the Vault option. Information displayed in the Media Vault Contents report is described in the following table.
Media Vault Contents Report Item Media Vault Media Label Description Location of the media. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Total number of media contained in the media vault.
Media Total
524
Available Reports
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 option. Information displayed in the Operations Overview report is described in the following table.
Operations Overview Item Description
Reports
Job summary for jobs Details Backup Exec job activity for the specified time period. completed in the past x Hours Completed (Canceled) Completed (Failed) Completed (Success) Exceptions 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.
Media Total Total Size (MB)
Alerts summary for active alerts Errors Warnings Information Attention Required Media Availability Scratch Media Overwritable Media Total number of scratch media available. Total number of overwritable media available. 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.
Chapter 10, Reports
525
Available Reports Operations Overview (continued) Item Appendable Media Recyclable Media Job Status Description Total number of appendable media available. Total number of recyclable media available. Displays the job status.
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.
Robotic Library Inventory Report Item Server Device Name Slot Media Label 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.
State
Modified Write MB
526
Available Reports Robotic Library Inventory Report (continued) Item Full Description 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.
Hours Mounts Append
Reports
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. Information displayed in the Scratch Media Availability report is described in the following table.
Scratch Media Availability Report Item Category Media Label 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.
Chapter 10, Reports
527
Available Reports Scratch Media Availability Report (continued) Item Size (MB) Available to Append (GB) Group Total Media Total Description Capacity of the scratch media available to which data can be written. Capacity of scratch media available for append.
Total number and capacity of scratch media available to the system. Total number of scratch media available.
Test Run Results Report

The Test Run Results report displays the results for the test run jobs set for the selected period and the selected media servers. You can limit the amount of data that appears in the report by selecting filter parameters for the Media server option and range parameters for the Hours option. Information displayed in the Test Run Results report is described in the following table.
Test Run Results Item Media Server Description Name of the media server on which the job ran.
Job Date and Time Run Date and time the backup job was processed. Job Name The name of the test run job.
Media Capacity Summary Media Type Max Needed Type of media used, such as 4mm. Amount of space needed on the media to run the job.
528
Available Reports Test Run Results (continued) Item Available to Append, MB Online Capacity of media available in the device to which data can be appended. Total amount of appendable media available to the system. Description
Media Total
Available to Overwrite, MB
Reports
Online Media Total
Capacity of media available in the device to which data can be written. Total amount of overwritable media available to the system.
Chapter 10, Reports
529
Available Reports
530
Disaster Preparation and Recovery
11
Disaster preparation planning is the implementation of strategies and procedures that will minimize damage in the event a catastrophe destroys your data. While precautions can be taken to minimize the effects of this type of occurrence (UPS devices, password protection, and so forth), unfortunately there is nothing that can safeguard your data 100 percent. The purpose of a Disaster Preparation Plan (DPP) is to return to an operational status as quickly as possible. Backup Exec is a crucial component of the DPP and this section discusses how to apply this powerful data management tool to your DPP. There are two basic methods available for disaster recovery:

Disaster Preparation
Manual recovery. This section provides procedures for manually recovering both local and remote Windows .NET/XP/2000/NT computers. Automated recovery. Backup Execs Intelligent Disaster Recovery (IDR) option automates the disaster recovery process for Windows .NET/XP/2000/NT computers. IDR is an option you must purchase separately.
See also: VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 Disaster Preparation of the Windows Computer on page 533 Manual Disaster Recovery of Windows Computers on page 540
531
Key Elements of a Disaster Preparation Plan (DPP)
Key Elements of a Disaster Preparation Plan (DPP)

The DPP you put in place with your Backup Exec system should be tailored to your network environment. While environments vary in different organizations, there are five elements to consider when creating a comprehensive DPP.
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 sound backup strategy. A well-designed backup strategy that includes a strong media rotation scheme plays a key role in quickly restoring your file server. Off-site storage of backups. 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. Effective DPP management. 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. 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.
See also: Selecting Data to Back Up on page 259
532
Disaster Preparation of the Windows Computer

In a disaster recovery situation, always try the simplest steps first. Using this approach, the greatest amount of information is recovered with the least amount of impact on the users and the network. The following sections detail simple solutions and more complex procedures for getting your Windows computer up and running again. See also: Creating an Emergency Repair Disk on page 535 Manual Disaster Recovery of Windows Computers on page 540
Returning to the Last Known Good Menu

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 NT and Windows 2000/XP/.NET computers. This section includes procedures for each type of computers. Note Any changes made to the system since the last time the configuration was saved are lost.
To return to a previous configuration: 1. Reboot the system. 2. For a Windows NT system, press the spacebar during the startup. The Hardware Profile/Configuration Recovery menu appears, which allows you to boot using a previous configuration. For other Windows systems, press <F8> during startup. A menu appears that allows you to diagnose and fix system startup problems.
Chapter 11, Disaster Preparation and Recovery
533
3. Select one of the following options: Safe Mode. This option allows you to diagnose and fix system startup problems. For more information, see your Microsoft documentation. Last Known Good Configuration. This option allows you to return to a previous saved configuration.
See also: Creating a Hardware Profile Copy on page 534 Creating an Emergency Repair Disk on page 535 Creating and Using an Emergency Boot Diskette on page 537
Creating a Hardware Profile Copy

Before making a major hardware change, copy the current hardware profile to a new hardware profile and boot into the new profile before adding or changing the hardware. This way, you can return to the previous configuration if something does not work properly.
To create a copy of the current hardware profile and make that the preferred boot option: 1. Right-click the My Computer icon. 2. Click Properties to display the System Properties dialog box. 3. Click Hardware. 4. Click Hardware Profiles. 5. Select the current hardware profile, and then click Copy. 6. Type the name for the new configuration in the To field, and then click OK. 7. To make the new profile the preferred boot option, select it, and then click the up arrow next to the list box to move the new hardware profile to the top of the box.
534
8. Choose whether Windows is to use the new hardware profile automatically (after a delay) during startup, or if the system should wait indefinitely until the hardware profile is chosen by selecting the appropriate option. 9. Click OK. The new configuration is saved, and the startup options are set. See also: Returning to the Last Known Good Menu on page 533 Creating an Emergency Repair Disk on page 535 Creating and Using an Emergency Boot Diskette on page 537
Creating an Emergency Repair Disk

When Windows NT or 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 .NET, 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.
535
To create the ERD for Windows NT: 1. Insert a disk into the A: drive. 2. From the Start menu, click Run. 3. Type rdisk, and then click OK to display the Repair Disk Utility dialog box. To back up the user account and file security, add a /S parameter after the rdisk command: rdisk /s This bypasses the initial screen and its confirmation step and directly updates the repair directory information (steps 4 and 5). After the current configuration has been saved, you are prompted to make the ERD (see step 6). 4. Click Update Repair Info. 5. Click Yes to update the repair information. Running rdisk overwrites any previously saved information. When updating after a major change, skip this step until the change has been verified as stable and desirable. Click No to skip. After the repair information has been updated, the system prompts you to create an Emergency Repair Disk. 6. Click Yes to make the disk. 7. Store the disk in a safe and secure place.
To create the ERD for Windows 2000: Note You must not change or delete the systemroot\repair folder because the repair process relies on information saved in this folder. 1. Click Start, point to Programs, and then to Accessories. 2. Point to System Tools, and then click Backup. 3. On the Tools menu, click Create an Emergency Repair Disk.
536
4. Insert a disk into the A: drive and follow the instructions. Note 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. See also: Returning to the Last Known Good Menu on page 533 Creating a Hardware Profile Copy on page 534 Creating and Using an Emergency Boot Diskette on page 537
Using Windows Automated System Recovery and System Restore to Recover a Windows XP or Windows .NET System
The ASR feature, which replaces the Emergency Repair Disk for Windows XP and Windows .NET, allows you to restore the operating system to a previous state so that you can start Windows XP Professional or Windows .NET when other recovery methods do not work. Microsoft recommends using System Restore, which saves only incremental changes, or shadow copies, 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.
Creating and Using an Emergency Boot Diskette

Tip If the system will not boot, use the Windows installation disks to boot it or use an Emergency boot diskette, which is a quicker way of getting the system up and running. After booting from the Emergency boot diskette, go directly into the existing Windows partition, even if a critical file in the system partition has been deleted or corrupted.
Instructions are provided for creating Emergency boot diskettes on the following types of systems:

x86 systems (see To create an Emergency boot diskette (x86 version): on page 538) RISC-based systems (see To create an Emergency boot diskette (RISC Version): on page 538) Mirrored boot partitions (see To create an Emergency boot diskette (Mirrored boot partition): on page 539)
537
Note The boot diskette is NOT generic for every Windows machine. If there is a fairly standard configuration across several machines, however, this disk will work. For example, it will work for all systems that use the same partition and disk controller as their Windows boot partition.
To create an Emergency boot diskette (x86 version): 1. Format a diskette (the diskette must be formatted under Windows). 2. Copy the following files to the diskette from the root directory of the system partition: BOOT.INI NTBOOTDD.SYS (if present) NTDETECT.COM NTLDR
The file NTBOOTDD.SYS is present only if a SCSI controller exists that does not use its BIOS to control the boot process. If NTBOOTDD.SYS is not on the boot partition, it is not needed.
To create an Emergency boot diskette (RISC Version): 1. Format a diskette (the diskette must be formatted under Windows). 2. Copy the following files to the diskette from the root directory of the system partition: OSLOADER.EXE HAL.DLL
On RISC based systems, the information stored in nonvolatile RAM is the equivalent of the information stored in the BOOT.INI file on an x86-based computer. You must modify the boot selection menu to add an option that points to the floppy disk. The Advanced RISC Computing (ARC) name used for the SYSTEM-PARTITION on the floppy disk is: scsi(0)disk(0)fdisk(0) Set the necessary values for: OSLOADER: the pointer to the floppy drive that was just created. OSLOADPARTITION: the primary partition (unless there are mirrored boot partitions, in which case point to the secondary mirror partition). OSLOADFILENAME: the path to the \SYSTEMROOT directory.
538
To create an Emergency boot diskette (Mirrored boot partition): 1. Format a diskette (the diskette must be formatted under Windows NT/2000). 2. Copy the following files to the diskette from the root directory of the system partition: NTLDR NTDETECT.COM NTBOOTDD.SYS (if present) BOOT.INI
The file NTBOOTDD.SYS is present only if a SCSI controller exists that does not use its BIOS to control the boot process. If NTBOOTDD.SYS is not on the boot partition, it is not needed. 3. For an Intel x86 processor, edit the BOOT.INI file on the floppy disk to change the ARC name on the boot partition so that it points to the secondary mirror partition rather than to the primary boot partition. For example, if there are a pair of Adaptec 2940 adapters and duplexes boot drives using the SCSI BIOS to boot off the primary partition on the first hard disk, there might be a line similar to this in the BOOT.INI: multi(0)disk(0)rdisk(0)partition(1)\NTS40=Windows NT Server 4. Change the line to the following: multi(1)disk(0)rdisk(0)partition(4)\NTS40=Windows NT Server
539
Manual Disaster Recovery of Windows Computers

Note If your system is protected by Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR), see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 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 NT computer (see Disaster Recovery of a Local Windows NT Computer on page 541) Remote Windows NT computer (see Disaster Recovery of a Remote Windows NT Computer on page 543) Local Windows 2000 computer - non-authoritative (see Disaster Recovery of a Local Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) on page 546) Remote Windows 2000 computer - non-authoritative (see Disaster Recovery of a Remote Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) on page 549)
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:

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 containing the Windows operating system needs to be replaced.
540
Disaster Recovery of a Local Windows NT Computer

Note If your system is protected by Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR), see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 for information on automated disaster recovery. The procedure described in the following section allows you to manually recover a computer not protected by IDR. 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 database agents. If any of your data is protected by Backup Exec agents, see Backup Exec Options on page 36 before beginning disaster recovery. A media drive must be attached to the computer that is being recovered. You will also need:

A current full backup of the computer to be recovered and any subsequent incremental/differential backups. The Windows NT installation media.
The Backup Exec for Windows Servers installation media.
To recover a local Windows NT computer: 1. Install Windows NT. Note You must also install Windows NT Service Pack 5 or higher. This basic Windows NT installation is necessary to provide Backup Exec with a target to which it can restore the system. This basic installation will later be overwritten by the backed up version, which will restore your system configuration, application settings, and security settings, including the Registry. For this basic Windows NT installation: Use the same computer name. Use a workgroup (not a domain).
This will allow you to recover your original Security Information Descriptor (SID) through Backup Exec, so you will not have to re-establish trust relationships with all domains. If you are recovering from an entire hard disk failure, use Windows NT setup to partition and format the new disk during installation. Format the partitions with the same file system as before the failure.
541
2. Install Backup Exec for Windows Servers to a directory other than where it was originally installed (this is a temporary installation). Note Always log on to Windows NT using the Administrator account or its equivalent during this procedure. 3. Using the Device Driver Installation Wizard, install the appropriate device driver for the attached media drive. For more information, see First Time Startup Wizard on page 74. 4. Reboot the computer to load the device driver. 5. Start Backup Exec for Windows Servers. 6. On the navigation bar, click Devices. 7. Inventory the media containing the latest full backup of the computer to be recovered (see Inventorying Media in Devices on page 165). 8. Catalog the media containing the latest full backup of the computer to be recovered (see Cataloging Media in a Drive on page 397). If the subsequent differential/incremental backups are on separate media, catalog those also. 9. On the navigation bar, click Restore. 10. On the Properties pane, under Source, click Selections, 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. 11. On the Properties pane, under Settings, click General, and then select the following options: Restore over existing files Restore security Preserve tree
12. On the Properties pane, under Settings, click Advanced, and then select the following options: Restore Windows NT 4.0 registry Overwrite the existing hardware configuration and registry services with data to be restored
542
Note If you use a different computer name, on the Properties pane, under Destination, click File Redirection, and then redirect each restore job to the new destination. 13. Click Run Now to start the restore. 14. After the restore completes, reboot the 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. See also: Creating a Manual Restore Job by Configuring Job Properties on page 404 Disaster Recovery of a Remote Windows NT Computer on page 543 Disaster Recovery of a Local Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) on page 546
Disaster Recovery of a Remote Windows NT Computer

Note If your system is protected by Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR), see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 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 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 database agents. If any of your data is protected by Backup Exec database agents, see Backup Exec Options on page 36 before beginning disaster recovery. You will need:

A current full backup of the computer to be recovered and any subsequent incremental/differential backups. The Windows NT installation media.
Note Always log on to Windows NT using the Administrator account or its equivalent during this procedure.
543
To recover a remote Windows NT computer: At the remote computer: 1. Install Windows NT. Note You must also install Windows NT Service Pack 5 or higher. This basic Windows NT installation is necessary to provide Backup Exec with a target to which it can restore the system. The basic installation will later be overwritten by the backed up version, which will restore your system configuration, application settings, and security settings, including the Registry. For this basic Windows NT installation: Use the same computer name. Use a workgroup (not a domain).
This will allow you to recover your original Security Information Descriptor (SID) through Backup Exec, so you will not have to re-establish trust relationships with all domains. If you are recovering from an entire hard disk failure, use Windows NT setup to partition and format the new disk during installation. Format the partitions with the same file system as before the failure. At the media server: 2. Start Backup Exec for Windows Servers. 3. Inventory the media containing the latest full backup of the computer to be recovered (see Inventorying Media in Devices on page 165). 4. 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 in a Drive on page 397). 5. From the navigation bar, click Restore. 6. 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. 7. On the Properties pane, under Settings, click Advanced and make sure the Restore Windows NT 4.0 registry option is cleared.
544
8. On the Properties pane, under Settings, click General, and select the following options: Restore over existing files Restore security Preserve tree
Note If you use a different computer name, you must go to the File Redirection dialog box and redirect each restore job to the new computer name and share (see Redirecting a Restore Operation on page 436). 9. Click Run Now. At the remote computer: 10. When the restore operation has completed, reboot the remote computer. All files have now been restored. You must now restore the Windows NT Registry. At the media server: 11. Start Backup Exec for Windows Servers. 12. From the navigation bar, click Restore. 13. Select only the directory \<SystemRoot>\System32\Config from the last restored backup set. 14. On the Properties pane, under Settings, click General, and select the following options: Restore over existing files Restore security Preserve tree
15. On the Properties pane, under Settings, click Advanced, and then select the following options: Restore Windows NT 4.0 registry Overwrite the existing hardware configuration and registry services with data to be restored
545
16. Click Run Now. At the remote computer: 17. When the restore operation has completed, reboot the remote computer using the restored Windows NT system. 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. See also: Creating a Manual Restore Job by Configuring Job Properties on page 404 Disaster Recovery of a Local Windows NT Computer on page 541 Disaster Recovery of a Remote Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) on page 549 Disaster Recovery of a Local Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) on page 546 Manual Disaster Recovery of Windows Computers on page 540
Disaster Recovery of a Local Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller)
Note If your system is protected by Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR), see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 for information on automated disaster recovery. The procedure described in the following section allows you to manually recover a computer not protected by IDR. 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 database agents. If any of your data is protected by Backup Exec agents, see Backup Exec Options on page 36 before beginning disaster recovery. A media drive must be attached to the computer that is being recovered. You will also need:

A current full backup of the computer to be recovered and any subsequent incremental/differential backups. The Windows 2000/XP/.NET installation media. The Backup Exec for Windows Servers installation media.
546
To recover a local Windows 2000/XP/.NET computer: 1. Install Windows 2000/XP/.NET. 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. Do not join a domain; leave the computer in a Workgroup. Do not install Active Directory. 2. Install Backup Exec for Windows Servers to a directory other than where it was originally installed (this is a temporary installation). Note Always log on to Windows using the Administrator account or its equivalent during this procedure. 3. Using the Device Driver Installation Wizard, install the appropriate device driver for the attached media drive. For more information, see First Time Startup Wizard on page 74. 4. Start Backup Exec for Windows Servers. 5. From the navigation bar, click Devices. 6. Inventory the media containing the latest full backup of the computer to be recovered (see Inventorying Media in Devices on page 165). 7. Catalog the media containing the latest full backup of the computer to be recovered (see Cataloging Media in a Drive on page 397). If the subsequent differential/incremental backups are on separate media, catalog those also. 8. From the navigation bar, click Restore. 9. Select all sets from the full and incremental backups that contain logical drives on the hard disk. If differential backup sets are to be restored, select only the last differential set. Make sure you include System State as part of the restore selections.
547
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 412). 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 its pre-disaster state. Your data files have been restored, except those protected by Backup Exec database agents. See also: Creating a Manual Restore Job by Configuring Job Properties on page 404 Disaster Recovery of a Local Windows NT Computer on page 541 Disaster Recovery of a Remote Windows NT Computer on page 543 Disaster Recovery of a Remote Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) on page 549 Manual Disaster Recovery of Windows Computers on page 540
548
Disaster Recovery of a Remote Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller)
Note If your system is protected by Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR), see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 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 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 Options on page 36 before beginning disaster recovery. You will need:

A current full backup of the computer to be recovered and any subsequent incremental/differential backups. The Windows 2000/XP/.NET installation media.
Note Always log on to Windows using the Administrator account or its equivalent during this procedure.
To recover a remote Windows 2000/XP/.NET computer: At the remote computer: 1. Install Windows 2000/XP/.NET. 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. Do not join a domain; leave the computer in a Workgroup. Do not install Active Directory.
549
At the media server: 2. Install the Backup Exec Remote Agent to the remote computer. For more information, see Installing the Remote Agent to Remote Windows Servers on page 823. 3. Start Backup Exec for Windows Servers. 4. From the navigation bar, click Devices, and then inventory the media containing the latest full backup of the computer to be recovered (see Inventorying Media in Devices on page 165). 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 in a Drive on page 397). 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 as part of the restore selections. 7. On the Properties pane, under Settings, click General, and then select the following options: Restore over existing files Restore security Preserve tree
8. On the Properties pane, under Settings, click Advanced, and then select the appropriate options (see Advanced options for restore on page 412). 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.
550
9. Click Run Now. 10. After the job completes, reboot 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. See also: Creating a Manual Restore Job by Configuring Job Properties on page 404 Disaster Recovery of a Local Windows NT Computer on page 541 Disaster Recovery of a Remote Windows NT Computer on page 543 Manual Disaster Recovery of Windows Computers on page 540
551
552
Troubleshooting
12
This section provides information about hardware, backup, restore, and error messages. It also includes answers to questions about versions, builds, and product updates, along with answers to common questions about drives, device drivers, changers, storage devices, tape drives, and hardware errors. Note For more information, the VERITAS web site provides an updated list of Frequently Asked Questions (FAQs), release notes, and a technical knowledge base for each product.
General Questions
How can I determine version and build information for my Backup Exec installations? Locally, the version and build information can be located by selecting the About Backup Exec option from the Help menu. Using ExecView, the versions of remote installations of Backup Exec can be determined by viewing the properties of each remote server. How do I update Backup Exec from an evaluation copy to a serialized copy? Obtain a serial number for Backup Exec from your software vendor. Run the Backup Exec installation program to re-install the software on top of your evaluation copy and enter the serial number when prompted. De-select all installation options - it will prompt that no items have been selected to be installed. All configuration and backup information from the evaluation copy will be retained in the serialized copy. Only the serial number information will be updated in the registry. 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 not? After setting up bar code rules, you must set up two more items 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
Troubleshooting
553
General Questions
your mixed media library you should indicate what type of media can be used and whether that media can be used for read or write operations. For more information, see Bar Code Labeling in Mixed Media Libraries on page 199. How do I use Backup Execs diagnostic utility, BEDIAG.EXE? Using Backup Execs Diagnostic Utility BEDIAG Backup Exec includes a diagnostic application (BEDIAG.EXE) that gathers information about a Windows NT, Windows 2000, or .NET computer for troubleshooting purposes. This application is located in the Backup Exec for Windows Servers directory on your hard drive (by default, \Program Files\VERITAS\Backup Exec\NT). The basic syntax for BEDIAG is BEDIAG COMPUTERNAME, which will query the selected Windows server and place the contents in a file called bediag.txt. Please use BEDIAG before calling technical support so that you can quickly answer any questions they may ask. To see other BEDIAG options, type BEDIAG /?. The type of information collected in the bediag.txt file includes:

Account groups, account privileges and environment settings. Backup Exec software version and registry information, Backup Exec Agent listing, Windows version information, SCSI hardware configuration, SQL Server information, Driver services information and Windows Services information. File Server information, supported shared directories and Windows sockets information.
VERITAS Technical Support can use the results of BE Diagnostics to troubleshoot problems. Note You can also run BE Diagnostics for a remote server (see Running Diagnostics on Remote Server on page 556)
To create a BEDIAG.TXT from within Backup Exec: 1. Start Backup Exec. 2. On the Tools menu, select Backup Exec Diagnostics. Note You can also create a BEDIAG.TXT file from the Devices and Media views. On the navigation bar, click Devices or Media. Select the backup server. On the Properties pane, under General Tasks, click Properties. Then select the System tab. 3. Click Run Diagnostics. The file BEDIAG.TXT will be created in the directory ...\Backup Exec\NT\Data.
554
General Questions
From a command line prompt on the media server: 1. Launch the command prompt. 2. From the directory ...\Backup Exec\NT\Data, type bediag servername (the server can be the media server or remote or if you are running this from a workstation, type bediag workstationname). 3. The file BEDIAG.TXT will be created in the directory ...\Backup Exec\NT\Data. 4. The following switches can be used with the command line option (bediag [switches] servername):
Switch /a /b:[server] /c /app /sys /bex /err /recs:n
Meaning 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
Troubleshooting
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
Dump SCSI hardware subkey from registry Dump Lotus Notes information Dump Windows Socket Network Protocols
Chapter 12, Troubleshooting
555
General Questions
Switch /p /q /s /v /w /x /?
Meaning Dump user privileges Dump Microsoft SQL Server information Dump information on Services Dump Server Information Dump Windows version information Dump Microsoft Exchange Server Information Display usage information
Running Diagnostics on Remote Server

You can run diagnostics on a remote server provided:

Backup Exec is installed on the remote server. Backup Exec services are running.
To run BE diagnostics on a remote system: 1. On the Tools menu, click Backup Exec Diagnostics.
Backup Exec Diagnostics dialog box
556
General Questions
2. Click Select Server and select the remote system on which you want to run the diagnostic utility. 3. Enter the logon credentials for this remote system. 4. Click OK. Diagnostic information appears in a .TXT file. 5. To print this information, on the File menu select Print. 6. After viewing this information, from the File menu, select Exit.
Troubleshooting
557
Hardware-related Questions
My drive is not listed in the drivers list for Windows NT/2000/XP/.NET. Which tape driver should I use? Some drives are repackaged and sold under various brand names. Following are various drive types and recommendations for drivers you can try:

For cartridge tape drives, 150 MB, 250 MB, 525 MB or larger, try using the Archive or Wangtek drivers. For DAT drives, use the 4mm DAT driver for all drives except Sony. If you have a Sony DAT drive, use the 4mm Sony driver. For 8mm tape drives (other than Sony), try the two Exabyte drivers.
Driver load failures can occur if Windows NT/2000/XP/.NET does not support the device. Run the Device Configuration wizard on the Tools menu to see if the device is recognized by the operating system. Note For more information on what devices are support by Windows NT/2000/XP/.NET, see the Microsoft Hardware Compatibility List contained in Microsofts documentation or on their online support knowledge base. For more information on what devices are supported by Backup Exec for Windows Servers, refer to the Hardware Compatibility List available on the VERITAS support web site, at www.support.veritas.com. 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. The device is displayed as offline if:

The device was turned off after Backup Exec was started. The device was being used by another application (such as a Windows NT/2000/XP/.NET 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 drive was updated; Backup Exec will behave as if the drive with its old name or identity no longer exists.
558
To place the device online, try the following:

Check to make sure the device has power and that cables are properly attached. Turn the device on and reboot the server, or stop and restart the Backup Exec services. 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 NT 4.0, go to Settings|Control Panel|Services and restart all services related to Backup Exec. For Windows 2000, go to Computer Management|System Tools|Services and Applications, and then restart all services related to Backup Exec.
If the drives firmware is updated or changed:

If the drive 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.
How do I get the latest device drivers for my hardware? The latest hardware device drivers are available on the VERITAS web site, at www.support.veritas.com. Download the file BNT86IDRVxx_xxxxxx.EXE. Instructions are included in the downloadable package. Backup Exec doesnt detect my robotic library. What could be wrong?
Troubleshooting
Be sure that Windows NT/2000/XP/.NET properly recognizes the device. This can be verified by checking the Tape Devices component in the control panel. For configuration and setup instructions, see VERITAS Backup Exec - Library Expansion Option on page 1143. You may also want to read Using Microsofts Removable Storage Feature with Backup Exec on page 161. Backup Exec does not display any storage devices for me to select. Why is that? Windows NT/2000/XP/.NET may not recognize the device. Make sure the storage device was powered on before Windows NT/2000/XP/.NET was loaded. If the drive was not on, power down the server and power on the tape device before powering on the server. Check the SCSI cable to make sure the cables are plugged in tightly. If the cable is loose, re-attach it and reboot Windows NT. Make sure each SCSI device (if you have more than one) has its own unique SCSI address (0 - 7). SCSI address 0 is generally reserved for the systems boot drive. Never change the SCSI address of a device while it is powered on. While configuring your SCSI devices, remember that the SCSI controller card uses a SCSI address (usually set to SCSI address 7).
559
The SCSI bus must be properly terminated in order for all of the devices on the chain to operate properly. For more information, refer to the documentation that came with the device. Note It is recommended that the tape device be on its own SCSI controller. If you have not installed the correct storage device driver, launch the Device Configuration wizard from the Tools menu within the Backup Exec console. Frequently, I get Hardware Error or Fatal Tape Format Inconsistency messages. What can I do to fix this? Try the following:

Make sure you have the SCSI bus properly terminated. For more information, refer to the documentation that came with the device. Make sure you have the correct media for your drive; many media cartridges look the same but are not supported by different media drives. For example DDS3 tapes look similar to DDS2 tapes, but they are incompatible. If the wrong media type is inserted into the drive, the drive may attempt to use the cartridge and experience problems. Use a new media cartridge; the media may be worn. Clean the tape device with the correct cleaning cartridge. Tape devices must be routinely cleaned in order to operate properly. For more information, refer to the documentation that came with the device. Set up the tape device as the only device on the SCSI bus. Sometimes different SCSI devices do not share the bus well together. SCSI cable length and quality can affect performance. If possible, replace the SCSI cable with a shorter SCSI cable. If your drive and controller support both SCSI 1 and SCSI 2 modes, be sure they are set to use SCSI 2 mode. However, if you have an older drive, it may only operate in SCSI 1 mode even though the controller may support both modes.
My storage device hangs whenever a Catalog operation is started. Why is this? Some storage devices with older firmware may not work correctly with the Use Storage Media-Based Catalogs option selected. From the Tools|Options|Catalog menu within the Backup Exec administration console, de-select the Use Storage Media-Based Catalogs option. Note This will cause catalog operations to take longer.
560
Can I restore a hardware-compressed tape using a drive that does not support data compression? Can the tape be reused? A drive that supports hardware compression must be used to restore the data on the tape. Preferably, the same drive type and firmware should be used to ensure compatibility. Because different hardware uses different compression methods, a tape created with hardware compression on one device may not be readable by another device. The tape can only be reused in the non-compression drive if you first perform a quick erase operation on the tape. If the drive supports compression, the media can simply be erased and reused. Note Make sure the tape can be bulk-erased without destroying the media. Some tape manufacturers write a signature, such as DDS2 or DDS3, to the tape that is used for identification. If the tape is bulk-erased, the signature is destroyed and the tape cannot be used for backup operations. Why does my DLT tape drive hang when cataloging some tapes? The DLT tape drive maintains internal information about the tape on a tape directory track. The directory track is updated before the tape is ejected from the drive. If the drive is powered off without ejecting the tape first, this information is lost. Re-generating the tape directory information takes several hours to complete, which makes it seem like the drive is hung. Allow sufficient time for the operation to complete and then eject the tape. Normal operation will resume after the directory track has been updated.
Troubleshooting
561
Backup Questions
Backup Questions
I am unable to back up certain files on my system that are being used by other processes. Why is that? When Backup Exec encounters a file that is in use by another process, it either skips the file or waits for the file to become available, depending on the Backup open files setting. When Backup Exec is configured to back up open files, it attempts to open the files in a different mode. It locks these files while they are being backed up to prevent other processes from writing to them. This mode should be a last resort to obtaining a backup of open files; in most circumstances, it is more desirable to close applications that leave files open so their files may be backed up in a consistent state. If you want to back up open files on Windows NT servers and workstations, Backup Execs Open File Option (sold separately) provides uninterrupted data protection for network environments. I cant see any Windows 95/98 agents from Backup Exec; why is this? Be sure the Enable Agents Using TCP/IP Protocol or Enable Agents Using NetWare IPX/SPX Protocol options are selected in the Network tab of the Tools|Options menu. If IPX/SPX is being used, try configuring the agent to use TCP/IP protocol (see Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent on page 576). You may also use the IP address of the media server rather than the actual computer name in the Windows 95/98 Agent Configuration utility. Why do Backup Execs services 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 in v7.x and later, 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.
562
Backup Questions
How do I keep storage devices from being managed exclusively by Backup Exec? If you must exclude a storage device from being managed by Backup Exec, there are two methods to consider:

Disabling the storage device for Backup Exec through the administration console. Including a BESTOP pre-job command and a BESTART post-job command in a script executed by applications other than Backup Exec. The BESTOP and BESTART commands must be copied from the utilities directory on the installation CD. Use this method only if you want to release all drives.
Following are details on these methods.
Disable storage devices for Backup Exec through the administration console: You can change the storage device properties so that the device is not used by Backup Exec. This is the best method to use if you want to:

Permanently exclude a storage device from being managed by Backup Exec. Specify which storage devices to exclude from Backup Exec.
1. In the Backup Exec administration console, click the Job Monitor tab to view all scheduled and active jobs, and make sure that the device you want to exclude is inactive. 2. Click the Devices tab, and then right-click the device to display the shortcut menu. 3. On the shortcut menu, click Properties. 4. On the Drive Properties window, click the Configuration tab. If the field Enable Device for Backup Exec is checked, then Backup Exec has exclusive access to this device. 5. Clear the Enable Device for Backup Exec check box to disable the device for Backup Exec, and allow it to be available for other applications. Note If the device is active, it is not released for use by other applications even if it is marked as Disabled in this field. 6. After changing the option, click OK.
Troubleshooting
563
Backup Questions
Release storage devices from Backup Exec by including commands in scripts: Include a BESTOP pre-job command and a BESTART post-job command in scripts executed by applications that need to use storage devices that are otherwise owned by Backup Exec. Run BESTOP to stop the services and release the storage device. Then, after the application has completed and no longer needs the storage device, run BESTART to restart the services. You can copy the BESTOP.BAT and BESTART.BAT commands from the WINNT/UTILS directory on the Backup Exec for Windows NT installation CD. This is the best method to use if you want to:

Use many storage devices in other applications. Return management of all storage devices to Backup Exec each time after other applications are finished.
Note When a storage device is excluded from Backup Exec, the Advanced Device and Media Management services cannot collect statistics on usage for that device and any media used in that device. Therefore, any thresholds set for device and media usage, such as when cleaning jobs are to be performed, or when media should be discarded, are no longer valid since statistics were not collected while the device was excluded from Backup Exec management. Additionally, the Advanced Device and Media Management services cannot provide media overwrite protection for media inserted in a storage device that is excluded from Backup Exec. Any media placed in a storage device that is not managed by Backup Exec may be overwritten. 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 NT Explorer, File Manager, or the DIR command. 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 NT Explorer displays the compressed byte count of the files on the hard drive. For example, a NTFS partition that contains 1 GB of data is compressed by Windows NT to 500 MB. Backup Exec reports that 1 GB of data was backed up, even though Windows NT 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.
564
Backup Questions
Converting to NTFS will regain disk space since it is more efficient and the default cluster size (automatically set by Windows NT) in NTFS is less than FAT. Windows NT allows you to specify a cluster size other than the default; however system performance may decrease. For more information, see the Windows NT documentation. The following tables display the cluster sizes for NTFS partitions.
NTFS Partition Cluster Sizes Partition Size (MB) <= 255 256 - 511 512 - 1023 1024 - 2047 Cluster Size 512 1024 2048 4096
The following tables display the cluster sizes for FAT partitions.
FAT Partition Cluster Sizes Partition Size (MB) <= 127 128 - 255 256 - 511 512 - 1023 512 - 1023 Cluster Size (K) 2
Troubleshooting
4 8 16 32
565
Restore Questions
Restore 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 NT operating system 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).
Error Messages
Error Message Invalid filename [filename].
Problem The file name contains characters not permitted by Backup Exec for Windows Servers. Refer to your Backup Exec for Windows Servers Administrators Guide.
Solution Enter a valid file name.
The path cannot contain The path contains a drive a drive designator. designator (e.g., c:, g:, etc.). The path cannot contain The path contains a file name. a file name. Warning: This media is out of sequence. File name is not valid.
Remove the drive designator and try again. Remove the file name and try again.
While using multiple media, you Remove the media and insert the loaded the media out of sequence. correct media in the sequence. The file name contains characters not permitted by Backup Exec for Windows Servers. Refer to your Backup Exec for Windows Servers Administrators Guide. Enter a valid file name.
None of the sets matched the requested volume.
The search did not find any backup If the path entered is not correct, sets that matched the correct it and try again. drive/volume specified.
566
Error Messages
Error Message
Problem
Solution
Too many files matched The search criteria was too general. Enter more specific search criteria the selection criteria. or increase the Maximum Search More files were found Results and try again. than will be displayed. This set is not completely cataloged. The backup set is not completely cataloged. The backup set may have crossed media or cataloging was canceled before it was completed. The set is partially cataloged. Catalog the media again.
This set must be cataloged before it can be viewed. Storage device not responding.
Fully catalog the set by clicking OK in the window.
Backup Exec cannot access the storage device.
Exit Backup Exec, power down the server and the storage device, if it is external. Check the connections on the storage device, and then power on the storage device before you power on the server. Check your server or check with your network administrator.
Unable to attach to [computer name]. The network path was not found.
This is a network error. A server may not be available or not responding.
Troubleshooting
Storage device <device There may be a bad drive, cabling, Correct the hardware problem and name> reported an error driver, or SCSI card. try again. on a request to <string describing operation>. Error reported: Timeout before function completed. Storage device <device The drive could be dirty or the name> reported an error media may be bad. There could on a request to <string also be a drive problem. describing operation>. Error reported: Bad data. Clean the drive and/or try a new or different media.
567
Error Messages
Error Message
Problem
Solution
Storage device <device There may be a drive problem or a Correct the problem and try again. name> reported an error problem or conflict with some on a request to <string other peripheral on the same bus. describing operation>. Error reported: Bus reset. Storage device <device There may be a bad drive, cabling, Correct the hardware problem and name> reported an error or SCSI card. try again. on a request to <string describing operation>. Error reported: Hardware failure. WARNING: Media # [number] is out of sequence. The selections for [device name] will be omitted from the operation. This media is part of a multi-media Remove the media, insert the family and the media you have correct media, and try again. loaded is out of sequence. The device specified in the selections is not available. Correct the problem and try again.
This media is part of a multi-media Unexpected end of backup set encountered family with a format that requires that the media be processed in on [filename]. sequential order.
If you want to catalog this media and restore data from it, you must start the catalog operation with media #1 in the drive.
Media is out of This media is part of a multi-media Remove the media and insert the sequence. Insert media family and the media you have correct media. one of this media family. loaded is out of sequence.
568
VERITAS Backup Exec - Workstation Agents
13
Workstations interact with the media server through Backup Exec Agents. Installing, configuring, and running the workstation agent software allows drives and directories on the workstation to be protected by Backup Exec. The Backup Exec Windows 98 and Windows Me Agent files, along with the Macintosh and UNIX Agent files are copied automatically during installation from the Backup Exec installation CD to the appropriate subdirectory in Program Files\VERITAS\Backup Exec\NT\Agents on the media server. Instructions for installing the agent files on workstations are given in each of the agent sections. After installing the agent on the workstation, you can configure:

The directories and drives on the workstation that you want the media server to be able to access for operations (these are called published directories or drives). The level of access that the Backup Exec administrator has to each published directory and/or drive. For example, you can assign a password to any directory or drive. Then, before the directory or drive can be backed up, the administrator must provide that password. You can also designate directories or drives as read-only, which prevents data from being restored to those directories or drives.
Workstation Agents
569
The Backup Exec Windows 98 and Windows Me Agents

The Backup Exec Windows 98 and Windows Me Agent enables Backup Exec to perform backup and restore operations on Windows 98/Me workstations that are connected to the network. The Backup Exec Windows 98/Me Agent files are copied automatically during installation from the Backup Exec installation CD to the Program Files\VERITAS\Backup Exec\NT\Agents directory on the media server. See also: Requirements for Running the Backup Exec Windows 98/Me Agent on page 570 Installing the Backup Exec Windows 98/Me Agent on the Workstation on page 571 Configuring the Backup Exec Windows 98/Me Agent on page 572 Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent on page 574 Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent on page 576
Requirements for Running the Backup Exec Windows 98/Me Agent

You must have access to the Network option on the workstations Control Panel. The server must run the IPX/SPX or TCP/IP network protocols.
570
Installing the Backup Exec Windows 98/Me Agent on the Workstation

The Backup Exec Windows 98/Me agents supplied on the Backup Exec Installation CD provide several improvements, such as an agent status window, that are not included with the Microsoft agent supplied with Windows 98/Me. Note If an earlier version of the Backup Exec Windows 98/Me agent is already installed and running on the Windows 98/Me workstation, you must shut down the agent before upgrading it.
To install the Windows 98/Me agent on a Windows 98/Me workstation: 1. Log on to the media server from the workstation, and from the Program Files\VERITAS\Backup Exec\NT\Agents\win9x\[language] directory on the media server, double-click Setup.exe. 2. Follow the instructions. 3. When the Help screen appears, follow its directions.
Backup Exec Windows 98/Me Agent
Workstation Agents
4. When you have completed the instructions, you are prompted to reboot the Windows 98/Me workstation. You must reboot the workstation for the agent to run properly.
Chapter 13, VERITAS Backup Exec - Workstation Agents
571
Configuring the Backup Exec Windows 98/Me Agent

By default, when the agent is installed, all local fixed disk drives on the workstation are published at their root level without password protection. You can change the default configuration to publish other directories, or to password-protect the agent.
To change configuration settings on a Windows 98/Me workstation: 1. For Windows 98 or Windows Me, right-click the Network Neighborhood or My Network Places icon on the desktop. 2. Click Properties and then click the Configuration tab. 3. In the list of installed network components, double-click Backup Exec Agent.
Backup Exec Agent Publisher dialog box
572

Backup Exec Agent Publisher Properties Option General tab Disable network backup Keeps the workstation from being backed up by the media server. When Disable Network Backup is on, the agent is not loaded when the workstation is started, and the media server will no longer see the computer as a published agent. If you turn on this option while the agent is running, the agent is stopped. Enable network backup Enable network backup Computer Name Enables the media server to back up or restore to the workstation. Identifies the workstation with an alphanumeric label (up to 36 characters) to the media server. You can use the default, which is the name used in the Windows 98/Me network. Used to enter a password (up to 32 characters, upper- or lower-case) in the password field. This password is required before anyone performing a backup or restore from the media server can access the workstations published directories or drives. To change a password, select this option, then enter the new password in the password field. Current Status Displays the current status of the agent. Status messages include: Not Running, Idle, and Connected. Not Running indicates the agent is either disabled or shut down. Idle indicates the agent has loaded and is waiting for a connection by a user or the media server. Connected indicates that a user or the media server has connected to the agent and is accessing it. Action
Password
Workstation Agents
Registry Allow Registry to be restored Enables the workstations Windows 98/Me registry to be restored.
573
The Backup Exec Windows 98 and Windows Me Agents Backup Exec Agent Publisher Properties (continued) Option Published Folders Name, Path, Access Control Lists any published directories and drives, or their aliases, and the level of access control assigned. By default, all local drives are published. Used to add directories and drives to the list of published folders. Used to remove the selected directory or drive from the list of published folders. Used to change the access control for published folders. Action
Add Remove
Details
See also: Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent on page 574 Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent on page 576
Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent
To have the media server back up drives and directories, you must add them (or publish them) to the Published Folders list (all local drives are published by default). You can list up to eight published folders. When you publish the drives and directories, you can also choose to password-protect them, or to designate them as read only.
To publish drives and directories using the Windows 98/Me Agent: 1. For Windows 98 or Windows Me, right-click the Network Neighborhood or My Network Places icon on the desktop. 2. Click Properties and then click the Configuration tab. In the list of installed network components, double-click Backup Exec Agent.
574
3. At the bottom of the General tab, click Details.

Folder Details dialog box

Folder Details options Item Path Description Enter the path to the folder you want to protect, or click Browse to help locate a folder. (Optional) In Folder Name, enter an alias that you want to use for this folder. (Optional) Sets or changes access control for a published folder, do one of the following Password-protects a published folder. Using a password protects the published folder from unauthorized backup. Designates the folder as read-only. Clicking Read Only enables only backup operations to be performed on the path; restore operations are not allowed.
Folder Name
Access Control
Requires Password (PW) Read Only (RO)
Workstation Agents
5. Click OK. The drives and folders you selected, and any access control that you designated for those folders, are displayed in the Published Folders window on the Backup Exec Agent Properties dialog box.
575
Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent
To use the Backup Exec Windows 98/Me agent, the computer on which Backup Exec is installed must be running either the IPX/SPX or TCP/IP communications protocols. Choosing which protocol to use is your decision; either one can be used, or you can run them both simultaneously. If you use TCP/IP, make sure all Backup Exec Windows 98/Me agent computers are configured to advertise their IP addresses directly to the media server and servers that are used for remote administration purposes. No additional configuration is needed when the IPX/SPX protocol is used. To set up and run the IPX/SPX or TCP/IP protocols on the media server, refer to your Windows documentation. Note If you use Dynamic Host Configuration Protocol (DHCP) on a media server or a server that is used for remote administration purpose, and plan to use the Windows 98 Agent on TCP/IP, read the following: By using DHCP to dynamically configure the IP address of the host computer running Backup Exec for Windows Servers, the possibility exists that a different IP address will be assigned to the host computer each time it is restarted. Because the IP address assigned to the Backup Exec Windows 98/Me agent during agent installation is supposed to match the IP address of the computer running Backup Exec, agent-to-host communication problems may occur since the hosts IP address might change each time it boots. You can also enter a DNS host name instead of an IP address. This eliminates the need for a static IP address. In order to ensure that the Backup Exec Windows 98/Me agent consistently communicates with the Backup Exec host computer, you should RESERVE an IP address for the host running Backup Exec using the Windows DHCP Administrator program. Refer to your Windows documentation for details.
To configure the Windows 98/Me Agent network protocol: 1. For Windows 98 or Windows Me, right-click the Network Neighborhood or My Network Places icon on the desktop. 2. Click Properties and then click the Configuration tab. 3. In the list of installed network components, double-click Backup Exec Agent.
576
4. Click the Protocol tab.

Backup Exec Agent Publisher dialog box
5. Select the appropriate options from the following:

Backup Exec Agent Publisher options Item SPX/IPX Description Configures the Backup Exec Agent for use with SPX/IPX-based networks. Typically used with Novell NetWare-based networks. Configures the Backup Exec Agent for use with TCP/IP-based networks. TCP/IP is the communications protocol typically used in heterogeneous networks. Shows all previously configured media servers.
TCP/IP
Workstation Agents
Configured Media Servers
6. If you select TCP/IP, click Add.
577
The Backup Exec Macintosh Agent
7. In the Adding Media Server box, type the host name or IP address of the media server that will be used to back up this computer, then click OK. 8. Click OK to close the Backup Exec Agent Properties dialog box.

The Backup Exec Macintosh Agent allows Backup Exec to perform backup and restore operations on Macintosh workstations that are connected to the network. This agent must be running on the Macintosh workstation before backup or restore operations can be performed. After the agent is installed, configured and the Macintosh workstation is restarted, the workstation is ready for backup. When backing up data using the Backup Exec Macintosh Agent, Backup Exec allows you to protect data using full or working set backup types. Note The Backup Exec Macintosh Agent only supports Mac OS X; Macintosh Operating System versions 6.x though 9.x are not supported. See also: Understanding Backup Methods and Their Advantages on page 340 Installing and Configuring the Macintosh Agent on a Mac OS X Workstation on page 579 Requirements for Running the Backup Exec Macintosh Agent on page 578
Requirements for Running the Backup Exec Macintosh Agent

To install the Mac OS X Agent, the root account must be activated and you must have access to it. The Mac OS X BSD Subsystem and its associated utilities must be installed. A media server must be reachable from the host using DNS, NIS, NetInfo, LDAP, or another naming system. Otherwise, the media server must be added to the local NetInfo database on the host. As a third option, you can also use the Backup Exec media servers IP address, in place of the media server name. Agents using the TCP/IP protocol must be enabled from the Backup Exec media server.
578
Installing and Configuring the Macintosh Agent on a Mac OS X Workstation
To install the Mac OS X - based Backup Exec Macintosh Agent using a naming service: Caution Having a working knowledge of UNIX is highly recommended and extremely helpful when installing the Mac OS X - based Backup Exec Macintosh Agent. 1. At the Mac OS X workstation, start NetInfo Manager. Using the Finder, click Applications and then Utilities. 2. Log on using an administrative account. Use Domain and then select Security and then Authenticate. 3. Enable the root account. Use Domain and then select Security and then Enable Root User. 4. Log on again if necessary using the same administrative account. Use Domain and then select Security and then Authenticate. 5. Set the root password. Use Domain and then select Security and then Change Root Password. 6. Exit NetInfo Manager. 7. Using Finder, select Applications and then Utilities and then Terminal. 8. In the Terminal window, change to the root user by typing su at the command prompt and then pressing <Enter>. 9. Because the Macintosh Agent must communicate with the Backup Exec media server, you must either specify the IP address, use a naming service or enter the media servers IP address in the NetInfo database in order for communications to occur. To use a naming service (DNS, NIS, LDAP, etc.), you must configure the Macintosh to use this feature. For more information, see your Macintosh OS X documentation. To use the media servers IP address, specify it in place of the media servers name in step 31. To use NetInfo, perform the steps listed in Modifying the NetInfo Database on page 583 and then continue with step 10 in this section.
Workstation Agents
579
10. Copy the be_agnt.tar file, which contains the Macintosh OS X Agent, to a temporary directory on the workstation to be protected. The be_agnt.tar file is located on the Backup Exec installation CD and in the Agents subdirectory of the Backup Exec media servers Programs directory. You can copy the file to the workstation via the network using FTP, a Macintosh share on the media server, or any other method you prefer. Or you can insert the Backup Exec installation CD in the workstation to be protected and copy the file from the CD. Note If you are pushing the Macintosh OS X Agent from the media server to the workstation using FTP, ensure that you use the binary transfer mode, not the ascii mode. Prior to starting the file transfer, type binary at the command prompt on the media server, and then press <Enter>. 11. At the workstation, from the temporary directory you want to use, type tar -xvf be_agnt.tar 12. Press <Enter>. 13. Then, run the installation script by typing ./INSTALL 14. Press <Enter>. The installation begins by reporting the Macintosh platform to which the agent is being installed. You are prompted for information to complete the installation and configuration of the Backup Exec Macintosh Agent. 15. If prompted, select a language by typing the number that corresponds to the language you want to use, then press <Enter>. 16. Enter the full directory path where you want the Backup Exec Macintosh Agent to be installed. By default, the agent is installed in /etc/bkupexec. You can specify another directory. If the full directory path that you specify does not exist, you are prompted to have it created. 17. Enter the name for this workstation. By default, the network node name is used. If you want to use a different name, make sure it is a unique name not used by other Backup Exec Macintosh agents. 18. You can choose to require a password for this workstation. If you do, you are prompted to enter a password.
19. You are asked about the number of network interfaces in your workstation. If you have more than one network interface, you are asked if you want to specify which network interface to use. If you answer yes, then you must specify an IP address of a local network interface for the agent to use. Should you have more than one network interface and choose not to specify which one to use, the agent will use an appropriate interface to communicate with a media server 20. Enter the directory path that you want backed up. If you want to back up the Macintosh workstations entire hard disk, simply define a directory path as /. This allows the network administrator to select the entire disk for backup. You can create and publish up to eight unique directory paths. Note If your computer has more than one file storage volume on the same physical hard disk, or has more than one hard disk, then specifying the root directory (/) for backup will not protect all of the volumes. To back up the desired additional volumes, they must be specified individually. For example, to back up a disk called Videos, you must also specify /Volumes/Videos as one of the directories to be backed up. 21. Enter a unique resource name for each published path. The resource name is used by the media server to identify the contents of each published path. If you chose a directory path of /, by default the resource name is [root]. For any other path, the default name is the path name. 22. To allow files to be restored to a published path, type y, when prompted. If you do not want to allow the Backup Exec application to restore files, type n. 23. You can choose to require a password for each published path. If you choose to password-protect the path, the password is required before Backup Exec can perform operations on this path.
Workstation Agents
24. You can continue to publish directory paths for backup and restore operations by repeating these steps. 25. When you have finished creating published paths, you are prompted to enter the names of the media servers that will back up your workstation. A maximum of twenty media servers is allowed. After entering a media server name, the server is located and added to the list of valid media servers.
581
26. You are prompted to enter the frequency (in seconds) that you want the Backup Exec Macintosh Agent to send advertisement messages to the media servers so that the servers are aware that the workstation is accessible. Note It is recommended that you use the default frequency of 30 seconds. 27. You are prompted to choose a method to back up symbolic links. Choose one of the following methods: Method 1: The symbolically linked directory is handled as a special file and only the information required to create the symbolic link is backed up. Method 2: The symbolically linked directory is backed up as a normal directory. All files and subdirectories within the symbolically linked directory are also backed up.
28. After choosing a backup method for symbolic links, your Backup Exec Macintosh Agent configuration is complete. You can edit the agent.cfg file to change your agent configuration at any time. Changes to the configuration file take effect after the Macintosh workstation is rebooted. 29. Start the Mac OS X Agent by moving to the folder where the Backup Exec Macintosh Agent is installed. 30. At the command prompt, type: ./agent.be & The agent starts and runs in the background. The data on the Macintosh is now available for backup.
582
Modifying the NetInfo Database

If a media server or other host is not reachable using a naming service, add it to the local NetInfo database.
To modify the NetInfo Database: 1. Using Finder, select Applications and then Utilities and then Terminal. In the Terminal window, change to the root user by typing su at the command prompt and then pressing <Enter> 2. Run the following commands in the Terminal window, replacing the myhost name and IP address with the name and IP address of your Backup Exec media server: niutil -create . /machines/myhost niutil -createprop . /machines/myhost name myhost niutil -createprop . /machines/myhost ip_address 10.88.100.201 niutil -createprop . /machines/myhost serves ./local ping -c 3 myhost 3. When finished, type exit to close the terminal window. See also: Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent on page 574
Workstation Agents
583
About the Backup Exec UNIX Agent

The Backup Exec UNIX Agent allows Windows Server network administrators to perform backup and restore operations on UNIX workstations and servers that are connected to the network. This agent must be running on the UNIX device before backup or restore operations can be performed. After the agent is configured and the UNIX device is restarted, the workstation is ready for backup. When backing up data using the Backup Exec UNIX Agent, Backup Exec allows you to protect data using multiple backup types. These include:

Full Differential Incremental Working set
See also: Understanding Backup Methods and Their Advantages on page 340 Requirements for Running the Backup Exec UNIX Agent on page 584 Installing the Backup Exec UNIX Agent on the Workstation on page 585 Configuring the Backup Exec UNIX Agent on page 588
Requirements for Running the Backup Exec UNIX Agent

You must have root privilege on the UNIX computer to install the UNIX agent. TPC/IP is required on the media server. The names and IP addresses of each media server used to access UNIX workstations must be in the /etc/hosts file on the UNIX workstations.
584
Installing the Backup Exec UNIX Agent on the Workstation

When you install the Backup Exec UNIX agent, you are prompted to configure it as well. The agent configuration information is saved to a text file called agent.cfg that you can edit to change any configuration options. Before installing the Backup Exec UNIX agent on a system using a network name service (for example NIS), you must modify the networks master database /etc/services file. Make sure you have root privileges at the master server. Note During the initial installation of Backup Exec, the Backup Exec UNIX Agent files are copied automatically from the Backup Exec installation CD to the Program Files\VERITAS\Backup Exec\NT\Agents\UNIX directory on the media server.
To modify the /etc/services files: 1. Edit the input file (/etc/services) for the map you want to change. 2. Add the following line, then save and exit the file: grfs 6101/tcp # Backup Exec Agent 3. Type the following: cd /var/yp make services.byname The make command updates the NIS map according to the changes made to the input file, then propagates the changes to all other NIS servers on the network. The Backup Exec UNIX agent is then installed by using ftp to push the agent files from the server to the workstation.
Installing the Backup Exec UNIX Agent from the Server:
Workstation Agents
1. Log on as root on the media server, and put the Backup Exec installation CD in the servers CD-ROM drive. 2. The be_agnt.tar file must be transferred to the UNIX workstation. One way to transfer this file is to open a command prompt window, and at the prompt, type ftp xx.xx.xx.xx <Enter> where xx.xx.xx.xx is the IP address of the UNIX workstation where you want to install the agent.
585
3. Because the UNIX agent file must be pushed from the server to the workstation in binary mode, change from the ASCII default mode to the binary mode by typing the following at the prompt: binary <Enter> 4. Create a temporary directory on the workstation. If you prefer, you can use the /tmp directory. Go to the temporary directory or /tmp directory, and then type put be_agnt.tar <Enter> 5. At the workstation, from the temporary directory you want to use, type tar -xvf be_agnt.tar <Enter> 6. Then, run the installation script by typing ./INSTALL <Enter> The installation begins by reporting the UNIX platform to which the agent is being installed. You are prompted for information to complete the installation and configuration of the Backup Exec UNIX Agent. 7. If prompted, select a language by typing the number that corresponds to the language you want to use, then press <Enter>. 8. Enter the full directory path where you want the Backup Exec UNIX Agent to be installed. By default, the agent is installed in /etc/bkupexec. You can specify another directory. If the full directory path that you specify does not exist, you are prompted to have it created. 9. Enter the name for this workstation. By default, the network node name is used. If you want to use a different name, make sure it is a unique name not used by other Backup Exec UNIX agents. 10. You can choose to require a password for this workstation. If you do, you are prompted to enter a password. 11. You are asked about the number of network interfaces in your workstation. If you have more than one network interface, you are asked if you want to specify which network interface to use. If you answer yes, then you must specify an IP address of a local network interface for the agent to use. Should you have more than one network interface and choose not to specify which one to use, the agent will use an appropriate interface to communicate with a media server.
586
12. Enter the directory path that you want backed up. If you want to back up the workstations entire hard disk, simply define a directory path as /. This allows the network administrator to select the entire disk for backup. You can create and publish up to eight unique directory paths. 13. Enter a unique resource name for each published path. The resource name is used by the media server to identify the contents of each published path. If you chose a directory path of /, by default the resource name is [root]. For any other path, the default name is the path name. 14. To allow files to be restored to a published path, type y, when prompted. If you do not want to allow the Backup Exec application to restore files, type n. 15. You can choose to require a password for each published path. If you choose to password-protect the path, the password is required before Backup Exec can perform operations on this path. 16. You can continue to publish directory paths for backup and restore operations by repeating these steps. 17. When you have finished creating published paths, you are prompted to enter the names of the media servers that will back up your workstation. A maximum of twenty media servers is allowed. After entering a media server name, the server is located and added to the list of valid media servers. Note You can also enter the media servers IP address in place of the media servers name. 18. You are prompted to enter the frequency (in seconds) that you want the Backup Exec UNIX Agent to send advertisement messages to the media servers so that the servers are aware that the workstation is accessible. Note It is recommended that you use the default frequency of 30 seconds.
Workstation Agents
587
19. You are prompted to choose a method to back up symbolic links. Choose one of the following methods: Method 1: The symbolically linked directory is handled as a special file and only the information required to create the symbolic link is backed up. Method 2: The symbolically linked directory is backed up as a normal directory. All files and subdirectories within the symbolically linked directory are also backed up.
After choosing a backup method for symbolic links, your Backup Exec UNIX Agent configuration is complete. You can edit the agent.cfg file to change your agent configuration at any time. Changes to the configuration file take effect after the UNIX workstation is rebooted.
Configuring the Backup Exec UNIX Agent

To configure the Backup Exec UNIX agent, edit the agent configuration file, agent.cfg, and make changes. By default, the agent.cfg file is installed on each UNIX agent workstation in the /etc/bkupexec subdirectory. You can use any text editor to make changes to the agent.cfg file. The first portion of the agent.cfg file contains instructions that define and explain each of the configuration lines. The actual agent configuration commands are found at the end of the file. The following table lists the commands and parameters used with the Backup Exec UNIX agent.cfg file. Commands are bold; parameters within [] are optional.
Agent.cfg Commands Item Description
name <workstation name> Use this command to enter another name for this workstation. This name appears in the Backup Exec selection screens. This item is optional. If a workstation name is not provided, the workstations network node name (for example, uname -n) is used. password <passwd> Use this command to assign a password to this workstation. If you assign a password, then in order to access this workstation, the Backup Exec administrator must enter the password during operations. If a password was not provided during installation, the Backup Exec administrator must press <Enter> when prompted for a password. This item is optional.
588
About the Backup Exec UNIX Agent Agent.cfg Commands (continued) Item export Description Use this command to specify a directory tree to publish so that it will be accessed by Backup Exec. The following commands are used with export:
<resourcename> - Use this command to identify the exported paths of the agent workstation. This name appears in the Backup Exec Networks window under Backup Exec Agents. [write_protected] - Use this command if you want the published path to be accessed for backup operations but not for restore operations. <password> - Use this command to assign a password to a specific published path. The Backup Exec administrator is required to enter the password before the published path can be accessed by backup operations. [include_remote]- Use this command to access remotely mounted (NFS) file systems through their normal mount points. export / as ROOT include_remote <no_nfs_locking> - Use this command to prevent locking of files during backup operations if they are located in remotely mounted file systems with mount points within a directory tree.
Example: export <directory> as <resourcename> [write_protected] [password <passwd>] [include_remote][no_nfs_locking] tell <machine name> Use this command to specify a media server name as an argument. This server name is added to the list of computers to which advertisements will be sent. This machine name must be found in the /etc/hosts file. Use this command to specify the number of seconds the agent waits before re-advertising itself to the media server. If you enter a number other than the default setting (30 seconds), the number should not be more than a few minutes or less than 60 seconds. Longer numbers cause a delay in the workstations network broadcast verification and shorter numbers cause excessive network traffic. Each advertisement transaction requires eight (8) network packets. Use this command to specify that the contents of the linked directories be backed up but not the symbolic links themselves. By default, the contents of symbolically linked directories are not backed up, but the symbolic links themselves are.
tell_interval <number_of_seconds>
Workstation Agents
follow_symdirs
589
About the Backup Exec UNIX Agent Agent.cfg Commands (continued) Item exclude_file <filename> Description Use this command to specify individual files which should never be backed up. The <filename> must include a fully specified path. No wildcards are permitted. Use this command to exclude individual directories or directory trees from being backed up. The <directory path> must be fully specified. Use this command to force the agent to ignore the message which sets objects (files and directories) attributes when a backup occurs. Normally, during a backup, the backup engine preserves an objects last access timestamp by resetting the last access timestamp to the value before the backup occurred. When the agent modifies the objects last access timestamp, the OS internally updates the objects ctime. An objects ctime is the time when an objects attributes (permissions, timestamps, etc.) have been modified. By not attempting to reset the attributes after a backup, the objects ctime is not updated. This option does not affect object attributes set during restore operations.
exclude_dir <directory path>
preserve_ctime
590
VERITAS Backup Exec Command Line Applet
14
The Backup Exec Command Line Applet is a convenient way to access some of the most useful features of Backup Exec from a command prompt. The Command Line Applet allows management of only one media server at a time, but allows for remote management of media servers within an enterprise. Backup Exec must be installed and running on a media server in order for the Command Line Applet to target it, but the Command Line Applet does not have to be run from a media server. The Command Line Applet uses functional command switches typed in a command prompt window to perform most Backup Exec functions and utilities, including:

Run or cancel a previously created backup or restore job. Create and run backup and restore jobs for local or remote file selections, including databases on Microsoft Exchange, SQL, Lotus Domino, Oracle, and SharePoint installations. Create selection lists. Create backup job templates. Create, run, and monitor utility jobs.
Note This release of the Command Line Applet does not support submission of catalog, verify, or rewind jobs.

Set default options for all jobs. Obtain job status and the number of scheduled, active, and completed jobs. Create media sets and drive pools. Perform drive utilities and get information about the status of drives. Start and stop Backup Exec system services. Retrieve information on and respond to job alerts.
Command Line
591
Command Line Applet Requirements
Determine if the media server is available on the network. View and print Backup Exec reports.
Note The Command Line Applet can target clustered media servers. The only limitation is that the Command Line Applet can target a drive pool, but not a specific device in that drive pool.
Command Line Applet Requirements

The Backup Exec Command Line Applet works with a local or remote Backup Exec server installation. Minimum system requirements include:
Command Line Applet requirements Operating System Microsoft Windows NT Workstation version 4.0 or Microsoft Windows NT Server version 4.0; Service Pack 6a. Microsoft Windows 2000 Professional or Server version, Microsoft Windows 2000 Advanced Server, or Microsoft Windows 2000 Datacenter. Windows XP .NET family Processor Memory Disk Space Pentium system Required 16 MB RAM A minimum of 1 MB of hard disk space after Microsoft Windows is installed CD-ROM
Other Hardware
592
Using the Command Line Applet
Using the Command Line Applet

The Backup Exec Command Line Applet is installed with Backup Exec for Windows Servers. After installation, to run the applet on another computer, copy bemcmd.exe to a computer that meets the minimum requirements and is running Windows RPC services. To use the Command Line Applet, type bemcmd followed by a series of command switches in a command prompt window. The Command Line Applet will attempt to complete the requested task, and then return a value to the command prompt indicating success or failure.
Using Command Line Switches

To use the Command Line Applet on your computer, type the appropriate command line switch and any additional information required. For example, to run a previously created backup job named Operations Weekly, type the following at the command prompt: bemcmd -o1 -j"Operations Weekly" In this example, -o1 is the operation to submit the backup job. The command line switch -j specifies the name of the backup job. Because the job name is alphanumeric, quotation marks are required around the job name. The job Operations Weekly was previously created through the Backup Exec administration console. By default, the backup will be done on the computer where the Command Line applet is executed. To run this same job on a remote computer named Genesis, type the following at the command prompt: bemcmd -cGenesis -o1 -j"Operations Weekly" The command line switch -c specifies the name of the media server where the job is to be run. When connecting to a remote server, if you are required to provide a user name and password, type the following at the command prompt, substituting the text appearing in italics with the correct names: bemcmd -cGenesis -nuser name -ppassword -o1 -j"Operations Weekly" Note Type quotation marks before and after the user name and password if they contain spaces or a colon.
Command Line
Chapter 14, VERITAS Backup Exec Command Line Applet
593
In each of the previous examples, a -1 is returned if the job fails. You can also track the status of the job submission by including the Verbose Output command line switch -v. Command line switches are described in the following sections. Substitute the text that appears in italics next to the command, such as job name, with a value, such as the correct job name. Note If the value contains a space or a colon, enclose the value with quotation marks. If the switch contains more than one letter and you are not using quotation marks to enclose the value, a colon must appear immediately after the switch. For commands using Job IDs, this version of Backup Exec uses a globally unique identifier (GUID) in a 16-byte hex string format for each job. Note Command line switches appearing in BOLD are required.
Switches Used With All Operations

The following command line switches can be used with all operations.
Command line switches for all operations Item -? -?switch -cmedia server Description Displays help on all command line switches. Displays help about a command line switch. Specifies the name of the media server where the operation is to be performed. If a media server name is not specified, the local computer name is used by default. Directs all output to a specified logfile and to the console. You must specify the logfile name where the output is to be written. Appends all output to the specified logfile and to the console. You must specify the logfile name where the output is to be written. Note The colon (:) must be included. -nuser name Specifies the user name credential for logging into a remote Backup Exec server. If a user name is not specified, the current credential is used.
-llogfile
-la:logfile
594
Using Command Line Switches Command line switches for all operations Item -ppassword Description Specifies the password credential for logging into a remote Backup Exec server. If a password is not specified, the current password credential is used. Specifies the type of OS the server is running. The default is Windows. To specify a NetWare server, type -tNW. To specify a Windows server, type -tNT. -v Displays information detailing what has occurred while running the Command Line Applet and the specified option. This command is useful when tracing the sequence of events using the command line applet.
-tBackup Exec server type
The switch -w (Waits for the job to complete before exiting the program) can be used with switches -o1 through -o8, -o17, -o18, -o42, -o46, and -o90. This command returns a 1 if successful or -1 on failure.
Command Line
595
Backup Job Switches

You can run a previously created job or submit a new backup job using the commands presented in the following table. You can also create a backup job script file that the Command Line Applet can use instead of command line switches.
Backup Job Commands Operation Additional Switches Function Description
-o1
Run backup job
Runs a backup job that has been previously defined. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Required. Specifies the name of the previously defined job that Backup Exec should run. Note If there are jobs with the same name, only one of the jobs will run. To ensure that the correct job runs, you should use the job ID instead of the job name to specify which job will should run.
-jjob name
-pr:priority
Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-w
Wait for job completion.
Instructs the Command Line Applet to wait for the operation to complete before returning. Creates and runs a backup job for a specified list of files. This operation returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails.
-o2
Create backup job
596
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -jjob name Function Description
Specifies the name that Backup Exec will assign to this job. Specifies the name of the device Backup Exec should use for backup. When backing up a remote server, the device name will be the name of the remote server. Use this switch instead of the -d switch to indicate that this device name should be checked against the devices (and device pools) on the target server, and the job should only run if the device exists. If the device does not exist, and if the -v (verbose) switch is used, the following message appears: Device or Device Pool specified does not exist. Specifies to use the image option for a backup job, where Intelligent Image value corresponds to: 1 = Use Intelligent Image Option for this backup operation. 2 = Use Intelligent Image Option and use server free backup if available. Note The colon (:) must be included.
-ddevice name
-sd:device name
-fi:Intelligent Image value
-pr:priority
Command Line
597
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -sfile list Function Description
Specifies the list of files to back up. The list should be comma delimited. By default, subdirectories will be recursed; to skip subdirectories during backup, the characters /n should appear before the comma separating the entries, and the last quotation mark. For example, "c:\winnt\*.* /n". The order resource selections are specified is the order in which the resources will be backed up. 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 or shadow copy components must be ordered last. Note This switch cannot be used with the -sf switch.
-sf:file name
Specifies the name of a file that contains a list (one per line) of files to be backed up. Note This switch cannot be used with the -s switch.
-mmedia set
Specifies the name of the media set Backup Exec should target. Specifies the media protection level: 0 = Overwrite 1 = Append to media, overwrite if not available 2 = append to media, terminate if not available
-mp:media protection level
598
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -r Function Description
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the command line or the Backup Exec administration console, as long as that job has already been created and saved. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning. Creates and runs a backup job to back up the specified drive on the media server. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Specifies the name that Backup Exec will assign to this job. Specifies the drive letter of the drive that Backup Exec should backup. If no drive letter is specified, the job will default to C drive. When backing up a remote server, the device name will be name of the remote server. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-w
-o3
Back up server drive
-jjob name
-ddrive name
-pr:priority
Command Line
599
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the command line or the Backup Exec administration console, as long as that job has already been created and saved. Specifies the Intelligent Image Option for a backup job, where Intelligent Image Option value corresponds to: 1 = Use Intelligent Image Option for this backup operation. 2 = Use Intelligent Image Option and use server free backup if available. Note The colon (:) must be included.
-fi:Intelligent Image Option value
-w
Wait for job completion
Instructs the Command Line Applet to wait for the operation to complete before returning.
-o4
Back up This operation is not for Exchange. If you are Exchange server running Exchange 2000, use operation -o6. Creates and runs a backup job to back up the Microsoft Exchange Server on the media server. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Note While individual mailboxes cannot be selected for backup, all mailboxes are included in a server backup. The Agent for Microsoft Exchange Server must be enabled on the Backup Exec server in order to back up the Exchange Server.
600
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -jjob name Function Description
Specifies the name that Backup Exec will assign to this job. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-pr:priority
-r
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the Command Line Applet or the Backup Exec administration console, as long as that job has already been created and saved. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning.
-w
Command Line
601
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches Function Description
-o5
Back up SQL server
This option is not for SQL 2000. If you are running SQL 2000, use operation -o8. Creates and runs a backup job to back up the Microsoft SQL Server on the media server. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Note While individual tables and file groups cannot be selected for backup, all subcontainers (except for the master filegroup) are included in a server backup. The Agent for Microsoft SQL Server must be enabled on the Backup Exec server in order to back up a SQL Server.
-jjob name
Specifies the name that Backup Exec will assign to this job. Specifies the log backup option.
-lo:database mode -db:database name -pr:priority
Specifies the name of a database to backup.
602
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the command line or the Backup Exec administration console, as long as that job has already been created and saved. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning. Creates and runs a backup job for Exchange 2000 Server. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Note The Agent for Microsoft Exchange Server must be enabled from the media server in order for this command to work.
-w
-o6
Back up Exchange 2000 server
-jjob name
Specifies the name that Backup Exec will assign to this job. Required. Specifies the storage group to back up. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-sg:storage group -pr:priority
Command Line
603
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the Command Line Applet or the Backup Exec administration console, as long as that job has already been created and saved. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning. Creates and runs a backup job for SQL Server 2000. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Note The Agent for Microsoft SQL Server must be enabled on the media server in order for this command to work.
-w
-o8
Back up SQL Server 2000
-jjob name
Specifies the name that Backup Exec will assign to this job. Specifies the name of the database to back up.
-db:database name -ni:named instance -pr:priority
Specifies the named instance to back up.
604
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the command line or the Backup Exec administration console, as long as that job has already been created and saved. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning. Places a Microsoft SQL Server database in either standby mode or in a loading state. Values are: 0 = None. 1 = Standby. Place database in standby mode. 2 = No recover. Place database in a loading state. Note The colon (:) must be included.
-w
-lo:database mode
-o9
Back up SharePoint Portal Server
Creates and runs a backup job for the Microsoft SharePoint Portal Server. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Note The Agent for Microsoft SharePoint Portal Server must be enabled on the media server in order for this command to work.
-pr:priority
Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest
Command Line
If this switch is absent, the priority will be set as Medium.
605
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the command line or the Backup Exec administration console, as long as that job has already been created and saved. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning. Specifies the name that Backup Exec will assign to this job. Back up Lotus Notes server Creates and runs a backup job of the Lotus Notes server. Returns 1 if successful or -1 if there is an error. Specifies the name that Backup Exec will assign to this job. Required. Specifies the drive letter where Lotus Notes is installed. Specifies the complete path to the transaction log file. Note The colon (:) must be included.
-w
-jjob name
-o17
-jjob name
-ddrive name
-tl:path
-pr:priority
606
Replace existing Specifies Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the command line or the Backup Exec administration console, as long as that job has already been created and saved. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning. Creates and runs a backup job of the Oracle server. Returns 1 if successful or -1 if there is an error. Note Only one SID can be specified per command. Use -si to indicate the SID name to back up.
-w
-o18
Back up Oracle server
-jjob name
Specifies the name that Backup Exec will assign to this job. Required. Specifies the SID name to back up. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-si:SID name -pr:priority
-r
Replace existing Instructs Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the Command Line Applet or the Backup Exec administration console, as long as that job has already been created and saved.
Command Line
607
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -w Function Description
Instructs the Command Line Applet to wait for the operation to complete before returning. Creates and runs an alias backup. Files to be backed up are specified as a comma delimited list (for example, c:\dir\file or \\server\share name\...) with a matching comma delimited list of aliases. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. An alias backup allows you to specify a share to back up, and then specify another share from which the backup will appear to have originated. This type of backup is useful when the location of the data to be backed up is temporary. For example, a temporary share may be created when a mirror is split. Or a share may be cloned and placed on another device while it is backed up in order to off load traffic from a busy device. If a temporary share is backed up, the restore path for the share may not exist if a restore becomes necessary. Instead, you can specify an alias to a location where you want the share to appear to have been backed up from.
-o19
Create alias backup job
-jjob name
Required. Specifies the name that Backup Exec will assign to this job. Specifies using a frozen image (no Open File Option) for the backup. Specifies the name of the media set that Backup Exec should target.
-g
-mmedia set
608
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -mp:media protection level Function Description
Specifies the media protection level: 0 = Overwrite 1 = Append to media, overwrite if not available 2 = append to media, terminate if not available
-ddevice name
Specifies the name of the device that Backup Exec should use for the alias backup. Use this switch instead of the -d switch to indicate that this device name should be checked against the devices (and device pools) on the target server, and the job should only run if the device exists. If the device does not exist, and if the -v (verbose) switch is used, the following message appears: Device or Device Pool specified does not exist.
-sd:device name
Command Line
609
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -sfile list Function Description
Specifies the host path of files to be backed up and aliased. The list should be comma delimited. By default, subdirectories will be recursed; to skip subdirectories during backup, /n should be placed before the last quotation mark. For example: c:\dir\file or \\server\ share name\..."/n The order resource selections are specified is the order in which the resources will be backed up. 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 or shadow copy components must be ordered last. Note This switch cannot be used with the -sf switch.
-aalias list
Specifies a second host drive (the device alias) for all the selections listed in the -s switch list. The device that you specify must be a drive letter followed by a colon, such as "G:". You must include a matching comma delimited list of aliases for the selections specified in the -s switch list. Note This switch cannot be used with the -sf switch.
610
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -sf:filename Function Description
Use this switch instead of -s and -a to specify the name of a file that contains a list (one per line) of files to be backed up. Note This switch cannot be used with the -s and -a switches.
-pr:priority
-r
Replace existing Specifies Backup Exec to replace a previously job defined job with this new one. You can replace a job that was created either through the Command Line Applet or the Backup Exec user interface, as long as that job has already been created and saved. Specifies the Intelligent Image Option for a backup job, where Intelligent Image Option value corresponds to: 1 = Use Intelligent Image Option for this backup operation. 2 = Use Intelligent Image Option and use server free backup if available. Note The colon (:) must be included.
-fi:
-w
Specifies that the Command Line Applet should wait for the operation to complete before returning.
Command Line
611
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches Function Description
-o90
Launch job using Executes a job based on the contents of a job script file script file. Return values depend on the type of script. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. For more information about Backup Job Script Files, see Using Backup or Restore Job Script Files on page 660. -fscript file Required. Specifies the name of the Backup Exec script file. If the job is a scheduled job (not a run now job), the -w is ignored. Wait for job completion Instructs the Command Line Applet to wait for the operation to complete before returning. If the job is a scheduled job (not a run now job), the -w is ignored. Creates a list of resource selections to be used when creating a backup job. Required. Specifies the name of the script to run with this command. Describes the script being used.
-w
-o220
Create selection list -sscript name
-dscript description -fscript file
Required. Specifies the selections to be contained in this selection list. Format for scripts is [MACHINE] MACHINE1=machine name|logon ID Each path must be on a separate line. For example: PATH1=C:\test\*.*|logon ID PATH2=C:\test2\*.*
-o230
Create backup job template
Creates a backup job template that can be used for creating jobs. Displays the job ID if successful. Required. Specifies a name for the template being created.
-tn:job template name
612
Using Command Line Switches Backup Job Commands (continued) Operation Additional Switches -fscript file Function Description
Required. Specifies the name of the Backup Exec script file. For more information about Backup Job Template script files, see Using Scripts and Backup Job Templates on page 713. Create backup job from template Creates a backup job using a previously created backup job template.
-o240
-jjob name
Required. Specifies the name that Backup Exec will assign to this job. Required. Specifies the name of the template to use when creating this job. Required. Specifies any previously created selection list to be used when creating this job. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-tn:job template name -s:selection list -pr:priority
-ac:auto cancel time
Specifies that the job is to be automatically canceled if not completed within a certain time. Specifies that the job is to be submitted on hold.
-h
Command Line
613
Switches for Administrating Jobs

Several command switches allow you to administer your jobs. These switches, which allow you to obtain information about the jobs, view job histories, and cancel a job, include:
Job monitoring switches Operation Additional Switches Function Description
-o10
Get number of scheduled jobs
Displays the number of scheduled jobs on a computer. Returns a 1 if the command succeeds or a -1 if the command fails. Instructs Backup Exec to dump the job IDs to the screen.
-i
Dump job IDs
-j
Dump job names Instructs Backup Exec to dump the job names to the screen. Get number of active jobs Displays the number of active jobs on a computer. Returns a 1 if the command succeeds or a -1 if the command fails. Instructs Backup Exec to dump the job IDs to the screen.
-o11
-i
Dump job IDs
-j
Dump job names Instructs Backup Exec to dump the job names to the screen. Get number of completed jobs Displays the number of completed jobs on a computer. Returns a 1 if the command succeeds or a -1 if the command fails. Instructs Backup Exec to dump the job IDs to the screen.
-o12
-i
Dump job IDs
-j
Dump job names Instructs Backup Exec to dump the job names to the screen.
614
Using Command Line Switches Job monitoring switches (continued) Operation Additional Switches Function Description
-o13
Get number of Displays the number of active utility jobs on a active utility jobs computer. Returns a 1 if the command succeeds or a -1 if the command fails. A utility job is one involving drive utility operations such as inventory, erase, retension, format, label media, and eject.
-o14
Get number of completed utility jobs
Displays the number of completed utility jobs on a computer. Also returns a 1 if the command succeeds or a -1 if the command fails. A utility job is one involving drive utility operations such as inventory, erase, retension, format, label media, and eject.
-o15
Get job status
Displays one of many predefined job statuses if the command was successful. Also returns a 1 if the command succeeds or a -1 if the command fails. Specifies the job ID of a specific job. Note The colon (:) must be included.
-i:job ID
-o16
Dump job status Copies to the console the job information and for scheduled descriptive headings for each item associated and active job with the job ID. Returns 1 if the command was successful or -1 if the command failed. -i:job ID Specifies the job ID of a specific job. Note The colon (:) must be included. -a Abbreviated form Specifies Backup Exec to display the job information in comma delimited, or data only (no headings) form. Cancels a job. Returns 1 if the command was successful or a -1 if the command failed. Required. Use this switch to specify the job ID of a specific job. Note The colon (:) must be included.
-o20
Cancel job
-i:job ID
Command Line
615
-o21
Dump completed job status -ijob ID
Displays completed job status. Returns 1 if the command was successful or -1 if the command failed. Use this switch to display the last job history for the specified job ID. Use this switch with -ijob ID to display details for the last instance of the job. Use this switch to display details of the specified job history record. Note The colon (:) must be included.
-e
-hi:job history ID
-li:job ID
Use this switch to display a list of all job history IDs for the specified job ID. Note The colon (:) must be included.
-o30
Dump job log name of completed job
Copies to the console the job log name that is associated with the specified job ID. Returns 1 if the command was successful or -1 if the command failed. Required. Use this switch to specify the job ID of a specific job. Note The colon (:) must be included.
-i:job ID
-o31
Dump job log contents
Copies to the console the contents of the job log specified on the command line. Returns 1 if the command was successful or -1 if the command failed. Specifies the job log name.
-ffile name -o200 Place Job on Hold -jjob name
Places the specified job on hold. Returns 1 if the command is successful or -1 if it failed. Required. Specifies the name of the job to be placed on hold.
616
-o201
Take Job off Hold -jjob name
Takes the specified job off hold. Returns 1 if the command is successful or -1 if it failed. Required. Specifies the name of the job to be taken off hold.
-o202
-i:jobID
Delete scheduled job
Required. Use this switch to specify a job ID of a specific job. Returns 1 if successful or -1 if it failed. Displays all available backup job templates. Returns 1 if the command is successful or -1 if it failed. Displays all available backup selection lists. Returns 1 if the command is successful or -1 if it failed. Disables an error handling rule.
-o250
List all backup job templates
-o251
List all backup selection lists
-o312
Disable error handling rule -irule ID
Specifies the ID of the rule being disabled. Dump Job Information Displays job, selection, and schedule information stored on this server. Also returns a 1 if the command succeeds or a -1 if the command fails. Specifies the name of the job that contains information you want dumped. Specifies a file to direct the output to.
-o506
-jjob name
-foutput file
Command Line
617
Restore Job Switches

You can run a previously created restore job or launch a restore job script file through the following command line switches:
Restore job commands Operation Additional Switches Function Description
-o7
Restore job
Runs a restore job that has been previously defined for a media server. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. Required. Specifies the name of the previously defined job that Backup Exec should run. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-jjob name
-pr:priority
-w
-o90
Launch job using Executes a job based on the contents of a job script file script file. Return values depend on the type of script. Returns a job instance ID. Also returns a 1 if the command succeeds or a -1 if the command fails. For more information about Backup Job Script Files, see Using Backup or Restore Job Script Files on page 660. -fscript file Required. Specifies the name of the Backup Exec script file. If the job is a scheduled job (not a run now job), the -w is ignored.
618
Using Command Line Switches Restore job commands (continued) Operation Additional Switches -w Function Description
Instructs the Command Line Applet to wait for the operation to complete before returning. If the job is a scheduled job (not a run now job), the -w is ignored.
See also: Using Backup or Restore Job Script Files on page 660
Switches for Viewing and Responding to Alerts

Alerts are events that require administrator attention. Several command switches allow you to view and respond to alerts. These include:
Managing alerts switches Operation Additional Switches Function Description
-o40
Get number of alerts
Displays the number of alerts on the computer. Returns a 1 if the command succeeds or a -1 if the command fails. Displays all the alert IDs on the screen. Displays titles of alerts. Dumps the alert title and message to the console. Returns 1 if the command is successful and -1 if it fails. Specifies the alert ID of the text to be displayed. If the -i command switch is not used, all alerts are dumped by default. Note The colon (:) must be included.
-i -tl -o42
Dump alert IDs Show titles Dump alert text
-i:alert ID
-w
Instructs the Command Line Applet to prompt for a response to the alert.
Command Line
619
Using Command Line Switches Managing alerts switches (continued) Operation Additional Switches Function Description
-o43
Get number of Displays the number of non-critical information only (information only alerts) on the computer. alerts Also returns a 1 if the command succeeds or a -1 if the command fails. -i Dump all alert IDs Show titles Get number of user intervention (critical) alerts -i Dump all alert IDs Show titles If -i is used with this command, all alert IDs will be displayed on the screen. Displays alert titles. Displays the number of user intervention alerts on the computer. Also returns a 1 if the command succeeds or a -1 if the command fails. If -i is used with this command, all alert IDs will be displayed on the screen. Displays alert titles.
-tl -o44
-tl -o45
Clear all Clears all current information only alerts. information only Returns 1 if the command was successful or -1 if the command fails. alerts Respond to alert Allows you to respond to an alert. Returns 1 if the command succeeds, 0 if the alert was already responded to, or -1 if the command fails. -i:alert ID Required. Specifies the alert ID that you want to respond to. Note The colon (:) must be included. -rresponse Required. Specifies a response. Responses are OK, YES, NO, CANCEL, RETRY,or IGNORE. Wait for job completion Get all warning alerts Instructs the Command Line Applet to prompt for a response. Displays the number of warning alerts on the computer. Also returns a 1 if the command succeeds or a -1 if the command fails.
-o46
-w
-o47
620
Using Command Line Switches Managing alerts switches (continued) Operation Additional Switches -i Function Description
Dump all alert IDs Show titles Get all error alerts
If -i is used with this command, all alert IDs will be displayed on the screen. Displays alert titles. Displays the number of error alerts on the computer. Also returns a 1 if the command succeeds or a -1 if the command fails. If -i is used with this command, all alert IDs will be displayed on the screen. Displays alert titles. Displays alert categories. Returns 1 if command is successful and -1 if the command fails. If -i is used with this command, all alert IDs will be displayed on the screen. Displays alert names on screen.
-tl -o48
-i
Dump all alert IDs Show titles List alert categories
-tl -o49
-i
Dump all alert IDs Display alert category name Display event category Dump alert configuration
-j
-ac
Displays the alert category on screen.
-o50
Displays the configuration for alerts on screen. Returns 1 if command is successful and -1 if the command fails. Specifies an alert ID to display configuration information for.
-ialert category ID -o51 Set alert configuration -ialert category ID
Modifies the alert configuration.
Required. Specifies an alert ID to display configuration information for.
Command Line
621
Using Command Line Switches Managing alerts switches (continued) Operation Additional Switches -e Function Description
Enable alert
Enables the specified alert for reporting by Backup Exec. Some alerts types such as error and attention required are always enabled. Disables the specified alert for reporting by Backup Exec. Some alerts types such as error and attention required are always enabled and cannot be disabled. Enables the sending of notification when the alert occurs. Recipients must be configured to use this option. Disables the sending of notification when the alert occurs.
-d
Disable alert
-no:
Enable notification
-nn:
Disable notification
-jl:
Enable inclusion Sends the job log to the alert recipient of job log configured for notification. Disable inclusion of job log Enable sending of SNMP notifications Disables the inclusion of the job log to the alert recipient configured for notification.
-nj:
-s
Enables the sending of alert notifications through SNMP.
-ns:
Disable sending Disables the sending of alert notifications of SNMP through SNMP. notifications Enable event logging Disable event logging Set time for automatic clearing of alert Enables logging of events in Windows event log. Disables logging of events in Windows event log. Sets the time in minutes for Backup Exec to automatically clear the alert.
-rl:
-nr:
-ac:timeout
622
Using Command Line Switches Managing alerts switches (continued) Operation Additional Switches -na: Function Description
Disable automatic alert clearing
Disables the automatic clearing of alerts.
Switches for Error Handling Rules

Backup Exec has system-defined error-handling rules which determine how job errors are handled. They apply to all backup jobs and are defined based on the cause of the failure. The rules can be configured to automatically perform operations such as retry, pause, or cancel a job after a failure occurs. Error-handling rules are disabled by default.
Error Handling Rules switches Operation Additional Switches Function Description
-o310
Display error handling rules Enable error handling rule -irule ID -mr:maximum retries
Displays the error handling rules
-o311
Required. ID of rule that is to be enabled. Indicates retry job and the number of times the job is to be retried. The range for maximum retries is 1 to 9999. Indicates retry job and the number of minutes to wait before the job is retried. The range for the retry interval is 1 to 9999. Pause job on error Indicates the job is to be paused until the user has taken action to clear the error. If this switch is absent, the job will be canceled until its next scheduled run. Indicates the job is to be canceled if an error occurs.
-ri:retry interval
-pj:
-cj:
Cancel job on error
Command Line
623
Using Command Line Switches Error Handling Rules switches (continued) Operation Additional Switches Function Description
-o312
Disable error handling rule -irule ID
Disables the specified error handling rule.
Required. Specifies the error handling rule that is to be disabled.
Switches for Managing Media and Devices

Through the Command Line Applet, you can manage the storage devices attached to your media server, manage media in these devices, launch utility operations, and obtain status of your media server. You can also use commands to stop and start Backup Exec system services and create logon accounts for accessing systems. The device and media management switches available include:
Device and media management switches Operation Additional Switches Function Description
-o60
Pause drive
Pauses the drive specified. Returns a 1 if successful or -1 if the command fails. Required. Specifies the drives name. Resumes a previously paused drive specified on the command line. Returns a 1 if successful or -1 if the command fails. Required. Specifies the drives name.
-ddrive name -o61
. Resume drive
-ddrive name -o62 Is drive paused
Returns 1 if the drive specified on the command line is paused, 0 if not, and -1 if the command failed. Required. Specifies the drives name.
-ddrive name -o63 Get number of drives
Displays the number of managed drives. Returns a 1 if the command succeeds or a -1 if the command fails.
624
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -i -j -o64 Get number of drives available Function Description
Displays drive IDs for all drives. Displays names for all drives. Displays the number of managed drives that are online and not paused. Drives that are being used are considered online and are included in the number displayed. Returns a 1 if the command succeeds or a -1 if the command fails. Displays the number of managed drives that are paused. Returns a 1 if the command succeeds or a -1 if the command fails. Displays the number of managed drives that are offline. Returns a 1 if the command succeeds or a -1 if the command fails. Displays general properties of a drive. Returns a 1 if the command succeeds or a -1 if the command fails. Specifies the ID for the drive you want to display properties for. Specifies the name for the drive you want to display properties for. Abbreviated form Specifies Backup Exec to display the information in comma delimited, or data only (no headings) form.
-o65
Get number of drives paused
-o66
Get number of drives offline
-o67
Dump drive properties
-i:drive ID
-ddrive name
-a
-o68 -o69
Query devices Get number of media sets Displays the number of media sets. Returns a 1 if the command succeeds or a -1 if the command fails. Displays the media set IDs for all media sets. Displays the names of all media sets.
-i -j
Command Line
625
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches Function Description
-o80
Import drive slots
Imports a list of backup tapes. Returns job ID and 1 if the command was successful, or -1 if the command failed. Required. Specifies the robotic library to target for this operation. Auto inventory all slots. Note The colon (:) must be included.
-arobotic library -ai:
-s:slot numbers
Specifies the slots in the robotic library to target. This list should be comma delimited. If no slots are specified, then all will be targeted by default. Schedules the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. For more information about schedule file scripts, see Using a Schedule Script with Device and Media Operations on page 730. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-fschedule file
-pr:priority
-w
626
-o81
Export drive slots
Exports a list of backup tapes. Returns the job ID and a 1 if the command was successful, or a -1 if the command fails. Required. Specifies the robotic library to target for this operation. Specifies the slots in the robotic library to target. This list should be comma delimited. If no slots are specified, then all will be targeted by default. Schedule the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. For more information about schedule file scripts, see Using a Schedule Script with Device and Media Operations on page 730. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-arobotic library -s:slot numbers
-fschedule file
-pr:priority
-w
Instructs the Command Line Applet to wait for the operation to complete before returning. Specifies the export of expired media only.
-x -o82 Designate cleaning slot -arobotic library
Designates slot to be a cleaning slot. Returns 1 if successful or -1 if the command fails.
Command Line
Required. Specifies the robotic library to target for this operation.
627
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -s:slot numbers Function Description
Specifies the slots in the robotic library to target. This list should be comma delimited. If no slots are specified, then all will be targeted by default. Reset slot to be non-cleaning slot Designates a slot to be a non-cleaning slot. Returns 1 if successful or -1 if the command failed. Required. Specifies the robotic library to target for this operation. Specifies the slots in the robotic library to target. This list should be comma delimited. If no slots are specified, then all will be targeted by default. Get number of robots Displays the number of managed robots. Returns a 1 if the command succeeds or a -1 if the command fails. Displays the names of managed robots. Displays the robot IDs. Dump robot properties Displays property information for the specified robotic library. Returns 1 if the command is successful or -1 if the command fails. Required. Either -i or -d must be provided.If both -i and -d are provided, the -d parameter is used. Specifies the ID of the robotic library to display properties for.
-o83
-arobotic library -s:slot numbers
-o84
-a -i -o85
-irobot ID
-drobot name
Required. Either -i or -d must be provided. If both -i and -d are provided, the -d parameter is used. Specifies the name of the robotic library to display properties for.
628
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -a Function Description
Abbreviated form
Specifies Backup Exec to display the robotic library properties information in comma delimited, or data only (no headings) form. Displays the slot information with header descriptions. Required. Either -i or -d must be provided. If both -i and -d are provided, the -d parameter is used. Specify the robot ID for the library containing the slots.
-o86
Dump slot content -irobot ID
-drobot name
Required. Either -i or -d must be provided. If both -i and -d are provided, the -d parameter is used. Specify the robot name for the library containing the slots.
-s:slot number
Specify the slot number to display information for. If the slot number is not specified, the contents of all slots for the robotic library are displayed. Abbreviated form Specifies Backup Exec to display the slot information in comma delimited, or data only (no headings) form. Creates and runs a cleaning job on the specified drive. Returns the job ID and 1 if successful, or -1 if the command failed. Required. Specifies the name of the robotic library drive you want to target. Schedules the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. For more information about schedule file scripts, see Using a Schedule Script with Device and Media Operations on page 730.
-a
-o100
Create cleaning job
-ddrive name
-fschedule file
Command Line
629
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -pr:priority Function Description
-w
-o101
Create media set Creates a media set with the specified name. Returns a 1 if successful or -1 if the command fails. -mmedia name Required. Specifies the name of the new media set. Required. Specifies the overwrite protection period for the new media set. Enter the value -1 to set the overwrite protection level to infinite. Note The colon (:) must be included. -ap:append Required. Specifies the append period for the new media set. Note The colon (:) must be included.
-op:overwrite protection period
-o102
Create drive pool
Creates a drive pool with the specified name and assigns the given drives to it. Returns a 1 if successful, 0 if one or more specified drives cannot be found, or -1 if the command fails.
-dpdrive pool
Required. Specifies the name of the new drive pool.
630
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -ddrives Function Description
Required. Specifies a list of drives to add to the drive pool. The list should be comma delimited. Create inventory Creates an inventory job on a specified robotic job for robotic library. library Returns the job ID and 1 if successful, or -1 if the command failed. When using this command, you must also use the -arobotic library switch which is used to inventory all slots and drives on a specified robotic library.
-o103
-arobotic library -fschedule file
Required. Specifies the robotic library to target for this operation. Schedules the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. For more information about schedule file scripts, see Using a Schedule Script with Device and Media Operations on page 730. Specifies the slots in the robotic library to target. This list should be comma delimited. If no slots are specified, then all will be targeted by default. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-s:slot numbers
-pr:priority
Command Line
-w
Instructs the Command Line Applet to wait for the operation to complete before returning. 631
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -x Function Description
Uses media auxiliary memory for inventory, which allows the media to be identified without having to be mounted. Lock library door Locks the specified robotic library door. Returns the job ID and a 1 if successful, or -1 if the command failed. When using this command, you must also use the -arobotic library switch. Required. Specifies the robotic library to target for this operation. Schedules the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. For more information about schedule file scripts, see Using a Schedule Script with Device and Media Operations on page 730. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-o104
-pr:priority
-w
632
-o105
Unlock library door
Unlocks the specified robotic library door. Returns the job ID and a 1 if successful, or -1 if the command failed. When using this command, you must also use the -arobotic library switch. Required. Specifies the robotic library to target for this operation. Schedule the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. For more information about schedule file scripts, see Using a Schedule Script with Device and Media Operations on page 730. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-pr:priority
-w
Command Line
633
-o106
Set media overwrite protection period
Specifies the media overwrite level and overwrite options. Returns 1 if successful or -1 if the command failed. When using this command, you must also use the -o1 and -o0 switches. Required. Specifies the overwrite level; for example, -o1:4. Overwrite Levels include: 1 = None 2 = None with prompt 3 = Partial 4 = Partial with prompt 5 = Full
-ol:overwrite level
-o0:recyclable
Required. Specifies the overwrite options; for example, -o0:0. Overwrite options include: 0 = Use scratch media first 1 = Use recyclable media first
-o111
Erase media
Erases the tape in the specified drive according to the specified erase type (-e). Returns the job ID and a 1 if successful, or -1 if the command failed.
-ddrive name
Required. Specifies the drive name you want to target. If -s is used, -ddrive name will be the name of the robotic library. Required. Specifies the erase type. Erase types are: 1 = quick erase 3 = long erase Note The colon (:) must be included.
-e:erase type
634
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -fschedule file Function Description
Schedule the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. For more information about schedule file scripts, see Using a Schedule Script with Device and Media Operations on page 730. Specifies the slot numbers containing the media to be erased. If this switch is used, -d will represent the robotic library name. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-s:slot numbers
-pr:priority
-w
-o112
Retension media Retensions the tape in the specified drive. Returns the job ID and a 1 if successful, or -1 if the command failed. -ddrive name Required. Specifies the drive name. If -s is used, -ddrive name will be the name of the robotic library. Specifies the slot numbers containing the media to be retensioned.
-s:slot numbers
Command Line
635
-w
Instructs the Command Line Applet to wait for the operation to complete before returning. Labels the tape in the specified drive. Returns the job ID and a 1 if successful, or -1 if the command failed.
-o113
Label media
-ddrive name
Required. Specifies the drive name. If -s is used, -ddrive name will be the name of the robotic library. Required. Specifies the media name. Specifies the slot numbers containing the media to be labeled. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-mmedia name -sslot numbers
-pr:priority
636
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -w Function Description
Instructs the Command Line Applet to wait for the operation to complete before returning. Formats the tape in the specified drive. Returns the job ID and a 1 if successful, or -1 if the command failed. When using this command, you must also use the -ddrive name command.
-o114
Format media
-ddrive name
Required. Specifies the drive name. If -s is used, -ddrive name will be the name of the robotic library. Specifies the slot numbers containing the media to be formatted. Specifies the priority for the job. Priority options include: Low Lowest Medium High Highest
-s:slot numbers
-pr:priority
-w
-o115
Eject media from Ejects the tape in the specified drive. drive Returns the job ID and a 1 if successful, or -1 if the command failed. When using this command, you must also use the -ddrive name command. -ddrive name Required. Specifies the drive name.
Command Line
637
-w
-o116
Create a backup Creates a Backup Folder. Backup Exec allows folder you to create virtual devices called Backup Folders on the hard disk. These Backup Folders are used as destination devices for backup jobs. When you direct a backup job to a Backup Folder, the data is saved on disk as backup files. Returns 1 if the command is successful or -1 if it failed. -r Use this switch to make the backup folder being created a removable backup-to-disk folder. Otherwise, the folder will be a fixed (non-removable) folder. Specifies the folder name. When you create a Backup Folder, Backup Exec initially assigns it a name and path. You can rename a Backup Folder as long as you use a unique name. Renaming a Backup Folder changes the way it appears in Backup Exec, but does not change the location of the Backup Folder on the disk.
-ffolder name
638
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -ddirectory Function Description
Specifies the location for the folder. Note Backup jobs submitted to a Backup Folder cannot span disks. If the size of a backup job exceeds the amount of free space on the disk where the Backup Folder is located, the job will fail. Make sure that there is sufficient free space on a disk for a backup job before submitting it. Use the software data compression option to maximize the amount of data that can be stored on a disk. If the backup job fails because of insufficient disk space, the data backed up before the job fails can still be restored.
-o117
Inventory a stand-alone drive
Creates an inventory job on a specified stand-alone drive. Displays the job instance ID. Returns 1 if the command is successful, or -1 if the command fails. Required. Specifies the drive name. Schedules the job. If -fschedule file represents a scheduled job (not a run now job), then the -w option is ignored. Specifies the priority for the job. Priority options include: Highest High Medium Low Lowest If this switch is absent, the priority will be set as Medium.
-ddrive name -fschedule file
-pr:priority
Command Line
-x
Uses media auxiliary memory for inventory, which allows the media to be identified without having to be mounted. 639
Using Command Line Switches Device and media management switches (continued) Operation Additional Switches -w Function Description
Instructs the Command Line Applet to prompt for a response.
-o120
Delete media set Deletes the specified media set. Returns 1 if the command is successful or -1 if it failed. -mmedia set Required. Specifies the name of the media set. Delete drive pool -dp:drive pool Deletes the specified drive pool. Returns 1 if the command is successful or -1 or if it fails. Required. Specifies the name of the drive pool.
-o121
640
Backup Exec Services Commands

Several command line switches allow you to monitor and manage the Backup Exec services. These commands include:
Backup Exec service switches Operation Additional Switches Function Description
-o107
Set wizards as run
Sets the registry so that the startup wizards do not run. Returns 1 if successful or -1 if the command failed. Checks if the Backup Exec server is available. Returns 1 if the Backup Exec Server is available on the network, 0 if the server is not available, or -1 if the command fails. Required. Specifies the name of the media server.
-o500
Is Backup Exec server available
-cserver_name
-o501
Are Backup Exec Checks if the Backup Exec system services are system services running. Returns 1 if the Backup Exec services are running on the computer. If the system running services are not running, a 0 is displayed. If the command fails, a -1 is displayed. Start Backup Exec system services Starts all Backup Exec services on the specified computer. Returns 1 if all services start, 0 if any services fail, or -1 if the command fails. Stops all Backup Exec services on the specified computer. Returns 1 if all services stop, 0 if any services fail, or -1 if the command fails. Copies to the console each Backup Exec system service name and status. Returns 1 if successful or -1 if the command fails. This command outputs properties for a specified Backup Exec server. Returns 1 if successful. If an error occurs, a -1 is returned.
-o502
-o503
Stop Backup Exec system services
-o504
Dump Backup Exec system services status Dump Backup Exec server properties
-o505
Command Line
641
Logon Account Switches

The following switch and subswitches allow you to create logon accounts for accessing specific systems:
Logon Account switches Operation Additional Switches Function Description
-o210
Create logon account
Creates a logon account for accessing specific systems being backed up or restored. This operation returns a logon account ID and 1 if the command is successful, or -1 if the command fails. Required. Specifies the user name for this logon account. Required. Specifies the password for this logon account. Provides a description for this logon account. Use as default login account.
-nluser name
-plpassword
-ddescription -dl: -o211 Display logon accounts
Displays the logon account information on the console. Returns 1 if the command is successful, or -1 if the command fails.
642
Report Switches
The following switch and subswitches allow you to view and manage Backup Exec reports from the command line:
Report switches Operation Additional Switches Function Description
-o400 -i -rreport ID -j -psparamstr
Display report
Displays the report on screen. Lists all available report IDs. Specifies the report ID to view. Lists available parameter names. Specifies parameters and values to use in the form @param1name=value, =value..., @param2name=value, =value....
-o401 -i -rreport ID -j -psparamstr
Print report
Prints the report on the default printer. Lists all available report IDs. Specifies report ID to view. Lists available parameter names. Specifies parameters and values to use in the form @param1name=value, =value..., @param2name=value, =value....
-o402
Copy report to selected file format -i -rreport ID -j
Copies the report to a selected file format.
Lists all available report IDs. Specifies report ID to view. Lists available parameter names.
Command Line
643
Using Command Line Switches Report switches (continued) Operation Additional Switches -psparamstr Function Description
Specifies parameters and values to use in the form @param1name=value, =value..., @param2name=value, =value.... Fully qualified file name for storage location of output file. This option is valid only for reports saved in -RPT:, -DOC:, -XLS:, and -XML file types. Fully qualified directory name for storage location of output files. This command is only valid for reports saved in .HTML format. Use: -ft:0 to use .rpt with save data file type (default). -ft:1 for HTML file type. -ft:2 for XML file type. -ft:3 for Microsoft Excel file type. -ft:4 for Microsoft Word file type.
-ffilename
-ddirectory
-ft:format
-o403 -i -ffilename
Insert report
Adds a report to the available file list. Lists all available report IDs. Fully qualified filename for storage location of report file.
644
Setting Default Options

The command line switch -o300 allows you to set default options to be used for Backup Exec operations. The default options are set through a series of -do parameters and the use of a -dv parameter followed by the default value. For example, to set the job priority default to high, enter: -300 -do"DO_JOB_PRIORITY" -dv"3" or -300 -do:DO_JOB_PRORITY -dv:3 Note If the value contains a space or a colon, enclose the value with quotation marks. If the switch contains more than one letter and you are not using quotation marks to enclose the value, a colon must appear immediately after the switch. The default parameters set through the -o300 switch can be overridden when creating an individual job. The following default options can be set using the -o300 switch:
Default option parameters Option Name General Default Options DO_GENERAL_ ENABLESTATS Display progress Enter 1 to display the percent indicators for backup jobs complete number and gauge while a backup job is processing; otherwise, enter 0. These indicators allow you to monitor the progress of the job. Backup jobs may take a little longer to complete when this option is set because the target device must be scanned to determine the amount of data to be backed up. Note Due to the time required to scan the target device, selecting is option when backing up remote devices is not recommended. Function Description
Command Line
645
Using Command Line Switches Default option parameters (continued) Option Name DO_GENERAL_ STARTUPINVENTORY Function Inventory all drives on Backup Exec services startup Description Enter 1 to inventory all of the media in the storage devices when Backup Exec services are starting; otherwise, enter 0. Depending on the number of storage devices attached to the system, this process may take a few minutes. If you are using a robotic library, all of the robotic librarys slots are inventoried.
Job Default Options DO_JOB_PRIORITY Set job priority Specifies the priority for the job. If another job is scheduled to run at the same time as this job, the priority determines which job runs first. If a priority is not entered, the priority will be Medium. Priority options include: 0 = Low 1 = Lowest 2 = Medium 3 = High 4 = Highest DO_JOB_CMDEXELOC Select systems for preand post-job commands Specifies whether an .EXE or batch file command should run on both local and remote systems, on local systems only, or on remote systems only. Values that can be used with this command are: 0 = The command is to run on both local and remote systems. 1 = The command is to run only on the local system. 2 = The command is to run only on the remote systems. DO_JOB_RUNJOBIFPRE SUCCESS Run job only if the pre-job Enter 1 to run the job only if the pre-job command is successful. command is successful; otherwise, enter 0. If the pre-job command is not successful, the job does not run, and is marked as failed.
646
Using Command Line Switches Default option parameters (continued) Option Name DO_JOB_RUNPOSTIFJOB FAILS DO_JOB_RUNPOST Function Run post-job command even if the job fails. Description Enter 1 to run the post-job command even if the job fails; otherwise, enter 0.
Run post-job command if Enter 1 to run the post-job command pre-job command is only if the pre-job command is successful successful; otherwise, enter 0. Specify time interval for command Specifies the amount of time before or after the job in which the pre or post command should run.
DO_JOB_CMDTIMEOUT
DO_JOB_FAILIFCMDFAILS
Mark job as failed if either Enter 1 to have the job marked as command fails failed if either the pre-job or post-job command fails; otherwise, enter 0. Cancel the job if not completed within the specified time. Specifies the amount of time Backup Exec should wait for the job to complete before cancelling the job. This value should be provided in minutes. Specifies the drive pool or stand-alone drive to be used for processing the backup. Specifies the media set for the job.
DO_JOB_ CANCELTHRESHOLD
DO_JOB_ DEVICEGUID
Set default device for job
DO_JOB_ MEDIASETGUID
Set the default media set
Command Line
647
Using Command Line Switches Default option parameters (continued) Option Name Backup Default Options DO_BACKUP_TYPE Select default backup method Specifies the backup method to be used. Methods are: 0 = Full 1 = Copy 2 = Differential changed files 3 = Incremental changed files 4 = Daily 5 = Working set 6 = Incremental modified time 7 = Differential modified time 8 = Full modified time If 5 is entered as the value, a value must also be entered for DO_BACKUP_ LASTACCCESSEDDAY Function Description
DO_BACKUP_ SINGLEBACKUPNTFS
Enable single instance Enter 1 to ensure that only one instance backup for NTFS volumes of the backing file for NTFS volumes will be backed up regardless of the number of single instance store (SIS) links that point to it; otherwise, enter 0. Set last access date Note If 5 was entered as the value for DO_BACKUPT_TYPE, the DO_BACKUP_ LASTACCESSEDDAYS entry must be completed. Enter the number of days to include files last accessed during. For example, to specify a working set backup to include all files last accessed within 30 days, type: -do:DO_BACKUP_ LASTACCESSEDDAYS -dv:30
DO_BACKUP_ LASTACCCESSEDDAYS
648
Using Command Line Switches Default option parameters (continued) Option Name DO_BACKUP_ MEDIAOVERWRITE Function Set media overwrite protection Description Specify one of the following values: 0 = Overwrite 1 = Append, overwrite if no media available 2 = Append, no overwrite DO_BACKUP_ COMPRESSIONTYPE Set compression method Enter a number from 0 to 3 that corresponds with the type of compression to use. Options include: 0 = Hardware compression 1 = Software compression 2 = Hardware if available, otherwise software 3 = None DO_BACKUP_AUTOVERIFY Verify after backup Enter 1 to have Backup Exec automatically perform a verify operation to make sure the media can be read after the backup has been completed; otherwise, enter 0. Verifying all backups is recommended. Enter 1 if the checksums are to be calculated for each data stream written to tape, and then written in a separate stream immediately following the data stream. If 0 is entered, backup performance may be improved, but there will be no way to verify the integrity of the data on the tape. Enter 1 to back up mount points that direct a file or directory to a local disk or directory path; otherwise, enter 0. Using this option allows you to back up data that is linked to local files, but stored on another device without having to actually select the data.
DO_BACKUP_ INSERTCHECKSUMS
Calculate checksums
DO_BACKUP_ TRAVERSEPOINTS
Back up local mount points
Command Line
649
Using Command Line Switches Default option parameters (continued) Option Name DO_BACKUP_HSM Function Back up data in remote storage Description Enter 1 to back up data that has been migrated from primary storage to secondary storage; otherwise, enter 0. When using this option, the data will not be recalled to its original location; it will be backed up directly to the backup media. This option should not be used if: A single device containing one drive is used for secondary storage and backups because Remote Storage and Backup Exec will compete for use of the drive. You want to run a backup of the entire system because Backup Exec attempts to access all data that has been migrated to secondary storage and this may take a considerable amount of time. DO_BACKUP_ USECHANGEJOURNAL Use change journal Enter 1 to use Windows NTFS Change Journal to determine which files have been modified since the last full backup; otherwise, enter 0. This option can only be used with NTFS volumes and only when the backup method selected is either DIFFERENTIAL Using modified time or INCREMENTAL - Using modified time. Enter 1 to use the Open File Option if available; otherwise, enter 0.
DO_BACKUP_ USEOPENFILEOPTION
Use Open File Option if available
650
Using Command Line Switches Default option parameters (continued) Option Name DO_BACKUP_ OPENFILEMETHOD Function Description
Back up open files if Open Enter a number from 0 to 3 to specify File Option is not how to back up open files if the Open available File Option is not available. Values include: 0 = Never 1 = With a lock 2 = Without a lock 3 = If closed within x seconds
DO_BACKUP_ OPENFILESKIPSECS
Back up open file if closed If 3 was entered for the value for within x seconds DO_BACKUP_OPENFILEMETHOD, enter a number from 1 to 999 to specify the number of seconds Backup Exec is to wait for an open file to close before continuing the backup. If the files do not close during the specified interval, they are skipped.
Restore Default Options DO_RESTORE_ EXISTINGMETHOD Restore over existing files Enter 1 to overwrite files on the target device that have the same name as files that are being restored; otherwise, enter 0. Restore corrupt files Enter 1 to allow Backup Exec to restore corrupted files during the restore process; otherwise, enter 0 to allow Backup Exec to automatically exclude corrupt files from the restore process. Enter 0 if you want to restore the information for the junction points and the files and directories to which they are linked, overwriting existing junction points on your system. Enter 1 if you want to restore files and directories backed up from junction point links while retaining the systems current junction points.
DO_RESTORE_CORRUPT
DO_RESTORE_ JUNCMETHOD
Restore junction points method
Command Line
651
Using Command Line Switches Default option parameters (continued) Option Name Trial Job Default Options DO_TRIAL_ CHECKCREDENTIALS Check logon credentials for trial run job Enter 1 to verify that the logon account is correct for the volumes being backed up; otherwise, enter 0. Function Description
DO_TRIAL_ CHECKCAPACITY
Check media capacity for Enter 1 to test whether enough tape is trial run job available to complete the job; otherwise, enter 0. Note During the test run job, the number of scheduled jobs in the queue is not checked; therefore, jobs that are scheduled before the test run job may use the media that was available when the test run job was performed.
DO_TRIAL_CHECKMEDIA
Check media for trial run Enter 1 to test whether the media is job online and overwritable for a trial run job; otherwise, enter 0. Select method for determining trial run job size Enter 0 if you want to determine job size from a previous job history, or enter a 1 if you want to perform a pre-scan. Enter 1 to have the scheduled job placed on hold if any failures are detected during the test run; otherwise, enter 0.
DO_TRIAL_ DETERMINESIZEMETHOD
DO_TRIAL_ HOLDONFAILURE
Place job on hold if trial job fails
Advanced Open File Options DO_OPENFILE_METHOD Enter one of the following values: 0 = None 1 = Use Advanced Open File Option 2 = Use Intelligent Image Option and Advanced Open File Option 3 = Use Intelligent Image Option with server free backup
652
Using Command Line Switches Default option parameters (continued) Option Name Job Log Default Options DO_LOG_SUMMARYLEVEL Select summary level for job log Enter one of the following values for the job log summary level: 0 = Summary only 1 = Summary and directories 2 = Summary, directories, and files 3 = Summary, directories, files, and details. Function Description
DO_LOG_FILEBASE
Specify job log name
Specify a job log name FILENAME#.txt. The # starts at 00. The default is BEX#.txt.
SQL Default Options DO_SQL_BACKUPMETHOD Select the SQL backup method Select the backup method to be used for SQL databases by entering one of the following values: 0 = full 1 = log 2 = log no truncate 3 = differential
DO_SQL_ CHECBEFOREBACKUP
Consistency check before Select a consistency check to run before backup a backup. Values are: 0 = none 1 = full 2 = full with indexes 3 = physical
DO_SQL_ CONTINUEIFCHECKFAILS
Continue with backup if consistency check fails
Enter 1 if you want the backup job to continue if the consistency check fails; otherwise, enter 0.
Command Line
653
Using Command Line Switches Default option parameters (continued) Option Name DO_SQL_ CHECKAFTERBACKUP Function Consistency check after backup Description Select a consistency check to run after a backup. Values are: 0 = none 1 = full 2 = full with indexes 3 = physical DO_SQL_RESTOREMETHOD SQL restore method Select the default restore method for SQL databases. Values include: 0 = no recover 1 = recover 2 = standby DO_SQL_REPLACE Replace database or filegroups Enter 1 if you want to replace a Microsoft SQL Server v7.0 or later database or filegroup, even if another database or filegroup with the same name already exists on the server. Otherwise, enter 0. Select a consistency check to run after a restore. Values include: 0 = none 1 = full 2 = full with indexes 3 = physical DO_SQL_ ENABLEFGSUPPORT Exchange Default Options DO_XCH_ENABLE Enable Exchange support Enter 1 if you want to enable Exchange support; otherwise, enter 0. Enable filegroup support Enter 1 if you want to enable filegroup support; otherwise, enter 0.
DO_SQL_ CHECKAFTERRESTORE
Consistency check after restore
654
Using Command Line Switches Default option parameters (continued) Option Name Function Description
DO_XCH_BACKUPMETHOD Exchange backup method Select the default backup method to use for Exchange databases. Values include: 0 = full 1 = copy 2 = differential 3 = incremental DO_XCH_ MBOXBACKUPMETHOD Exchange mailbox backup method Select the default method for backing up Exchange mailboxes. Values are: 0 = full 1 = copy 2 = differential 3 = incremental DO_XCH_ SINGLEINSTANCEBACKUP Enable single instance backup for message attachments No loss restore Enter 1 if you want to enable single instance backup for message attachments; otherwise, enter 0. Enter 1 to restore without deleting existing job logs; otherwise, enter 0. Enter 1 to restore a public folder; otherwise, enter 0.
DO_XCH_NOLOSS
DO_XCH_PUBLIC
Restore public folder
DO_XCH_PRIVATE
Restore private mailboxes Enter 1 to restore private mailboxes; otherwise, enter 0. Select temporary location Enter the temporary location for log for log and patch files and patch files. Automatically recreate user accounts and mailboxes Enter 1 to have Backup Exec automatically recreate user accounts and mailboxes if they do not already exist on the server; otherwise, enter 0.
DO_XCH_LOGPATH
DO_XCH_ AUTOCREATEMAILBOX
Command Line
655
Using Command Line Switches Default option parameters (continued) Option Name Function Description
Lotus Domino Default Options DO_DOMINO_ BACKUPMETHOD Lotus Domino backup method Select the default method for backing up Lotus Domino databases. Values include: 0 = full 1 = differential 2 = incremental DO_DOMINO_ RECYCLELOGS DO_DOMINO_ SECONDSTOWAIT Mark archive logs for recycling Seconds to wait for database Enter 1 to mark archive logs for recycling; otherwise, enter 0. Specify the number of seconds for the restore process to wait for a database that is in use by entering a value from 0 to 999. Select the default option for handling database IDs during a restore. Values include: 0 = retain original IDs 1 = assign new database ID 2 = assign new database ID and replica ID. NetWare SMS Default Options DO_SMS_ BACKUPASEXPANDED Back up compressed files Enter 1 to have Backup Exec in decompressed form decompress, or expand, compressed files as they are backed up; otherwise, enter 0. Restore volume restrictions Enter 1 to restore NetWare volume restrictions; otherwise, enter 0.
DO_DOMINO_ RECOVEROPTION
Database identification
DO_SMS_ RESTOREVOL RESTRICT Catalog Default Options DO_CAT_USECATALOGS
Use storage media-based Enter 1 to use the catalog information catalogs from the media; otherwise, enter 0.
656
Using Command Line Switches Default option parameters (continued) Option Name DO_CAT_TRUNCATEFLAG Function Truncate catalogs Description Enter 1 to retain only the header information and to remove all file and directory details after the specified number of days; otherwise, enter 0. If you select this option, you must enter a value for DO_CAT_TRUNCATEDAYS. Enter the amount of days before file and directory details are removed from the catalogs. The value can be between 1 and 999.
DO_CAT_TRUNCATEDDAYS Amount of days before truncating catalogs
DO_CAT_REMOVEFLAG
Remove unused catalogs Enter 1 to remove unused catalogs after a specified number of days; otherwise, enter 0. If you select this option, you must enter a value for DO_CAT_REMOVEDAYS. Amount of days before removing unused catalogs Set catalog path Enter the amount of days before unused catalogs are removed. The value can be between 1 and 999. Specify a path on the volume for the catalog files.
DO_CAT_REMOVEDAYS
DO_CAT_PATH
Media Default Options DO_MEDIA_B2DLOCATION Backup-to-Disk default folder location DO_MEDIA_ OVERWRITELEVEL Set media overwrite protection level Specify a path on the volume for the Backup-to-Disk folder. Enter one of the following values: 1 = None 2 = None with prompt 3 = Partial 4 = Partial with prompt 5 = Full
Command Line
657
Using Command Line Switches Default option parameters (continued) Option Name DO_MEDIA_ OVERWRITEOPTIONS Function Set the media overwrite options Description Enter one of the following values: 0 = Overwrite scratch media before overwriting recyclable media contained in the targeted media set 1 = Overwrite recyclable media contained in the targeted media set before overwriting scratch media Intelligent Disaster Recovery Default Options DO_DISASTER_DATAPATH Disaster recovery data path Specify a path where a copy of the DR files for the protected computers will be stored. Specify an alternate data path where a second copy of the DR files can be stored.
DO_DISASTER_ ALTERNATEPATH
Alternate disaster recovery data path
Database Maintenance Default Options DO_DB_GROOM Remove old data from the Enter 1 if you want Backup Exec to Backup Exec database automatically delete old data from its database, using specified criteria. Otherwise, enter 0. Number of days to keep job history data Enter the number of days for job history data to remain on the Backup Exec database. Enter the number of days for alert history data to remain on the Backup Exec database. Enter the number of days for job logs to remain on the Backup Exec database. Enter the number of days for report data to remain on the Backup Exec database. Enter 1 if you want to perform a database consistency check; otherwise, enter 0. Administrators Guide
DO_DB_JOBHISTORYDAYS
DO_DB_ ALERTHISTORYDAYS
Number of days to keep alert history data
DO_DB_JOBLOGDAYS
Number of days to keep job logs Number of days to keep report data
DO_DB_REPORTDAYS
DO_DB_CONSISTENCY
Perform database consistency check
658
Using Command Line Switches Default option parameters (continued) Option Name DO_DB_COMPACT Function Description
Compact the Backup Exec Enter 1 if you want to compact the database Backup Exec database; otherwise, enter 0. Dump contents of Backup Enter 1 if you want to dump the Exec database contents of the Backup Exec database to the Backup Exec data directory so that it may be backed up. Otherwise, enter 0.
DO_DB_DUMP
Command Line
659
Using Backup or Restore Job Script Files

A job script file is a text (.txt) file that the Command Line applet can use with command line switch -o90 to create and launch backup or restore jobs. The backup job script file can contain all of the switches you would normally specify on the command line when using the Command Line Applet as well as additional switches that you set when creating the backup job script file. The backup job script file can also be used in conjunction with some of the switches. A sample backup job script file (bjscript.txt) and restore job script file (rjscript.txt) are included in the UTILS directory on the installation CD. To activate an entry in this sample file, delete the backslashes (\\) that comment out the line.
Creating a Backup Job Script File

Use a text editor, such as Notepad, to create a Backup Job Script File that contains seven sections and entries for each section. The seven sections of a Backup Job Script File are:

[General] [Backup_Options] [Media_Options] [Miscellaneous] [Schedule] [W2K] [Selections]
Each entry included for the various sections must be typed in capital letters and be immediately followed by an equal (=) sign. The value for the entry must immediately follow the equal sign and contain no spaces or quotes unless they are part of the value itself. For example, to specify in the script that the job name is Workstation Backups and the job type is backup, the script file for the [General] section would appear as: [General] JOB_TYPE=Backup JOB_NAME=Workstation Backups All possible entries for a Backup Job Script File are described in the following table. In creating a script file, you would not want to include all entries. For example, either INTERVAL_DAY or INTERVAL_WEEK, but not both entries, could be present in a script file.
660
Using Backup or Restore Job Script Files Possible backup job script file entries Section [General] JOB_TYPE=job type This field must be completed with a value of Backup. Type the name of the backup job. Type the name of the Backup Exec server where the operation is to be performed. If a server is not specified, the local server is used by default. Type the user name for logging into a remote Backup Exec server. If a user name is not specified, the current user name is used. Enter the password for logging into a remote Backup Exec server. If a password is not specified, the current password is used. Enter the priority for the job. If another job is scheduled to run at the same time as this job, the priority set determines which job runs first. If a priority is not entered, the priority will be Medium. Options are: Lowest Low Medium High Highest [Backup Options] BK_SET_NAME=backup set name Type the name of the backup set to be used by the job. Entry Description
JOB_NAME=job name SERVER
USERNAME=username
PASSWORD=password
JOB_PRIORITY=priority
Command Line
661
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry BK_METHOD=# Description Enter a number 0 through 9 corresponding to the backup method you want. Methods are: 0 = Full 1 = Copy 2 = Differential changed files 3 = Incremental changed files 4 = Daily 5 = Working set 6 = Incremental modified time 7 = Differential modified time 8 = Full modified time 9 = Archive - Delete files after successful copy backup If 5 is entered as the value, a value must also be entered for WORKING_SET_DAYS. IMAGE_BACKUP=# Select the method to be used for image backups. Methods are: 0 = None 1 = Use image option 2 = Use ServerFree Option DEVICE_NAME=device name Type the name of the device to be used for the backup. Enter YES as the value if you want to use the Advanced Open File Option if available. If Advanced OFO is unavailable, the OPEN_FILES_METHOD specified will be used.
USE_OPEN_FILE_OPTION=YES/NO
662
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry USE_FROZEN_IMAGE=YES/NO Description Specifies that the job will use frozen image backup without using the Advanced Open File Option. If the value is YES, the values IMAGE_BACKUP=1 and USE_OPEN_FILE_OPTION=NO must also be used. Enter a number 0 through 3 to specify how to back up open files. Selections include: 0 = Never 1 = If closed within a specified number of seconds. If this method is selected, use flag OPEN_FILE_WAIT_TIME to set the number of seconds for Backup Exec to wait; otherwise, the value set for default options will be used. 2 = With a lock 3 = Without a lock Note If 1 is entered as the value, Backup Exec will wait the number of seconds specified in OPEN_FILE_WAIT_TIME for the file to close before continuing the backup. If the files do not close during the specified interval, they are skipped. OPEN_FILE_WAIT_TIME=# Specifies the number of seconds Backup Exec is to wait for a file to close before continuing with the backup. Enter YES to retension the media before backup; otherwise, enter NO. Enter YES to retain the directory structure on the hard drive of the files backed up in an archive job; otherwise, enter NO.
OPEN_FILES_METHOD=#
RETENSION_MEDIA=YES/NO
PRESERVE_TREE_ON_ARCHIVE= YES/NO
Command Line
663
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry SINGLE_INSTANCE_FOR_NTFS=YES/NO Description Enter YES if single instance store is being used, and you want to ensure that only one instance of a file for NTFS volumes will be backed up regardless of the number of single instance store (SIS) links that point to it. Otherwise, enter NO. 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. Note Allocating fewer CPU cycles to a backup job results in slower backup performance. This field contains the following options: MEDIUM. Select this option to allocate the default number of CPU cycles the protected server will use during a Remote Agent backup. LOW. Select this option to allocate fewer server CPU cycles to the backup job. LOWEST. Select this option to allocate the fewest number of CPU cycles to the backup job.
REMOTE_AGENT_PRIORITY=#
664
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry WORKING_SET_DAYS=# Description Note If 5 was entered as the value for entry BK_METHOD=#, the WORKING_SET_DAYS entry must be completed and included in the Backup Job Script File. Enter the number of days to include files last accessed during. For example, if you want to specify for a working set backup to include all files last accessed within 30 days, type WORKING_SET_DAYS=30. EXCHANGE_ROOT=Exchange Server name If you are backing up an Exchange server, specify the Exchange server name, and then use the EXCHANGE_METHOD entry to specify how the backup is to be done. If you are backing up an Exchange server, use this entry. Enter a number 0 through 3 corresponding to the backup method you want for the Exchange database. Methods are: 0 = Backup All 1 = Backup Copy 2 = Backup Log Differential 3 = Backup Log Incremental SQL_ROOT=SQL Server name If you are backing up a SQL server, specify the SQL Server name and then use the SQL_METHOD entry to specify how the backup is to be done. If you are backing up a SQL server, use this entry. Enter a number 0 through 2 corresponding to the backup method you want for the SQL database. Methods are: 0 = Backup All
EXCHANGE_METHOD=#
SQL_METHOD=#
Command Line
1 = Backup Log 2 = Backup Log No Truncate
665
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry LOTUS_DOMINO_METHOD=# Description If you are backing up a Lotus Domino server, use this entry. Enter a number 0 through 2 corresponding to the backup method you want for the Lotus Domino database. Methods are: 0 = Full 1 = Differential 2 = Incremental LOTUS_DOMINO_RECYCLE_LOGS= YES/NO If you are backing up a Lotus Domino server, use this entry to indicate that the Lotus Domino server will reuse the transaction log after it has been backed up. YES = Recycle logs NO = Do not recycle logs NW_BK_MIGRATED=YES/NO Enter YES to back up migrated files, files that have been moved to an alternative storage medium, such as optical disk, by NetWare. Otherwise, enter NO. If you are backing up NetWare shares or volumes, include this entry in the Backup Job Script File. If you want to back up compressed files in decompressed form, enter YES as the value; otherwise, enter NO. Enter YES as the value if you want Backup Exec to overwrite a duplicate job if one exists; otherwise, enter NO. Enter YES if you are backing up a SQL server, have specified that a database consistency check is to be performed before the backup, and want the job to continue if the pre-backup database consistency check failed.
NW_BK_DECOMPRESS_FILES= YES/NO
OVERWRITE_JOB=YES/NO
CONTINUE_ON_DBCC=YES/NO
666
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry PRE_BK_DBCC=# Description If you are backing up a SQL server, include this entry and enter a value of 0 to 2 corresponding to an option for performing a pre-backup database consistency check. Options are: 0 = None 1 = No Index 2 = Full POST_BK_DBCC=# If you are backing up a SQL server include this entry and enter a value of 0 to 2 corresponding to an option for performing a post-backup database consistency check. Options are: 0 = None 1 = No Index 2 = Full SQL_STANDBY_OPTION=# This entry is for Microsoft SQL Server 2000 only. Select the Standby value to put the database in standby mode when the job log backup completes. Select the No Recover value to put the database in a loading state when the job log backup completes. Users cannot connect to or query the database while it is in a loading state. Values are: 0 = Standby 1=No Recover [Media Options] MEDIA_NAME=Media Name Specify a label for the new or overwritable media. Enter the name of the media set to be used for the backup. If the media has a password, specify the password.
MEDIA_SET=Media Set Name
MEDIA_PASSWORD=Media Password
Command Line
667
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry APPEND=YES/NO Description To append the job to the media set specified in the MEDIA_SET entry, enter YES as the value. If you want the job to overwrite the media set specified in the MEDIA_SET entry, enter NO as the value. If you do not enter a value, by default the job will be an overwrite job. APPEND_NO_OVERWRITE=YES If you want the job to either append to the media set specified in the MEDIA_SET entry, or if no appendable media is available then to overwrite, enter YES. Enter YES as the value to have Backup Exec automatically perform a verify operation to make sure the media can be read once the backup has been completed; otherwise, enter NO. Verifying all backups is recommended. Enter a number from 0 to 3 that corresponds with the type of compression to use. Options include: 0 = Hardware compression 1 = Software compression 2 = Hardware if available, otherwise software 3 = None Note To use the default Backup Exec compression type, do not include this entry in the script.
VERIFY=YES/NO
COMPRESSION_TYPE=#
668
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry CHECKSUM=YES/NO Description Enter YES as the value if checksums are to be calculated for each data stream written to tape, and then written in a separate stream immediately following the data stream. If NO is entered as the value, backup performance may be improved, but there will be no way to verify the integrity of the data on the tape. Enter YES to eject the media when the job completes; otherwise, enter NO.
EJECT_MEDIA=YES/NO
[Miscellaneous] PRE_JOB_COMMAND=command Specify a .EXE or batch file command that is to run on the media server before the backup operation starts. Specify a .EXE or batch file command that is to run after the backup operation completes. Enter YES to execute the post-job command only if the pre-job command was successful; otherwise, enter NO.
POST_JOB_COMMAND=command
COMMAND_RUN_POST_IF_ PRE_SUCCESS=YES/NO
COMMAND_RUN_JOB_IF_PRE_SUCCESS Enter YES to execute the job only if the =YES/NO pre-job command is successful; otherwise, enter NO. COMMAND_RUN_POST_ IF_JOB_FAILS=YES/NO Enter YES to execute the post-job command even if the job fails; otherwise, enter NO.
Command Line
669
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry COMMAND_FAIL_JOB_IF_FAILS= YES/NO Description Enter YES to allow the pre- and post-job commands to be successful only if completed with a return code of zero. Otherwise, enter NO. 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 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 pre- and post-job commands. If you enter NO, the success of the preand post-job commands is not determined based on the return code. COMMAND_AUTO_CANCEL_TIME=# Enter the number of minutes Backup Exec should wait before canceling a command that did not complete. Enter 0 to run the command on this media server or 1 to run the command on each server being backed up. Enter YES to print the job log when the job completes; otherwise, enter NO. Enter YES to use the job defaults from the Backup Exec Administration console for this job. All other options will be overwritten. Enter NO if you do not want the job defaults used. Enter YES to use the MAC address or service entry name specified with the NIC_ADDRESS entry. Enter NO to clear previous settings for the network interface, and to use any available network adapter. 670 Administrators Guide
COMMAND_RUN_OPTION=#
PRINT_LOG_FILE=YES/NO
USE_JOB_DEFAULTS=YES/NO
NIC_ENABLED=YES/NO
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry NIC_ADDRESS Description For Windows 2000 and later operating systems, enter the Media Access Control (MAC) address for the network interface you selected. For Windows NT 4 and earlier operating systems, enter the service entry name. To use this setting, NIC_ENABLED must be set to YES. NIC_SUBNET_ADDRESS If the setting used in NIC_ADDRESS is connected to multiple subnets, then enter the network ID based on the IP address and the subnet mask of the network interface card you selected. To view this ID, click the Tools menu, then click Options, then under Properties, click Network, and view the Network ID field. This setting corresponds to the network interface used in NIC_ADDRESS. You must also enter the NIC_SUBNET_MASK. NIC_SUBNET_MASK If the setting used in NIC_ADDRESS is connected to multiple subnets, then enter the mask that determines the subnet to which the network interface belongs. To view this ID, click the Tools menu, then click Options, then under Properties, click Network, and view the Subnet mask field. This setting corresponds to the network interface used in NIC_ADDRESS. You must also enter the NIC_SUBNET_ADDRESS. NIC_SUBNET_AUTOGET=YES/NO Enter YES to have Backup Exec use any available network adapter.
Command Line
671
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section [W2K] BACKUP_LOCAL_MOUNT_POINTS= YES/NO Enter a value of YES to back up mount points which direct a file or directory to a local disk or directory path. Using this command allows you to back up data that is linked to local files, but stored on another device without having to actually select the device. Enter a value of YES 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. This command should not be used if: A single device is used for secondary storage and backups and it contains one drive because Remote Storage and Backup Exec will compete for use of the drive. You want to run a backup of your entire system because Backup Exec attempts to access all data that has been migrated to secondary storage and this may take a considerable amount of time. [Schedule] SCHED_STARTTIME=HH:MM:SS Enter the start time in HH:MM:SS format for this job. Enter the latest time this job can start in HH:MM:SS format. Entry Description
BACKUP_REMOTE_STORAGE_HSM= YES/NO
SCHED_ENDTIME=HH:MM:SS
672
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry Description
SCHED_RESTART_INTERVAL=HH:MM:SS Enter the interval in HH:MM:SS format for the job to restart on each run day. For example, if you have set the job up to run every seven days, you can also set it up to run every four hours on its run day by entering SCHED_RESTART_INTERVAL=04:00: 00. SCHED_REPEAT_INTERVAL=X Enter the interval in days in which the job is to run. For example, if you want the job to run every seven days, enter SCHED_REPEAT_INTERVAL=7. Enter the date in mm/dd/yyyy format the interval is calculated from. Enter the date in mm/dd/yyyy format that the schedule becomes effective. Enter the days of the month you want the job to run in a comma delimited string. For example, to run the job on the first and 15th of the month, type: SCHED_DAYSOFMONTH=1,15 SCHED_DAYSOFWEEK Enter the day of the week, a forward slash, and the week of the month you want the job to run in a comma delimited string. Enter a value of 1-7 for the day of the week with 1 equaling Sunday, 2 equaling Monday, and so on. For the week of the month, values can be 1 for the first week, 2 for the second week, 3 for the third week, 4 for the fourth week, and 5 for the last week. For example, to run the job on Sunday for the first three weeks of the month, type: SCHED_DAYSOFWEEK=1/1,1/2,1/3
SCHED_ANCHOR=MM/DD/YYYY
SCHED_EFFECTIVE=MM/DD/YYYY
SCHED_DAYSOFMONTH=x
Command Line
673
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry SCHED_INCLUDEDATEx=MM/DD/YYYY Description Enter a specific date when the job should run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to run the first and 15th of August, type: SCHED_INCLUDEDATE1=08/01/2002 SCHED_INCLUDEDATE2=08/15/2002 SCHED_EXCLUDEDATEx=MM/DD/YYYY Enter a specific date, such as a holiday, when the job should not run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to not run on the first and 25th of August, type: SCHED_EXCLUDEDATE1=08/01/2002 SCHED_EXCLUDEDATE2=08/25/2002 DATE=MM/DD/YYYY Enter the start date for the job in mm/dd/yyyy format. Enter the start time for the job in hh:mm:ss format. Note The hour, minutes, and seconds must be separated by colons.
TIME=hh:mm:ss
674
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry INTERVAL_MINUTES=# Description If a number is specified, the job is scheduled to run every specified number of minutes. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. INTERVAL_HOURS=# If a number is specified, the job is scheduled to run every specified number of hours. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
Command Line
675
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry INTERVAL_DAYS=# Description If a number is specified, the job is scheduled to run every specified number of days. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. INTERVAL_WEEKS=# If a number is specified, the job is scheduled to run every specified number of weeks. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
676
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry WEEKS=FIRST,SECOND,THIRD, FOURTH,LAST or WEEKS=1,2,3,4,5 Description The job will be scheduled for the specified week of the month. For example, if the entry appears as WEEKS=FIRST, the job will be scheduled to run the first week of the month. Note If this entry is included in the Backup Job Script File, a value must also be provided for the WEEKDAY entry. Do not use this entry in conjunction with the INTERVAL entries, the DAYS, or the DAY_OF_MONTH entries. Note If the entry WEEKS is included in the Backup Job Script File, a value must also be provided for this entry. Enter the day of the week the job should be completed. Only one day can be entered in this entry, which works in conjunction with the WEEKS entry. DAYS=SUN/MON/TUES/WED/THU/FRI/SA If this entry is included in the Backup T Job Script File, the backup job will be scheduled for the indicated day or days. Multiple days can be included, but must be separated by commas. For example: DAYS=MON,WED,FRI Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAY_OF_MONTH entries.
WEEKDAY=SUN/MON/TUES/WED/ THU/FRI/SAT
Command Line
677
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry DAY_OF_MONTH=# Description If this entry is included in the Backup Job Script File, the backup job will be scheduled for the indicated day of the month. The value can range from 1 to 31. Only one number can be specified. Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAYS entries. RUN_IMMEDIATE=YES/NO Enter a value of YES if the job is to run immediately; otherwise, enter NO. Note This entry should be used only if no other entries are specified under the schedule section. If no other scheduling options have been selected and this entry is not set to YES, the job will be created but not scheduled. HOLD=YES/NO Enter YES as the value if you want to schedule the job on hold; otherwise, enter NO. Enter the number of minutes after which the job is canceled if it is not completed. Backup Exec starts timing the job when the job is queued, not when the job begins. Enter the value of YES to place a job on hold if it fails; otherwise, enter NO.
AUTO_CANCEL_TIME=#
HOLD_ON_JOB_FAILURE= YES/NO
678
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section [Selections] PATHx=String Specify which files or directories get backed up. For example, PATH1=\\Myserver1\Myshare1\Myd ir1\*.* or PATH2=\\Myserver2\Myshare2\Myd ir2\*.* The order resource selections are specified is the order in which the resources will be backed up. INCLUDEx=YES/NO Enter YES to include this item in the backup job; otherwise, enter NO. Enter YES to include all subdirectories; otherwise, enter NO. Change x to a unique number and specify the name of the Exchange Server to back up. Specifies the name of the Exchange 2000 Server that contains this selection. Change ? to a number that corresponds to the number of the selection. The selections must be in a sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. Each selection must specify at least the server name and the storage group. See the example in EXCH2DB?=Exchange 2000 Server database name. Entry Description
SUBDIRSx-YES/NO
EXCHANGEx=Exchange Server name
EXCH2ROOT?=Exchange 2000 Server name
Command Line
679
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry EXCH2SG?=Exchange 2000 Server storage group name Description Specifies the name of the Exchange 2000 Server storage group to back up, or that contains the database to back up. Change ? to the same number used to identify the selection for the Exchange 2000 Server. See the example in EXCH2DB?=Exchange 2000 Server database name. EXCH2DB?=Exchange 2000 Server database name Specifies the name of the Exchange 2000 Server database to back up. Change ? to the same number used to identify the selection for the Exchange 2000 Server and storage group. In the following example, SERVER_NAME is an Exchange 2000 server name, and it is the same server in all of the selections. The first selection backs up the First Storage Group, the second selection backs up the Mailbox database in the Second Storage Group, and the third selection backs up the Users database in the Second Storage Group. EXCH2ROOT1=SERVER_NAME EXCH2SG1=First Storage Group EXCH2ROOT2=SERVER_NAME EXCH2SG2=Second Storage Group EXHC2DB2=Mailboxes EXCH2ROOT3=SERVER_NAME EXCH2SG3=Second Storage Group EXHC2DB3=Users SQLx=SQL Server name Change x to a unique number and specify the name of the SQL Server to back up.
680
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry SQL2S? =SERVER_NAME Description Specifies the name of the SQL Server 2000 that contains this selection. Change ? to a number that corresponds to the number of the selection. The selections must be in a sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. See the example in SQL2NI?=SQL Server 2000 named instance name. SQL2NI?=SQL Server 2000 named instance name Specifies the named instance on the SQL Server 2000 to back up. Change ? to the same number used to identify the selection for the SQL Server 2000. For example, to back up the named instance ONE, the named instance TWO, and the SQL Server 2000 itself, the entries would be: SQL2S1=SERVER_NAME SQL2NI1=ONE SQL2S2=SERVER_NAME SQL2NI2=TWO SQL2S3=SERVER_NAME
Command Line
681
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry LNSERVER?=SERVER_NAME Description Specifies the name of the Lotus Notes server that contains this selection. Change ? to a number that corresponds to the number of the selection. The selections must be in a sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. See the example in LNDRIVE?=Drive letter. LNDRIVE?=Drive letter Change ? to the same number used to identify the selection for the Lotus Notes server. In the following example, SERVER_NAME is a Lotus Notes server name, and it is the same server in all of the selections. To back up the D drive and the E drive on the Lotus Notes server SERVER_NAME, the entries would be: LNSERVER1=SERVER_NAME LNDRIVE1=D LNSERVER2=SERVER_NAME LNDRIVE2=E ORCLSRV?=SERVER_NAME Specifies the name of the Oracle server that contains this selection. Change ? to a number that corresponds to the number of the selection. The selections must be in a sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. See the example name in ORCLSID?=System Identifier for database.
682
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry ORCLSID?=System Identifier for database Description Specifies the SID (System Identifier) for the Oracle database to back up. Change ? to the same number used to identify the selection for the Oracle server. In the following example, SERVER_NAME is an Oracle server name, and it is the same server in all of the selections. To back up the databases SID1 and SID2 on the Oracle server, the entries would be: ORCLSRV1=SERVER_NAME ORCLSID1=SID1 ORCLSRV2=SERVER_NAME ORCLSID2=SID2 SPPSx=SharePoint Portal Server name Change x to a unique number and specify the name of the Microsoft SharePoint Portal Server to back up.
Command Line
683
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry APATHx=String Description Specify which files or directories get backed up and aliased when running an alias backup. The order resource selections are specified is the order in which the resources will be backed up. Change x to a unique number for each device aliasing backup selection. An alias backup allows you to specify a share to back up, and then specify another share from which the backup will appear to have originated. This type of backup is useful when the location of the data to be backed up is temporary. For example, a temporary share may be created when a mirror is split. Or a share may be cloned and placed on another device while it is backed up in order to off load traffic from a busy device. If a temporary share is backed up, the restore path for the share may not exist if a restore becomes necessary. Instead, you can specify an alias to a location where you want the share to appear to have been backed up from. For example: APATH1=\\MachineA\C$\*.* AINCLUDE1=yes ASUBDIRS1=yes AALIAS1=\\MachineB\D$ indicates that \\MachineA\C$\*.* and all its subdirectories should be backed up and aliased as \\MachineB\D$. Note The schedule option RUN_IMMEDIATE=YES must be included or the alias selection will be ignored.
684
Using Backup or Restore Job Script Files Possible backup job script file entries (continued) Section Entry AINCLUDEx=YES/NO Description Enter YES to include this item in the backup job when running an alias backup; otherwise, enter NO. Change x to a unique number for each alias backup selection. ASUBDIRSx-YES/NO Enter YES to include all subdirectories when running an alias backup; otherwise, enter NO. Change x to a unique number for each device aliasing backup selection. AALIASx=String Specify the share from which the backup will appear to have originated, when running an alias backup. Change x to a unique number for each device aliasing backup selection. For example: AALIAS1=\\MachineB\D$ See also the example for APATHx=String
Command Line
685
Creating a Restore Job Script File

Use a text editor, such as Notepad, to create a restore job script file that contains entries for the restore job options. The restore job script file has similar entries, or values, as those used in the backup job script file. Sections of a Restore Job Script include:

[General] [Restore_Options] [Selections] [Schedule]
Each entry included in the restore job script file must be typed in capital letters and be immediately followed by an equal (=) sign. The value for the entry must immediately follow the equal sign and contain no spaces or quotes unless they are part of the value itself. For example, to specify in the script that the job name is Workstation Restore and the job type is restore, the script file would appear as: [General] JOB_TYPE=Restore JOB_NAME=Workstation Restore All possible entries for a restore job script file are described in the following table. In creating a script file, you would not want to include all entries.
Possible restore job script file entries Section [General] JOB_TYPE=job type This field must be completed with a value of Restore. Type the name of the restore job. Type the name of the media server where the operation is to be performed. If a server is not specified, the local server is used by default. Type the user name for logging into the system being restored. If a user name is not specified, the current user name is used. Entry Description
JOB_NAME=job name SERVER=server name
USERNAME=user name
686
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry PASSWORD=password Description Type the password for logging into the system being restored. If a password is not specified, the current password is used. Enter the priority for the job. If another job is scheduled to run at the same time as this job, the priority set determines which job runs first. If a priority is not entered, the priority will be Medium. Options are: Lowest Low Medium High Highest [Restore Options] RESTORE_CORRUPT_FILES=YES/NO Enter YES if you do not want Backup Exec to automatically exclude corrupt files from the restore process; otherwise, enter NO. Enter YES to restore over existing files; otherwise, enter NO. Enter YES to restore file level security information on NTFS partitions if it exists in the selected data; otherwise, enter NO. Enter YES to restore the data with its original directory structure intact. Enter NO to restore all data (including the data in subdirectories) to the path specified in SHARE_REDIRECT_PATH.
JOB_PRIORITY=priority
RESTORE_EXISTING=YES/NO
RESTORE_SECURITY=YES/NO
RESTORE_PRESERVE=YES/NO
Command Line
DEVICE_NAME=device name
Type the name of the device, such as a drive or backup-to-disk folder, containing the data to be restored.
687
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry SHARE_REDIRECT_DRIVE=drive letter Description Type a destination drive, other than where the data was originally backed up, to which the data is to be restored. Type the target path on the drive specified in SHARE_REDIRECT_DRIVE. To retain the original directory structure, make sure that the value for RESTORE_PRESERVE=YES. If the RESTORE_PRESERVE=NO option is not selected, all of the data will be restored to the path designated in this field. SQL_REDIRECT_SERVER= SQL Server Name If you are redirecting SQL data, type the name of the SQL server where the data is to be restored. If you are redirecting SQL data to a named instance, specify the instance name. Otherwise, the data is restored to the default instance. If you are redirecting this restore to a different database on the target server, specify the target database name. If you are restoring a differential or log backup, and the associated database backup was restored to a renamed database, the new database name must be entered. If you are redirecting Exchange data, specify the Exchange server where the data is to be restored. If you are redirecting an Exchange mailbox, specify the name of the target mailbox. The mailbox must already exist before you can restore to it.
SHARE_REDIRECT_PATH=path name
SQL_REDIRECT_INSTANCE= instance name
SQL_REDIRECT_DATABASE= database name
XCH_REDIRECT_SERVER=Exchange server name
XCH_REDIRECT_MAILBOX=Exchange mailbox name
688
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry SP_REDIRECT_SETS_SERVER= SERVER/DOCUMENT SP_REDIRECT_DRIVE=drive name Description Specify whether server sets or document sets are being restored. Enter the name of the local drive or the UNC path to which you want to redirect the restore. If you type a UNC path, use the format server name\share name. Type the folder location on the drive to which you want to redirect the restore.
SP_REDIRECT_PATH=path
SP_REDIRECT_SERVER=\\server name Type the name of the computer to which you want to redirect the restore. Use the format \\server name. SP_REDIRECT_WORKGROUP= workspace name Type the name of the workspace to which you want to redirect the restore. Note You must type an entry in this field, even if you are restoring the data to the original workspace. You cannot redirect the restore to a different folder in the workspace. RESTORE_RSM_DATA=YES/NO Enter YES to restore the Removable Storage database; otherwise, enter NO. Enter YES to restore disk quota data; otherwise, enter NO. 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. Enter YES to restore the Terminal Services database, which contains licensing data for client licenses; otherwise, enter NO.
RESTORE_DISK_QUOTA=YES/NO
RESTORE_TERMINAL_SERVICES= YES/NO
Command Line
689
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry RESTORE_WMI=YES/NO Description Enter YES to restore the Windows Management Instrumentation (WMI) respository, which provides support for monitoring and controlling system resources and provides a consistent view of your managed environment; otherwise, enter NO. Enter YES to restore the cluster configuration; otherwise, enter NO. Enter YES to force the recovery of the cluster quorum even if other nodes are online the and/or disk signatures do not match option; otherwise, enter NO. Enter YES if all the domain controllers in the domain are being restored and you want to designate this server as the primary arbitrator. If you enter NO, replication may not function. Use this option when you perform a restore of a domain controller in a domain that does not have any other domain controllers. RESTORE_REGISTRY=YES/NO Enter YES to restore registry information if it exists in the selected data; otherwise, enter NO. This option applies to Windows NT 4.0 only. Enter YES to merge existing hardware configuration and registry services with the data to be restored when restoring registry information; otherwise, enter NO. Enter YES to restore junction points, files and directories from backup media, or enter NO to preserve existing junction points and restore files and directories from backup media.
RESTORE_CLUSTER_DB=YES/NO
RESTORE_FORCE_RECOVERY= YES/NO
RESTORE_PRIMARY_REPLICA=YES/NO
RESTORE_PNP_MERGE=YES/NO
RESTORE_JUNCSASDIRS=YES/NO
690
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry PRE_JOB_COMMAND=command Description Specify a .EXE or batch file command that is to run on the media server before the backup operation starts. Specify a .EXE or batch file command that is to run after the backup operation completes. Enter YES to execute the post-job command only if the pre-job command was successful; otherwise, enter NO.
COMMAND_RUN_JOB_IF_PRE_SUCCESS Enter YES to execute the job only if the =YES/NO pre-job command is successful; otherwise, enter NO. COMMAND_RUN_POST_ IF_JOB_FAILS=YES/NO Enter YES to execute the post-job command even if the job fails; otherwise, enter NO. Enter YES to allow the pre- and post-job commands to be successful only if completed with a return code of zero. Otherwise, enter NO. 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 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 pre- and post-job commands. If you enter NO, the success of the preand post-job commands is not determined based on the return code.
COMMAND_FAIL_JOB_IF_FAILS= YES/NO
Command Line
COMMAND_AUTO_CANCEL_ TIME=#
Enter the number of minutes Backup Exec should wait before canceling a command that did not complete. 691
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry COMMAND_RUN_OPTION=# Description Enter 0 to run the command on this media server or 1 to run the command on each server being restored to. Enter one of the following values for recovering the database: 0 = No recover 1 = Recover database 2 = Standby database SQL_REPLACE_DATABASE=YES/NO Enter YES to replace a database or file group, even if another database or filegroup with the same name already exists on the server; otherwise, enter NO. Enter YES to enable Backup Exec to stop SQL so that the master can be restored; otherwise, enter NO. If you enter YES, all existing users are logged off, and the master is put into single-user mode. SQL_POSTRESTORE_DBCC=# Enter one of the following values for performing a consistency check after restore: 0 = None 1 = Full check, excluding indexes 2 = Full check, including indexes 3 = Physical check only (SQL 2000 only) SQL_DEFAULT_DRIVE=drive letter Enter the drive letter for an alternate drive to which SQL database files will be restored.
SQL_DATABASE_RECOVER=#
SQL_AUTOMASTER=YES/NO
692
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry SQL_USE_ALLDEFAULT=YES/NO Description Enter YES to restore all SQL Server database files to the alternate drive specified in SQL_DEFAULT_DRIVE even if the drive where they originally resided exists. Enter NO to restore SQL database files to the alternate drive specified in SQL_DEFAULT_DRIVE only when the drive where they originally resided does not exist. SQL_USE_DEFAULT_INSTDIR=YES/NO Enter YES to restore all database files to the target instances data location; otherwise, enter NO. Enter the date and time to restore transactions for 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. Enter the named transaction to include in the recovery of the transaction log. Recovery will be stopped after this named transaction is restored. Enter YES to restore transactions from a transaction log up to a named transaction in the transaction log. After the named transaction, recovery from the transaction log is stopped. Otherwise, enter NO. Enter the date and time after which the restore operation is to search for the named transaction. Enter YES if you are restoring Exchange data and want Backup Exec to automatically recreate user accounts and mailboxes; otherwise, enter NO.
SQL_POINTINTIME=MM/DD/YYYY, HH:MM:SS
SQL_LOGMARK_NAME=named transaction
SQL_LOGMARK_INCLUDE=YES/NO
SQL_LOGMARK_TIME=MM/DD/YYYY,HH :MM:SS
XCH_AUTOCREATE_MAILBOX=YES/NO
Command Line
693
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry XCH_NOLOSS_RESTORE=YES/NO Description Enter YES if you are restoring Exchange 2000 data and do not want to delete the existing job logs; otherwise, enter NO. Enter YES if you are restoring Exchange data and want to restore public folders; otherwise, enter NO. Enter YES if you are restoring Exchange data and want to restore private mailboxes; otherwise, enter NO. Enter YES to preserve the existing transaction logs on the Exchange 2000 server; otherwise, enter NO. If you enter YES, transaction logs from the storage media are then restored and added to the existing set of transaction logs on the Exchange 2000 server. When the restore operation finishes, Exchange 2000 automatically updates its databases with the uncommitted transactions found in the existing and newly-restored transaction logs. This option is selected by default.
XCH_RESTORE_PUBLIC=YES/NO
XCH_RESTORE_PRIVATE=YES/NO
ESE_NOLOSS_RESTORE=YES/NO
694
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry ESE_TEMPLOG_PATH=path Description Enter a location where the associated log and patch files are to be kept until the database is restored. The default location is \temp. If storage groups are being restored, a subdirectory in \temp is created for each storage group. The log and patch files for each storage group are kept in the corresponding subdirectory. 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). 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. ESE_COMMIT_AFTER=YES/NO Enter YES to enable the restore operation to play through log files and roll back any uncompleted transactions if your selection contains the last backup set to be restored. If you enter NO, the database is left in an intermediate state and is not yet usable. If this option is selected when an intermediate backup is being applied, you cannot continue to restore backups. You must restart the restore operation from the beginning.
Command Line
695
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry ESE_MOUNT_AFTER=YES/NO Description Enter YES to mount the database so that it is available to users; otherwise, enter NO. This checkbox is only available if EXE_LASTSET is set to YES. Specify 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. Enter one of the following options for recovering a Lotus Domino database: 0 = Retain original IDs 1 = Assign new database IDs 2 = Assign new database IDs and replica IDs LOTUS_POINTINTIME=MM/DD/YYYY,HH: Enter a date and time from which to MM:SS restore the Lotus Domino database. RESTORE_VOL_RESTRICT=YES/NO Enter YES if you are restoring NetWare data and want to restore volume restrictions; otherwise, enter NO. Enter YES to use the MAC address or service entry name specified with the NIC_ADDRESS entry. Enter NO to clear previous settings for the network interface, and to use any available network adapter.
LOTUS_WAIT_MSECS=x
LOTUS_DBRECOVER_OPTION=#
NIC_ENABLED=YES/NO
696
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry NIC_ADDRESS Description For Windows 2000 and later operating systems, enter the Media Access Control (MAC) address for the network card you selected. For Windows NT 4 and earlier operating systems, enter the service entry name. An example is 00-B0-D0-D3-99-33. To use this setting, NIC_ENABLED must be set to YES. NIC_SUBNET_ADDRESS If the setting used in NIC_ADDRESS is connected to multiple subnets, then enter the network ID based on the IP address and the subnet mask of the network interface card you selected, for example, 10.212.10.113. To view this ID, click the Tools menu, then click Options, then under Properties, click Network, and view the Network ID field. This setting corresponds to the network interface used in NIC_ADDRESS. You must also enter the NIC_SUBNET_MASK. NIC_SUBNET_MASK If the setting used in NIC_ADDRESS is connected to multiple subnets, then enter the mask that determines the subnet to which the network interface belongs, for example, 255.255.254.0. To view this ID, click the Tools menu, then click Options, then under Properties, click Network, and view the Subnet mask field. This setting corresponds to the network interface used in NIC_ADDRESS. You must also enter the NIC_SUBNET_ADDRESS.
Command Line
697
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry NIC_SUBNET_AUTOGET=YES/NO Description Enter YES to have Backup Exec use any available network adapter; otherwise, enter NO.
[Selections] JOBHISTORY_GUID Specifies the backup job that has already run.
[Schedule] SCHED_STARTTIME=HH:MM:SS Enter the start time in HH:MM:SS format for this job. Enter the latest time this job can start in HH:MM:SS format.
SCHED_RESTART_INTERVAL=HH:MM:SS Enter the interval in HH:MM:SS format for the job to restart on each run day. For example, if you have set the job up to run every seven days, you can also set it up to run every four hours on its run day by entering SCHED_RESTART_INTERVAL=04:00: 00. SCHED_REPEAT_INTERVAL=X Enter the interval in days in which the job is to run. For example, if you want the job to run every seven days, enter SCHED_REPEAT_INTERVAL=7. Enter the date in mm/dd/yyyy format the interval is calculated from. Enter the date in mm/dd/yyyy format that the schedule becomes effective. Enter the days of the month you want the job to run in a comma delimited string. For example, to run the job on the first and 15th of the month, type: SCHED_DAYSOFMONTH=1,15
SCHED_DAYSOFMONTH=x
698
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry SCHED_DAYSOFWEEK Description Enter the day of the week, a forward slash, and the week of the month you want the job to run in a comma delimited string. Enter a value of 1-7 for the day of the week with 1 equaling Sunday, 2 equaling Monday, and so on. For the week of the month, values can be 1 for the first week, 2 for the second week, 3 for the third week, 4 for the fourth week, and 5 for the last week. For example, to run the job on Sunday for the first three weeks of the month, type: SCHED_DAYSOFWEEK=1/1,1/2,1/3 SCHED_INCLUDEDATEx=MM/DD/YYYY Enter a specific date when the job should run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to run the first and 15th of August, type: SCHED_INCLUDEDATE1=08/01/2002 SCHED_INCLUDEDATE2=08/15/2002 SCHED_EXCLUDEDATEx=MM/DD/YYYY Enter a specific date, such as a holiday, when the job should not run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to not run on the first and 25th of August, type: SCHED_EXCLUDEDATE1=08/01/2002 SCHED_EXCLUDEDATE2=08/25/2002 DATE=MM/DD/YYYY Enter the start date for the job in mm/dd/yyyy format. Enter the start time for the job in hh:mm:ss format.
TIME=hh:mm:ss
Command Line
Note The hour, minutes, and seconds must be separated by colons.
699
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry INTERVAL_MINUTES=# Description If a number is specified, the job is scheduled to run every specified number of minutes. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. INTERVAL_HOURS=# If a number is specified, the job is scheduled to run every specified number of hours. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
700
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry INTERVAL_DAYS=# Description If a number is specified, the job is scheduled to run every specified number of days. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. INTERVAL_WEEKS=# If a number is specified, the job is scheduled to run every specified number of weeks. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
Command Line
701
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry WEEKS=FIRST,SECOND,THIRD, FOURTH,LAST or WEEKS=1,2,3,4,5 Description The job will be scheduled for the specified week of the month. For example, if the entry appears as WEEKS=FIRST, the job will be scheduled to run the first week of the month. Note If this entry is included in the Backup Job Script File, a value must also be provided for the WEEKDAY entry. Do not use this entry in conjunction with the INTERVAL entries, the DAYS, or the DAY_OF_MONTH entries. Note If the entry WEEKS is included in the Backup Job Script File, a value must also be provided for this entry. Enter the day of the week the job should be completed. Only one day can be entered in this entry, which works in conjunction with the WEEKS entry. DAYS=SUN/MON/TUES/WED/THU/FRI/SA If this entry is included in the Backup T Job Script File, the backup job will be scheduled for the indicated day or days. Multiple days can be included, but must be separated by commas. For example: DAYS=MON,WED,FRI Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAY_OF_MONTH entries.
702
Using Backup or Restore Job Script Files Possible restore job script file entries (continued) Section Entry DAY_OF_MONTH=# Description If this entry is included in the Backup Job Script File, the backup job will be scheduled for the indicated day of the month. The value can range from 1 to 31. Only one number can be specified. Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAYS entries. RUN_IMMEDIATE=YES/NO Enter a value of YES if the job is to run immediately; otherwise, enter NO. Note This entry should be used only if no other entries are specified under the schedule section. If no other scheduling options have been selected and this entry is not set to YES, the job will be created but not scheduled. HOLD=YES/NO Enter YES as the value if you want to schedule the job on hold; otherwise, enter NO. Enter the number of minutes after which the job is canceled if it is not completed. Backup Exec starts timing the job when the job is queued, not when the job begins. Enter the value of YES to place a job on hold if it fails; otherwise, enter NO.
AUTO_CANCEL_TIME=#
HOLD_ON_JOB_FAILURE= YES/NO
Command Line
703
Using Scripts and Selection Lists
Saving and Launching the Backup or Restore Job Script File

After creating the backup or restore job script file, save it as a plain text file. When launching the job script file, specify the directory where the file resides along with the filename. To launch a script file, type the following at the command prompt: bemcmd -o90 -fdrive letter\directory\script name For example, suppose you created a directory for your scripts called Scripts and named a script for differential backups of workstations DIFFBKWORK. To launch this script with the verbose command, type: bemcmd -o90 -v -fc:\scripts\diffbkwork.txt

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 script that you can use in regularly scheduled operations or once-only operations. A sample selection script file (selectionscript.txt) is included in the UTILS directory on the installation CD. To activate an entry in this sample file, delete the backslashes (\\) that comment out the line. The selection list script is used with command -o220 to create a selection list.
Creating a Selection List Script File

Use a text editor, such as Notepad, to create a selection script file that contains all data selections for the backup job. Each entry included in the selection list script file must be typed in capital letters and be immediately followed by an equal (=) sign. The value for the entry must immediately follow the equal sign and contain no spaces or quotes unless they are part of the value itself.
704
All possible entries for a backup job template script file are described in the following table. In creating your script file, you would not want to include all entries.
Values for selection list script Section [Selections] PATHx=String Specify which files or directories get backed up. For example, PATH1=\\Myserver\Myshare\Mydir \*.* The order resource selections are specified is the order in which the resources will be backed up. 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 or shadow copy components must be ordered last. INCLUDEx=YES/NO Enter a value of YES if you want to include this item in the backup job; otherwise, enter NO. Enter a value of YES if you want to include all subdirectories; otherwise, enter NO. If you are backing up an Exchange server, specify the Exchange server name, and then use the EXCHANGE_METHOD entry to specify how the backup is to be done. Entry Description
SUBDIRSx-YES/NO
EXCHANGE_ROOT=Exchange Server name
Command Line
705
Using Scripts and Selection Lists Values for selection list script (continued) Section Entry EXCHANGEx=Exchange Server name Description Change x to a unique number and specify the name of the Exchange Server you want to back up.
EXCH2ROOTx=Exchange 2000 Server Specifies the name of the Exchange name 2000 Server that contains this selection. Change x to a number that corresponds to the number of the selection. The selections must be in a sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. Each selection must specify at least the server name and the storage group. See the example in EXCH2DB?=Exchange 2000 Server database name on page 680. EXCH2SGx=Exchange 2000 Server storage group name Specifies the name of the Exchange 2000 Server storage group that you want to back up, or that contains the database you want to back up. Change x to the same number used to identify the selection for the Exchange 2000 Server. See the example in .
706
Using Scripts and Selection Lists Values for selection list script (continued) Section Entry EXCH2DBx=Exchange 2000 Server database name Description Specifies the name of the Exchange 2000 Server database you want to back up. Change x to the same number used to identify the selection for the Exchange 2000 Server and storage group. In the following example, SERVER_NAME is an Exchange 2000 server name, and it is the same server in all of the selections. The first selection backs up the First Storage Group, the second selection backs up the Mailbox database in the Second Storage Group, and the third selection backs up the Users database in the Second Storage Group. EXCH2ROOT1=SERVER_NAME EXCH2SG1=First Storage Group EXCH2ROOT2=SERVER_NAME EXCH2SG2=Second Storage Group EXHC2DB2=Mailboxes EXCH2ROOT3=SERVER_NAME EXCH2SG3=Second Storage Group EXHC2DB3=Users SQL_ROOT=SQL Server name If you are backing up a SQL server, specify the SQL Server name and then use the SQL_METHOD entry to specify how the backup is to be done. Change x to a unique number and specify the name of the SQL Server you want to back up.
SQLx=SQL Server name
Command Line
707
Using Scripts and Selection Lists Values for selection list script (continued) Section Entry SQL2S? =SERVER_NAME Description Specifies the name of the SQL Server 2000 that contains this selection. Change ? to a number that corresponds to the number of the selection. The selections must be in a sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. See the example in SQL2NI?=SQL Server 2000 named instance name. SQL2NI?=SQL Server 2000 named instance name Specifies the named instance on the SQL Server 2000 to back up. Change ? to the same number used to identify the selection for the SQL Server 2000. For example, to back up the named instance ONE, the named instance TWO, and the SQL Server 2000 itself, the entries would be: SQL2S1=SERVER_NAME SQL2NI1=ONE SQL2S2=SERVER_NAME SQL2NI2=TWO SQL2S3=SERVER_NAME
708
Using Scripts and Selection Lists Values for selection list script (continued) Section Entry LNSERVER?=SERVER_NAME Description Specifies the name of the Lotus Notes server that contains this selection. Change ? to a number that corresponds to the number of the selection. The selections must be in sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. See the example in LNDRIVE?=Drive letter. LNDRIVE?=DRIVE_LETTER Change ? to the same number used to identify the selection for the Lotus Notes server. In the following example, SERVER_NAME is a Lotus Notes server name, and it is the same server in all of the selections. To back up the D drive and the E drive on the Lotus Notes server SERVER_NAME, the entries would be: LNSERVER1=SERVER_NAME LNDRIVE1=D LNSERVER2=SERVER_NAME LNDRIVE2=E ORCLSRV?=SERVER_NAME Specifies the name of the Oracle server that contains this selection. Change ? to a number that corresponds to the number of the selection. The selections must be in sequential order. Increase the number by one for each new selection. For example, the first selection would be 1, the second selection would be 2, etc. If the selections are out of sequence, they are not processed. See the example name in ORCLSID?=System Identifier for database.
Command Line
709
Using Scripts and Selection Lists Values for selection list script (continued) Section Entry ORCLSID?=System Identifier for database Description Specifies the SID (System Identifier) for the Oracle database you want to back up. Change ? to the same number used to identify the selection for the Oracle server. In the following example, SERVER_NAME is an Oracle server name, and it is the same server in all of the selections. To back up the databases SID1 and SID2 on the Oracle server, the entries would be ORCLSRV1=SERVER_NAME ORCLSID1=SID1 ORCLSRV2=SERVER_NAME ORCLSID2=SID2 SPPSx=SharePoint Portal Server name Change x to a unique number and specify the name of the Microsoft SharePoint Portal Server you want to back up.
710
Using Scripts and Selection Lists Values for selection list script (continued) Section Entry Description
Note Alias selections will be ignored unless RUN_IMMEDIATE=YES in the [Schedule] section of backup job or backup job template. APATHx=String Specify which files or directories get backed up and aliased when running an alias backup. The order resource selections are specified is the order in which the resources will be backed up. Change x to a unique number for each device aliasing backup selection. An alias backup allows you to specify a share to back up, and then specify another share from which the backup will appear to have originated. This type of backup is useful when the location of the data to be backed up is temporary. For example, a temporary share may be created when a mirror is split. Or a share may be cloned and placed on another device while it is backed up in order to offload traffic from a busy device. If a temporary share is backed up, the restore path for the share may not exist if a restore becomes necessary. Instead, you can specify an alias to a location where you want the share to appear to have been backed up from. For example: APATH1=\\MachineA\C$\*.* AINCLUDE1=yes ASUBDIRS1=yes AALIAS1=\\MachineB\D$ indicates that \\MachineA\C$\*.* and all its subdirectories should be backed up and aliased as \\MachineB\D$. Note The schedule option RUN_IMMEDIATE=YES must be included or the alias selection will be ignored.
Command Line
711
Using Scripts and Selection Lists Values for selection list script (continued) Section Entry AINCLUDEx=YES/NO Description Enter a value of YES if you want to include this item in the backup job when running an alias backup; otherwise, enter NO. Change x to a unique number for each alias backup selection. ASUBDIRSx-YES/NO Enter a value of YES if you want to include all subdirectories when running an alias backup; otherwise, enter NO. Change x to a unique number for each device aliasing backup selection. AALIASx=String Specify the share from which the backup will appear to have originated, when running an alias backup. Change x to a unique number for each device aliasing backup selection. For example: AALIAS1=\\MachineB\D$ See also the example for APATHx=String
712
Using Scripts and Backup Job Templates
Using Scripts and Backup Job Templates

You can create a backup job template by using a script file with command line switch -o230. A backup job template includes all destination, settings, and schedule options or a backup. After the template has been created, it can be used with command line switch -o240 to quickly create backup jobs. A sample backup job template script file (bjtemplatescript.txt) is included in the UTILS directory on the installation CD. To activate an entry in this sample file, delete the backslashes (\\) that comment out the line.
Creating a Backup Job Template Script File

Use a text editor, such as Notepad, to create a backup job template script file that contains all settings and options for a backup job, except for the data selections. Each entry included in the backup job template script file must be typed in capital letters and be immediately followed by an equal (=) sign. The value for the entry must immediately follow the equal sign and contain no spaces or quotes unless they are part of the value itself. For example, to specify in the script that the backup method is working set and that the device name is Backup-to-Disk Folder 1, the script should appear as: BK_METHOD=1 DEVICE_NAME="Backup-to-Disk Folder 1" All possible entries for a backup job template script file are described in the following table. In creating your script file, you would not want to include all entries.
Values for backup job template script Section Entry Description
[Backup Options] BK_SET_NAME=backup set name Type the name of the backup set to be used by the job.
Command Line
713
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry BK_METHOD=# Description Enter a number 0 through 9 corresponding to the backup method you want. Methods are: 0 = Full 1 = Copy 2 = Differential changed files 3 = Incremental changed files 4 = Daily 5 = Working set 6 = Differential modified time 7 = Incremental modified time 8 = Full modified time 9 = Archive - Delete files after successful copy backup If 7 is entered as the value, a value must also be entered for WORKING_SET_DAYS. IMAGE_BACKUP=# Select the method to be used for image backups. Methods are: 0 = None 1 = Use image option 2 = Use ServerFree Option DEVICE_NAME=device name Type the name of the device to be used for the backup. Enter YES as the value if you want to use the Advanced Open File Option if available; otherwise, enter NO. If Advanced OFO is unavailable, the OPEN_FILES_METHOD specified will be used.
USE_OPEN_FILE_OPTION=YES/NO
714
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry USE_FROZEN_IMAGE=YES/NO Description Specifies that the job will use frozen image backup without using the Advanced Open File Option. If the value is YES, the values IMAGE_BACKUP=1 and USE_OPEN_FILE_OPTION=NO must also be used. Enter a number 0 through 3 to specify how to back up open files. Selections include: 0 = Never 1 = If closed within specified number of seconds. If this method is selected, use flag OPEN_FILE_WAIT_TIME to set the number of seconds for Backup Exec to wait; otherwise, the value set for default options will be used. 2 = With a lock 3 = Without a lock Note If 1 is entered as the value, Backup Exec will wait the number of seconds specified in OPEN_FILE_WAIT_TIME for the job to close before continuing the backup. If the files do not close during the specified interval, they are skipped. OPEN_FILE_WAIT_TIME=# Specifies the number of seconds Backup Exec is to wait for a file to close before continuing with the backup.
OPEN_FILES_METHOD=#
Command Line
715
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry WORKING_SET_DAYS=# Description Note If 5 was entered as the value for entry BK_METHOD=#, the WORKING_SET_DAYS entry must be completed and included in the Backup Job Script File. Enter the number of days to include files last accessed during. For example, if you want to specify for a working set backup to include all files last accessed within 30 days, type WORKING_SET_DAYS=30. RETENSION_MEDIA=YES/NO Enter YES if you want Backup Exec to retension the media before backup; otherwise, enter NO. Enter YES if you want Backup Exec to retain the directory structure on the hard drive of the files backed up in an archive job; otherwise, enter NO. Enter YES if single instance store is being used, and you want to ensure that only one instance of a file for NTFS volumes will be backed up regardless of the number of single instance store (SIS) links that point to it. Otherwise, enter NO.
PRESERVE_TREE_ON_ARCHIVE= YES/NO
SINGLE_INSTANCE_FOR_NTFS=YES/NO
716
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry REMOTE_AGENT_PRIORITY=# Description 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. Note Allocating fewer CPU cycles to a backup job results in slower backup performance. This field contains the following options: MEDUM. Select this option to allocate the default number of CPU cycles the protected server will use during a Remote Agent backup. LOW. Select this option to allocate fewer server CPU cycles to the backup job. LOWEST. Select this option to allocate the fewest number of CPU cycles to the backup job. EXCHANGE_METHOD=# If you are backing up an Exchange server, use this entry. Enter a number 0 through 3 corresponding to the backup method you want for the Exchange database. Methods are: 0 = Backup All 1 = Backup Copy 2 = Backup Log Differential 3 = Backup Log Incremental
Command Line
717
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry SQL_METHOD=# Description If you are backing up a SQL server, use this entry. Enter a number 0 through 2 corresponding to the backup method you want for the SQL database. Methods are: 0 = Backup All 1 = Backup Log 2 = Backup Log No Truncate LOTUS_DOMINO_METHOD=# If you are backing up a Lotus Domino server, use this entry. Enter a number 0 through 2 corresponding to the backup method you want for the Lotus Domino database. Methods are: 0 = Full 1 = Differential 2 = Incremental LOTUS_DOMINO_RECYCLE_LOGS= YES/NO If you are backing up a Lotus Domino server, use this entry to indicate that the Lotus Domino server will reuse the transaction log after it has been backed up. YES = Recycle logs NO = Do not recycle logs NW_BK_MIGRATED=YES/NO Enter YES to back up migrated files, files that have been moved to an alternative storage medium, such as optical disk, by NetWare. Otherwise, enter NO. If you are backing up NetWare shares or volumes, include this entry in the Backup Job Script File. If you want to back up compressed files in decompressed form, enter YES as the value; otherwise, enter NO. Enter YES as the value if you want Backup Exec to overwrite a duplicate job if one exists; otherwise, enter NO. Administrators Guide
NW_BK_DECOMPRESS_FILES= YES/NO
OVERWRITE_JOB=YES/NO
718
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry CONTINUE_ON_DBCC=YES/NO Description Enter YES if you are backing up a SQL server, have specified that a database consistency check is to be performed before the backup, and want the job to continue if the pre-backup database consistency check failed. If you are backing up a SQL server, include this entry and enter a value of 0 to 2 corresponding to an option for performing a pre-backup database consistency check. Options are: 0 = None 1 = No Index 2 = Full POST_BK_DBCC=# If you are backing up a SQL server include this entry and enter a value of 0 to 2 corresponding to an option for performing a post-backup database consistency check. Options are: 0 = None 1 = No Index 2 = Full SQL_STANDBY_OPTION=# Note This entry is for Microsoft SQL Server 2000 only. Select the Standby value to put the database in standby mode when the job log backup completes. Select the No Recover value to put the database in a loading state when the job log backup completes. Users cannot connect to or query the database while it is in a loading state. Values are: 0 = Standby 1=No Recover
PRE_BK_DBCC=#
Command Line
719
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry Description
[Media Options] MEDIA_NAME=Media Name Specify a label for the new or overwritable media. Enter the name of the media set to be used for the backup. If the media has a password, specify the password. If you want the job to append to the media set specified in the MEDIA_SET entry, enter YES as the value. If you want the job to overwrite the media set specified in the MEDIA_SET entry, enter NO as the value. If you do not enter a value, by default the job will be an overwrite job. APPEND_NO_OVERWRITE=YES If you want the job to either append to the media set specified in the MEDIA_SET entry, or if no appendable media is available then to overwrite, enter YES. Enter YES as the value to have Backup Exec automatically perform a verify operation to make sure the media can be read once the backup has been completed; otherwise, enter NO. Verifying all backups is recommended.
MEDIA_SET=Media Set Name
MEDIA_PASSWORD=Media Password
APPEND=YES/NO
VERIFY=YES/NO
720
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry COMPRESSION_TYPE=# Description Enter a number from 0 to 3 that corresponds with the type of compression to use. Options include: 0 = Hardware compression 1 = Software compression 2 = Hardware if available, otherwise software 3 = None Note To use the default Backup Exec compression type, do not include this entry in the script. CHECKSUM=YES/NO Enter YES as the value if checksums are to be calculated for each data stream written to tape, and then written in a separate stream immediately following the data stream. If NO is entered as the value, backup performance may be improved, but there will be no way to verify the integrity of the data on the tape. Enter YES as the value if you want Backup Exec to eject the media when the job completes; otherwise, enter NO.
EJECT_MEDIA=YES,NO
[Miscellaneous] PRE_JOB_COMMAND=command Specify a .EXE or batch file command that is to run on the media server before the backup operation starts. Specify a .EXE or batch file command that is to run after the backup operation completes. Enter YES if you want the post-job command to be executed only if the pre-job command was successful; otherwise, enter NO.
Command Line
721
COMMAND_RUN_JOB_IF_PRE_SUCCESS Enter YES to execute the job only if the =YES/NO pre-job command is successful; otherwise, enter NO. COMMAND_RUN_POST_ IF_JOB_FAILS=YES/NO Enter YES to execute the post-job command even if the job fails; otherwise, enter NO. Enter YES to allow the pre- and post-job commands to be successful only if completed with a return code of zero. Otherwise, enter NO. 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 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 pre- and post-job commands. If you enter NO, the success of the preand post-job commands is not determined based on the return code. COMMAND_AUTO_CANCEL_TIME=# Enter the number of minutes Backup Exec should wait before canceling a command that did not complete. Enter 0 if you want the command to run on this media server or 1 if you want the command to run on each server being backed up. Enter YES as the value if you want the job log to print when the job completes; otherwise, enter NO.
COMMAND_FAIL_JOB_IF_FAILS= YES/NO
COMMAND_RUN_OPTION=#
PRINT_LOG_FILE=YES/NO
722
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section [W2K] BACKUP_LOCAL_MOUNT_POINTS= YES/NO Enter a value of YES to back up mount points which direct a file or directory to a local disk or directory path; otherwise, enter NO. Using this command allows you to back up data that is linked to local files, but stored on another device without having to actually select the device. Enter a value of YES to back up data that has been migrated from primary storage to secondary storage; otherwise, enter NO. The data will not be recalled to its original location; it will be backed up directly to the backup media. This command should not be used if: A single device is used for secondary storage and backups and it contains one drive because Remote Storage and Backup Exec will compete for use of the drive. You want to run a backup of your entire system because Backup Exec attempts to access all data that has been migrated to secondary storage and this may take a considerable amount of time. [Schedule] SCHED_STARTTIME=HH:MM:SS Enter the start time in HH:MM:SS format for this job. Enter the latest time this job can start in HH:MM:SS format. Entry Description
BACKUP_REMOTE_STORAGE_HSM= YES/NO
Command Line
723
SCHED_RESTART_INTERVAL=HH:MM:SS Enter the interval in HH:MM:SS format for the job to restart on each run day. For example, if you have set the job up to run every seven days, you can also set it up to run every four hours on its run day by entering SCHED_RESTART_INTERVAL=04:00: 00. SCHED_REPEAT_INTERVAL=X Enter the interval in days in which the job is to run. For example, if you want the job to run every seven days, enter SCHED_REPEAT_INTERVAL=7. Enter the date in mm/dd/yyyy format the interval is calculated from. Enter the date the schedule becomes effective. Enter the days of the month you want the job to run in a comma delimited string. For example, to run the job on the first and 15th of the month, type: SCHED_DAYSOFMONTH=1,15 SCHED_DAYSOFWEEK Enter the day of the week, a forward slash, and the week of the month you want the job to run in a comma delimited string. Enter a value of 1-7 for the day of the week with 1 equaling Sunday, 2 equaling Monday, and so on. For the week of the month, values can be 1 for the first week, 2 for the second week, 3 for the third week, 4 for the fourth week, and 5 for the last week. For example, to run the job on Sunday for the first three weeks of the month, type: SCHED_DAYSOFWEEK=1/1,1/2,1 /3
SCHED_DAYSOFMONTH=X
724
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry SCHED_INCLUDEDATEx=MM/DD/YYYY Description Enter a specific date when the job should run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to run the first and 15th of August, type: SCHED_INCLUDEDATE1=08/01/2002 SCHED_INCLUDEDATE2=08/15/2002 SCHED_EXCLUDEDATEx=MM/DD/YYYY Enter a specific date, such as a holiday, when the job should not run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to not run on the first and 25th of August, type: SCHED_EXCLUDEDATE1=08/01/2002 SCHED_EXCLUDEDATE2=08/25/2002 DATE=MM/DD/YYYY Enter the start date for the job in mm/dd/yyyy format. Note The start date month, day, and year must be separated by forward slashes. TIME=hh:mm:ss Enter the start time for the job in hh:mm:ss format. Note The hour, minutes, and seconds must be separated by colons.
Command Line
725
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry INTERVAL_MINUTES=# Description If a number is specified, the job is scheduled to run every specified number of minutes. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. INTERVAL_HOURS=# If a number is specified, the job is scheduled to run every specified number of hours. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
726
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry INTERVAL_DAYS=# Description If a number is specified, the job is scheduled to run every specified number of days. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. INTERVAL_WEEKS=# If a number is specified, the job is scheduled to run every specified number of weeks. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
Command Line
727
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry WEEKS=FIRST,SECOND,THIRD, FOURTH,LAST or WEEKS=1,2,3,4,5 Description The job will be scheduled for the specified week of the month. For example, if the entry appears as WEEKS=FIRST, the job will be scheduled to run the first week of the month. Note If this entry is included in the Backup Job Script File, a value must also be provided for the WEEKDAY entry. Do not use this entry in conjunction with the INTERVAL entries, the DAYS, or the DAY_OF_MONTH entries. Note If the entry WEEKS is included in the Backup Job Script File, a value must also be provided for this entry. Enter the day of the week the job should be completed. Only one day can be entered in this entry, which works in conjunction with the WEEKS entry. DAYS=SUN/MON/TUES/WED/THU/ FRI/SAT If this entry is included in the Backup Job Script File, the backup job will be scheduled for the indicated day or days. Multiple days can be included, but must be separated by commas. For example: DAYS=MON,WED,FRI Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAY_OF_MONTH entries.
728
Using Scripts and Backup Job Templates Values for backup job template script (continued) Section Entry DAY_OF_MONTH=# Description If this entry is included in the Backup Job Script File, the backup job will be scheduled for the indicated day of the month. The value can range from 1 to 31. Only one number can be specified. Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAYS entries. RUN_IMMEDIATE=YES/NO Enter a value of YES if the job is to run immediately; otherwise, enter NO. Note This entry should be used only if no other entries are specified under the schedule section. If no other scheduling options have been selected and this entry is not set to YES, the job will be created but not scheduled.
Creating a Backup Job Template Using a Script File

After a backup job template script file has been created and saved, you can create a backup job template by using command -o230 and its subswitches. For example, if you have created a script file called daily_script and you want to now created a template called daily_backup_template, you would enter the following at the command prompt: bemcmd -o230 -tn:daily_backup_template -fdrive letter\directory\daily_script
Creating a Backup Job from a Template

You can quickly create a backup job using the command switch -o240, a backup job template, and a selection list. For example, suppose you have created a template called daily_backup_template and a selection list called daily_backup_selections. You can now create a backup job called daily_backup by entering the following at the command prompt:
Command Line
bemcmd -o240 -jdaily_backup -tn:daily_backup_template -sdaily_backup_selections
729
Using a Schedule Script with Device and Media Operations
Using a Schedule Script with Device and Media Operations

Use a text editor, such as Notepad, to create a schedule script file that contains all settings and options for a device and media operation, such as cleaning a robotic library drive, that can be scheduled as a recurring job. Each entry included in the schedule script file must be typed in capital letters and be immediately followed by an equal (=) sign. The value for the entry must immediately follow the equal sign and contain no spaces or quotes unless they are part of the value itself. All possible entries for a schedule script file are described in the following table. In creating your script file, you would not want to include all entries. The following values are in the schedule script file:
Values for schedule script file Section [Schedule] SCHED_STARTTIME=HH:MM:SS Enter the start time in HH:MM:SS format for this job. Enter the latest time this job can start in HH:MM:SS format. Entry Description
SCHED_RESTART_INTERVAL=HH:MM:SS Enter the interval in HH:MM:SS format for the job to restart on each run day. For example, if you have set the job up to run every seven days, you can also set it up to run every four hours on its run day by entering SCHED_RESTART_INTERVAL=04:00: 00. SCHED_REPEAT_INTERVAL=X Enter the interval in days in which the job is to run. For example, if you want the job to run every seven days, enter SCHED_REPEAT_INTERVAL=7. Enter the date the day interval is calculated from. Enter the date the schedule becomes effective.
730
Using a Schedule Script with Device and Media Operations Values for schedule script file (continued) Section Entry SCHED_DAYSOFMONTH Description Enter the days of the month you want the job to run in a comma delimited string. For example, to run the job on the first and 15th of the month, type: SCHED_DAYSOFMONTH=1,15 SCHED_DAYSOFWEEK Enter the day of the week, a forward slash, and the week of the month you want the job to run in a comma delimited string. Enter a value of 1-7 for the day of the week with 1 equaling Sunday, 2 equaling Monday, and so on. For the week of the month, values can be 1 for the first week, 2 for the second week, 3 for the third week, 4 for the fourth week, and 5 for the last week. For example, to run the job on Sunday for the first three weeks of the month, type: SCHED_DAYSOFWEEK=1/1,1/2,1 /3 SCHED_INCLUDEDATEx=MM/DD/YYYY Enter a specific date when the job should run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to run the first and 15th of August, type: SCHED_INCLUDEDATE1=08/01/2002 SCHED_INCLUDEDATE2=08/15/2002 SCHED_EXCLUDEDATEx=MM/DD/YYYY Enter a specific date, such as a holiday, when the job should not run. For this field, x is a number starting at 1, which allows you to specify multiple dates. For example, if you want the job to not run on the first and 25th of August, type: SCHED_EXCLUDEDATE1=08/01/2002 SCHED_EXCLUDEDATE2=08/25/2002
Command Line
731
Using a Schedule Script with Device and Media Operations Values for schedule script file (continued) Section Entry DATE=MM/DD/YYYY Description Enter the start date for the job in mm/dd/yyyy format. Note The start date month, day, and year must be separated by forward slashes. TIME=hh:mm:ss Enter the start time for the job in hh:mm:ss format. Note The hour, minutes, and seconds must be separated by colons. INTERVAL_MINUTES=# If a number is specified, the job is scheduled to run every specified number of minutes. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
732
Using a Schedule Script with Device and Media Operations Values for schedule script file (continued) Section Entry INTERVAL_HOURS=# Description If a number is specified, the job is scheduled to run every specified number of hours. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. INTERVAL_DAYS=# If a number is specified, the job is scheduled to run every specified number of days. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other.
Command Line
733
Using a Schedule Script with Device and Media Operations Values for schedule script file (continued) Section Entry INTERVAL_WEEKS=# Description If a number is specified, the job is scheduled to run every specified number of weeks. Note Only one of the INTERVAL values should be specified (i.e., if you specify a value for INTERVAL_MINUTES, do not specify a value for INTERVAL_HOURS, INTERVAL_DAYS, or INTERVAL_WEEKS. Also, use either one of the INTERVAL values, or the WEEKS and WEEKDAYS, or the DAYS, or the DAYS_OF_MONTH entries. Unless specifically noted, these scheduling options should not be used in conjunction with each other. WEEKS=FIRST,SECOND,THIRD, FOURTH,LAST or WEEKS=1,2,3,4,5 The job will be scheduled for the specified week of the month. For example, if the entry appears as WEEKS=FIRST, the job will be scheduled to run the first week of the month. Note If this entry is included in the Backup Job Script File, a value must also be provided for the WEEKDAY entry. Do not use this entry in conjunction with the INTERVAL entries, the DAYS, or the DAY_OF_MONTH entries. Note If the entry WEEKS is included in the Backup Job Script File, a value must also be provided for this entry. Enter the day of the week the job should be completed. Only one day can be entered in this entry, which works in conjunction with the WEEKS entry.
734
Using a Schedule Script with Device and Media Operations Values for schedule script file (continued) Section Entry DAYS=SUN/MON/TUES/WED/THU/ FRI/SAT Description If this entry is included in the Backup Job Script File, the backup job will be scheduled for the indicated day or days. Multiple days can be included, but must be separated by commas. For example: DAYS=MON,WED,FRI Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAY_OF_MONTH entries. DAY_OF_MONTH=# If this entry is included in the Backup Job Script File, the backup job will be scheduled for the indicated day of the month. The value can range from 1 to 31. Only one number can be specified. Note Do not use this entry in conjunction with the INTERVAL entries, the WEEKS, or the DAYS entries. RUN_IMMEDIATE=YES/NO Enter a value of YES if the job is to run immediately; otherwise, enter NO. Note This entry should be used only if no other entries are specified under the schedule section. If no other scheduling options have been selected and this entry is not set to YES, the job will be created but not scheduled. AUTO_CANCEL_TIME=XMINUTES/HOURS Enter a number and select either MINUTES or HOURS to specify to cancel a job if not completed with the selected time. HOLD=YES/NO Enter YES if you want the job to be submitted on hold; otherwise, enter NO.
Command Line
735
Understanding Job Status Messages

The Command Line Applet displays job statuses as numeric values. Descriptions of possible job status return values are:
Possible job statuses Return Value Status 1 2 Canceled Completed Description Job is terminal due to cancellation. Job has been completed by the engine and is waiting final disposition. Job is terminal with success but there are some exceptions. Job has been sent for execution. Job is in a hold state. Job is terminal with an error. The schedule for the task is invalid. The time window is mutually exclusive thus job will never run. Job is eligible for dispatch and is late. Date of job makes it eligible to run, but time is not in window. Job is ready, but dispatcher is paused. The job needs to be dispositioned to an actual state. The system forced recovery of the job. Job has been disabled in the system. The job will be restarted with check point restart enabled, this value is only set in the job history summary. Job is currently running on server.
Success with exceptions
4 5 6 7 8
Dispatched Hold Error Invalid schedule Invalid time window
9 10
Missed Not in window
11 12 13 14 15
Ready but paused Pending Recovered Disabled Resumed
16
Active
736
Understanding Job Status Messages Possible job statuses (continued) Return Value Status 17 18 19 20 Ready Scheduled Success Superseded Description Job is eligible for dispatch. The job has a due date in the future. Job is terminal with success. Job is ready, but another higher precedence task is eligible to run. The job was aborted due to Abort Threshold time-out. The job needs to have the due date calculated. The job is linked to another job so will not start until the master job is finished.
21
Threshold auto-abort
22 23
To be scheduled Linked job
Command Line
737
738
Server Clusters
Using VERITAS Backup Exec with Server Clusters
15
In a server cluster, Backup Exec can protect data on local disks and shared disks, as well as Microsoft SQL and Exchange databases. Server clusters provide high availability of applications and data to users. In a server cluster, 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. Backup Exec protects data on the shared disks, as well as data on the nodes local disks. Backup Exec can also protect Microsoft SQL Server and Exchange Server 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). See also: Installing Backup Exec on a Cluster on page 742 Configurations for Backup Exec and Clusters on page 752 Backing Up Clusters on page 762 Restoring Data To Clusters on page 767 Requirements for Installing Backup Exec on a Cluster on page 741 Installing Additional Backup Exec Options on a Cluster on page 743 Specifying A Different Failover Node on page 749 Disaster Recovery of A Cluster on page 773
739
How Backup Exec Works in a Cluster
How Backup Exec Works in a Cluster

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. If the rule is enabled to retry jobs on a cluster failover, 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, and you can specify a different failover node if you add a new failover node. Additionally, 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. 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. See also: Configurations for Backup Exec and Clusters on page 752 Installing Backup Exec on a Cluster on page 742
740
Server Clusters
Requirements for Installing Backup Exec on a Cluster
Requirements for Installing Backup Exec on a Cluster
Two-node clusters are supported with Backup Exec for Windows NT, Windows 2000, and Windows.NET and Microsoft Windows 2000 Advanced Server and Windows.NET Enterprise. Two-node, four-node, and eight-node clusters are supported with Backup Exec for Windows NT, Windows 2000, and Windows.NET and Microsoft Windows 2000 DataCenter and Windows.NET DataCenter. Backup Exec Cluster can be installed on a Windows.NET majority node configuration. However, there must be a shared disk in the configuration in order for Backup Exec to share its database files between nodes. In this type of configuration, if the majority of the cluster nodes fail, then the entire cluster will fail. This configuration normally uses more than two nodes in the cluster configuration. The cluster administrator software must be installed on all Windows NT 4 and Windows 2000 servers that Backup Exec is installed on, including Backup Exec Remote Administrator installations; you must also have administrator rights to the server cluster. The cluster administrator allows you to view databases by their specific virtual server name; otherwise, databases appear to exist under all virtual server names in the cluster. The controlling node and designated failover nodes must be online during installation of Backup Exec. During installation of a Backup Exec cluster, the shared disk should be owned by the node on which the installation is run. An individually licensed copy of Backup Exec for Windows Servers, as well as any applicable agents and options, is required for each node in the cluster as defined in the End User License Agreement. You must enter a serial number for each node in the cluster (the cluster must have at least two nodes). When installing an evaluation version of Backup Exec, a cluster environment is automatically detected and serial numbers are not required. To upgrade a previous cluster version of Backup Exec, you must first uninstall the cluster version and save the data and catalog directories. Then reinstall Backup Exec and run the cluster wizard. Then copy the data and catalogs back to the cluster. 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.
See also: Installing Backup Exec on a Cluster on page 742 Configurations for Backup Exec and Clusters on page 752
Chapter 15, Using VERITAS Backup Exec with Server Clusters
741
Installing Backup Exec on a Cluster

Note We do not recommend installing Backup Exec on the same disk that the cluster quorum is installed on. If you have to specify a new drive letter for the quorum disk during a recovery process, Backup Exec will not recognize the new drive and will not run. For more information, see Specifying a New Drive Letter for the Cluster Quorum Disk on page 771. 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. For more information about the Remote Agent, see Installing the Remote Agent to Remote Windows Servers on page 823.
To install Backup Exec on a cluster: 1. Install Backup Exec on all the nodes that you want in the cluster. 2. From the node that you want to be the active node, start Backup Exec. 3. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. 4. Follow the instructions on the screen. Note On the Virtual Server Information screen, Backup Exec automatically displays a default name called BACKUPEXECVRS for the virtual server. You can type a new default name if you do not want to use the default. 5. When the Cluster Configuration Wizard completes, create a drive pool that contains all the locally-attached storage devices on each node to be used when failover occurs. This ensures that jobs can be run on the storage devices that are attached to the failover nodes. For more information, see Creating Drive Pools for Clusters on page 745. See also: Creating Drive Pools for Clusters on page 745 Enabling or Disabling Checkpoint Restart on page 747
742
Server Clusters
Configurations for Backup Exec and Clusters on page 752 Specifying A Different Failover Node on page 749
Installing Additional Backup Exec Options on a Cluster

Install additional Backup Exec options on each node of the cluster. For details on installing each option, see the appropriate section in this guide, or in online Help. Note If you are using the Advanced Open File Option, set those defaults on each physical node the option is installed on, not on the virtual server. Because the default settings for the static volume can be different on each node, Advanced Open File Option defaults do not fail over.
To install additional Backup Exec options: 1. On the controlling node, make sure the Backup Exec group is online before you start installing additional options. 2. Follow the instructions in Installing Backup Exec Options on a Local Server on page 49. 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. Note To install the Backup Exec Agent for Oracle Server and the R/3 Agent for Oracle Server on other nodes, map a drive to the shared disks where Backup Exec is installed on the cluster, and run SETUP. For more information, see Installing the Oracle Agent on page 1160 and Installing the Backup Exec R/3 Agent on page 1201.
743
Uninstalling Backup Exec From A Cluster
To uninstall Backup Exec from a cluster: 1. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. 2. Use the wizard to remove Backup Exec Cluster from all selected servers. You can now uninstall Backup Exec from the node. 3. 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. 4. On any node, click Start, point to Settings, and then click Control Panel to uninstall Backup Exec. 5. Double-click Add/Remove Programs, and then in the list of currently installed programs, select VERITAS Backup Exec for Windows Servers and click Change/Remove. 6. Repeat steps 4 and 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
744
Server Clusters
Creating Drive Pools for Clusters
Creating Drive Pools for Clusters

When Backup Exec is installed on a cluster, it creates default drive pools named All Drives (<Node Name>) for each node in the cluster. If a node has storage devices, those storage devices are automatically assigned to All Drives (<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 drive 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 drive pool. You must also select this drive pool as the destination device for all jobs that you want to be restarted. You can create either a single drive pool, or you can create drive pools for device or media types so that when jobs fail over they can be restarted on like devices and media.
To create a drive pool for a cluster: 1. From the controlling node, open Backup Exec. 2. Create a new drive pool. For information on creating drive pools, see Creating Drive Pools on page 97. 3. Add locally-attached storage devices and then exit Backup Exec. If there are tape devices on a shared SCSI bus, then add the tape device name used by each node. For information on adding devices to a drive pool, see Adding Drives to a Drive Pool on page 98. 4. Using the cluster administrator, move the Backup Exec resource group to the next appropriate node. 5. Open Backup Exec, add locally-attached storage devices for this node to the previous drive pool and then exit Backup Exec. If there are tape devices on a shared SCSI bus, then add the tape device name used by each node. 6. Repeat step 4 and step 5 for each node in the cluster.
745
Using Checkpoint Restart on Cluster Failover

You can enable or disable checkpoint restart for each backup job run on the cluster (by default, checkpoint restart is enabled). When checkpoint restart is enabled, jobs that were interrupted because of a failover continue from the point of interruption rather than starting over. Files that were already backed up are skipped, and only the remaining files in the job are backed up when the job is restarted. If this option is not selected, jobs are restarted from the beginning. Checkpoint restart works best for the following file types:

NTFS GRFS SMS Exchange mailboxes and public folders SQL database non-snapshot backups
The following types of files cannot use checkpoint restart:

System State Lotus Domino Exchange IS and DS GRFS Oracle NTFS Image sets NTFS Snapped volumes SQL database snapshot backups SQL transaction log backups
In addition, incremental backups based on the archive bit cannot use checkpoint restart. Jobs that are restarted from the point of failover display a status of Resumed in the Job Monitor. Before using checkpoint restart, review the following:
If a resource was completely backed up prior to a cluster failover, that resource is skipped upon checkpoint restart, regardless of whether the backup type or file type of that resource is supported by checkpoint restart. This saves media space and backup time.
746
Server Clusters
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 adequate 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. For more information about restore settings, see Restoring Data to a Server or Workstation on page 403.
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.
Enabling or Disabling Checkpoint Restart

Note 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 386.
To enable or disable checkpoint restart: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click Clusters. 3. Select or clear Apply CheckPoint Restart (resume jobs from point of failover).
747
Using Checkpoint Restart on Cluster Failover Cluster Backup Job Properties
Defaults set in Backup Exec remain the same on the failover nodes as they were on the controlling node when failover occurs. 4. Enable the Cluster Failover error-handling rule. On the Tools menu, select Configure Error-Handling rules. 5. Select the Cluster Failover rule, and then click Settings.
748
Server Clusters
Specifying A Different Failover Node
6. Verify that the Enabled field is selected.

Cluster Failover Error-Handling Rule

You can

Change the order in which the nodes fail over. Add a failover node to the cluster. Remove a failover node from the cluster.
To change the order in which nodes fail over:
By default, in a 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.
749
To add or remove a failover node: Before you add a node to the Backup Exec cluster configuration, you must install Backup Exec on it. Cluster services for a node should be online before you add or remove it from the cluster. If you are removing a node, do not run the cluster configuration wizard from the node you want to remove. 1. On the controlling node, on the Tools menu, point to Wizards. 2. Click Cluster Configuration Wizard. 3. Follow the instructions on the screen to add or remove a node. 4. If you have added a failover node, also add any locally attached storage devices that are to be used when failover occurs to the cluster drive pool. This ensures that jobs can be run on the storage devices that are attached to the failover nodes. See also: Creating Drive Pools for Clusters on page 745 Specifying A Different Failover Node on page 749 Configurations for Backup Exec and Clusters on page 752
750
Server Clusters
Designating a New SAN SSO Database Server in a Cluster
Designating a New SAN SSO Database Server in a Cluster

To designate a new database server for a cluster in a SAN Shared Storage Option environment, use BEUtility.exe. 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 member server with the Library Expansion Option and SAN Shared Storage Option installed. Make sure connections to the Backup Exec Cluster and other member servers are working properly. 2. Using the cluster administrator, shut down the Backup Exec Cluster services. Be sure to keep the Disk resource online. 3. Move the catalog files from the Backup Exec Cluster installation path to the respective installation paths on the new database server. 4. Use BEUtility.exe to connect all Backup Exec servers to the new database server and to start all Backup Exec services. 5. Stop and restart the Backup Exec Services on the new database server. 6. Using the Cluster Administrator, move the Backup Exec resource group to the failover node and make sure services start on that node. 7. Use BEUtility.exe to stop and restart the Backup Exec Services on all the member servers of the SAN in order for them to connect to the new database server. See also: Two-node Clusters on a Fibre Channel SAN with the SAN SSO on page 758 Four-node Clusters on a Fibre Channel SAN with the SAN SSO on page 760
751
Configurations for Backup Exec and Clusters

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, 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. For more information about hot-swapping devices, see Hot Swap for Storage Devices on page 94. See the following for examples of various cluster configurations: Two-node Cluster with Locally-attached Storage Devices on page 753 Two-node Cluster with Tape Devices on a Shared SCSI Bus on page 754 Two-node Clusters on a Fibre Channel SAN with the SAN SSO on page 758 Four-node Clusters on a Fibre Channel SAN with the SAN SSO on page 760
752
Server Clusters
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 Drives (<Node Name>) drive pool, which is also the default destination device on that node when you create backup or restore jobs. You must create a drive pool that includes storage devices on the controlling node and on each failover node in order for jobs to run when failover occurs. For more information, see Creating Drive Pools for Clusters on page 745. To restore data in this configuration, media must be moved to the failover nodes locally-attached storage device and reinventoried before a restore operation can be started.
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
See also: Two-node Clusters on a Fibre Channel SAN with the SAN SSO on page 758 Four-node Clusters on a Fibre Channel SAN with the SAN SSO on page 760
753
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, this configuration requires you to create a drive pool that includes the tape device name used by each node in order for jobs to run when failover occurs. For more information, see Creating Drive Pools for Clusters on page 745. When failover occurs, a SCSI bus reset is issued. Therefore, tape devices and shared drives should not be connected to the same SCSI bus; each should be connected to separate SCSI buses. For more information, see Configuring a Shared SCSI Bus for Tape Devices on page 755.
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
See also: Two-node Clusters on a Fibre Channel SAN with the SAN SSO on page 758 Four-node Clusters on a Fibre Channel SAN with the SAN SSO on page 760
754
Server Clusters
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 754, 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 755, 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:
755
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. 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.
Tip
Example of a Y cable
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.
756
Server Clusters
Configurations for Backup Exec and Clusters Example of a Trilink connector
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. Note Do not have power on to both nodes while configuring the systems, 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. See also: Two-node Cluster with Tape Devices on a Shared SCSI Bus on page 754
757
Two-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 to a designated node 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. In this configuration, you should create a failover drive pool for the cluster. For details about creating a failover drive pool, see Creating Drive Pools for Clusters on page 745. This configuration also 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.
758
Server Clusters
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.
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
Note You can designate any server on the fibre channel SAN as the Shared Storage Option Database server.
759
Four-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. Note You can designate any server on the fibre channel SAN as the Shared Storage Option Database server. In this configuration, you should create a failover drive pool for the cluster. For details about setting up a drive pool, see Creating Drive Pools for Clusters on page 745. This configuration also 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.
760
Server Clusters
Configurations for Backup Exec and Clusters 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
For details on installing the SAN SSO, see Installing the SAN Shared Storage Option on page 915. See also: Two-node Clusters on a Fibre Channel SAN with the SAN SSO on page 758 Designating a New SAN SSO Database Server in a Cluster on page 751
761
Backing Up Clusters
Backing Up Clusters
To protect all data in the cluster, including file systems, databases, and the cluster quorum, back up the following:
Local disks and System State on each node. The cluster quorum, which contains recovery information for the cluster and information about changes to the cluster configuration, is included in the System State backup. For more information, see Backing Up Local Disks in a Cluster on page 764. All shared disks, including the data in the MSCS folder on the Quorum disk. For more information, see Backing Up Shared Disks on page 764. Virtual servers, which may contain data or contain applications such as Microsoft SQL Server or Exchange Server. Use Backup Exec database agents to back up databases. For more information, see Backing Up Database Files in a Cluster on page 765.
For details on setting up and running backup operations, see Creating a Backup Job on page 235. 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 drive pool, but not a specific device in that pool. For more information, see Using the Command Line Applet on page 593. See also: Backing Up Local Disks in a Cluster on page 764 Backing Up Shared Disks on page 764 Backing Up Database Files in a Cluster on page 765 Backing Up Windows 2000 and Windows.NET Features on page 763
762
Server Clusters
Backing Up Clusters
Backing Up Windows 2000 and Windows.NET Features

You must purchase and install the Backup Exec Remote Agent for Windows Servers on all remote Windows 2000 and Windows.NET systems 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) Cluster quorum (if the server is part of a cluster)
Note You can select System State for backup on a remote system only when the Remote Agent is installed on the remote system. See also: Restoring Windows 2000 and Windows.NET Features on page 767
763
Backing Up Clusters
Backing Up Local Disks in a Cluster

Select local disks for backup from the physical node they are attached to.
To back up local disks in a cluster: 1. On the navigation bar, click Backup. 2. On the Backup selection pane, expand Remote Selections, expand the domain that contains the nodes, and then select the local disks on each node. Note When making backup selections for nodes running Windows 2000, be sure to select System State. For more information, see Selecting Data to Back Up on page 259. When making backup selections for nodes running Windows.NET, select Shadow Copy Components, which include System State. For more information, see Protecting Windows.NET Systems on page 333. 3. Continue with the full backup procedure as usual. For more information, see Creating a Backup Job on page 235. Tip If you created a drive pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs.
Backing Up Shared Disks

Select shared disks for backup by selecting them from the Microsoft Cluster Server virtual server or from the Backup Exec virtual server.
To back up shared disks: 1. On the navigation bar, click Backup. 2. On the Backup selection pane, expand Remote Selections, 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. 3. Select the drive letters that represent the shared disks.
764
Server Clusters
Backing Up Clusters
4. Continue with the full backup procedure as usual. For more information, see Creating a Backup Job on page 235. Tip If you created a drive pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs.
Backing Up Database Files in a Cluster

Select database files for back up from a database icon on a virtual server. If a virtual server contains a database application such as Microsoft SQL Server or Exchange Server, use the appropriate Backup Exec database agent to perform the backup operations; otherwise, only the file system is backed up, not the database files.
To back up database files in a cluster: 1. On the navigation bar, click Backup. 2. In the Backup selections pane, expand Remote Selections. Expand the domain that contains the cluster, then expand the virtual server that contains the database files. Then select the database icon.
765
Backing Up Clusters
The following example shows the virtual server EXCLUSTER2K selected for backup.
Virtual Server Selected for Backup
Refer to the specific Backup Exec database agent documentation for details on how to set backup defaults for the database. 3. After setting any database-specific defaults, continue with the full backup procedure as usual. For more information, see Creating a Backup Job on page 235. Tip If you created a drive pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs.
766
Server Clusters
Restoring Data To Clusters

For all file restore operations, including redirecting restores, use the normal procedures as described in Restoring Data to a Server or Workstation on page 403. 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. See also: Restoring the Cluster Quorum for Windows 2000 and Windows.NET Systems on page 768 Restoring the Cluster Quorum to a Windows 2000 or Windows.NET Node Running Active Directory on page 769 Specifying a New Drive Letter for the Cluster Quorum Disk on page 771
Restoring Windows 2000 and Windows.NET Features

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 cannot use a media server running Windows NT to restore Windows 2000 features to a Windows 2000 system. You can restore Windows.NET features from either a Windows 2000 media server or a Windows.NET media server. You can restore a Windows NT 4 system from a media server running on either Windows NT 4 or Windows 2000. It is not necessary to have the Remote Agent installed to perform the restore.
767
Restoring the Cluster Quorum for Windows 2000 and Windows.NET Systems
The cluster quorum is backed up as part of System State. If Active Directory is running on the target server in the cluster, do not select Restore cluster quorum. For more information, see Restoring the Cluster Quorum to a Windows 2000 or Windows.NET Node Running Active Directory on page 769. 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 771.
To restore the cluster quorum: Note If possible, take the other nodes in the cluster offline before restoring the cluster quorum. If the nodes cannot be taken offline, you should select the Force the recovery... option on the Advanced Restore Job Properties dialog box (explained in step 4). 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click Advanced. 3. Select Restore Cluster Quorum. 4. 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.
5. Continue the restore operation by following the steps in Restoring Data to a Server or Workstation on page 403. 6. When the restore operation is complete, use the cluster administrator software to restart the cluster service on nodes on which it was stopped.
768
Server Clusters
Restoring the Cluster Quorum to a Windows 2000 or Windows.NET Node Running Active Directory
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, %SystemRoot%\cluster\BackupExec. Then, use the command-line utility clrest.exe to restore the cluster quorum from the default location to the quorum drive.
To restore the cluster quorum to a node running Active Directory without using Backup Exec Cluster: Note If possible, take the other nodes in the cluster offline before restoring the cluster quorum. If the nodes cannot be taken offline, you should use the -f option with the clrest.exe command, explained in step 8. 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. For instructions on starting the Backup Exec services, see Starting and Stopping Backup Exec Services on page 65. 2. On the Backup Exec navigation bar, click Restore. 3. In the Restore Selections pane, click System State. 4. On the Properties pane, under Settings, click Advanced. 5. Clear the Restore cluster quorum option. This option must not be selected. 6. Start the restore operation. During the restore, the cluster quorum files are copied to the default location %SystemRoot%\cluster\BackupExec. 7. When the restore has completed, reboot the target node.
769
8. After reboot is complete, run clrest.exe from the command line to restore the cluster quorum from the default location to the quorum disk: clrest path where path is the complete path to the cluster quorum; typically, the pathname is %SystemRoot%\cluster\BackupExec. 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 path [-f] {drive letter] where [-f] forces the restore to proceed even if other cluster nodes are online and/or the disk signatures do not match. When this option is selected, the cluster service for any nodes that are online is stopped. This option also allows the drive letter of the disk that the cluster quorum was on to remain the same, even if the configuration has changed and the disk signatures contained in the restore media do not match the disk signatures contained in the cluster quorum. [drive letter] specifies another drive letter for the quorum disk. If you use this option, the drive letter that the cluster quorum resides on will be changed to the drive letter specified. Otherwise, the drive letter that the cluster quorum resides on will stay the same as it was previously. 9. After the cluster quorum is restored, use the cluster administrator to bring the other cluster nodes online.
770
Server Clusters
Specifying a New Drive Letter for the Cluster Quorum Disk
To specify a new drive letter for the cluster quorum disk on Windows 2000: 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. 1. On the Backup Exec navigation bar, click Restore. 2. In the Restore Selections pane, click System State. 3. On the Properties pane, under Settings, click Advanced. 4. Clear the Restore cluster quorum option. This option must not be selected. 5. Start the restore operation. During the restore, the cluster quorum files are copied to the default location %SystemRoot%\cluster\BackupExec. 6. When the restore has completed, reboot the target node. 7. After reboot is complete, run clrest.exe from the command line to restore the cluster quorum from the default location to the quorum disk. clrest path [-f] [drive letter] where path is the complete path to the cluster quorum; typically, the pathname is %SystemRoot%\cluster\BackupExec. A pathname is required. [-f] forces the restore to proceed even if other cluster nodes are online and/or the disk signatures do not match. When this option is selected, the cluster service for any nodes that are online is stopped. This option also allows the drive letter of the disk that the cluster quorum was on to remain the same, even if the configuration has changed and the disk signatures contained in the restore media do not match the disk signatures contained in the cluster quorum. [drive letter] specifies another drive letter for the quorum disk. If you use this option, the drive letter that the cluster quorum resides on will be changed to the drive letter specified. Otherwise, the drive letter that the cluster quorum resides on will stay the same as it was previously.
771
8. After the cluster quorum is restored, use the cluster administrator to bring the other cluster nodes online.
To specify a new drive letter for the cluster quorum disk on Windows NT 4: 1. Use the Cluster Administrator to create a Physical Disk resource. Refer to your Cluster Administrator documentation for details. 2. Start the cluster services using the -fixquorum startup parameter. 3. Go to Cluster Properties and click the Quorum Resource tab. 4. Change the quorum disk to the new drive letter in the Quorum Disk field and the Partition field. 5. Close the Cluster Administrator, and then restart the cluster services. Do not use the -fixquorum startup parameter.
772
Server Clusters
Disaster Recovery of A Cluster

Prepare for recovery by creating a disaster preparation plan, as described in Key Elements of a Disaster Preparation Plan (DPP) on page 532. Prepare to restore SQL, Exchange, Oracle, and Lotus Domino databases in a cluster after a disaster by reading the sections on preparing for disaster recovery in the appropriate chapters. In addition to the initial preparation instructions, further action is required to completely protect the Microsoft cluster servers. If a disaster occurs, the following information is required to successfully recover the cluster:
General Cluster Information Cluster name Cluster IP address and subnet mask Cluster node names Node IP addresses Local and shared drive letters and partition scheme Disk signatures
Cluster Groups Group name Preferred nodes Failover/failback policies
Cluster Resources Resource name Resource type Group membership Possible owners Resource dependencies Restart and Looks Alive/Is Alive properties Resource-related parameters Application-specific configuration (SQL Database Character Set)
Run Dumpcfg.exe from the Microsoft 2000 Resource Kit to retrieve the disk signatures from the shared disk. The Microsoft 2000 Resource Kit allows you to replace disk signatures.
773
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. Exchange, SQL, and Oracle servers, and the R/3 agent cannot be restored using IDR. For more information about disaster recovery for these options, see the appropriate chapters. For details on using IDR to prepare for disaster recovery, see VERITAS Backup Exec Intelligent Disaster Recovery Option on page 855. Note If you want to change your setup and 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 Only one set of diskettes needs to be created for Windows NT 4 cluster nodes; you do not need to create a set of disaster recovery diskettes for each node in the cluster. You do need to include the machine-specific disaster recovery file for both nodes on the disaster recovery diskettes. You must create a set of diskettes for each Windows 2000 cluster node; each set of disaster recovery diskettes is customized for a single computer. You will not be able to use the set of diskettes 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. See the table Windows hard drive numbering scheme on page 901, which lists the normal order that Windows uses to assign disk drive numbers. If you cannot get the IDR 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 Recovery Wizard. After this is done, you can continue with automated restore of your backup media afterward.
774
Server Clusters
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. Use the following sequence to recover the nodes. For detailed instructions, see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855.
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. The shared disks should be disconnected before recovery begins. 2. To restore the nodes, follow the steps in Using IDR to Recover a Computer on page 891. 3. Bring the shared drives and nodes online. 4. Restore the data files through the virtual server or through the node that controls the resource. 5. To restore a database to the shared drives, use the appropriate Backup Exec agent. For procedures, read the following sections: Disaster Recovery of SQL 2000 on page 1020 Disaster Recovery for Exchange Server 5.5 on page 1138 Disaster Recovery of a Lotus Domino Server on page 1196 Recovering a Remote Oracle Database Server from a Disaster on page 1175
Recovering Backup Exec on a Cluster Using IDR

To fully restore a cluster on which Backup Exec is installed, you can restore the cluster node and all shared disks using IDR or you can rebuild the cluster. To restore the cluster remotely, you should catalog the media that contains the backup sets of the cluster nodes and the shared disk. 1. Replace all shared disks, if necessary. 2. Perform IDR 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.
775
3. Reboot the server. The cluster service and all other cluster applications should come online. 4. Perform IDR on all other nodes. Restore only the local disk and system state.
Recovering the Entire Cluster Using a Manual Disaster Recovery Procedure

Note 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. For more information, see Recovering Nodes on the Cluster Using IDR on page 774.
To recover the entire cluster manually: 1. On the first node you want to recover, reinstall Windows, including the last service pack applied before the failure. For details on how to do this, see Manual Disaster Recovery of Windows Computers on page 540. Caution 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. See the table Windows hard drive numbering scheme on page 901 that lists the normal order that Windows uses to assign disk drive numbers. 2. On the other nodes you want to recover, reinstall Windows, including the last service pack applied before the failure. Refer to the previous Caution as well. 3. Reinstall the cluster services and bring the cluster online. 4. Use the Cluster Wizard to reinstall Backup Exec for Windows Servers on the cluster. You must use the same settings used during the initial installation. For more information, see Installing Backup Exec on a Cluster on page 742. 5. Catalog the media in the cluster. 6. On the Backup Exec navigation bar on the active node, click Restore. 7. In the Restore selections pane, select the last full backup sets made of the active node, and then select System State.
776
Server Clusters
8. On the Properties pane, under Settings, click Advanced. 9. Select the Restore cluster quorum option. This option must be selected. 10. Start the restore operation. 11. When the restore has completed, reboot the active node. 12. For each node that you need to recover, repeat step 6 through step 11. 13. After all nodes are recovered, restore the Backup Exec data files, and all other data files, to the shared disks. 14. To restore a database to the shared disks, use the appropriate Backup Exec agent. For procedures, read the following sections: Disaster Recovery of SQL 2000 on page 1020 Disaster Recovery for Exchange Server 5.5 on page 1138 Disaster Recovery of a Lotus Domino Server on page 1196 Recovering a Remote Oracle Database Server from a Disaster on page 1175
Recovering the 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 recovering the data files.
To restore the cluster data files: 1. Shut down the secondary nodes. 2. Start the primary node. 3. On the Computer Management menu, select System Tools. Then select Device Manager. 4. Right-click the cluster disk driver, and then select Disable. 5. Click OK. 6. Reboot the primary node.
777
7. On the Backup Exec navigation bar, click Restore. 8. In the Restore selections pane, select the most recent backup set of the MSCS folder. Note The cluster service should not be running. 9. Redirect the restore of the MSCS folder to the designated Quorum disk. 10. After the cluster data files have been restored to the Quorum disk, you can enable the cluster disk driver and start the cluster service. 11. After the cluster quorum is restored, use the cluster administrator to bring the other cluster nodes online.
Recovering All Shared Disks

There are two ways to recover shared disks. One way uses the Dumpcfg option from the Microsoft 2000 Resource Kit, which helps automate the recovery process. If you do not have the Microsoft 2000 Resource Kit, you can perform a total manual recovery.
To recover all shared disks using Dumpcfg: 1. Disable the cluster disk driver on all nodes in order to gain access to the new disk. 2. Replace and then repartition the shared disk. Use Disk Manager to verify that all nodes see the shared disk the same. 3. Run Dumpcfg to replace the disk signature for the Quorum disk. 4. Using a remote BE server, restore the cluster files to the Quorum disk via the node that has access to the disk. 5. Enable the cluster disk driver on all nodes. 6. Reboot all cluster nodes.
To recover all shared disks without using Dumpcfg: 1. Uninstall all cluster applications and the cluster software from both nodes. 2. Replace and then repartition the shared disk to the previously saved configuration. 3. Reinstall the cluster software.
778
Server Clusters
Troubleshooting Clusters
4. Reinstall the cluster-aware version of Backup Exec for Windows Servers on the cluster. For more information, see Installing Backup Exec on page 46. 5. Reinstall additional cluster-aware software applications on the shared disk. 6. Use Backup Exec to restore any data from the catalogs. For more information, see Restore Operations and the Catalog on page 396.
Recovering Clustered Backup Exec

If you used the IDR option to prepare disaster recovery diskettes for the shared disks, you must use a manual process to recover Backup Exec on a shared disk.
To use a manual process to recover Backup Exec on a shared disk: 1. Replace the shared disk if necessary, and add that disk to the cluster as a disk resource. 2. Reinstall the cluster-aware version of Backup Exec for Windows Servers on the cluster using the same information used in the original installation. For more information, see Installing Backup Exec on page 46. 3. Use Backup Exec to restore any data from the catalogs.
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 to replace the disk signature by typing: dumpcfg.exe /s 12345678 0 Replace 12345678 with the disk signature and replace 0 with the disk number. You can find the disk signature and the disk number in the event log. If you do not have the Microsoft 2000 Resource Kit, you can use -Fixquorum to change the Quorum disk signature.
779
1. Start the cluster service on one node with the -Fixquorum option in the startup parameters. 2. Open the Cluster Administrator and right-click the cluster, and then select Properties. 3. Select the Quorum tab. 4. In the Quorum resource field, select a different disk. 5. Click OK. 6. Stop the cluster services and then restart them without the -Fixquorum option. Note You may run the -Fixquorum option as many times as needed to redesignate a Quorum disk signature. 7. Bring all other nodes online. I used the Checkpoint Restart option for my backups. During one of my backups, a 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.
780
BEWAC
VERITAS Backup Exec Web Administration Console
16
The VERITAS Backup Exec Web Administration Console (BEWAC) is an optional user interface for using Backup Exec 9.0 on server appliances and Windows.NET servers with the Remote Administration (HTML) components installed. You can connect to the Web Administration console on the media server from a client (remote computer) using Internet Explorer and remotely administrate the media server. You can use BEWAC to back up and restore data on the server appliance on which Backup Exec is installed or on other servers to which the appliance is attached. Note In version 8.6 of Backup Exec, this feature was called Backup Exec Server Appliance Kit (BESAK).
Requirements for BEWAC

Before you install BEWAC, be sure that you have the following required items. There are different requirements for the server and the client. Server requirements:

Windows 2000 Server or above with Service Pack 2, or Windows.NET Server with Remote Administration (HTML) components installed Microsoft Server Appliance Kit 2.0 or above Backup Exec for Windows Servers 9.0
Client requirements:

Internet Explorer 5.5 or later Windows NT 4.0 or later
781
Installing BEWAC
Installing BEWAC
To install BEWAC, select the Web Administration Console option when you install Backup Exec for Windows Servers. For details about installing Backup Exec, see Installing Backup Exec Using the Installation Program on page 47.
Starting BEWAC
To start BEWAC after installing it: 1. Open Internet Explorer. 2. In the Address field, type http://server name:port number Example http://BackupServer:8099 Note It is recommended that you add a link to this address for quick access. 3. On the primary navigation bar, click Backup Exec. 4. If this is the first time you have started Backup Exec, run the First Time Startup Wizard.
Differences Between BEWAC and Backup Exec for Windows Servers

Although every effort was made to duplicate the user interface of Backup Exec for Windows Servers in BEWAC, some differences exist. The following items are not available in BEWAC:
Alerts view. You can view and respond to alerts through the server appliance Status area. For more information, see Viewing, Clearing, and Responding to Alerts on page 786. Alternate server selection for Backup Exec Diagnostics AppleTalk network support Audit logging Bar code rules Calendar view in the Job Monitor. Only the Jobs list view is available. Connect to another media server
782
Differences Between BEWAC and Backup Exec for Windows Servers
IDR settings and the ability to create bootable media Menus. Many of the options that are available through menus in Backup Exec for Windows Servers are available on the Tools tab in BEWAC. For more information, see Tools on page 785.
BEWAC
Right-click functionality. The ability to right-click an item and then select an option from a Backup Exec shortcut menu is available only in the Selection pane and Results pane on the Backup Job Properties and Restore Job Properties dialog boxes. For example, if you right-click the icon for the C: drive in the Backup Selection pane, you can refresh the screen, select advanced file selection or user-defined selection options, connect as a different user, check or uncheck the drive, or view properties. If you right-click an item in any other area of BEWAC, the Internet Explorer shortcut menu displays.
Wizards. The wizards that display on the Tools menu in Backup Exec for Windows Servers, such as the Media Rotation Wizard and the Logon Account Wizard, are not available. However, the First Time Startup Wizard is available in both BEWAC and Backup Exec for Windows Servers. Preview panes for media and device properties. The BEWAC user interface does not have the preview pane that displays in the lower right side of the screen in Backup Exec for Windows Servers. Pop-up alerts and error messages. BEWAC does not support most pop-up alerts and messages. Alerts display in the status area of the server appliance.
Accessing Help
To access Help for BEWAC, click the question mark (?) in the upper right corner of each screen. If you click the Help tab on the primary navigation bar or press F1, the Windows Server Appliance Kit help displays. You can refer to the Backup Exec for Windows Servers Administrators Guide and Help for overview information and procedures for BEWAC. If a different step is required for BEWAC, the alternate step is indicated in a note in the procedure.
Chapter 16, VERITAS Backup Exec Web Administration Console
783
Navigating in BEWAC
Navigating in BEWAC
Navigation in BEWAC differs from navigation in Backup Exec for Windows Servers. BEWAC contains a status area at the top of the screen, which is where alerts display. This status area replaces the Alerts view in Backup Exec for Windows Servers. Below the status area are two navigation bars. The blue bar is the primary navigation bar. From the primary navigation bar you can select the tab for the application or task you want to work with, such as Backup Exec. The white bar is the secondary navigation bar. From the secondary navigation bar you select BEWAC options, such as backup and restore. The secondary navigation bar in BEWAC is the equivalent of the navigation bar in Backup Exec for Windows Servers. You also can click the icons to access BEWAC options.
BEWAC screen layout
Status area Primary navigation bar Secondary navigation bar Help button
784
Tools
Tools
The Tools tab serves the same function in BEWAC as the Tools menu in Backup Exec for Windows Servers. When you are following instructions in the Backup Exec for Windows Servers Administrators Guide, replace any mention of the Tools menu with the Tools tab. From the Tools tab, you can:

BEWAC
Start or stop Backup Exec services, and change logon credentials for the services Configure alert categories Configure notification recipients Create and view a diagnostics log Configure e-mail and pager notification Configure error-handling rules Configure default options for Backup, Restore, Media, Database Maintenance, Job Logs, Catalogs, and Agents Add, delete, edit, and replace logon accounts Add or remove serial numbers Initiate VERITAS update
Chapter 16, VERITAS Backup Exec Web Administration Console
785
Viewing, Clearing, and Responding to Alerts
Viewing, Clearing, and Responding to Alerts

In BEWAC, alerts display in the status area above the primary navigation bar. This takes the place of the Alerts view in Backup Exec for Windows Servers. The alert status displays, but not the details of the alert. For some types of alerts, you can respond to Backup Exec. With other types of alerts, you can only view the details. Both Backup Exec and server appliance alerts display in the status area and on the Status tab. Alerts for Backup Exec are titled Backup Exec Alert, so you can quickly distinguish them from the server appliance alerts. You can configure alert categories, notification recipients, and e-mail and pagers using Backup Exec. For details, see Configuring Alert Category Properties on page 463, Configuring Recipients on page 472, and Configuring E-mail and Pager Notification Methods on page 467.
To view the alert details and respond to an alert: 1. Click the alert or click Status in the primary navigation bar. 2. Under Alerts, click the alert for which you want to view details. 3. At the bottom of the screen, click the name of the alert to view details or respond to it. 4. After viewing the alert details or responding to the alert, click OK to clear the alert from the alert list. 5. On the primary navigation bar, click Backup Exec to return to BEWAC.
To clear an alert without viewing it or responding to it: 1. Click the alert or click Status in the primary navigation bar. 2. Under Alerts, click the alert for which you want to clear. 3. At the bottom of the screen, click Clear Message. The alert is cleared from the alert list in BEWAC.
786
Backup Exec Utility
17
Backup Exec Utility
The Backup Exec Utility (BEUTILITY.EXE) enables you to do various types of configuration and maintenance operations on your Backup Exec for Windows Servers media servers. It is automatically installed in your Backup Exec working directory during the initial Backup Exec for Windows Servers installation. With the Backup Exec Utility, you can:

Reconfigure Backup Exec SAN Shared Storage environments by moving primary media server responsibilities among Backup Exec media servers. Configure logical groups of Backup Exec media servers, enabling you to perform operations on all computers at the same time in the group. These operations can include starting or stopping services or configuring application service security, such as changing service account information as well as startup options for one or more servers in the group. With the Backup Exec Utility, you can also add or remove media servers from the group. Start immediate database utility operations on the Backup Exec Database (BEDB) that are normally initiated by the database maintenance utilities themselves. These maintenance operations include database dumps, shrink and grooming operations, along with BEDB database consistency and data integrity checks.
See also: Starting the Backup Exec Utility on page 788 Completing Tasks using the Backup Exec Utility on page 790 Running Backup Exec Utility General Tasks on page 792 Running Backup Exec Utility Services Tasks on page 798 Running Backup Exec Utility SAN SSO Tasks on page 804 Running Database Tasks on page 809 Running Media Server Group Tasks on page 816
787
Starting the Backup Exec Utility
Starting the Backup Exec Utility
To start the Backup Exec Utility:
From the Backup Exec main program directory, double-click BEUtility.exe. By default, the main program directory is Program Files/VERITAS/Backup Exec/NT.
The Backup Exec Utility
results pane
task pane
Media Servers pane
preview pane
See also: Completing Tasks using the Backup Exec Utility on page 790
788
Getting Started
Getting Started
Before you can reconfigure or modify Backup Exec media servers, you must add the names of the media servers to the list of media servers that the Backup Exec Utility knows about.
To add media servers: 1. On the Media Servers pane, click All Media Servers. 2. On the task pane, under General Tasks, click New Media Server.
Backup Exec Utility
3. Select the appropriate options from the following:

New Media Server dialog box options Item Media Server Description Enter the name of a media server you want to add, or click Browse to find a server to add. Validates that the media server is indeed a media server before adding it to the Backup Exec Utility master list of known servers. Adds other media servers that may be part of a SAN SSO environment to the Backup Exec Utility master list of known servers.
Check server status
Include all servers known by this server
Get Server Information Shows the properties of the media server entered in the Media server field.
4. Click OK. The media server name appears in the results pane when All Media Servers is selected. See also: Completing Tasks using the Backup Exec Utility on page 790
Chapter 17, Backup Exec Utility
789
Completing Tasks using the Backup Exec Utility
Completing Tasks using the Backup Exec Utility

The Backup Exec Utility enables you to run media server-related operations on your Backup Exec media servers. Each of these operations (tasks) are found in the Backup Exec Utilitys task pane. Use the following table as a guide to the types of operations the Backup Exec Utility can perform. Note The task pane can be toggled on and off by selecting Task Pane under View.
Backup Exec Utility tasks If you want to: Add a media server Add a new media server group Delete a media server Delete a media server group Run Backup Exec diagnostics View media server properties See: Running Backup Exec Utility General Tasks on page 792
Start and stop services on media servers Change media server service accounts Edit media server configurations.
Running Backup Exec Utility Services Tasks on page 798
Set or remove the primary SAN SSO server Configure the SAN Shared Storage Option Promote a Backup Exec media server to the primary server in a SAN Shared Storage Option environment Move the primary SAN Shared Storage Option server to a different Backup Exec media server.
Running Backup Exec Utility SAN SSO Tasks on page 804
790
Completing Tasks using the Backup Exec Utility Backup Exec Utility tasks (continued) If you want to: Check Backup Exec Database consistencies Age Backup Exec Databases Compact Backup Exec Databases, and Dump Backup Exec Databases. Rebuild, repair and recover Backup Exec Databases. Change the SQL Server sa password. Change the database access See: Running Database Tasks on page 809
Backup Exec Utility
Add a media server to a media server group Remove a media server from a media server group
Running Media Server Group Tasks on page 816
Edit cluster configuration information
Running Cluster Tasks on page 818
791
Running Backup Exec Utility General Tasks

This section guides you through the following Backup Exec Utility tasks:

Add a New Media Server on page 792 enables you to add a media server to Backup Exec Utilitys list of known Backup Exec media servers. Create a New Media Server Group on page 793 enables you to create a container where you can logically group together multiple media servers. Delete a Media Server from the All Media Servers Subnode on page 794 enables you to remove Backup Exec media servers from the Backup Exec Utility master list of known servers. Delete a Media Server Group on page 795 enables you to remove user-defined media server groups from the Media Server Groups subnode. Run Backup Exec Diagnostics on page 796 enables you to run Backup Exec for Windows Servers Diagnostics application on media servers listed in the Backup Exec Utility. View Media Server Properties on page 797 enables you to view server and system properties, along with the installed options for any Backup Exec media server that appears in Backup Exec Utility.
Add a New Media Server

New Media Server is used to add a media server to Backup Exec Utilitys list of known Backup Exec media servers. After adding a media server, it appears under the node, All Media Servers.
To add a new media server: 1. On the Media Servers pane, click All Media Servers. 2. On the task pane, under General Tasks, click New Media Server.
792
3. Enter the appropriate options as follows.

New Media Server dialog box options Item Media Server Description Enter the name of a media server you want to add, or click Browse to find a server to add. Validates that the media server is indeed a media server before adding it to the Backup Exec Utility master list of known servers.
Check server status
Backup Exec Utility
Include all servers known by this server
Adds other media servers that may be part of a SAN SSO environment to the Backup Exec Utility master list of known servers.
Get Server Information Shows the properties of the media server entered in the Media server field.
4. Click OK. See also: Delete a Media Server from the All Media Servers Subnode on page 794 Completing Tasks using the Backup Exec Utility on page 790
Create a New Media Server Group

New Media Server Group is used to create a container where you can logically group together multiple media servers. After creating the group, Backup Exec media servers are added to it using the task Add Server, which is found under Server Group Tasks in the task pane. Grouping media servers enables you to perform operations such as starting and stopping services on the entire group, at the same time.
To create a new media server group: 1. On the Media Servers pane, click Media Server Group. 2. On the task pane, under General Tasks, click New Server Group.
793

New Server Group dialog box options Item Media Server Group Description Enter the name of a media server you want to add, or click Browse to find a server to add.
Create group from SAN Enables you to create the new media server group and populate it SSO configuration with the computers found in your SAN SSO environment. Primary SAN SSO server The name of your primary SAN SSO server from which this new media server group will be created.
4. Click OK. See also: Add Media Server on page 816 Delete a Media Server Group on page 795 Completing Tasks using the Backup Exec Utility on page 790
Delete a Media Server from the All Media Servers Subnode

Delete Media Server enables you to remove Backup Exec media servers from the Backup Exec Utility master list of known servers, which is reflected by the servers that appear in the All Media Servers node. Deleting a media server does not affect the operational status of the media server. Note Delete Media Server cannot be used to remove media servers from the Media Server Groups subnode. To remove media servers from the Media Servers Group subnode, see Remove Media Server.
To delete a media server from the All Media Servers subnode: 1. On the Media Servers pane, click All Media Servers. 2. On the task pane, under General Tasks, click Delete Media Server.
794
Running Backup Exec Utility General Tasks Delete Server selection box
Backup Exec Utility
3. Select a media server or servers to delete. 4. Click OK. See also: Remove a Media Server on page 817 Add a New Media Server on page 792 Completing Tasks using the Backup Exec Utility on page 790
Delete a Media Server Group

Delete Media Server Group enables you to remove user-defined media server groups from the Media Server Groups subnode. Note All media servers contained in the media server group are deleted along with the media server group itself. Although they are deleted from the group, the deleted media servers are not removed from the Backup Exec Utilitys All Media Servers subnode.
To delete a media server group: 1. On the Media Servers pane, click Media Server Groups. 2. On the task pane, under General Tasks, click Delete Media Server Group.
795
Running Backup Exec Utility General Tasks Delete Server Group selection box
3. Select a media server or servers to delete. 4. Click OK. See also: Create a New Media Server Group on page 793 Add Media Server on page 816 Completing Tasks using the Backup Exec Utility on page 790
Run Backup Exec Diagnostics

BE Diagnostics enables you to run Backup Exec for Windows Servers Diagnostics application on media servers listed in the Backup Exec Utility. Backup Exec for Windows Servers Diagnostics gathers information about Windows NT, Windows 2000, or Windows.NET computers for troubleshooting purposes. This application is located in the Backup Exec for Windows Servers directory on your hard drive (by default, \Program Files\VERITAS\Backup Exec\NT).
To run BE Diagnostics: 1. On the Media Servers pane, click All Media Servers. 2. On the results pane, select a media server.
796
3. On the task pane, under General Tasks, click BE Diagnostics. Diagnostic output from BEDIAG is sent to a ASCII text file called bediag.txt and is located in the default Backup Exec installation directory (\Program Files \VERITAS\Backup Exec\NT). See also: Using Backup Execs Diagnostic Utility BEDIAG on page 554 Completing Tasks using the Backup Exec Utility on page 790
Backup Exec Utility
View Media Server Properties

Properties enables you to view server, options and system properties for any Backup Exec media server that appears in Backup Exec Utility.
To view media server properties: 1. On the Media Servers pane, click All Media Servers. 2. On the results pane, select a media server. 3. On the task pane, under General Tasks, click Properties. 4. After reviewing the media server properties, click OK. See also: Viewing Server Properties and Running Server Diagnostics on page 112 Completing Tasks using the Backup Exec Utility on page 790
797
Running Backup Exec Utility Services Tasks


Stop Services on page 798 enables you to remotely stop Backup Exec services on any Backup Exec media server that appears in the Backup Exec Utility. Start Services on page 799 enables you to remotely start Backup Exec services on any Backup Exec media server that appears in the Backup Exec Utility. Change Service Accounts on page 799 enables you to configure the credentials that comprise the Backup Exec service account. Edit Server Configurations on page 801 enables you to configure Backup Exec to set automatic responses to several media alerts.
Stop Services
Stop Services enables you to remotely stop Backup Exec services on any Backup Exec media server that appears in the Backup Exec Utility. Caution When stopping services on a clustered Backup Exec media server, the entire Backup Exec cluster group will be taken offline. To bring the entire group back online, restart the services using Start Services.
To stop Backup Exec services on a media server: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Services Tasks, click Stop Services. 3. Click Yes to confirm the stop services operation. 4. After the services stop, click Close on the Operation Progress screen. See also: Start Services on page 799 Running Backup Exec Utility Services Tasks on page 798 Completing Tasks using the Backup Exec Utility on page 790
798
Start Services
Start Services enables you to remotely start Backup Exec services on any Backup Exec media server that appears in the Backup Exec Utility. Caution When starting services on a clustered Backup Exec media server, the entire Backup Exec cluster group will be placed online. To bring the entire group back offline, stop the services using Stop Services.
To start Backup Exec services on a media server:
Backup Exec Utility
1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Services Tasks, click Start Services. 3. After the services start, click Close on the Operation Progress screen. See also: Stop Services on page 798 Running Backup Exec Utility Services Tasks on page 798 Completing Tasks using the Backup Exec Utility on page 790
Change Service Accounts

Change Service Account enables you to reconfigure the credentials that comprise the Backup Exec service account.
To change a media server service account: 1. Select a media server from either a media server group or from the All Media Servers subnode. Note If you are changing the service account on a clustered Backup Exec media server, you must first bring the Backup Exec cluster group offline using Stop Services. On the task pane, under Services Tasks, click Change Service Account.
799

Set Service Account dialog box options Item Server(s) Description The name of the media server where the service account is being changed. The user account designated for the Backup Exec services. The service account must previously exist and be a member of the Administrators or Backup Operators groups. The service account is assigned the following rights: Log on as a service, Act as part of the operating system, and Create a token object. The password used to access to the service account. Used to re-enter the password to ensure it matches the one entered in the Password field. Enables you to change the start up behavior of the service. Choices include Automatic, Manual, Disabled.
Account
Password Confirm Password
Start type
3. Click OK. 4. Click Close when the service account changes are completed. Before the new service account configuration takes affect, you must stop and restart the services on the media server. See also: Stop Services on page 798 Start Services on page 799 Running Backup Exec Utility Services Tasks on page 798 Completing Tasks using the Backup Exec Utility on page 790
800
Edit Server Configurations

Edit Configuration enables you to configure Backup Exec to set automatic responses to several media alerts if those alerts have been configured to use the option, Automatically clear after. This option is found on Backup Execs Alert Configuration dialog box. If an alert appears and no user intervention is taken by the user defined specified time, the following responses will occur, based on what you have selected in the following table. These responses include:
Automated Alert Responses
Backup Exec Utility
Item Yes or OK
Description Automatically responds Yes or OK to the generated alert, if you take no action. Automatically responds No to the generated alert, if you take no action. Automatically responds Cancel to the generated alert, if you take no action.
No Cancel
The following media alerts can be configured to use automatic responses: Media Overwrite, Media Remove, Media Insert and Library Insert. You can also use the Edit Configuration dialog box to change the amount of time that a media server waits to release a tape drive before attempting to acquire another tape drive. In addition, you can also change the amount of time that the media server keeps possession of a tape drive after a job completes.
To edit a media server configuration: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Services Tasks, click Edit Configuration.
801
Running Backup Exec Utility Services Tasks Edit Server Configuration dialog box
3. Enter the appropriate options as follows:

Edit Server Configuration dialog box options Item Server(s) Description The name of the media server where the service account is being changed.
General Delay before mount time (in seconds) Changes the amount of time the media server waits after releasing a tape drive and before attempting to acquire a storage device. Note In a SAN SSO environment, this option should be used in order to keep one media server from monopolizing the storage device.
802
Running Backup Exec Utility Services Tasks Edit Server Configuration dialog box options (continued) Item Next job wait time (in seconds) Description Changes the amount of time that the media server keeps possession of a storage device after a job completes.
Caution This option should be set to 0 in a SAN SSO environment.

Note This option is useful when multiple append jobs are targeted to a particular media server during the same backup window, and you want to save some time. In a SAN SSO environment, as soon as a job finishes, the media server releases the storage device, which enables the media dismount sequence to begin. When another job is submitted for processing, the media mount sequence is initiated. Each of these mount/dismount sequences take time to complete. In a non-SAN SSO environment, increasing the wait time between jobs delays the start of the media dismount sequence. If an append job is sent to the storage device before the allotted time expires, the media dismount sequence is averted and the job starts immediately. If an append job is not sent to the storage device in the allotted time, the media dismount sequence begins. When finished, the storage device is then released by the media server, enabling it to be accessed by other media servers. Mount poll time Changes the time interval (in seconds) before Backup Exec retries mounting media in order to run a job, or attempts to acquire a storage device with media in it. Note In a SAN SSO environment, all media servers should use the same time interval, as this gives them all equal opportunity to acquire a storage device when jobs are submitted for processing. Automated Alert Responses Media Overwrite Alert automated response Media Remove Alert automated response Enable you to set the automated response for the Media Overwrite Alert. Responses include: Yes or OK, No, or Cancel. Enable you to set the automated response for the Media Remove Alert. Responses include: Yes or OK, No, or Cancel.
Backup Exec Utility
803
Running Backup Exec Utility SAN SSO Tasks Edit Server Configuration dialog box options (continued) Item Media Insert Alert automated response Library Insert Alert automated response Description Enable you to set the automated response for the Media Insert Alert. Responses include: Yes or OK, No, or Cancel. Enable you to set the automated response for the Library Insert Alert. Your choices are Yes or OK, No, or Cancel.
See also: Running Backup Exec Utility Services Tasks on page 798 Completing Tasks using the Backup Exec Utility on page 790
Running Backup Exec Utility SAN SSO Tasks


Set the Primary SAN SSO Server on page 804 enables you to add a media server to an existing SAN SSO-enabled storage area network. Remove the Primary SAN SSO Server on page 805 enables you to remove a media server in a SAN SSO storage area network and return it to standalone status. Configure the SAN SSO on page 806 enables you to create a primary SAN SSO Server from one of the media servers found within a Media Server Group. Promote a Media Server to a Primary SAN SSO Server on page 806 enables you to reconfigure a media server as the primary SAN SSO Server. Move the Primary SAN SSO Server on page 808 enables you to change the computer that serves as a primary SAN SSO Server.
Set the Primary SAN SSO Server

Set Primary SAN SSO Server is used to add a media server to an existing SAN SSO-enabled storage area network by configuring the media server to point to the SANs primary SAN SSO server. Note If the media server is currently part of another SAN SSO storage area network, it will first be removed from that SAN.
To add the media server to an existing SAN SSO server: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under SAN SSO Tasks, click Set Primary SAN SSO Server. 3. Enter the name of the target SAN SSO storage area networks primary SAN SSO server. 4. After the operation finishes, click Close on the Operation Progress screen.
Backup Exec Utility
See also: Running Backup Exec Utility SAN SSO Tasks on page 804 Completing Tasks using the Backup Exec Utility on page 790
Remove the Primary SAN SSO Server

Remove Primary SAN SSO Server enables you to remove a media server in a SAN SSO storage area network and return it to standalone status. Note When converting to standalone status, the servers Backup Exec Database reverts to the previous state it was in before the media server was converted to a SAN SSO Server.
To convert a SAN SSO storage area network media server to a standalone media server: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under SAN SSO Tasks, click Remove Primary SAN SSO Server. 3. When prompted for confirmation of this operation, click Yes.
4. After the operation finishes, click Close on the Operation Progress screen. See also: Running Backup Exec Utility SAN SSO Tasks on page 804 Completing Tasks using the Backup Exec Utility on page 790
805
Configure the SAN SSO

Configure SAN SSO enables you to create a primary SAN SSO Server from one of the media servers found within a Media Server Group. Note You must create a Media Server Group that contains at least two media servers to use this option.
To configure a SAN SSO Server: 1. On the Media Server pane, under Media Server Groups, click a Media Server Group containing at least two media servers. 2. On the task pane, under SAN SSO Tasks, click Configure SAN SSO. 3. In the Primary SAN SSO server fields list box, click the name of a media server. 4. Click OK. 5. After the operation finishes, click Close on the Operation Progress screen. See also: Running Backup Exec Utility SAN SSO Tasks on page 804 Completing Tasks using the Backup Exec Utility on page 790
Promote a Media Server to a Primary SAN SSO Server

Promote to Primary SAN SSO Server enables you to reconfigure a media server as the primary SAN SSO Server in a SAN SSO storage area network. This is helpful if for some reason the original primary server goes down. During the reconfiguration process, a fresh copy of the Backup Exec Database is created and installed on the target media server. Although other media servers in the SAN SSO storage area network will point to the new primary server after the reconfiguration finishes, all job configurations contained in the original primary SAN SSO servers Backup Exec Database must be recreated.
806
To reconfigure a media server as a primary SAN SSO server: 1. On the Media Server pane, under Media Server Groups, click a media server group containing at least two media servers. 2. On the Task pane, under SAN SSO Tasks, click Promote to Primary SAN SSO Server. 3. Select the name of the media server to be promoted.
Promote Primary SAN SSO Server dialog box
Backup Exec Utility
Promote Primary SAN SSO Server Options. Item Servers Description Lists the names of the media servers that comprise the media server group. The name of the media server to be promoted. The target media server is selected from the list of media servers that appear in the Servers field.
Primary SAN SSO server
4. Click OK. After the operation finishes, click Close on the Operation Progress screen. See also: Running Backup Exec Utility SAN SSO Tasks on page 804 Completing Tasks using the Backup Exec Utility on page 790
807
Move the Primary SAN SSO Server

Move Primary SAN SSO Server enables you to change the computer that serves as a primary SAN SSO Server in a SAN SSO storage area network. This is helpful if for example, you want to permanently change the primary SAN SSO Server to another computer. During the reconfiguration process, the complete Backup Exec Database is physically moved to the new target SAN SSO Server. As such, all job configurations contained in the Backup Exec Database are saved.
To move the primary SAN SSO Server: 1. On the Media Server pane, under Media Server Groups, click a media server group containing at least two media servers. 2. On the Task pane, under SAN SSO Tasks, click Move Primary SAN SSO Server. 3. Select the name of the media server to be promoted.
Move Primary SAN SSO Server list box
Move Primary SAN SSO Server List Box Options Item Servers Description Lists the names of the media servers that comprise the media server group. The name of the existing primary SAN SSO Server.
Old primary SAN SSO server
808
Running Database Tasks Move Primary SAN SSO Server List Box Options Item Description
New primary SAN SSO The name of the media server to be converted to the new primary server SAN SSO Server. The target media server is selected from the list of media servers that appear in the Servers field.
4. Click OK. After the operation finishes, click Close on the Operation Progress screen. See also: Running Backup Exec Utility SAN SSO Tasks on page 804 Completing Tasks using the Backup Exec Utility on page 790
Backup Exec Utility
Running Database Tasks


Check the Database Consistency on page 810 enables you to check the consistency or validity of a media servers Backup Exec Database) Age the Database on page 810 enables you to age a media servers Backup Exec Database by deleting information considered old. Compact a Media Server Database on page 811 enables you to shrink the database by removing a databases unused space. Dump a Media Server Database on page 811 enables you to back up the Backup Exec Database to your hard drive. Rebuild Media Server Database Indices on page 812 enables you to rebuild media server database indices in the event the indices become corrupt. Repair a Media Server Database on page 812 enables you to repair a database. Recover a Media Server Database on page 813 enables you to recover a database. Change the SQL Server sa Password on page 814 enables you to change a media servers SQL Server sa password. Change Database Access on page 815 enables you to grant or revoke a users database access.
809
Check the Database Consistency

Check Database Consistency enables you to check the consistency or validity of a media servers Backup Exec Database before you back it up. A consistency check enables you to find problems in a database before you back it up.
To check the consistency of a media server database: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Check Database Consistency. 3. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
Age the Database

Age Database enables you to age a media servers Backup Exec Database by deleting information considered old, based on user-defined configuration criteria.
To age a media server database: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Age Database. 3. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
810
Compact a Media Server Database

Compact Database enables you to shrink the database by removing a databases unused space.
To compact a media server database: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Compact Database.
Backup Exec Utility
3. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
Dump a Media Server Database

Dump Database enables you to back up the database to your hard drive.
To dump a media server database: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Dump Database. 3. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
811
Rebuild Media Server Database Indices

Rebuild Indices enables you to rebuild media server database indices in the event the indices become corrupt.
To rebuild media server database indices: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Rebuild Indices. 3. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
Repair a Media Server Database

Repair Database enables you to repair a database after you find problems that may have been uncovered during a database consistency check.
To repair a media server database: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Repair Database. 3. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
812
Recover a Media Server Database

Recover Database enables you to recover a database that has been lost or corrupted.
To recover a media server database: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Recover Database. 3. On the Recover Database dialog box, select the appropriate option for your situation.
Backup Exec Utility
Item Server
Description The name of the media server on which the Backup Exec Database is being recovered.
Recovery method Use best recovery method for current configuration As the Backup Exec Utility default, this option attempts to fix and recover the existing Backup Exec Database before either deleting it and creating a new database, or deleting it and recovering from the previous database dump.
Drop existing database Deletes the existing Backup Exec Database and restores the backup. and reload from backup This option works in conjunction with the Backup Exec for Windows Servers option, Save contents of database to the Backup Exec data directory, found in the Database Maintenance node. If this option is set, Backup Exec automatically dumps the Backup Exec Database to the media servers hard drive at a predetermined, user-defined schedule. When you run the Backup Exec Utility task Recover Database and select the option, Drop existing database and reload from backup, the existing BE Database is deleted and replaced with the copy of the database that was dumped to Backup Execs data directory. For more information, see Configuring Database Maintenance on page 389. Drop existing database Deletes the existing Backup Exec Database and creates, in its place, a and reload from base new and empty database. For more information, see Configuring Database Maintenance on page 389.
813
4. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
Change the SQL Server sa Password

Change SQL Server sa Password enables you to change a media servers SQL Server sa password.
To change a media servers SQL Server sa password: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Database Tasks, click Change SQL Server sa Password. 3. In the Old sa Password field, enter the old password. 4. In the New sa Password field, enter the new password. 5. Confirm the password by re-entering it in the Confirm sa Password field. 6. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
814
Change Database Access

Change Database Access enables you to grant or revoke a users database access to the media servers Backup Exec Database. This is useful for example, if you change the Backup Exec service account. After changing the service account, you can use Change Database Access to give the new account access to the Backup Exec Database.
To change database access: 1. Select a media server from either a media server group or from the All Media Servers subnode.
Backup Exec Utility
2. On the task pane, under Database Tasks, click Change Database Access. 3. In the User Name field, enter a user name. 4. In the Domain field, enter the users domain. Note To use a local account, enter the local machine name in the domain field. Backup Exec Utility assumes the local machine name if the field is left blank. 5. Click Grant access or Revoke access. 6. Click OK. 7. After the operation finishes, click Close on the Operation Progress screen. See also: Running Database Tasks on page 809 Completing Tasks using the Backup Exec Utility on page 790
815
Running Media Server Group Tasks


Add Media Server on page 816 enables you to add a media server to a media server group. Remove a Media Server on page 817 enables you to remove a media server from a media server group.
Add Media Server

Add Media Server enables you to add a media server to a media server group; it does not remove a media server from the All Media Servers node.
To add a media server to a media server group: 1. On the Media Servers pane, click a media server group. 2. On the task pane, under Media Servers Group Tasks, click Add Media Server. 3. Select a media server to add.
Add Servers To Group selection box
816
4. Click OK. See also: Delete a Media Server from the All Media Servers Subnode on page 794 Remove a Media Server on page 817 Completing Tasks using the Backup Exec Utility on page 790
Remove a Media Server

Remove Media Server enables you to remove a media server from a media server group. Note Remove Media Server does not delete the media server from the All Media Servers node.
Backup Exec Utility
To remove a media server from a media server group: 1. On the Media Servers pane, click a media server group. 2. On the task pane, under Media Server Group Tasks, click Remove Media Server. 3. Select a media server to remove.
Remove Server selection box
817
Running Cluster Tasks
4. Click OK. See also: Delete a Media Server from the All Media Servers Subnode on page 794 Add Media Server on page 816 Completing Tasks using the Backup Exec Utility on page 790

This section guides you through the following Backup Exec Utility task:
Edit Cluster Configuration on page 818 enables you to reset a SCSI bus or reset a specific SCSI LUN on a media server or a group of media servers that are in a clustered environment.
Edit Cluster Configuration

Edit Cluster Configuration enables you to reset either the entire SCSI bus or a specific SCSI LUN in a clustered environment. Cluster configuration options include:
Cluster Configuration Options Item Server(s) Description The name of the selected media server or servers on which the SCSI bus or specific SCSI LUN is being reset. Enables the device and media service to issue a SCSI bus reset to the first device found on the bus. This only occurs when there is a cluster fail-over and this option is enabled. Resetting the bus releases any device that may be reserved at the time of the fail-over. This option is typically enabled if storage device is being shared on a shared SCSI bus; do not use this option in a SAN SSO configuration.
SCSI Bus Reset
818
Running Cluster Tasks Cluster Configuration Options Item SCSI LUN Reset Description Enables the device and media service to issue a targeted LUN reset to a storage device that is being reserved in the cluster fail-over configuration. This targeted LUN reset will be issued only if the device (storage device, router, etc.) supports targeted LUN resets. Check your hardware documentation for support of this feature. This option is typically enabled in a Fibre channel SAN SSO configuration and your devices support targeted SCSI LUN reset.
Backup Exec Utility
To edit a cluster configuration: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. On the task pane, under Cluster Task, click Edit Cluster Configuration. 3. Select SCSI Bus Reset if your storage device is being shared on a shared SCSI bus. Caution Do not use the option, SCSI Bus Reset, in a SAN Shared Storage Option configuration. 4. Select SCSI LUN Reset if your device or devices support targeted LUN reset and your environment is using a Fibre Channel Storage Area Network (SAN). 5. Click OK. See also: Completing Tasks using the Backup Exec Utility on page 790
819
820
VERITAS Backup Exec - Remote Agent
The VERITAS Backup Exec for Windows Servers Remote Agent (Remote Agent) is installed as a separate, add-on component that must be used for the backup and restore of remote Windows resources. It is a system service that runs on remote Windows servers and workstations. The Remote Agent:

Enables the remote backup and restore of Windows features. Increases backup throughput on Windows systems. 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. Enables you to backup and restore in firewall environments. Enables you to backup and restore using the Specified Network feature in Backup Exec for Windows Servers.
Remote Agent
In order to backup and restore the following platforms, the Remote Agent must be purchased and installed. These platforms include:

Windows.NET (all versions) Windows 2000 (all Server versions) Windows NT 4.0 (all Server versions)
Note To protect the Workstation versions of these platforms, you must install the Remote Agent on each platform; however a license is not required. To install the Remote Agent on Workstation versions of the platforms, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
821
Requirements for the Remote Agent
Significant performance increases are attained 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. 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. See also: Requirements for the Remote Agent on page 822 Installing the Remote Agent to Remote Windows Servers on page 823 Enable Remote Agent TCP dynamic port range on page 328 Backing Up Data in a Mixed Environment Using the Remote Agent on page 825
Requirements for the Remote Agent

Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server 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 serial numbers for each remote Windows server that you want to protect. To back up a remote Windows server from more than one media server, you must enter the same Remote Agent serial number on each media server. Backup Exec database agents, the Intelligent Image Option (IIO), and the Advanced Open File Option (AOFO) also include a Remote Agent that allows you to protect one remote Windows server. The Remote Agent license is enabled when you install the database agent, the IIO, and the AOFO serial numbers on the media server. However, if you are using the database agent, IIO, or AOFO on the local media server only, you are entitled to install the Remote Agent that was included with one of those options to one remote Windows server so that resource can be protected by Backup Exec. You must install the Remote Agent on XP Professional, Windows 2000 Professional, and Windows NT 4 workstations in order to protect them; however, a Remote Agent serial number is not required for these installations. See also: Installing the Remote Agent to Remote Windows Servers on page 823 Enable Remote Agent TCP dynamic port range on page 328
822
Installing the Remote Agent to Remote Windows Servers
Installing the Remote Agent to Remote Windows Servers

Installation of the Remote Agent software on remote Windows servers is accomplished from a Backup Exec media server using push installation technology. Push installations save time by eliminating the need for local access at the target computer for the installation to be successful. Note If you have a previous version of the Remote Agent installed, it will automatically be upgraded when you initiate a new Remote Agent installation. Previous versions of the Remote Agent are automatically detected on the remote systems and replaced with the new version during installation of the new Remote Agent. Note that the name of the system service may have changed when the upgrade is complete. To install the Remote Agent on a remote server, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. Note You can also install and uninstall the Remote Agent on remote servers using the Windows command line. See Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
Remote Agent
Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line
You can also install the Remote Agent using silent mode on a remote server using the Windows command line. Note Silent mode runs the installation operation without the benefit of a user interface.
To install the Remote Agent on a remote server using the Windows command line: 1. Move to a remote server. 2. Map a drive letter to the Backup Exec for Windows Servers media server RANT32 directory using the following path: \Program Files\VERITAS\Backup Exec\NT\Agents\RANT32 3. Open a command prompt and enter the drive letter you mapped in step 2. 4. Run the following command: setup.exe /RANT32: -s
Appendix A, VERITAS Backup Exec - Remote Agent
823
Stopping and Starting the Remote Agent
5. The Remote Agent is installed on the remote server in the following directory: \Program Files\VERITAS\Backup Exec\RANT 6. The Remote Agent installation log file is installed in \WINNT\bkupinst.log.
To uninstall the Remote Agent from a remote server using the Windows command line: 1. At the remote server, open a command prompt. 2. Change directories to the Remote Agent install directory using the following path: \Program Files\VERITAS\Backup Exec\RANT 3. Run the following command: setup.exe /RANT32: -s -u Note 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 server.
Stopping and Starting the Remote Agent

The Remote Agent is automatically started as a service when Windows is started on the remote server.
To stop or start the Remote Agent on a Windows 2000, Windows XP, or .NET system: 1. On the Windows desktop, right-click My Computer, and then click Manage. 2. In the Scope pane of the Management Console, double-click Services and Applications and then click Services. 3. In the Results pane, right-click the Backup Exec Remote Agent for Windows Servers service. Click Stop to stop Remote Agent or click Start to start the Remote Agent.
To stop or start the Remote Agent on a Windows NT system: 1. Click Start, and then point to Settings. 2. Point to Control Panel, and then double-click Services.
824
Backing Up Data in a Mixed Environment Using the Remote Agent
3. Select the Backup Exec Remote Agent for Windows Servers service. 4. Click Stop to stop the Remote Agent or click Start to start the Remote Agent. See also: Enable Remote Agent TCP dynamic port range on page 328

You must install the Remote Agent on all remote Windows systems that you want to be backed up. Without the Remote Agent, the following Windows features cannot be backed up correctly:

Encrypted files SIS files
Remote Agent
Disk quota data Removable Storage data Remote Storage data Mount points Sparse files System State data, including: COM+ Class Registration database Boot and system files Registry Certificate Services database (if the server is operating as a certificate server) Active Directory (if the server is a domain controller) SYSVOL (if the server is a domain controller) Cluster quorum
Note You can select System State for backup on a remote system running Windows 2000, Windows XP, or Windows.NET only when the Remote Agent is installed on the remote system.
Appendix A, VERITAS Backup Exec - Remote Agent
825
826
VERITAS Backup Exec Admin Plus Pack Option
The Admin Plus Pack Option provides features designed for distributed data management of your media and remote servers. Through the Admin Plus Pack Option, you can:

Create a clone CD image so you can install Backup Exec on additional servers using the same installation settings. Remotely install the same Backup Exec installation parameters to multiple systems. Copy jobs, scripts, and job templates between media servers. Run advanced Backup Exec reports. Schedule a report to run recurringly. Distribute reports through notification.
Installing the Admin Plus Pack Option

Admin Plus Pack
To use the Admin Plus Pack Option features, the media server must have the Admin Plus Pack Option installed. Separate serial numbers are required for each remote server you plan on cloning or using to copy jobs, scripts, or templates. For more information about requirements for media servers, refer to System Requirements on page 42. You can install the Admin Plus Pack Option while installing Backup Exec by following the procedures described in Installing Backup Exec Using the Installation Program on page 47. If you have already installed Backup Exec and now want to install the Admin Plus Pack Option, complete the procedures described in Installing Backup Exec Options on a Local Server on page 49 or Installing Backup Exec Remote Agents and Options on Remote Servers on page 54.
827
Using a Clone CD Image

A clone CD image captures the Backup Exec installation program and your installation settings, such as account information, additional options, and destination directory. You can create this CD image during the installation process provided you have entered a serial number for the Admin Plus Pack Option or are installing Not for Resale, Evaluation, or Open Option Suite edition. 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.
Creating a Clone CD Image
To create a clone CD image: 1. Begin installing Backup Exec following the procedures described in Installing Backup Exec on page 46. You must use the Backup Exec installation CD when creating the clone CD image for the first time. 2. When the list of features being installed appears, ensure Create Clone CD is selected. Features that are not selected will have a red X appearing next to the feature name.
Create Clone CD option selected
828
3. Click Next and continue with the installation procedures. 4. When the Create Clone CD Image dialog box appears, ensure the directory listed is the directory where you want the clone CD image file copied. If the location is not correct, click Change and browse to select the correct location. The directory install will be copying the clone CD image file to should be an empty directory. 5. Click Next and continue with the installation procedures. Note 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 use a clone CD image to install to a local system:
Insert the CD containing your clone CD image into the CD drive.
Note If autorun is not enabled on your system, run SETUP.CMD, which is in the root of the installation CD directory.
Admin Plus Pack
Because the installation parameters, or options, have already been captured in the clone CD image, you will not be prompted for these options.
Appendix B, VERITAS Backup Exec - Admin Plus Pack Option
829
Installing to a Remote System Using a Clone CD Image
To install remotely using a clone CD image: 1. Begin the Backup Exec installation procedures as described in Installing Backup Exec on page 46. 2. Add the remote systems to which you are installing.
Remote install options
3. When the Select Push Method dialog box appears, select from one of the following options:
Remote install options Item Remote install with serialized options Description Select this option if you want to enter serial numbers for the remote systems. During the install, a dialog asking for the serial numbers for the remote system appears. Select this option if you want to install remotely using all of the installation options installed on the local system. When this option is used, you cannot change any settings on the remote system. For example, if you have installed the Intelligent Disaster Recovery option locally, this option will also be installed remotely. Select this option if you want to install remotely using the clone file settings that may be contained on a clone CD image or could also be contained in a previously created parameter file (see Creating and Using Installation Parameter Files on page 62). When this option is selected, you will be able to browse to a parameter file.
Remote install with cloned local settings
Remote install from clone file settings
4. Follow the on-screen prompts.

830
Copying Jobs, Selection Lists, and Job Templates Between Servers
Copying Jobs, Selection Lists, and Job Templates Between Servers

With the Admin Plus Pack Option, you can copy backup jobs, selection lists, and backup job templates that were created on your media server to another server. Backup Exec sends an alert with the job success or failure status along with a log file that allows you to view results.
To copy jobs, selection lists, or job templates: 1. On the media servers navigation bar, click Job Setup. 2. Select the job, template, or backup selection list you want to copy. 3. Under Backup Tasks in the task list, select Copy to media servers.
Copy to media server
Admin Plus Pack
831
Advanced Reporting Capabilities
4. Enter the options as described in the following table:

Copy options Item Server Name Description Enter the name of the server you want to copy to, and then click Add. Each server added to the list will receive a copy. Select this option if you want to overwrite an existing job, selection list, or template having the same name.
If this item already exists on the destination server, overwrite it
5. Click OK. The operation is queued. The default timeout is five minutes; if the transfer cannot be completed within five minutes, the transfer is aborted and an alert is issued.

The Admin Plus Pack Option provides advanced reporting capabilities, including:

Ability to run an additional 24 reports as well as the 13 standard reports available with Backup Exec. Ability to schedule a report to run at a specified times or specify a recurring schedule for the report to run. Ability to have Backup Exec distribute reports through notification.
The following advanced reports are provided with the Admin Plus Pack Option:
Advanced Reports Report Name Active Alerts by Media Server Description 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 835). 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 836).
Alert History by Media Server
832
Advanced Reporting Capabilities Advanced Reports (continued) Report Name Description
Backup Job Success Rate Lists the success rate for backup jobs run to protect selected servers (see Backup Job Success Rate Report on page 837). 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 838). 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 839). Lists the success rate for backup jobs for a specific number of days for selected servers (see Backup Success Rate Report on page 840). Lists all the jobs that ran within the last 72 hours in chronological order (see Daily Job Summary Report on page 841). Lists drive summary history for each archive device for the past 30 days including daily job count, bytes processed, and the percentage of drive utilization (see Daily Network Device Utilization Report on page 842).
Backup Size by Resource
Backup Success Rate
Daily Job Summary
Daily Network Device Utilization
Device Usage by Template Lists all the job templates that are targeted to specific drive selections (see Device Usage by Template on page 843). Event Recipients Lists all events registered by each notification recipient (see Event Recipients Report on page 843). Lists all the failed backup jobs sorted by the resource server and time frame (see Failed Backup Jobs Report on page 844).
Admin Plus Pack
Failed Backup Jobs
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 845). Job Queue Status Lists the jobs in the queue sorted by status (see Job Queue Status Report on page 845). Lists all the job templates that are defined for the server (see Job Templates Report on page 846).
Job Templates
833
Advanced Reporting Capabilities Advanced Reports (continued) Report Name Machines Backed Up Description Lists all the servers that have been protected by Backup Exec (see Machines Backed Up Report on page 847). 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 848). 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 849). 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 849). Lists all the problem files reported for jobs. The files are grouped by day and resource (see Problem Files Report on page 850). Lists all media that have been modified in the last 24 hours (see Recently Written Media Report on page 851). 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 852). Lists all reusable media currently in the specified vault (see Retrieve Media from Vault Report on page 853). Lists the estimated scheduled workload for the next 24-hour period by server (see Scheduled Server Workload on page 853).
Media Required for Recovery
Move Media to Vault
Overnight Summary
Problem Files
Recently Written Media
Resource Risk Assessment
Retrieve Media from Vault
Scheduled Server Workload
Template Definition Usage Lists the usage of template definitions by resources (see Template Definition Usage Report on page 854).
See also: Reports on page 501
834
Scheduling Report Jobs and Setting Notification Recipients

With the Admin Plus Pack Option installed, you can create a report job and schedule it to run at a specific time or specify a recurring schedule for a report to run. For information about creating a report job, see Running and Viewing a New Report Job on page 506. For information about scheduling the job, see Scheduling Jobs on page 358. You can also assign notification recipients to the report job just as you would for other Backup Exec jobs, such as backups and restores. For more information about setting notification recipients, see Selecting Recipients for Job Notification on page 492. 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.
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 Media server option. Information displayed in the Active Alerts by Media Server report is described in the following table.
Active Alerts by Media Server Report Item Time Job Name Device Name Category Message Description
Admin Plus Pack
Date and time the alert occurred. The 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.
835
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 Media server option. Information displayed in the Alert History by Media Server report is described in the following table.
Alert History by Media Server Report Item Media Server Time Received Responded Responding User Job Name Category Message 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. The 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.
836
Backup Job Success Rate Report

The Backup 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 selecting filter parameters for the Protected server option and range parameters for the Days option. Information displayed in the Backup Success Rate report is described in the following table.
Backup Success Rate Report Item Server Date Total Jobs Successful Success Rate 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.
Admin Plus Pack
837
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 selecting filter parameters for the Protected server option and range parameters for the Hours option. Information displayed in the Daily Jobs by Resource report is described in the following table.
Backup Set Details by Resource Report Item Resource Start Time Job Statistics Duration Size (MB) Files Directories MB/Minute Exceptions Skipped Corrupt FIles Files in Use Status 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. 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. Description The name of the system being protected. Date and time the operation started.
838
Backup Size By Resource Report

The Backup Size By Resource report lists the backup size for each resource job for up to seven previous jobs run. It also computes the trailing average, which is the average of the amount of data backed up in the seven previous jobs. 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 Backup Size by Resource report is described in the following table.
Backup Size by Resource Job Report Item Server 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.
Resource Job
Job Date and Time Run Date and time the backup job was processed. Backup Size, MB Trailing Avg, MB Difference % Amount of data backed up in megabytes. 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.
Admin Plus Pack
839
Backup Success Rate Report

The Backup Success Rate report lists the success rate for backup jobs for a specific number of days for selected servers. 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 Backup Success Rate by Resource report is described in the following table.
Backup Success Rate by Resource Report Item Resource Date Backup Sets Successful Success Rate Description The 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.
840
Daily Job Summary Report

The Daily Job 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 Daily Jobs report is described in the following table.
Daily Job Summary Item Start Time Job Name Job Statistics Duration Size (MB) Files Directories MB/Minute File Exceptions Skipped Corrupt FIles Files in Use Status Type 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. For more information on backup methods, see Backup method for files on page 248. 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. Description Date and time the operation started. The name of the completed job.
Admin Plus Pack
841
Daily Network Device Utilization Report

The Daily Network Device Utilization report lists drive summary history for each archive device for the specified period including daily job count, bytes processed, and the percentage of drive utilization. You can limit the amount of data that appears in the report by selecting range parameters for the Days option. Information displayed in the Daily Network Device Utilization report is described in the following table.
Daily Network Device Utilization Report Item Drive Name 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. The number of bytes processed by the media servers storage device. Percentage of device utilization.
Date Jobs Bytes Processed Utilization (%)
842
Device Usage by Template

The Template Drive Usage report lists all the job templates that are targeted to specific drive selections. Information displayed in the Template Drive Usage report is described in the following table.
Template Drive Usage Report Item Drive Name Description Name of the storage device and the media server where the device is located. Specific type of backup. For more information on backup methods, see Backup method for files on page 248. Name of the job template. Describes the data that was backed up and the location of the data.
Method
Template Name Set Description
Admin Plus Pack
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.
Event Recipient Report Item Recipient Type Recipient Name Event Type Event Name Description The type of recipient, such as Person, Net Send, Printer, or Group. Name of the recipient. The alert category or ad hoc job. Detail for the alert category or ad hoc job.
843
Failed Backup Jobs Report

The Failed Backup Jobs report lists all the failed backup jobs sorted by the server and specified time frame. 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 Failed Backup Jobs report is described in the following table:
Failed Jobs Report Item Resource Start Time Duration Type Description The name of the system being protected. Date and time the backup job started. Length of time the operation took to process. Specific type of backup. For more information on backup methods, see Backup method for files on page 248. The category for the failed job that may be generated by a system, job, media, or device error. Describes the event that caused the alert. Status of the operation, such as Completed. Name of the device on which the job ran.
Error Category
Error Text Status Device Name
844
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.
Job Distribution by Device Report Item Device Description Name of the device on which the job ran.
Job Date and Time Run Date and time the job was processed. Job Names of the jobs that ran on the device.
Job Queue Status Report

Admin Plus Pack
The Job Queue Status report provides details about the job queue sorted by status. You can limit the amount of data that appears in the report by selecting filter parameters for the Job status. Information displayed in the Job Queue Status report is described in the following table.
Job Queue Status Report Item Job Status Job Next Due Date Original Due Date 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.
845
Advanced Reporting Capabilities Job Queue Status Report (continued) Item Priority Description Job priority that determines which job runs first. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Available priorities include:

Highest High Medium Lowest Low
On Hold 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.
Job Templates Report

The Job Templates report lists all the job templates that are defined for the server. Information displayed in the Job Templates report is described in the following table.
Job Templates Report Item Template Name Set Description Method Description Name of the job template. Describes the data that will be backed up and the location of the data. Specific type of backup. For more information on backup methods, see Understanding Backup Methods and Their Advantages on page 340. Type of job that will run, such as Backup. Name of the device on which the job will run.
Type Device
846
Advanced Reporting Capabilities Job Templates Report (continued) Item Media Set Overwrite/Append Description Name of the media set on which the job will run. The media overwrite protection option configured for the backup job template properties.
See also: Running a Report on page 503 Viewing Report Properties on page 512
Machines Backed Up Report

The Machines Backed Up report lists all the protected servers and the times they were backed up. You can limit the amount of data that appears in the report by selecting range parameters for the Days option. Information displayed in the Machines Backed Up report is described in the following table.
Machines Backed Up Report Item Server Total Backup Count Last Backup Description
Admin Plus Pack
Name of the server that was backed up. Total number of backups performed. Date of the last backup job for this server.
847
Media Required for Recovery Report

The Media Required for Recovery report lists the media that contain the backup sets for each system backed up on the selected media server for the specified time period. However, this report may be inaccurate if media overwrite settings allow the media to be overwritten. You can limit the amount of data that appears in the report by selecting filter parameters for the Protected server option and range parameters for the Days option. Information displayed in the Media Required for Recovery report is described in the following table.
Media Required for Recovery Report Item Resource Type Description Name of the system that was backed up. Specific type of backup. For more information on backup methods, see Backup method for files on page 248. 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.
Date Media Label
848
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 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 range parameters for the Days option. Information displayed in the Move Media to Vault report is described in the following table.
Move Media to Vault Report Item Media Label Description Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Location of the media.
Location
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. Information displayed in the Overnight Summary report is described in the following table.
Overnight Summary Report Item Resource Type Description System being protected. Specific type of backup. For more information on backup methods, see Backup method for files on page 248. Date and time the operation started. 849
Admin Plus Pack
Start time
Advanced Reporting Capabilities Overnight Summary Report (continued) Item Status Error Category Description Status of the operation. The 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.
Media Server Device Name Total Tasks
Uncorrected Exceptions Number of jobs that failed and were not run again with successful completion. Service Level Percentage of jobs that ran successfully.
Problem Files Report

The Problem Files report lists all the problem files reported for jobs. The files are grouped by day and resource. You can limit the amount of data that appears in the report by selecting filter parameters for the Protected server option and range parameters for the Days option. Information displayed in the Problem Files report is described in the following table.
Problem Files Report Item Date Resource Time Reason Description Date the problem file was encountered. System on which the problem file is located. Time the problem file was encountered. The error code listed in the log file summary.
850
Advanced Reporting Capabilities Problem Files Report (continued) Item File Name Type Media Server Description Name of the problem file. Specific type of file that caused the problem. Name of the server on which the file is located.
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.
Recently Written Media Item Media Label 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.
Admin Plus Pack
Location Set
851
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.
Resource Risk Assessment Report Item Resource Error Text Start Time Job Error Category Description The 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.
Media Server Device Name
852
Retrieve Media from Vault Report

The Retrieve Media from Vault report lists all reusable media currently in a specified media vault. You can limit the amount of data that appears in the report by selecting filter parameters for the Vault option. Information displayed in the Retrieve Media from Vault report is described in the following table.
Retrieve Media from Vault Report Item Media Label Description Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Name of the vault where the media is located.
Location
Scheduled Server Workload

The Scheduled Server Workload report displays the estimated scheduled workload for a server during the next 24-hour period or a user-defined time period. The report only displays recurring jobs that have already run at least one time, not jobs scheduled to run once. You can limit the amount of data that appears in the report by selecting filter parameters for the Media server option and range parameters for the Hours option. Information displayed in the Scheduled Server Workload report is described in the following table.
Scheduled Server Workload Report Item Media Server Job Next Due Date Description Name of the media server that will process the scheduled jobs. Name of the job scheduled to run. The time and day the next job is scheduled to run.
Admin Plus Pack
853
Advanced Reporting Capabilities Scheduled Server Workload Report (continued) Item Backup Size, MB Description 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.
Total Size (MB)
Total Size (MB)
Template Definition Usage Report

The Template Definition Usage report shows the usage of template definitions by 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 Template Definition Usage report is described in the following table.
Template Definition Usage Report Item Template Name Job Set Description Description Name of the job template. Name of the job that used the template. Describes the data that was backed up and the location of the data.
Resources protected by System being protected. this template
854
VERITAS Backup Exec - Intelligent Disaster Recovery Option
Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR) Option enables you to quickly and efficiently recover Windows computers after a disaster. The IDR wizards guide you in preparing for disaster recovery and in recovering a local or remote computer to its pre-disaster state. A complete intelligent disaster recovery consists of: a. Specifying a location where a copy of the computer-specific disaster recovery file will be stored. b. Running full backups of the hard drives of the computers to be protected. c. Running the IDR Preparation Wizard to create bootable media and recovery diskettes for each computer. d. Recovering a computer using the IDR Recovery Wizard and the recovery media. During initial startup, a wizard guides you through setting an alternate data path for the computer-specific disaster recovery file, called a *.dr file, in which the asterisk (*) represents the name of the computer for which the file was created. A *.dr file contains specific information for the computer you are protecting, including:
Hardware-specific information for each computer, such as hard disk partition information (Windows 2000 and NT only), 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 .NET computers, Windows Automated System Recovery (ASR) configuration information. The ASR files are necessary to recreate partitions on Windows XP and .NET computers during the recovery process.
IDR
The default data path for the *.dr file is on the media servers hard drive, but it is recommended that you specify an alternate data path to store another copy of the *.dr file in case the media servers hard drive is damaged.
Final: 25 November 2002
855
The IDR Preparation Wizard guides you through the preparation of bootable media used to recover protected computers and copies the *.dr file and other recovery information to the Intelligent Disaster Recovery diskette. You can create three types of bootable media with the IDR Preparation Wizard:

Diskettes (not supported for Windows XP or Windows .NET) CD-R (CD-Recordable) or CD-RW (CD-Rewritable) Bootable tape (the tape device must support bootable specifications)
Consider what type of Windows computer is being protected, the available hardware, and the system BIOS when selecting the type of bootable media to create. You can also combine media to make updating the *.dr files easier. If you are using bootable CD-R or CD-RW, or tape, you can still back up the *.dr files to diskette using the IDR Preparation Wizard so that you can easily update them when required. Use the chart below to decide which type of media to use.
Bootable Media Comparison Chart Type of Media Diskettes Advantages Works on most computers. Can also be used to protect remote Windows computers on the network. Can create bootable diskettes for remote computers. CD-R, CD-RW Disadvantages Requires more preparation and recovery time than CDs and tapes. Not supported for Windows XP or Windows .NET.
Requires less preparation and Requires a BIOS that supports recovery time than diskettes. booting from a CD. Can also be used to protect remote Windows computers on the network. Can create bootable CD images for remote computers. Requires a CD burner.
Bootable tape
Requires less preparation and Requires a BIOS that supports recovery time than diskettes. booting from a SCSI CD and a bootable tape device that emulates a SCSI CD drive. Cannot create bootable tape images for remote computers.
856
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. After setting up an alternate data location for the *.dr file, run full backups for the hard drives, and then run the IDR Preparation Wizard to create the bootable and recovery media. Note When creating a bootable tape image, the bootable tape image must be created before running full backups. You will be prepared to successfully recover local or remote computers, using any of the following recovery methods:

Restore a media server (Backup Exec server) using a locally attached storage device. 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
See also: Getting Started with IDR on page 859 Creating and Updating Recovery Media on page 865
IDR
Appendix C, VERITAS Backup Exec - Intelligent Disaster Recovery Option
857
Requirements for Using IDR

VERITAS Backup Exec for Windows Servers. The VERITAS Backup Exec for Windows Servers Remote Agent must be installed on any remote computers to be protected with IDR. Windows NT recovery requires at least 40 MB of hard drive space to hold the minimal recovery system, as well as sufficient space for the data that is being restored. The required hard drive space for a 2.0 GB partition storing 1.8 GB of data is 1.8 GB plus 128 MB plus 40 MB for a total of 1.97 GB. Windows 2000/XP/.NET recovery requires sufficient hard drive space to hold an entire Windows installation (600 MB to 2 GB).
Note Disaster recovery from virtual devices must be done via Remote IDR using a media server with access to the virtual device. See also:
Requirements for Running the IDR Preparation Wizard on page 868 Using an Evaluation Version of the IDR Option on page 859
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. Install the Intelligent Disaster Recovery option on the media server first (the server on which Backup Exec is installed), and then enter a serial number for the Intelligent Disaster Recovery Additional Client option for each additional remote computer. All IDR serial numbers, both local and remote, are entered on the local media server. The Backup Exec Remote Agent must be purchased separately from the IDR option, and must also be installed on any remote computer on which the Intelligent Disaster Recovery Additional Client option is installed. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. The IDR Configuration Wizard runs as part of the First Time Startup Wizard when Backup Exec is started for the first time, and also runs when the IDR option is installed after Backup Exec is installed. See also: Getting Started with IDR on page 859
858
Getting Started with IDR
Using an Evaluation Version of the IDR Option

The Intelligent Disaster Recovery option can be installed and evaluated until the evaluation period expires or until IDR is 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 and the Intelligent Disaster Recovery diskette. If you must use the IDR Recovery Wizard to recover a computer after the evaluation period has expired, you will be prompted to enter a valid IDR serial number to continue the recovery process.

The IDR Configuration Wizard appears the first time Backup Exec is started after IDR is installed. This wizard prompts you to set an alternate data path for the computer-specific disaster recovery file, called a *.dr file. The asterisk (*) represents the name of the computer for which the file was created. A *.dr file contains specific information for the computer being protected, including:
Hardware-specific information for each computer, such as hard disk partition information (Windows 2000 and NT only), 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 .NET computers, Windows Automated System Recovery (ASR) configuration information. The ASR files are necessary to recreate partitions on Windows XP and .NET computers during the recovery process.
IDR
859
To run the IDR Configuration Wizard: 6. 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\VERITAS\Backup Exec\NT\IDR\Data\<computer name>.DR. The screen Enter An Alternate Data Path allows 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.
It is recommended that the alternate location be on another computer or on a different physical drive than the default location. Note 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. 7. Enter the alternate location where a copy of the *.dr file will be stored, and then click Next.
860
8. If the computer does not have a locally attached bootable tape device, the IDR configuration is complete. You are ready to run backups and create bootable media. Go to Creating and Updating Recovery Media on page 865 to continue disaster recovery preparation. If a bootable tape device is detected, you are prompted to create a bootable tape image.
9. Do one of the following: a. Click Yes, create the image now (recommended), click Next, and then continue with step 10. b. Click No, I will create the image later, and then click Next. The IDR Configuration wizard is finished. Create the bootable image for tape later by running the IDR Preparation Wizard before running the overwrite backup job or the tape will not be bootable.
IDR
Go to Creating and Updating Recovery Media on page 865 to continue disaster recovery preparation.
861
Setting Data Paths for the *.dr Files
10. When the Starting Tape Image Creation screen appears, the option Let IDR automatically partition the boot and system drive (Windows 2000 only) is selected by default. Selecting this option allows IDR to automatically partition the boot and system drives for a Windows 2000 computer during the recovery process, and to restore any utility partitions that previously existed. 11. If you clear this option, then before starting the recovery process, reinstall any utility partitions by using the OEM-supplied installation media. During the recovery, manually repartition or reformat the boot and system drives. Click Next to continue. The completed IDR Configuration screen appears . The bootable tape image is stored on this computer. When you run an overwrite backup job for this computer, the bootable image is written to the tape. Go to Creating and Updating Recovery Media on page 865 to continue disaster recovery preparation. See also: Creating and Updating Recovery Media on page 865
Creating a Bootable Tape Image on page 877

Copies of the *.dr files, which contain the computer-specific information for the computer being protected, are necessary to fully 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\VERITAS\Backup Exec\NT\IDR\Data\<computer name>.DR. It is recommended 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.
862
To set the default and alternate data paths for the *.dr file: 1. On the Tools menu, click Options. 2. On the Properties pane, under Settings, click Intelligent Disaster Recovery.
IDR
863
3. Enter the data paths as described in the following table:

Intelligent Disaster Recovery Options - Set Application Defaults Item Data path Description 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\VERITAS\Backup Exec\NT\IDR\Data\<computer name>.DR. Alternate data 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. 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. If you are specifying a remote computers hard drive as the alternate data path, browse to or type the path to the remote computers directory that will contain the disaster recovery data files: \\<remote_computer_name>\<directory_name> Check the directory later to make sure the *.dr files were copied. If you are specifying a directory on a different physical hard drive on the local computer, browse to or type the drive name and the path: d:\drfiles Note 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.
864
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 877 for details). The *.dr file is created when a full backup of the entire hard drive is run. 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. Update all *.dr files on the Intelligent Disaster Recovery diskette by running the IDR Preparation Wizard and selecting Update Intelligent Disaster Recovery diskette only. Whenever backups are run, an alert appears reminding you to use the IDR Preparation Wizard to update the *.dr files on the Intelligent Disaster Recovery diskette, or you can manually copy the *.dr file from a default location to the Intelligent Disaster Recovery diskette or to another diskette. If you use another diskette, label it and store it with the rest of the disaster recovery diskettes. To see the default locations, on the Tools menu, click Options, and then in the Properties pane, click Intelligent Disaster Recovery. If you do not run a full backup before running the IDR Preparation Wizard, you can still create all the media, but the computer-specific *.dr file will not contain the catalog entries for the backup sets, and during the recovery phase, you will have to manually search for and restore the backup sets necessary to recover the computer. The IDR Preparation Wizard guides you through creating or updating bootable media and creating or updating a recovery diskette that together contain all of the files required to recover a Windows computer: Note If the bootable media are diskettes, the Windows operating system CD is also required for recovery; it is not required if the bootable media is tape or CD.
The bootable media contain the system files necessary to make a failed Windows computer operational after a disaster. Create a new bootable image whenever hardware, SCSI drivers, or storage device drivers change on the computer that is being protected. For Windows NT, more information on choosing SCSI drivers during the SCSI host adapter (HBA) detection phase of the IDR Preparation Wizard is in Choosing Generic or Current SCSI Drivers for Windows NT on page 867. Prepare and test bootable media before a disaster to make sure that the media was prepared correctly. For more information on testing the bootable media, see Booting the Computer in an IDR Recovery on page 894.
IDR
865
The recovery diskette, which you can create and update separately from the bootable media by using the IDR Preparation Wizard, is labeled the Intelligent Disaster Recovery diskette and contains: One or more *.dr files, which include computer-specific information such as hardware-specific information, and catalog entries that identify the media necessary to recover the computer. For XP and .NET computers, Windows Automated System Recovery (ASR) configuration information is also included and is required in order to recreate critical partitions on these computers during the recovery process. Any necessary drivers. The Disaster Recovery Wizard. These items are copied to the Intelligent Disaster Recovery diskette. Create and update this diskette separately from the bootable media. At times, the *.dr file may not fit on the Intelligent Disaster Recovery diskette. If this occurs, copy the *.dr file to a separate diskette.
See also: Creating A Full Set of Diskettes on page 871 Creating a Bootable CD Image on page 875 Creating a Bootable Tape Image on page 877 Creating the Intelligent Disaster Recovery Diskette Only on page 879 Updating the Full Set of Disaster Recovery Diskettes on page 881 Updating the Intelligent Disaster Recovery Diskette Only on page 883 Updating Bootable Media on page 886
866
Choosing Generic or Current SCSI Drivers for Windows NT

For Windows NT only, after you have selected all of the computers for which to prepare recovery media, the IDR Preparation Wizard searches for SCSI host adapter (HBA) information. If a SCSI driver version is detected on any of the selected computers that is different from the version on the Windows installation CD, you are prompted to use either the default SCSI drivers that are on the Windows installation CD, or the SCSI drivers that are installed on those computers.
Select Use default SCSI drivers that are available on the inserted CD when creating disaster recovery media for multiple computers or for a computer other than the selected computer. If you do not know whether or not Windows NT supports a driver, select this option and add the driver at a later time. For more information, see Recovering Computers Requiring OEM-Specific SCSI Drivers on page 904.
Select Use SCSI drivers currently installed on this system, which is the default, when creating disaster recovery media for the selected computer. This option adds the drivers currently installed on the selected computer to the Setup diskettes.
Note In most cases, use the SCSI drivers currently installed on the computer being protected because the drivers contained on the Windows installation CD may not be up-to-date. If there is an IDE hard disk greater than 8 GB, select Use SCSI drivers currently installed on this system. Since IDR runs at a Service Pack 0 or 1 level, some SCSI drivers, such as Symbios Logic drivers, will not work because they rely on later Service packs. If there are different SCSI driver versions on the selected computers, the Driver Versions Do Not Match screen appears. Select which driver version is to be put into the bootable image. Options include: First version found. Hardware installation diskettes may be required for the highlighted computers. Latest date time stamp. The newest drivers may not work on older hardware. Only drivers from Windows setup media. Hardware installation diskettes may be required for some computers.
IDR
Note Click Back to try a different set of computers. If more computers are highlighted as incompatible, try clearing the first computer name in the list to find a larger set of computers with compatible SCSI driver versions. Consider updating all computers to the same service pack level to eliminate SCSI driver version differences.
867
Requirements for Running the IDR Preparation Wizard

Please note the following before running the IDR Preparation Wizard:
Run a full backup of the hard drive before creating the boot and recovery media (unless you are creating a bootable tape image). When running full backups for IDR preparation: Make sure that the default shares on each hard disk volume (C$, D$, etc.) have been backed up. The *.dr files are not created or updated if only individual directories are backed up. Additionally: For Windows 2000, back up System State. For Windows XP and .NET, back up Shadow Copy components.
Make sure that if utility partitions are present on the computer, they are selected for backup. Utility partitions are usually small partitions installed on the hard disk by OEM vendors and contain system diagnostic and configuration utilities. Do not include or exclude files from the backup using the Advanced File Selection feature. Make sure that if the computer is a remote computer, a compatible version of the Backup Exec Remote Agent has been installed on it. To determine if the Remote Agent is installed on a remote computer, from Windows Explorer, right-click the remote server and then from the shortcut menu, click Properties. The status of the Remote Agent, if installed, is displayed.
868
The Windows installation CD that matches the version and language (English, French, etc.) installed on the protected system is required. For example, if you are running the IDR Preparation Wizard from a computer running Windows 2000, but the computer you want to prepare recovery media for is running Windows NT, then you must have a Windows NT installation CD with the same language and type of licensing that is on the Windows NT computer. To prepare recovery media for a remote computer, note that: A Windows 2000 computer can create recovery media only for another Windows 2000 computer or for a Windows NT computer. A Windows NT computer can create recovery media only for other Windows NT computers. Windows XP and .NET computers can create recovery media for all Windows 2000, NT, XP, and .NET computers.
Note To prepare recovery media for a computer that is running Windows NT 4.0 Terminal Server edition, insert a standard Windows NT 4.0 installation CD when prompted instead of the Windows NT 4.0 Terminal Server installation CD that matches the operating system in the target computer.
For Windows 2000, XP, and .NET: If the Windows product key does not appear on this screen by default, type the Windows product key in the space provided, and then click Next. This product key is saved on the recovery media so that it does not have to be manually entered during recovery.
Administrative privileges for the protected computer are required.
See also:
Creating A Full Set of Diskettes on page 871 Creating a Bootable CD Image on page 875 Creating the Intelligent Disaster Recovery Diskette Only on page 879 Creating a Bootable Tape Image on page 877 Updating the Full Set of Disaster Recovery Diskettes on page 881 Updating the Intelligent Disaster Recovery Diskette Only on page 883 Updating Bootable Media on page 886.
IDR
869
Running the IDR Preparation Wizard

The IDR Preparation Wizard guides you through the creation or update of bootable media used to recover protected computers and through the creation or update of the Intelligent Disaster Recovery diskette. To start the IDR Preparation Wizard, on the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard. When running the IDR Preparation Wizard, the local computer that the IDR option is installed on 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 different media server to select another media server on which the IDR option is installed in order to create or update the media. See also: Creating and Updating Recovery Media on page 865 Requirements for Running the IDR Preparation Wizard on page 868 Preparing IDR Media Via Other Media Servers on page 889 Creating A Full Set of Diskettes on page 871 Creating a Bootable CD Image on page 875 Creating a Bootable Tape Image on page 877 Creating the Intelligent Disaster Recovery Diskette Only on page 879 Updating the Full Set of Disaster Recovery Diskettes on page 881 Updating the Intelligent Disaster Recovery Diskette Only on page 883 VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855
870
Creating A Full Set of Diskettes

Use the IDR Preparation Wizard to create the bootable diskettes and the Intelligent Disaster Recovery diskette. The IDR Preparation Wizard also enables you to update the *.dr file on the Intelligent Disaster Recovery diskette on a regular basis and to recreate the bootable diskettes whenever hardware, SCSI drivers, or tape drivers change on the protected computer. In addition to the requirements listed in Requirements for Running the IDR Preparation Wizard on page 868, note the following:

For Windows XP or Windows .NET, bootable diskettes are not supported. At least five blank, formatted 1.44 MB diskettes for each set of disaster recovery diskettes to be created are required (for Windows NT computers, at least four diskettes are required). Do not use the Quick Format option when formatting the diskettes. Quick Format removes files from the diskette without scanning it first for bad sectors that can make the diskette unusable.
For Windows NT: Since SCSI information for each computer can be included on the disaster recovery media, create a set of disaster recovery diskettes for each computer on the enterprise.
For Windows 2000: To allow IDR to automatically partition the boot and system drives for a Windows 2000 computer during recovery, and to restore any utility partitions that existed, select the option Let IDR automatically partition the boot and system drive (Windows 2000 only) when creating recovery media for a computer. If this option is not selected, then before starting the recovery process, reinstall any utility partitions by using the OEM-supplied installation media. During the recovery, manually repartition and reformat the boot and system drives. See Using IDR To Recover Windows 2000 Computers on page 893. If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) is selected, create a full set of recovery diskettes for every Windows 2000 computer to be protected with IDR. If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) is not selected, you can use the same diskettes 2 through 5 for all IDR-protected Windows 2000 computers, but you must modify diskette 1 for each computer. The Intelligent Disaster Recovery diskette may also store computer-specific *.dr files, and may need to be recreated for each computer as well.
IDR
871
For instructions on modifying diskette 1, see Modifying Diskette Sets for Use with Multiple Windows 2000 Computers on page 874. For instructions on update the Intelligent Disaster Recovery diskette, see Updating the Intelligent Disaster Recovery Diskette Only on page 883.
Prior to a disaster, test the bootable diskettes to ensure that the computer can boot from them.
To create bootable diskettes: 1. On the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard. By default, the IDR Preparation Wizard uses this computer to create the full set of disaster recovery diskettes. 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 disaster recovery diskettes. 2. Do one of the following: a. To use another computer to create the disaster recovery diskettes, select Choose a different media server, and see Preparing IDR Media Via Other Media Servers on page 889 for details. b. To use this computer to create disaster recovery diskettes, on the Welcome screen, click Next. The Create or Update IDR Boot Media screen appears.
872
3. Select Create - Full set of diskettes to boot the Windows Installation CD, and then click Next. The Starting Bootable Diskettes Creation screen appears. 4. Follow the prompts until the IDR Preparation Wizard is completed. 5. If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) is not selected when recovery media is created, you can use the same diskettes 2 through 5 for all IDR-protected Windows 2000 computers, but you must modify diskette 1 for each computer. For details, see Modifying Diskette Sets for Use with Multiple Windows 2000 Computers on page 874. See also: Booting the Computer in an IDR Recovery on page 894 Choosing Generic or Current SCSI Drivers for Windows NT on page 867
IDR
873
Modifying Diskette Sets for Use with Multiple Windows 2000 Computers
If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) is not selected when recovery media is prepared, create a different diskette 1 for each computer protected with IDR, and then use the same diskettes 2 through 5 for all of the Windows 2000 computers. Diskette 1 contains a file named winnt.sif, which is the script used to automate the installation of Windows 2000 for disaster recovery when using the IDR option. This scripted installation of Windows 2000 requires that a computer name be listed in the winnt.sif file to name the computer during Windows 2000 setup.
Winnt.sif file
Because Windows 2000 automated installations allow only one computer name to be listed in this script, edit the winnt.sif file and change the computer name to another Windows 2000 computer to be recovered. If the computer name is not modified, duplicate computer names on the network may result, and may prevent the recovered server from participating on the network. The Intelligent Disaster Recovery diskette may also store computer-specific *.dr files, and may need to be recreated for each computer as well. See also: Updating the Intelligent Disaster Recovery Diskette Only on page 883
874
Creating a Bootable CD Image

Use the IDR Preparation Wizard to create a bootable CD image, and then run the wizard again to create the Intelligent Disaster Recovery diskette to complete the disaster recovery media. The IDR Preparation Wizard also enables you to update the *.dr file on the Intelligent Disaster Recovery diskette on a regular basis and to recreate the bootable CD image whenever hardware, SCSI drivers, or tape drivers change on the computer. For Windows XP and .NET computers, you will be prompted to copy the Windows Automated System Recovery (ASR) files to either a diskette or to the CD, along with the bootable image. The ASR files are necessary to recreate critical partitions on these computers during the recovery process. If you choose to add the ASR files to the CD image, it may make the recovery process easier since you would not need to locate the diskette that the files are stored on. In addition to the requirements listed in Requirements for Running the IDR Preparation Wizard on page 868, note the following:
Backup Exec includes support for burning the disaster recovery CD image to supported CD-R and CD-RW drives. Supported drives include all CD writing systems supported with VERITAS Simple Backup. If a CD-R or CD-RW drive is not supported by this component, use a third party ISO 9660-compliant application. 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. A blank, writable or rewritable CD is required if the VERITAS IDR CD writing feature is used. To allow IDR to automatically partition the boot and system drives for a Windows 2000 computer during recovery and to restore any utility partitions that existed, select the option Let IDR automatically partition the boot and system drive (Windows 2000 only) when creating recovery media for a computer. If you do not select this option, then before starting the recovery process, reinstall any utility partitions by using the OEM-supplied installation media. During the recovery, manually repartition and reformat the boot and system drives. See Using IDR To Recover Windows 2000 Computers on page 893.
IDR
Prior to a disaster, test the bootable CD to ensure that the computer can boot from it.
875
To create a bootable CD image: 1. On the Tools menu, click Wizards, and then click 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. 2. Do one of the following: a. To use another computer to create the bootable CD image, select Choose a different media server, and see Preparing IDR Media Via Other Media Servers on page 889 for details. b. To use this computer to create the bootable CD image, on the Welcome screen, click Next. The Create or Update IDR Boot Media screen appears.
3. Select Create - Bootable CD Image for use with CD Writers (ISO 9660), and then click Next.
876
4. Follow the prompts until the wizard is completed. During the creation of the CD image, the logging area of the screen is inactive. When the process completes, the logging window can be scrolled or copied to the clipboard by selecting the text and pressing <Ctrl + C>. This logging information can then be pasted into a text editor or e-mailed to Technical Support. 5. When the bootable CD image is complete, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskette. See also: Booting the Computer in an IDR Recovery on page 894 Creating the Intelligent Disaster Recovery Diskette Only on page 879 Choosing Generic or Current SCSI Drivers for Windows NT on page 867
Creating a Bootable Tape Image

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. Next, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskette. The IDR Preparation Wizard also enables you to update the *.dr file on the Intelligent Disaster Recovery 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 boot 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 868.
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.
IDR
1. On the Tools menu, click Wizards, and then click 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.
877
2. Do one of the following: a. To use another computer to create the bootable tape image, select Choose a different media server, and see Preparing IDR Media Via Other Media Servers on page 889 for details. b. To use this computer to create the bootable tape image, on the Welcome screen, click Next. The Create or Update IDR Boot Media screen appears.
3. Select Create - Bootable Tape Image for use with bootable tape devices, and then click Next. The Starting Tape Image Creation screen appears. 4. To allow IDR to automatically partition the boot and system drives for a Windows 2000 computer during recovery, and to restore any utility partitions that existed, select the option Let IDR automatically partition the boot and system drive (Windows 2000 only). If you do not select this option, then before starting the recovery process, reinstall any utility partitions by using the OEM-supplied installation media. During the recovery, manually repartition and reformat the boot and system drives. See Using IDR To Recover Windows 2000 Computers on page 893. 5. Continue following the prompts until the wizard is completed.
878
6. When the bootable tape image has completed, run an overwrite backup job so that the bootable image is written to the tape. 7. When the backup job has completed, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskette. See also:
Choosing Generic or Current SCSI Drivers for Windows NT on page 867 Updating Bootable Media on page 886 Booting the Computer in an IDR Recovery on page 894
Creating the Intelligent Disaster Recovery Diskette Only

Create just the Intelligent Disaster Recovery (IDR) diskette to complete the disaster recovery media if the computer being protected has a bootable tape image or bootable CD image already created or if the boot image has just been updated. The Intelligent Disaster Recovery diskette includes necessary drivers, the Disaster Recovery Wizard, and the computer-specific *.dr file. Note This option is not supported in Windows NT. When the Intelligent Disaster Recovery diskette is complete, click View Disk Configuration to display the Disk Configuration Report. It is recommended that you save this report to another drive or to a diskette, since this information may be helpful during recovery if you did not choose to allow IDR to automatically partition the boot and system drives.
To create the Intelligent Disaster Recovery diskette only: 1. On the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard. By default, the IDR Preparation Wizard uses this computer to create the Intelligent Disaster Recovery diskette. 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 Intelligent Disaster Recovery diskette.
IDR
879
2. Do one of the following: a. To use another computer to create the Intelligent Disaster Recovery diskette, select Choose a different media server, and see Preparing IDR Media Via Other Media Servers on page 889 for details. b. To use this computer to create the Intelligent Disaster Recovery diskette, on the Welcome screen, click Next. The Create or Update IDR Boot Media screen appears.
3. Select Intelligent Disaster Recovery diskette only, and then click Next. 4. Follow the prompts until the wizard is completed. 5. When the Finish screen appears, click View Disk Configuration to display the Disk Configuration Report. It is recommended that you save this report to another drive or to a diskette, since this information may be helpful during recovery if you did not choose to allow IDR to automatically partition the boot and system drives. 6. Remove the diskette from the drive and store it with the rest of the disaster recovery media. See also: Updating the Intelligent Disaster Recovery Diskette Only on page 883
880
Updating the Full Set of Disaster Recovery Diskettes

It is recommended that you update the full set of disaster recovery diskettes if there are hardware changes or if SCSI drivers or tape drivers change on the computer being protected. If you only need to update the *.dr file, choose the Update - Intelligent Disaster Recovery diskette only option, or manually copy this file from the default or alternate locations to the Intelligent Disaster Recovery diskette or to another diskette. If you use another diskette, label it and store it with the rest of the disaster recovery diskettes. To see the default locations, on the Tools menu, click Options, and then in the Properties pane, click Intelligent Disaster Recovery. To be reminded to update the disaster recovery diskettes, create a reminder message using Backup Execs Alert Notification Setup feature. When you have finished updating the recovery diskettes, click View Disk Configuration to display the Disk Configuration Report. It is recommended that you save this report to another drive or to a diskette, since this information may be helpful during recovery if you did not choose to allow IDR to automatically partition the boot and system drives. Note When updating diskettes for a Windows 2000 computer, you will need to have all of the diskettes available during the update.
To update the disaster recovery diskettes: 1. Run a full backup of the target computer. When running full backups for IDR preparation: Make sure that the default shares on each hard disk volume (C$, D$, etc.) have been backed up. The *.dr files are not created or updated if only individual directories are backed up. Additionally: For Windows 2000, back up System State. For Windows XP and .NET, back up Shadow Copy components.
Make sure that if utility partitions are present on the computer, they are selected for backup. Utility partitions are usually small partitions installed on the hard disk by OEM vendors, and contain system diagnostic and configuration utilities. Do not include or exclude files from the backup using the Advanced File Selection feature. Make sure that if the computer is a remote computer, the Backup Exec Remote Agent has been installed on it.
IDR
881
2. On the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard. By default, the IDR Preparation Wizard uses this computer to update the full set of disaster recovery diskettes. 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 diskettes. 3. Do one of the following: a. To use another computer to update the disaster recovery diskettes, select Choose a different media server, and see Preparing IDR Media Via Other Media Servers on page 889 for details. b. To use this computer to update the disaster recovery diskettes, on the Welcome screen, click Next. The Create or Update IDR Boot Media screen appears.
4. Under Update, select Full set of diskettes used to boot the Windows Installation CD, and then click Next. 5. Follow the prompts until the wizard is completed.
882
6. When the Finish screen appears, click View Disk Configuration to display the Disk Configuration Report. It is recommended that you save this report to another drive or to a diskette, since this information may be helpful during recovery if you did not choose to allow IDR to automatically partition the boot and system drives. 7. Remove the diskette from the drive and store it with the rest of the disaster recovery media. The full set of diskettes used to boot the Windows installation CD are now updated. See also: Choosing Generic or Current SCSI Drivers for Windows NT on page 867
Updating the Intelligent Disaster Recovery Diskette Only

Select this option to update the Intelligent Disaster Recovery diskette. You do not have to recreate the Intelligent Disaster Recovery diskette, only update it. When you select this option, the following is updated:
Hardware-specific information for each computer, such as hard disk partition information (Windows 2000 and NT only), mass storage controller information, and Network Interface Card information. Catalog entries that identify the backup media used to recover the computer. For Windows XP and .NET computers, Windows Automated System Recovery (ASR) configuration files that are contained in the *.dr file. The ASR files are necessary to recreate partitions on Windows XP and .NET computers during the recovery process.
Note If you created a bootable CD image and chose to create and add the ASR files to the CD image, you must recreate the bootable CD image to update the ASR files.
Necessary drivers.
When you have finished creating the Intelligent Disaster Recovery diskette, click View Disk Configuration to display the Disk Configuration Report. It is recommended that you save this report to another drive or to a diskette, since this information may be helpful during recovery if you did not choose to allow IDR to automatically partition the boot and system drives.
IDR
883
To update the Intelligent disaster Recovery diskette only: 1. Run a full backup of the target computer. When running full backups for IDR preparation: Make sure that the default shares on each hard disk volume (C$, D$, etc.) have been backed up. The *.dr files are not created or updated if only individual directories are backed up. Additionally: For Windows 2000, back up System State. For Windows XP and .NET, back up Shadow Copy components.
Make sure that if utility partitions are present on the computer, they are selected for backup. Utility partitions are usually small partitions installed on the hard disk by OEM vendors, and contain system diagnostic and configuration utilities. Do not include or exclude files from the backup using the Advanced File Selection feature. Make sure that if the computer is a remote computer, the Backup Exec Remote Agent has been installed on it.
2. On the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard. By default, the IDR Preparation Wizard uses this computer to update the Intelligent Disaster Recovery diskette. 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 Intelligent Disaster Recovery diskette.
884
3. Do one of the following: a. To use another computer to update the Intelligent Disaster Recovery diskette, select Choose a different media server, and see Preparing IDR Media Via Other Media Servers on page 889 for details. b. To use this computer to update the Intelligent Disaster Recovery diskette, on the Welcome screen, click Next. The Create or Update IDR Boot Media screen appears.
4. Select Update - Intelligent Disaster Recovery diskette only, and then click Next. 5. Follow the prompts until the wizard is completed. 6. When the Finish screen appears, click View Disk Configuration to display the Disk Configuration Report. It is recommended that you save this report to another drive or to a diskette, since this information may be helpful during recovery if you did not choose to allow IDR to automatically partition the boot and system drives. The Intelligent Disaster Recovery diskette is now updated. 7. Remove the diskette from the drive and store it with the rest of the disaster recovery media.
IDR
885
Updating Bootable Media

If the media server hardware configuration changes, run the IDR Preparation Wizard and create a new bootable image. If you initially created a bootable image on CD, create a new bootable CD image, run a full backup of the protected computer, and then run the IDR Preparation Wizard to update the Intelligent Disaster Recovery diskette. For more information, see Creating a Bootable CD Image on page 875. If you initially created bootable diskettes, update the full set of diskettes. For more information, see Updating the Full Set of Disaster Recovery Diskettes on page 881. 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, and then click 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.
886
2. Do one of the following: a. To use another computer to update the bootable tape image, select Choose a different media server, and see Preparing IDR Media Via Other Media Servers on page 889 for details. b. To use this computer to update the bootable tape image, on the Welcome screen, click Next. The Create or Update IDR Boot Media screen appears.
3. Select Create - Bootable Tape Image for use with bootable tape devices, and then click Next. The Starting Tape Image Creation screen appears. 4. To allow IDR to automatically partition the boot and system drives for a Windows 2000 computer during recovery, and to restore any utility partitions that existed, select the option Let IDR automatically partition the boot and system drive (Windows 2000 only), and then click Next. If you do not select this option, then before starting the recovery process, reinstall any utility partitions by using the OEM-supplied installation media. During the recovery, manually repartition and reformat the boot and system drives. If you have previously prepared a bootable image for tape, the Disaster Recovery Image Found screen appears.
IDR
887
5. Select Delete the existing image to write the new bootable image to the bootable tape when the first overwrite backup job runs. 6. Continue to follow the prompts until the wizard is complete. 7. When the bootable image is completed, run an overwrite backup job so that the image is written to the tape. 8. When the backup job has completed, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskette. See also:
Booting the Computer in an IDR Recovery on page 894
888
Preparing IDR Media Via Other Media Servers

When running the IDR Preparation Wizard, the local computer that the IDR option is installed on 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 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. On the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard.
2. On the IDR Preparation Wizard Welcome screen, select the option Choose a different media server, and then click Next.
IDR
889
3. Click Browse to browse the network and select a media server that has the IDR option installed, and then click Next to continue preparing disaster recover media. The media server that you select here will be the computer that actually creates the media.
890
Using IDR to Recover a Computer

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. Restoring the media server to its pre-disaster status with IDR consists of the following phases and requirements:

Planning any hardware changes to the computer being recovered. Booting the computer using the bootable media created with the IDR Preparation Wizard to install a minimal version of Windows on the computer. Using the Windows Setup program to repartition and reformat the computer being recovered. Using the Disaster Recovery Wizard to restore the computer to its pre-disaster state and restore the data files.
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, an IDR recovery may render the computer unbootable, 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:

The hardware must be identical to the original computer except for hard disks, video cards, and network interface cards. 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 boot 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 partition information, including utility partitions.
IDR
See also:
Appendix C, VERITAS Backup Exec - Intelligent Disaster Recovery Option 891
Changing Hardware in the Computer to be Recovered on page 892 Booting the Computer in an IDR Recovery on page 894 Using the Windows Setup in an IDR Recovery on page 897 Using the Disaster Recovery Wizard on page 899
Changing Hardware in the Computer to be Recovered

If you plan to change the hardware in the computer being recovered, note the following:

Hard drives. Any hard drives being added should be the same size or larger than the drive being replaced or repartitioning problems may occur. SCSI cards. Install SCSI cards on the computer before running the IDR recovery process so that the cards can be incorporated during the restore. Only SCSI cards that are running during the recovery process are integrated into the restored Windows computer.
Note For Windows NT: Because IDR runs at a Service Pack 0 or 1 level, some SCSI drivers such as Symbios Logic drivers will not work since they rely on later service packs.
Network interface cards. When using IDR to recover a computer remotely, and if different network interface cards (NIC) have been installed, run the Windows Network Control Panel to remove the old NIC drivers and install the new NIC drivers. Video hardware. If you install different video hardware, install the video driver for that hardware after the original Windows operating system boots into VGA compatibility mode. IDR will not install new video drivers.
892
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:

The IBM ServeRAID controller card and ServeRAID software must be installed and configured in order for a boot partition to 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.
Using IDR To Recover Windows 2000 Computers

For Windows 2000, during the recovery phase, critical disks are automatically partitioned before Windows is reinstalled on the computer if the option Let IDR automatically partition the boot and system drive (Windows 2000 only) is selected when boot media are created for the computer. A disk is considered critical if it is required for the computer to boot successfully. Noncritical disks are repartitioned after Windows is installed on the system. To repartition noncritical disks, the boot and system partitions should be on the same partition as in the original layout, and the size of the boot and system partitions should be equal to or greater than the boot and system partitions in the original layout. If the drive letters assigned to the boot and system partitions by the Windows Setup program are not the same as they were in the original layout, they are changed back by the IDR Recovery Wizard. If the boot and system partition layouts are not compatible with the original layout, the disks are not repartitioned. The disks can be repartitioned later by using Windows Disk Administrator. For example, on the pre-disaster computer, C: was the boot drive on the first partition of the disk and D: was the system drive on the second partition. When creating the boot media, the option Let IDR automatically partition the boot and system drive (Windows 2000 only) was not selected. During disaster recovery, the disks are replaced and in the new configuration, C: is the boot drive as well as the system drive. In this case, since the drive layouts are not compatible, the disks will not be repartitioned. Only basic disks and upgraded dynamic disks (upgraded from basic) are supported. However if there are any drives created after upgrading the basic disks to dynamic, they are not supported.
IDR
893
For example, C: and D: are two partitions available on a basic disk. This disk is upgraded to dynamic, and two more drives, E: and F:, are created. Then, during disaster recovery, only C: and D: will be recreated. The disks will be basic, but can later be upgraded to dynamic by using the Windows Disk Administrator. For more information about basic and dynamic disks, refer to your Windows documentation. If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) was not selected during the IDR preparation for Windows 2000 computers, then use the OEM-supplied installation media to boot and re-create any utility partitions before continuing with the instructions in Booting the Computer in an IDR Recovery on page 894.
Booting the Computer in an IDR Recovery

This section provides details on how to boot the computer being recovered using the bootable diskettes, tape, or CD that were created using the IDR Preparation Wizard. The storage device connected to the computer being recovered must be able to boot from the bootable media. Go to one of the following topics:

To use bootable diskettes: on page 894 To use bootable tapes: on page 895 To use a bootable CD: on page 896
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.
To use bootable diskettes: The Windows installation CD that was used during the preparation of the disaster recovery diskettes is required. 1. At the computer being recovered, insert the first bootable diskette. 2. Follow the prompts on the screen, and continue with Using the Windows Setup in an IDR Recovery on page 897.
894
To use bootable tapes: 1. At the computer being recovered, insert the last full backup media containing the bootable image into the tape drive. 2. Follow the bootable tape drive manufacturers instructions for booting from the tape drive. You may have to change the SCSI BIOS settings to enable booting from a SCSI CD-ROM. Some bootable tape drives require that you hold the eject button while powering up the tape drive. After booting the computer, a magenta-colored Backup Exec Intelligent Disaster Recovery Bootstrap screen appears, and displays the following information. Backup Exec Intelligent Disaster Recovery for Windows (NT/W2K/XP/.NET) Copyright (c) VERITAS Software Corporation 1984-2002 All Rights Reserved.
You have successfully loaded a Backup Exec Disaster Recovery CD/Tape image. If you are testing the bootable media, the computer successfully booted the image. Remove the boot media and press <Esc> to stop the recovery. DO NOT PRESS <ENTER>. If you are performing a disaster recovery, press the <Enter> key to start the disaster recovery process, which will repartition and reformat the computers hard disks and DESTROY ALL EXISTING DATA. The Windows setup program and the Backup Exec Disaster Recovery Wizard are then loaded. 3. Do one of the following: If you are testing the bootable media, when the magenta-colored Backup Exec Intelligent Disaster Recovery Bootstrap screen appears, press <Esc> to cancel the disaster recovery process, and then eject the tape and power cycle the tape drive. If you are performing an actual disaster recovery, press <Enter> to begin the disaster recovery process, and continue with Using the Windows Setup in an IDR Recovery on page 897.
IDR
895
To use a bootable CD: If you do not have the Windows installation CD, use the Backup Exec IDR bootable CD instead. 1. At the computer being recovered, insert the bootable CD into the CD-ROM drive. Make sure the BIOS is enabled to boot from a CD. 2. Reset the computer or power it on. The computer will detect a bootable CD. After booting the computer, a magenta-colored Backup Exec Intelligent Disaster Recovery Bootstrap screen appears, and displays the following information. Backup Exec Intelligent Disaster Recovery for Windows (NT/W2K/XP/.NET) Copyright (c) VERITAS Software Corporation 1984-2002 All Rights Reserved.
You have successfully loaded a Backup Exec Disaster Recovery CD/Tape image. If you are testing the bootable media, the computer successfully booted the image. Remove the boot media and press <Esc> to stop the recovery. DO NOT PRESS <ENTER>. If you are performing a disaster recovery, press the <Enter> key to start the disaster recovery process, which will repartition and reformat the computers hard disks and DESTROY ALL EXISTING DATA. The Windows setup program and the Backup Exec Disaster Recovery Wizard are then loaded. 3. Do one of the following: If you are testing the bootable media, when the magenta-colored Backup Exec Intelligent Disaster Recovery Bootstrap screen appears, press <Esc> to cancel the disaster recovery process, and then eject the CD. If you are performing an actual disaster recovery, press <Enter> to begin the disaster recovery process, and continue with Using the Windows Setup in an IDR Recovery on page 897.
896
Using the Windows Setup in an IDR Recovery

Caution Windows Setup may repartition and reformat the hard drive to prepare for the recovery. You may need to use the following keys during the Windows Setup boot process if the ASR files are on diskette, or if there are OEM-specific SCSI drivers that must be installed:
Keys to use during the Windows Setup boot process Condition For Windows XP and .NET only, and if ASR files are on a diskette Action During the Windows Setup boot process, press <F2>, and insert the diskette containing the ASR files. IDR uses Windows Automated System Recovery (ASR) to restore the critical partitions that were previously on the computer. If the ASR files are included in the bootable image, you are not prompted to provide them. The partitions are created as they were defined in the ASR configuration file. If the computer being recovered contains OEM-specific SCSI drivers third party During the Windows Setup boot process, press <F6> to manually add the SCSI host adapter drivers or RAID controller drivers before loading Windows. If you do not add the drivers before loading the operating system, hard drive partitions on the computer are not recognized by Windows. For more information, see Recovering Computers Requiring OEM-Specific SCSI Drivers on page 904.
Note If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) was not selected during the IDR preparation for Windows 2000 computers, then manually repartition the boot and system partitions. Do not change the size of the partitions. When the Windows 2000 Setup screens display the partitions, if utility partitions are present, they appear as either unknown partitions or as EISA utilities. There is no drive letter assigned to these partitions. Do not delete these partitions.
IDR
897
To use the Windows Setup: 1. For bootable tape or bootable CD, go to step 2. For bootable diskettes, do the following: a. Replace the bootable diskettes as prompted. b. When prompted, insert the Windows installation CD in the computers CD drive, and then press <Enter>. c. To recover a Windows NT computer, go to step 2. To recover a Windows 2000 computer, go to step 3. Note If a logon screen appears during the setup process, press <Ctrl> + <Alt> + <Delete> to log on and then press <Enter> to continue. 2. For Windows NT, select a setup method when prompted: Use Express Setup if you do not want to make changes to the partitions. Use Custom Setup if the SCSI drivers are not present on the boot media, to reconfigure any RAID hardware, or to change the partition configuration during recovery. If a new hard drive is detected on the computer, select a file system (FAT or NTFS) for formatting the drive. To restore the original configuration format the partition using a FAT file system. 3. For Windows 2000, do one of the following: If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) was selected during the IDR preparation, then the boot and system drives are automatically created. Install Windows 2000 on the same partition as in the previous configuration. If the option Let IDR automatically partition the boot and system drive (Windows 2000 only) was not selected during the IDR preparation, and if a new hard drive is detected on the computer, then manually create the boot and system drives. Install Windows 2000 on the same partition as in the previous configuration. For more information, see Using IDR To Recover Windows 2000 Computers on page 893.
After selecting a file system, press <Enter>. 4. Remove any diskettes or CDs from the drives, and then press <Enter> to reboot the computer.
898
5. For Windows NT, XP, and .NET, after the reboot, the IDR Wizard is automatically started. Continue with Using the Disaster Recovery Wizard on page 899. For Windows 2000, do the following: a. After the computer is rebooted, at the logon prompt, enter Administrator as the username and leave the password field blank. b. When prompted, insert the Intelligent Disaster Recovery diskette. After all files are restored, the IDR Disaster Recovery Wizard welcome screen appears. c. Continue with Using the Disaster Recovery Wizard on page 899
Using the Disaster Recovery Wizard

The Disaster Recovery Wizard guides you through:

Restoring the computer to an operational state. You can choose to restore the original layout of the hard disks, or you can make changes. Restoring the computers data from the last backup set (including all Full, Incremental, and/or Differential sets). The Recovery Wizard prompts you for the correct media to use during restore operations by reading the Backup Exec catalog information recorded on the disaster recovery diskettes. You can also restore from other backup media if necessary.
To fully automate the recovery, the current *.dr file for the computer being recovered is required; however, if a *.dr file in unavailable or if *.dr file is not current, you can still use IDR to recover the computer. Instructions on recovering the computer without using a *.dr file are included in the following procedure. To restore using the IDR Disaster Recovery Wizard, the following are required:

The media set containing the full backup of the target computer being restored. For recovery on a local computer, a storage device must be connected to the computer being recovered. If bootable diskettes or bootable CD are being used, a media server that can restore the backup sets to the target computer must be connected on the network.
IDR
899
To use the Disaster Recovery Wizard: 1. After reading the Welcome screen, place the diskette containing the *.dr file into Drive A: and click Next. 2. Choose a level of assistance, and then click Next. Automated: Uses information saved in the *.dr file to fully automate the recovery process. All of the backup sets found in the *.dr file will be restored to their original locations. Minimal user interaction is required during recovery. Assisted: Backup set information in the *.dr file will be used, but you will have the opportunity to select which sets to restore. Manual: Backup set information from the *.dr file will not be used to automate the recovery process. Individual backup sets will be identified by reading backup media, and you will have the opportunity to select which sets to restore. If a *.dr file is unavailable or is not updated, select this option and refer to Performing a Manual Restore on page 905.
3. Select the *.dr file for the computer being recovered, and then click Next. Each *.dr file is labeled using the name of the computer from which it was created, and displays the date and time it was created. If the necessary *.dr file is not displayed, copy the *.dr file from the default locations on the media server that ran the last backup to any diskette. Insert this diskette into Drive A:, and then click Scan Drive A: to find the file that you just copied. To proceed without selecting a *.dr file, click Next. 4. After selecting a *.dr file, enter a valid serial number to continue. 5. For Windows NT/2000, if the hard disk partition layout changed, you are prompted to keep the current layout or restore the original layout that is contained in the *.dr file. If you are recovering a Windows NT/2000 computer, and you receive messages that one or more of the hard drives are smaller than the originals, the version of Windows NT/2000 that runs the Recovery Wizard may have detected the hard drives in a different order than they were originally configured.
900
If the original configuration does not match, then to a certain extent, you can control the hard drive numbering scheme that Windows NT/2000 devises. The following chart lists the normal order that Windows NT/2000 uses to assign disk drive numbers. The information in this chart may change if third party drivers are used.
Windows hard drive numbering scheme Primary IDE Master Slave Master Slave SCSI ID 0 SCSI ID 1 SCSI ID 7 (or 15 if Wide SCSI) SCSI ID 0 SCSI ID 1 SCSI ID 7 (or 15 if Wide SCSI) SCSI ID 0 SCSI ID 1 SCSI ID 7 (or 15 if Wide SCSI)
Secondary IDE
SCSI Adapter 0
(In order of the lowest I/O port address)
SCSI Adapter 1
SCSI Adapter <n>
Other types of mass storage controllers are usually seen as SCSI controllers by Windows. Note If the IDR Recovery Wizard cannot detect the hard drive order properly, set up hard drive partitions using the Windows Disk Administrator option within the IDR Recovery Wizard. Then, continue with the automated restore of the backup media.
IDR
For more information, see Using IDR To Recover Windows 2000 Computers on page 893.
901
6. When the Modify Hard Disk Layout screen appears, do one of the following: To use the original configuration from the *.dr file, click Next. To save the contents of this screen as a text file, click Save Configuration. To make changes to the hard disk layout, click Run Disk Manager. Use Disk Administrator to make additional changes to the partition information. For more information on these programs and fault tolerant configurations, please refer to your Windows documentation, and to Altering Hard Drive Partition Sizes on page 903. If a *.dr file does not exist for the computer being recovered, click Run Disk Manager and repartition the hard drive to match the partition layout found on the original computer. 7. If you are restoring with bootable CD or diskettes, select one of the following methods to access the storage device: Use locally attached media device and then click Next. Select the storage device from which you want to restore, and then click Next. Use the network to restore from a remote media server and then click Next.
A Finish screen appears. If changes were made to the partitions, the computer is rebooted. 8. After media devices are detected, click Next. 9. If the *.dr file is on a diskette, select the drives to be restored, and then click Next. Depending on the level of assistance selected earlier, all backup sets may be automatically restored, or you can select individual backup sets to restore. After the automated 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 on page 905. 10. Select the device that contains the restore media. 11. Insert the correct media and click Next. Note If a robotic library is being used to recover your computer, the first drive in the robotic library is for the restore. 12. Remove any diskettes and CDs from the drives.
902
13. To make changes to the computer before starting the operating system, click Run CMD.EXE to open a command prompt window, or click Edit BOOT.INI to modify the boot.ini file on the root of the system partition. Caution Modifying the boot.ini file incorrectly may prevent the computer from restarting. 14. Click Finish to exit the Recovery Wizard and restart the computer.
Altering Hard Drive Partition Sizes

When recovering a Windows NT/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 Administrator program (within the IDR Recovery Wizard) to alter the partition sizes to reflect the larger hard drive size. When recovering a Windows 2000 computer, if the option Let IDR automatically partition the boot and system drive (Windows 2000 only) was not selected, 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 it was replaced with a 9 GB model, IDR (using the *.dr file) will rebuild the hard disk partition table using the partition information found on the original 4 GB hard drive. As a result, only 4 GB of space will be allocated on the new 9 GB hard drive, with a partition map consisting of two 2 GB partitions. Use the Disk Administrator program to repartition the hard drive to include the additional space. For information regarding fault tolerant configurations under Windows NT, please refer to the Windows Resource Kit.
IDR
903
Recovering Computers Requiring OEM-Specific SCSI Drivers

Some third party controller drivers and RAID controller drivers are not bundled with the Windows operating systems. During the Windows Setup boot process, press <F6> to manually add the SCSI host adapter drivers or RAID controller drivers before loading Windows. If you do not add the drivers before loading the operating system, hard drive partitions on the computer are not recognized by Windows. In addition, because RAID controllers store their own configuration information that IDR cannot access, they may require configuration before you can perform a recovery. For information on configuring the controller, see the documentation that came with the hardware. Note These steps can also be used to specify the order in which the drivers are loaded.
Perform the following steps using the IDR full set of bootable diskettes: 1. When the blue Windows Setup screen appears after booting with the IDR boot diskette, press and hold down the <F6> key. You are prompted for diskette 2. 2. Insert diskette 2 and press and hold the <F6> key again. After loading additional drivers, a Setup screen appears that allows you to specify additional devices. 3. Release the <F6> key, and then press the <S> key. 4. Follow the on-screen instructions to load the controller driver software. 5. After loading the controller driver software, press <S> again to specify loading another device. 6. Follow the on-screen instructions to load any additional controller drivers. 7. When finished, press <Enter> and continue recovering the computer.
904
Performing a Manual Restore

Caution If the media to be restored contains both Full backup sets and Incremental or Differential backup sets, restore the Full backup sets first.
To perform a manual restore: 1. Follow step 1 through step 9 in Using the Disaster Recovery Wizard on page 899. 2. If you provided a *.dr file, make sure I will provide my own media is selected and then click Next. 3. Select the tape drive where the restore media resides. The Found a Backup Set dialog box appears, displaying the first backup set found on the media.
4. To restore to a location other than the one displayed, click Change, and then select a location where the data will be restored.
IDR
905
5. Do one of the following: a. Click Restore Set to restore the backup set displayed in Media Information and Set Information. IDR begins restoring the data to the selected partition. When the restore is complete, the Found Backup Set dialog box re-appears for the next backup set 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. b. Click Skip Set to skip the restoration of this backup set and search the media for another backup set from which to restore. c. Click Skip Media to eject the media and replace it with different media. 6. After the last backup set is restored, click Finish to end the recovery process and exit Intelligent Disaster Recovery. See also: Recovering Computers Requiring OEM-Specific SCSI Drivers on page 904
Performing Remote IDR

Remote IDR restores data to a Windows computer over a network from a media server.
To recover a computer using a remote media server: 1. Follow step 1 through step 7 of Using the Disaster Recovery Wizard on page 899. 2. Select Install networking and restore from a remote media server, and then click Next. 3. To recover a Windows NT computer, click Next, and continue with step 4; otherwise, continue with step 13.
906
4. Select either Automatic or Manual as the method to install networking: a. Select Automatic to use information saved in the recovery file to install networking. You must install the original or identical network adapters before using this method. The computer named in the selected *.dr file is displayed on the screen. b. Select Manual to use the Windows NT Network Setup Wizard. You may need to provide OEM network driver media when prompted. Enter the name of the computer being recovered, and then click Next. The NT Network Setup Wizard appears. 5. Make sure that Wired to the Network is selected, and then click Next. 6. To select a network adapter, do one of the following: If the network adapter requires a manufacturer supplied setup diskette, click Select from list, and then click Have disk. If the network adapter does not require a manufacturer supplied setup diskette, either click Select from list or Start search.
A list of network adapters appears. If the network adapter is not listed on the screen that appears, click Select from list, and then click Have disk to add an adapter to the Network Adapter list. On the next wizard screen, the default network protocols are displayed. 7. Select the networking protocols used on the network, and then click Next. 8. Windows NT is ready to install the networking components. Insert the Windows NT installation CD or the IDR bootable CD into the CD-ROM drive, and then click Next to continue. Note Additional setup screens that specifically address the Network Interface Card may appear. If so, follow the screen prompts. 9. If TCP/IP is selected as the network protocol, you are prompted to use DHCP. If you do not want to use DHCP, you are required to enter an IP address. The Windows NT Networking Installation dialog box appears. 10. Click Next to start the network and complete the installation of the networking components.
IDR
907
11. Enter the name of the workgroup or domain for the computer, and then click Next. Note Entering the name of a temporary workgroup, rather than the name of a domain, is recommended. The computer will be restored to its original workgroup or domain when the recovery is complete. 12. Click Finish to complete the network installation and continue with recovery. 13. On the Connect to Media Server screen, enter Backup Exec service account information to logon to a media server where the storage device is located, and then click Next. Note If the media server is in a workgroup, enter the server name again in the domain field. Intelligent Disaster Recovery lists drive letters that you can restore; each drive letter corresponds to a backup set listed in the computers data recovery file. 14. Select the drives to recover to do an automatic restore or select I will provide my own restore media. 15. Click Next. 16. If you selected I will provide my own restore media, go to the media server, select the backup set to restore, and then restore to the target computer being recovered. For the automatic restore, IDR runs jobs on the media server. See also: Microsoft SQL Server Recovery Notes on page 909 Microsoft Exchange Recovery Notes on page 909 Using IDR To Recover IBM Computers on page 893 Recovering Computers Requiring OEM-Specific SCSI Drivers on page 904 Using Backup-to-Disk Folders and Files on page 143
908
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. 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 only made when non-AOFO (Advanced Open File Option) backups of the master and model databases are run. If you are using AOFO for SQL backups, make at least one backup of the master and model databases without using AOFO. If SQL 2000 is upgraded, refresh the master and model database copies with another non-AOFO backup.
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 using 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.
SharePoint Portal Server Recovery Notes

After using Intelligent Disaster Recovery to recover the Windows server (after the last reboot), the SharePoint Portal Server software is installed but is not functional; SharePoint Portal Server must be removed and reinstalled before the SharePoint data can be restored.
IDR
909
910
VERITAS Backup Exec - SAN Shared Storage Option
The VERITAS Backup Exec for Windows Servers - Storage Area Network (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 Arbitrated Loop (FC-AL) or Fibre Channel Switched Fabric (FC-SW). 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 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. In the following example of a shared storage environment, the database server and the media servers transmit data over the FC-AL through a fibre to SCSI bridge (router) to secondary storage devices (SCSI robotic libraries).
Shared Storage
911
Example of the SAN Shared Storage Option using FC-AL
Workstation LAN Server A Database Server Server B Server C
Fibre Channel Arbitrated Loop
Fibre Channel Arbitrated Loop Hub
Fibre-to-SCSI Bridge
SCSI Tape Library SCSI Tape Library
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. See also: Sharing Media on page 931. Scheduling and Viewing Jobs on page 929 Requirements for the SAN Shared Storage Option on page 914
912
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. Recommendations for protecting the database server include the use of the Intelligent Disaster Recovery Option and the setting up of BEUTIL swap-ready 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 BEUTIL swap-ready server. Creating a swap-ready server involves:

Establishing a share to match the one on the current Backup Exec shared database server. Familiarizing yourself with BEUTIL so that you know how to use it should you need to perform the swap.
If you use this scheme, you can quickly switch the storage network to the swap-ready media server using BEUTIL. See also: VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 Designating a New Database Server and Setting Up Servers on page 933
Shared Storage
Appendix D, VERITAS Backup Exec - SAN Shared Storage Option
913
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 NT 4.0 with service pack 6a or greater, Windows 2000, or Windows .NET must be installed. Physical Memory Available, as shown in the Windows Task Manager, plus the File Cache should exceed 52 MB (20 MB for file cache and 32 MB for Backup Exec SAN Shared Storage Database services and administration console). The SAN Shared Storage Option must be locally installed at each server that will be sharing secondary storage devices. The devices in your SAN must be on the supported device list at www.support.veritas.com/info/sso.htm.
For a fibre channel-connected installation, note the following additional requirements:

A fibre channel host adapter and its device drivers must be installed and connected to the SAN. A hub or switch must be connected to all the fibre to SCSI bridges on the SAN. All the robotic libraries must be connected to the SCSI bridges. The hub or switch must be powered up before the bridges. 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).
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 VERITAS device drivers are uninstalled. See also: Installing the SAN Shared Storage Option on page 915
914
Installing the SAN Shared Storage Option

You must install the Backup Exec SAN Shared Storage Option on the shared database server before installing Backup Exec SAN Shared Storage Option on other servers. The server containing the shared database must be running before other media servers can be installed properly. Tip For best performance, install the shared ADAMM and catalog databases on the fastest server on the SAN that is not heavily loaded with non-Backup Exec tasks.
You can install the SAN Shared Storage Option while installing Backup Exec by following the procedures described in Installing Backup Exec Using the Installation Program on page 47. If you have already installed Backup Exec, follow the procedures described in Installing Backup Exec Options on a Local Server on page 49. If installing to the database server, select Primary. 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, First Time Wizard displays automatically. The First Time Startup Wizard is a collection of wizards that help you set up the important features of Backup Exec, including media sets, overwrite protection settings, devices, and logon accounts. You must complete the applicable sections of this wizard as it guides you in preparing Backup Exec for operations.The Media Overwrite Protection Wizard only appears on the database server. Setting the desired Media Overwrite Protection Level is important since the media is shared throughout the SAN. Note When uninstalling Backup Exec, you must uninstall from the secondary servers before uninstalling from the primary server. For more information about uninstall procedures, see Uninstalling Backup Exec on page 66. See also: VERITAS Backup Exec - Remote Agent on page 821 Starting Backup Exec on page 74 Scheduling and Viewing Jobs on page 929
Shared Storage
915
About Devices in the Shared Storage Environment

At startup, Backup Exec recognizes all local storage devices as well as the storage devices on the SAN. If you do not see one or more of your attached storage devices or if the shared storage devices do not appear when Devices is selected from the navigation bar, click Tools, point to Wizards, and then click 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 the fibre channel loop or 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 (see VERITAS Backup Exec - Library Expansion Option on page 1143). 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.
Note Cascaded drive pools, in which multiple drives are linked together to create the appearance of one drive with greater capacity, are not recommended for shared storage environments. See also: Using Drive Pools with the SAN Shared Storage Option on page 920 Using Device Operations with the SAN Shared Storage Option on page 921
916
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) 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.
View of Storage Devices on the SAN
Default drive pool for local server Shared devices Locally attached drive Default drive pool for server in SAN Shared devices
Stand-alone drive Robotic library Robotic library drives
Shared Storage
917
You can also run the Device Summary report to monitor drives in the SAN Shared Storage Option. Drive properties for shared devices can be viewed following steps described in Viewing and Using Drive Properties and Statistics on page 116. 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. See also: Device Summary Report on page 519 Viewing Drive Configuration Properties on page 119
918
Viewing Media in the Shared Storage Environment

If you select a drive or select Slots from the Devices view, information for the media contained in the drive or slot appears in the right pane. This information also appears when All Media is selected from the Media view. For more information about viewing media, see Viewing Media Information on page 92. Media List
See also: Using Drive Pools with the SAN Shared Storage Option on page 920 Using Device Operations with the SAN Shared Storage Option on page 921 Scheduling and Viewing Jobs on page 929
Shared Storage
919
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. VERITAS recommends creating a shared storage drive pool, which contains only shared devices. For the steps to creating a drive pool, see Creating Drive Pools on page 97. 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. See also: Managing Devices on page 89 Creating Drive Pools on page 97
920
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. See also: Managing Devices on page 89 Scheduling and Viewing Jobs on page 929 About Devices in the Shared Storage Environment on page 916 Sharing Media on page 931
Renaming Robotic Libraries and Drives

You cannot rename a server, but you can rename robotic libraries and drives to make them more easily identified. 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. See also: Pausing, Resuming, and Renaming Devices on page 94
Shared Storage
921
Sharing Robotic Libraries Between Backup Exec for NetWare and Backup Exec for Windows Servers
Backup Exec for NetWare 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 on the robotic libraries for use with Backup Exec for Windows Servers. Then you can create additional partitions on the same robotic libraries for use with Backup Exec for NetWare. With robotic library sharing you have to perform all utility jobs, such as Erase, Import/Export, and Cleaning, with Backup Exec for Windows Servers. If you have purchased and installed VERITAS ExecView you can monitor both the NetWare and Windows servers from one console. Otherwise, you can view NetWare servers from a NetWare console and Windows servers from a Windows console. If a Backup Exec for NetWare job is targeted to a drive being used for a Backup Exec for Windows Servers job, the drive appears as reserved. See also: Viewing Devices on page 90 Library Sharing Prerequisites on page 922 Configuring Media Servers for Robotic Library Sharing on page 923
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 version 8.5 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 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 Library Expansion Option.
Note The drive licenses you purchase for your robotic library are not platform-specific for this implementation. For example, if you are planning on sharing a ten-drive robotic library, you can purchase nine Backup Exec for Windows Servers or Backup Exec for NetWare drive licenses (the first drive in a robotic library does not require a Library Expansion Option license).
922
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. You also should have complete access to hardware and the ability to restart media servers. 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 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 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 9.0 on any of the media servers that will be sharing the library, all Backup Exec for NetWare media servers in the shared storage environment must be installed in the same media handling mode.
To configure Backup Exec for Windows Servers for robotic library sharing: 1. At the Windows server where the SAN Shared Storage Option is installed, start the Backup Exec administration console. 2. Click Devices. The tree pane contains a list of any fibre-attached or locally-attached devices. 3. Select the robotic library you want to share. 4. Under Robotic Library Tasks in the task pane, select Configure partitions. 5. Set up your partitions following the steps provided in Creating Robotic Library Partitions on page 140. 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.
Shared Storage
923
7.
Delete the drive to ensure no jobs run to the unused partition.
8. Repeat steps 6 and 7 for all drives in the unused partition. 9. If you are using Backup Exec for NetWare 8.5, for each drive connected to the shared robotic library, set the block size to 32K: Note Backup Exec for NetWare 8.5 does not support writing tapes higher than 32K block size. Some higher performance devices (such as DLT drives) support block sizes of 64K or higher. If you mix up your tapes and try to read a Backup Exec for Windows NT tape written with the 64K block size in Backup Exec for NetWare 8.5 it will appear empty and could be overwritten, resulting in data loss. Therefore, you should set the block size to 32K. This change only needs to be made at the Backup Exec for Windows NT database server. This restriction does not apply if using Backup Exec for NetWare 9.0. a. From the Devices tree pane, right-click a drive included in the partition you will be using, and select Properties. b. From the Configuration tab, check the block size. If it is larger than 32K, change it to 32K, and then click OK to save. c. If you are sharing more than one robotic library, repeat steps a through b for each robotic library. 10. Reboot all other Windows servers and make sure you can see the shared robotic library on each server. Note No fibre activity or backup jobs should be run until all Backup Exec for Windows Servers and all Backup Exec for NetWare servers are configured for robotic library sharing.
To configure Backup Exec for NetWare 8.5 for robotic library sharing: 1. At the Primary Group Server, open the Job Manager. Note Backup Exec for NetWare does not dynamically set 0-based robotic libraries at startup. If you are unsure whether your robotic library is 0-based, go to the Backup Exec for Windows NT Administration Console and look at the properties for the robotic library. It is critical that the robotic library is set the same way in both NT and NetWare so you do not overlap slots between the NetWare and Windows NT partitions.
924
2. If you are running a 0-based robotic library: a. Press <Ctrl + O> to display the Options menu. b. Select Hardware. c. Select Robotic Library Options. d. From the Robotic Library dialog, highlight any 0-based robotic libraries with the <Spacebar> and press <F2> to save your selections. 3. From the Options menu, select Partition Management, and then select Define/Maintain Partitions. 4. Press <Del> to delete existing partitions. 5. To create partitions for Backup Exec for NetWare: a. From the Options menu, select Partition Management, and then select Define/Maintain Partitions to create a partition to be used by Backup Exec for NetWare. b. Press <Ins> to create a new partition. c. From the screen listing the available robotic libraries, move the selection arrows next to a drive that you want to include in the partition, and then press <F2>. d. From the Partition Description window, select the starting slot and enter the total number of slots that will be in this partition. e. Repeat steps a and b for each partition in the shared robotic library that will be used by Backup Exec for NetWare. 6. If you plan to share more than one robotic library, repeat the above steps for each robotic library. 7. Restart Backup Exec for NetWare on the group servers and make sure you can see the shared robotic library on each server.
Shared Storage
925
To configure Backup Exec for NetWare 9.x running in the partition management mode: 1. From the Administration Console, ensure you are connected to the Primary Group Server and that you are running in partition management mode. From the Administration Console for NetWare at the Primary Group Server, ensure you are running in partition management mode. 2. Delete existing partitions. To delete a partition from the Administration Console: a. Click Drives. b. Click Partitions. c. Right-click the partition you want to delete, and click Delete. d. When prompted, click OK. e. Repeat step 3 and step 4 for each partition you want to delete. To delete a partition from the Administration Console for NetWare: a. Select Drives. b. Select Partitions. c. Select the partition you want to delete, and press <Del>. d. When prompted, press <Y>. e. Repeat step 3 and step 4 for each partition you want to delete. 3. Create the partitions in the shared library to be used by Backup Exec for NetWare. To create a partition from the Administration Console: a. From the Administration Console, click Drives. b. Right-click Partitions. c. Click New Partition.
926
d. Enter options on the New Partition dialog box. e. Click OK. 4. Enter options in the New Partition General dialog box. 5. Enter options in the New Partition Configuration dialog box. 6. Click OK. To create a partition from the Administration Console for NetWare: a. From the Administration Console for NetWare, select Drives. b. Select Partitions. c. Press <Ins>. d. Select a drive to be included in this partition. e. The General dialog box option appears. f. Ensure Configuration is selected, and press <Enter> to view or edit options on the Configuration dialog box.
g. Press <F2> to return to the General dialog box. h. Select Advanced Configuration and then press <Enter> to view or edit options on the Advanced Configuration dialog box. i. j. Press <F2> to return to the General dialog box. Press <F2>.
7. If you plan to share more than one library, repeat step 2 and step 3 for each library that will be shared. 8. Restart Backup Exec for NetWare on the group servers and make sure you can see the shared library on each server.
Shared Storage
927
To configure Backup Exec for NetWare 9.x running in the media management mode: 1. From the Administration Console, ensure you are connected to the Primary Group Server and that you are running in media management mode. From the Administration Console for NetWare at the Primary Group Server, ensure you are running in media management mode. 2. Select Drives. 3. Select Drive Pools. 4. Select All Drives. 5. From the Administration Console, right-click the robot you want to share, and then click Properties. From the Administration Console for NetWare, select the robot you want to share, and press <F4>. 6. Select Configuration. 7. Enter the starting slot and number of slots to be used by NetWare servers. 8. From the Administration Console, click OK. From the Administration Console for NetWare, press <F2>. 9. Restart Backup Exec for NetWare on the group servers and make sure you can see the shared library on each server. See also: VERITAS Backup Exec - Library Expansion Option on page 1143
928
Scheduling and Viewing Jobs

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. (ExecView does provide a central view of all servers on the SAN. For more information, refer to ExecView Administrators Guide on the installation CD.)
View of current jobs
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.
Shared Storage
929
With the SAN Shared Storage Option enabled, all of the media servers share access to the storage devices through the shared ADAMM database. The server that reserves the storage device first runs its job first. Therefore, a job scheduled by a server may not run exactly when scheduled if all the storage devices are being used by other servers. When a server releases control of a device, there is a short delay before the server looks for additional jobs to process. This delay provides a window of opportunity for other media servers to reserve the shared storage device. If a device fails during a nonrecurring job, that job will fail and will be rescheduled on hold. If a device fails during a recurring job, the job is rescheduled. The device is then released for the next job scheduled for that device. But, depending on why the device failed, the second job may become trapped. This might prevent other jobs from seeing the device, running to normal completion, or failing and being rescheduled to an "on hold" status. If you determine that a device is malfunctioning, you may want to retarget jobs to another drive or quickly replace the failed drive and resume the jobs that were placed on hold. See also: Backing Up Data on page 233 Restoring Data on page 395 Monitoring Jobs on page 365 Viewing Completed Jobs on page 378
930
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. See also: Media Sets on page 226
Cataloging Media in SAN SSO Environments

The SAN Shared Storage Option uses a shared catalog database. A tape that has already been cataloged can be physically moved from one device to another and will not have to be recataloged. If the primary server is not available over the network when a secondary server generates catalog information, the information is stored temporarily on the secondary server until automatic catalog synchronization occurs. Because catalogs are shared, information can be restored using any server that has access to a device where the tape resides. If the tape resided in a shared device, or in a local device on the server where you want to perform the restore, simply start a restore job. Otherwise, you have to move the tape into a drive that is accessible. See also: Cataloging Media in a Drive on page 397
Shared Storage
931
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 Rotation Wizard in a shared storage environment, you must use one of the following strategies:

Restrict use of the Media Rotation Wizard to a single media server. Use the same Overwrite Protection Periods and the same full backup day whenever you use the Media Rotation Wizard on all media servers in the shared storage environment. Edit the jobs and rename the media sets created by each Media Rotation Wizard used so the jobs and media sets are server-centric.
See also: Scheduling and Viewing Jobs on page 929
932
Designating a New Database Server and Setting Up Servers
Designating a New Database Server and Setting Up Servers

You can change the SAN Shared Storage Option configuration through Backup Exec Utility (BEUTILITY.EXE). This utility allows you to assign a new database server and attach media servers to or disconnect then from the database server. You may wish to replace the database server for several reasons, including:

A newer, faster server has become available. The database server has stopped functioning.
If the current database server is functioning, you should consider specifying the current database server when installing SAN Shared Storage Option to the new system. This will allow you to test the fibre connections before designating a new database server. If the current database server is not functioning, installing the new system as the database server is recommended. For steps on designating a new database server, see Running Backup Exec Utility SAN SSO Tasks on page 804.
Starting and Stopping Backup Exec Services on Multiple Servers

Stopping Backup Exec services is the first step in system maintenance. After system maintenance, you can start the services again. You can start and stop services at the same time, called "bouncing", which refreshes the database, re-establishes connections, and forces the system back into synchronization. It is similar to rebooting all the servers. For steps for starting and stopping servers, refer to Starting and Stopping Backup Exec Services on page 65 and Running Backup Exec Utility Services Tasks on page 798.
Shared Storage
933
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. See also: Checklist for Troubleshooting Devices That Have Gone Offline on page 934 Replacing a Fibre to SCSI Bridge on page 936 Replacing the Hub or Switch on page 937
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. Note Before you begin troubleshooting, verify that your devices are on the Backup Exec supported device list, which is located at www.support.veritas.com/info/sso.htm. 1. On the navigation bar, click Devices. 2. Verify the device is marked as offline in the tree pane. 3. Select the device. 4. Under General Tasks in the task pane, select Properties. 5. Click Configuration. 6. Clear the Enable this device field. 7. Click Apply. 8. Select the Enable this device field. 9. Click OK.
10. As a test, run a short backup job targeted to the device that was offline. 11. If the device is still marked as offline, verify that the operating system recognizes the device: For Windows 2000 and Windows .NET - From Computer Management, select Device Manager. For Windows NT - From the Windows Control Panel, select SCSI Devices.
12. Does the operating system recognize the device? If yes: Restart Backup Exec services. If no: There is a SAN connectivity problem.
13. If restarting the Backup Exec services did not resolve the problem, reboot the server. 14. If the operating system consistently sees the device, but Backup Exec fails to see it consistently and you are sure that the device is on the supported device list, then there may be a high error rate on the SAN that prevents communication. See also: SAN Hardware Tips on page 935
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. The proper device drivers might not be installed. To verify that the proper device drivers were installed: a. Run Tapeinst.exe The default location is C:\Program Files\VERITAS\Backup Exec\NT. b. Select Uninstall all device drivers. c. Reboot the server. d. Run Tapeinst.exe again.
Shared Storage
e. Select Install all device drivers. f. Reboot the server again.

935
2. Many problems in a SAN environment are caused by SCSI issues. Apply normal SCSI troubleshooting techniques at the fibre to SCSI bridge. Use the bridge administration tool to verify that the bridge can see all of the devices. 3. There may be a bad GBIC on the SAN. Replace the GBIC in the path between the server and the storage device, or contact your SAN hardware vendor. 4. SCSI error 9 or 11 in the system event log indicates faulty hardware or an incorrect version of a driver is installed. If you have verified that the driver is on the supported driver list, contact your hardware vendor. 5. Frequent events 32770 (Adamm Service Error: Write operation forced success! or Adamm Service Error: Read operation retry!) in the application event log indicate a faulty SAN component. Contact your hardware vendor.
Replacing a Fibre to SCSI Bridge

If the fibre to SCSI bridge is replaced, you should manually open and close each job definition after replacement to ensure that jobs already submitted will run. If the new fibre to SCSI bridge changes the SCSI addressing of the devices connected to the bridge (for example, if it is a different model), you must reboot all SAN SSO servers so that Windows NT/2000 will recognize the devices at their new locations. The SCSI bridge has an on-board SCSI host adapter. The firmware in the SCSI bridge may not be compatible with your tape drive. Please consult the SCSI bridge vendor for a list of supported tape devices. The choice of your fibre channel host adapter may also affect which tape drives will work.
To replace a fibre to SCSI bridge: 1. If jobs are running, let the jobs complete and place all other jobs on hold. 2. Stop Backup Exec services on all media servers. 3. Power down the bridge and all SCSI devices connected to the bridge.
4. Replace the bridge. 5. Power up all devices connected to the bridge.
936
6. Power up the bridge. 7. Start Backup Exec services on all media servers. See also: Starting and Stopping Backup Exec Services on Multiple Servers on page 933 Starting and Stopping Backup Exec Services on page 65
Replacing the Hub or Switch

There is no configuration required when a hub or switch is replaced. Once the replacement is completed and Backup Exec is resumed, any jobs scheduled will process.
To replace the hub or switch: 1. If jobs are running, let the jobs complete and place all other jobs on hold. 2. Stop all Backup Exec services on all of the servers. 3. Power down all bridge devices. 4. Power down the hub or switch. 5. Replace the hub or switch. 6. Power up the hub or switch. 7. Power up all bridge devices. 8. Start the Backup Exec services on all of the servers. See also: Starting and Stopping Backup Exec Services on Multiple Servers on page 933
Shared Storage
937
938
image Option
VERITAS Backup Exec for Windows Servers - ServerFree Option and Intelligent Image Option
This section guides you through the use of both the Backup Exec for Windows Servers ServerFree Option and the Backup Exec for Windows Servers Intelligent Image Option. See also: The ServerFree Option on page 939 The Intelligent Image Option on page 948
The ServerFree Option

The VERITAS Backup Exec for Windows Servers ServerFree Option is installed as a separate, add-on component of Backup Exec for Windows Servers. The ServerFree Option enables you to increase backup performance by freeing up media server processor resources and moving the backup processing operations to hardware solutions that may be installed in your storage area network environment. Note ServerFree backup operations on remote resources outside the SAN are not supported. ServerFree backups can only be run on the media server.
Understanding ServerFree Backup Technology

The ServerFree Option is designed to move data from a source such as a fibre disk array, to a target such as a SAN attached tape library, with minimal involvement from the media server. The actual process of moving data from the fibre channel disk array to the target backup device is done by hardware, which acts as a data mover, and is typically found in a Fibre-to-SCSI bridge or router. However, the data mover could actually reside in any hardware component in the SAN; its actual location is determined by the SAN hardware manufacturer.
939
Traditional backup operations (both SAN and direct attached) involve reading the data from the SANs disk array into the Backup Exec media servers memory. The backup data is processed and then sent across the SAN to the target backup device. This type of backup operation is heavily dependent on both the CPU and memory in the Backup Exec media server.
Traditional SAN backup operation without using the ServerFree Option Network
Backup Exec for Windows Servers
Fibre-to-SCSI bridge or router
Da
ta
Flo w
Fibre Channel Switch and attached disk array storage
SAN-attached target backup device
Backup operations from the disk array to the SAN-attached target backup device use media server CPU and memory cycles to process the backup operation. As such, engaging the media server during backup operations results in a decrease in media server performance.
Unlike traditional SAN backup operations, the VERITAS ServerFree Option keeps the use of Backup Exec media server CPU and memory resources to a minimum during the backup operation, thus enhancing performance. Using the ServerFree Option, the majority of the processing done by the Backup Exec media server is completed at the beginning of the backup operation. The actual process of moving data from the fibre
image Option
channel disk array to the target backup device is done by the Fibre-to-SCSI bridge or router, where the data mover is located. By using the ServerFree Option, along with the Fibre-to-SCSI bridge or router (data mover), Backup Exec media server processing is kept to a minimum. The media server is now free to use its processing power for other business operations.
SAN backup operations using the ServerFree Option Network
Minimal media server CPU cycles used during the backup operation Fibre-to-SCSI bridge or router Data mover operations occur in the Fibre-to-SCSI bridge or router
Fibre Channel Switch and attached disk array storage
Data Flow
SAN-attached target backup device Volume snapshot
Using the ServerFree Option, backup operations use minimal media server CPU cycles when backups are running. By essentially bypassing the media server, backup performance is enhanced, while also freeing the media servers processing resources for other important applications.
Appendix E, VERITAS Backup Exec for Windows Servers - ServerFree Option and Intelligent Image
ServerFree Backup Configuration

The ServerFree Option works in conjunction with other VERITAS high performance options including the SAN Shared Storage Option (SSO), Intelligent Image Option (IIO) and a snapshot provider such as the VERITAS Volume Snapshot Provider. By first creating a snapshot (a point in time view of the data) and then sending it directly to the storage device (through the data mover), backup operations and backup windows are optimized.
Required Components
If any of the following requirements are not met, the ServerFree backup job you have configured will run as an Intelligent Image Option backup job. If Intelligent Image Option is not available, a standard backup job will run. After the backup job completes, the Backup Exec job log will indicate what backup option was used. Hardware In order to benefit from ServerFree Option technology, you must have certified SAN hardware that supports data moving operations. This support is provided by SAN hardware manufacturers. Contact your hardware vendor for a complete list of required and supported components that support data moving operations. VERITAS Software will certify new ServerFree-supported SAN solutions as they become available. For more information on whether your hardware vendor supports this technology, and for a complete list of requirements, please contact the hardware vendor directly. You can also contact VERITAS Software by going to www.support.veritas.com/dsl for information regarding tested solutions. If you presently have storage area network hardware in place, you may need to update both the SANs hardware software drivers or firmware in order to use the ServerFree Option. Hardware components that may require updating include:

Fibre channel host bus adapter (HBA) Fibre-to-SCSI bridge or router Fibre channel disk array Fibre channel switch
942
image Option
Software To install the ServerFree Option on a media server, you need to purchase the following VERITAS Software products:

Backup Exec for Windows Servers SAN Shared Storage Option ServerFree Option (includes the Advanced Open File Option and the Intelligent Image Option)
Note ServerFree Option by default, uses the included VERITAS Volume Snapshot Provider from the Advanced Open File Option, to create a snapshot or frozen image of the volume on the fibre disk array. Alternatively, VERITAS Volume Manager, along with its separately purchased FlashSnap Option can be used to create the point in time snapshot of the volume on the fibre disk array.

(Optional) VERITAS Volume Manager and the Volume Manager FlashSnap Option One license key for each of the above items for each Backup Exec media server in your SAN. See your Backup Exec for Windows Servers Administrators Guide for more information on these options and how to install them.
See also: Installing Backup Exec Options on a Local Server on page 49 Supported Operating Systems for the media server

Windows NT 4.0 SP 6a Windows 2000
Note Consult your hardware documentation for Windows XP and Windows.NET compatibility.
Supported VERITAS Backup Exec Agents and Options The ServerFree Option works with the following:

VERITAS Backup Exec for Windows Servers Agent for Microsoft SQL Server Microsoft Windows NTFS file systems
Other agents and options may be supported in future releases of the ServerFree Option.
The ServerFree Option ServerFree Backup Component Configuration Network
Fibre channel host bus adapter (HBA)
- Backup Exec for Windows Servers - VERITAS SAN Shared Storage Option - VERITAS ServerFree Option - Windows 2000 or Windows NT 4 SP 6a - (optional) VERITAS Volume Manager and the Volume Manager FlashSnap Option
Fibre-to-SCSI bridge or router
Fibre Channel Switch with attached fibre channel storage disk array
SAN-attached target backup device
Installing the ServerFree option

To install the ServerFree Option, see Installing Backup Exec Options on a Local Server on page 49. Note The SAN Shared Storage Option must be installed on the media server before you can install the ServerFree Option.
944
image Option
Running the ServerFree Option

Note ServerFree backup operations on remote resources outside the SAN are not supported. ServerFree backups can only be run on the media server.
To set the ServerFree Option for a single backup job: 1. On the navigation bar, click Backup. 2. In the Backup Selections pane, select data to be backed up. Note Only fibre disk arrays that are connected to the same data path as the data mover on the SAN will use ServerFree Option technology for the backup operation. 3. On the Properties pane, under Settings, click Advanced Open File. 4. Select Use Advanced Open File Option. 5. Under Open file configuration, select a snapshot method. Note The ServerFree Option uses the VERITAS Volume Snapshot Provider by default. Note Microsoft Volume Shadow Copy Service cannot be used in a ServerFree backup job configuration. Note The VERITAS Volume Manager FlashSnap Option is compatible with Windows 2000 only. The volumes you want to use with the FlashSnap Option must first be snap-started through VERITAS Volume Manager, using the VERITAS Enterprise Administrator (VEA). For more information, see Snap Starting a VERITAS Volume Manager Volume on page 969. 6. Select Use Intelligent Image Option. 7. Select Use ServerFree Option. Start the backup job or select other options from the Properties pane.
To set the ServerFree Option as the default for all backup jobs: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Advanced Open File. 3. Select Use Advanced Open File Option. 4. Under Open file configuration, select a snapshot method. Note The ServerFree Option uses the VERITAS Volume Snapshot Provider by default. Note Microsoft Volume Shadow Copy Service cannot be used in a ServerFree backup job configuration. Note The VERITAS Volume Manager FlashSnap Option is compatible with Windows 2000 only. The volumes you want to use with the FlashSnap Option must first be snap-started through VERITAS Volume Manager, using the VERITAS Enterprise Administrator (VEA). For more information, see Snap Starting a VERITAS Volume Manager Volume on page 969. 5. Select Use Intelligent Image Option. 6. Select Use ServerFree Option.
946
image Option
Restoring A ServerFree Backup

ServerFree restore jobs are done in the same manner as an Intelligent Image Option restore job in Backup Exec. Note Unlike a ServerFree backup operation, a ServerFree restore job does not use the data mover during the restore operation. As a result, the Backup Exec media servers resources are used to process the job. Caution Because the ServerFree option uses the Intelligent Image Option, canceling a ServerFree 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 successfully completes. See also: Restoring Data on page 395 The Intelligent Image Option on page 948 Restoring Files From An Intelligent Image Backup on page 954
The Intelligent Image Option

The VERITAS Backup Exec for Windows Servers Intelligent Image Option is installed as a separate, add-on component of Backup Exec for Windows Servers. It also includes the VERITAS Advanced Open File Option. The Intelligent Image Option provides fast backup performance with less CPU processing by separately backing up all of the information about the files themselves (meta data), and then backing up all the data in the files as one image. Unlike some backups that use raw image solutions, the Intelligent Image Option does not back up unused and temporary-usage space. The decrease in the overall volume of the backup increases the speed of the backup. The Intelligent Image Option enables you to:

Back up and restore open files. Back up encrypted files using non-image methods in the same job in which the image method is used for other files. Use all Backup Exec devices, including Backup Folders (in the Backup-to-disk feature). Restore individual files or entire volumes. Make single-pass restores of multiple individual files. Restore compressed and non-compressed files. Restore using Intelligent Disaster Recovery (IDR).
Note While Backup Execs image technology can result in a high-performance backup operation, performance gains may not be apparent without a high-performance backup tape device. The Intelligent Image Option can also be run from the Command Line Applet. See also: Using the Command Line Applet on page 593 Requirements for the Intelligent Image Option on page 949 Installing the Intelligent Image Option on page 949 The ServerFree Option on page 939 Understanding the Advanced Open File Option on page 955
948
image Option
Requirements for the Intelligent Image Option

Following are requirements for using Backup Execs Intelligent Image Option:

The VERITAS Advanced Open File Option must be selected when configuring your backup job in order to use the Intelligent Image Option during backup operations. Volumes selected for backup using the Intelligent Image Option must also meet the requirements for using Advanced Open File Option.
See also: The Intelligent Image Option on page 948 Requirements for Using the Advanced Open File Option on page 958 Installing the Advanced Open File Option on page 959 Changing the Advanced Open File Option Default Settings on page 962
Installing the Intelligent Image Option

The Intelligent Image Option is installed as a separate add on component of Backup Exec for Windows Servers. To create a backup job as an image, you must purchase and install both the Advanced Open File Option and the Intelligent Image Option. Whenever the Intelligent Image Option is installed on the media server, the Backup Exec Remote Agent is included as part of the IIO installation. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server that you want to back up. You cannot select resources from a remote server for backup until a Remote Agent has been installed. If you are installing the Intelligent Image Option locally to protect the media servers data, you are entitled to move the Remote Agent that was included with the Intelligent Image Option installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the Intelligent Image Option is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to move it to another Windows server. To install the Intelligent Image Option on the local server, see Installing Backup Exec Options on a Local Server on page 49; to install it on a remote server, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. For instructions on moving the Remote Agent to another Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
Selecting the Intelligent Image Option for a Single Backup Job

Use the Intelligent Image Option for specific backup jobs, or set it as the default to be used for every backup job. If the volume selected for backup does not meet the requirements for using the image option, then a non-image backup is performed on the selected files instead. The job log will report that the Intelligent Image Option was not available and that a non-image backup was performed for the selected files.
To set the Intelligent Image Option for a single backup job: 1. On the navigation bar, click Backup. 2. In the Backup Selections pane, select data to be backed up. 3. On the Properties pane, under Settings, click Advanced Open File. 4. Select Use Advanced Open File Option. 5. Select Use Intelligent Image Option. 6. Start the backup job or select other options from the Properties pane. See also: Understanding the Advanced Open File Option on page 955 Setting Advanced Open File Option as the Default Setting for All Backup Jobs on page 966 Requirements for Using the Advanced Open File Option on page 958 Checking the Job Log When Using the Advanced Open File Option on page 968 Selecting the Image Option as the Default for All Backup Jobs on page 951
950
image Option
Selecting the Image Option as the Default for All Backup Jobs
You can set the Use Intelligent Image Option as the default to be used for every backup job. If the volume selected for backup does not meet the requirements for using the image option, then a non-image backup is performed on the selected files instead. The job log will report that the image option was not available and that a non-image backup was performed for the selected files.
To set the image option as the default: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Advanced Open File. 3. Select Use Advanced Open File Option. 4. Select the option Use Intelligent Image Option and if applicable, Use ServerFree Option. 5. Click OK. All backup jobs now default to using the Intelligent Image Option if it is available. See also: Checking the Job Log When Using the Advanced Open File Option on page 968 Requirements for Using the Advanced Open File Option on page 958 Selecting the Intelligent Image Option for a Single Backup Job on page 950
Checking the Job Log When Using An Image

Information about the image backup is displayed in the job log. Files backed up using the image option display an I after the file name. Following is an excerpt from a job log for a backup job using the image option. The job log was set to include summary information, directories, files, and file details. ================================================================= Job server: PUBS
Job name: Backup 0009 Job started: Wednesday, February 21, 2001 at 10:27:47 AM Job type: Backup Job Log: BEX15.txt ===================================================================== No appendable media could be mounted. Switching to overwrite operation on scratch media. Drive and media information from media mount: Robotic Library Name: SONY 1 Drive Name: SONY 1 Slot: 1 Media GUID: {EACA03E2-5D49-4CCC-95D7-D8E8145AB729} Media Label: 4MM000001 Overwrite Protection Time Left: 1 HOUR Append Time Left: 1 HOUR Targeted Media Set Name: Media Set 1 ===================================================================== Job Operation - Backup Media operation - overwrite. Hardware compression enabled. ===================================================================== Intelligent Image initialization successful. OFO: Started for device: "C:"
Media Name: "Media created 2/21/2001 10:27:47 AM" Backup of "C: " Backup set #1 on storage media #1 Backup set description: "Backup 0009" Backup Type: FULL - Back Up Files - Reset Archive Bit Backup started on 2/21/2001 at 10:37:37 AM. Directory \
952
image Option
Directory \Documents and Settings Directory \Documents and Settings\Administrator NTUSER.DAT <HA> 192512 2/21/2001 10:23 AM ntuser.dat.LOG <HA>I 1024 2/21/2001 10:23 AM ntuser.ini <HS>I 180 2/15/2001 9:51 AM ... Directory \Documents and Settings\snewman\Start Menu\Programs\Administrative Tools Directory \Documents and Settings\snewman\Start Menu\Programs\Startup Directory \Documents and Settings\snewman\Templates wordpfct.wpg <>I 57 12/7/1999 8:00 AM wordpfct.wpd <>I 30 12/7/1999 8:00 AM winword2.doc <>I 1769 12/7/1999 8:00 AM winword.doc <>I 4608 12/7/1999 8:00 AM sndrec.wav <>I 58 12/7/1999 8:00 AM quattro.wb2 <>I 4017 12/7/1999 8:00 AM presenta.shw <>I 461 12/7/1999 8:00 AM powerpnt.ppt <>I 12288 12/7/1999 8:00 AM amipro.sam <>I 4570 12/7/1999 8:00 AM excel.xls <>I 5632 12/7/1999 8:00 AM excel4.xls <>I 1518 12/7/1999 8:00 AM lotus.wk4 <>I 2448 12/7/1999 8:00 AM Verify completed on 2/21/2001 at 10:38:34 AM. Verified 335 files in 180 directories. 0 files were different. Processed 31,086,774 bytes in 14 seconds. Throughput rate: 127.1 MB/min --------------------------------------------------------------------===================================================================== Job ended: Wednesday, February 21, 2001 at 10:38:34 AM Job completion status: Successful =====================================================================
See also: Restoring Files From An Intelligent Image Backup on page 954
Restoring Files From An Intelligent Image Backup

Restoring files from an image backup job uses the same process as any other restore operation. Backup sets created using the image option are displayed in the Restore Selections pane with an icon showing a lightning bolt imposed on an aqua camera.
IIO icon
Caution Canceling an image option 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.
954
Open File Option
VERITAS Backup Exec for Windows Servers - Advanced Open File Option
The VERITAS Backup Exec for Windows Servers - Advanced Open File Option (AOFO) is installed as a separate, add-on component of Backup Exec for Windows Servers. The Advanced Open File Option uses advanced open file and image technologies designed to alleviate issues that are sometimes encountered during backup operations, such as protecting open files and managing shortened backup windows. See also: Understanding the Advanced Open File Option on page 955 Selecting the Advanced Open File Option for a Single Backup Job on page 964 Setting Advanced Open File Option as the Default Setting for All Backup Jobs on page 966 The Intelligent Image Option on page 948 The ServerFree Option on page 939
Understanding the Advanced Open File Option

When a job is submitted for backup with the Advanced Open File Option selected, a virtual point-in-time view of each volume is created. Original data is buffered on the static volume when changes are made to the files during a backup. Buffered data is then backed up, not the changed data. If the files selected for backup reside on more than one volume, Backup Exec creates a static volume for each volume containing data to be backed up. For example, if the data to be backed up resides on a single volume, a single static volume is created. If you have data residing on four volumes, four static volumes are created. After the selected files have been backed up, the static volumes are deleted. Backup Exec automatically calculates the sizes of the static volumes needed for the backup, as well as the location of the static volumes, or you can use the Advanced Open File Option wizard to enter specific values for the size and location of the static volume. However, if the amount of data that you have selected to back up is significantly less (30%) than the total amount of data on the volume, the backup may run faster if you use the Advanced Open File Option wizard to decrease the size of the static volumes, rather
955
than letting Backup Exec automatically calculate them. Use caution when you manually enter specific sizes for the static volumes since those sizes are used regardless of the sizes of the volumes being backed up. If you dont allocate enough space, the job could fail. By creating and backing up a snapshot view of the files on a volume, the Advanced Open File Option can back up files even as they are being changed. Note The recommended method for protecting databases is to use Backup Exec database agents. 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. You can also use the Advanced Open File Option on the same volume as a database to provide open file support for other applications. The Advanced Open File Option provides generic protection for data that is not supported by Backup Exec agents.
Snapshot Support
When creating a snapshot of a volume, Backup Exec uses advanced snapshot technologies to momentarily suspend write activity to a hard drive so that a point in time, or snapshot of a volume can be created. After creating a snapshot, the data can then be backed up. Note To use snapshot technologies with Backup Exec, you must first purchase the Advanced Open File Option. Backup Exec supports multiple snapshot technologies, which are found in the following options:

VERITAS Advanced Open File Option using the VERITAS Volume Snapshot Provider VERITAS Volume Manager FlashSnap Option Microsoft Volume Shadow Copy Service. Operating system vendors, as well as other third party software vendors often provide additional technologies that work in conjunction with the Microsoft Volume Shadow Copy Service. These technologies, called Writers, are used to close any open files residing in the computers memory before the Microsoft Volume Shadow Copy Service makes a snapshot of the volume to be backed up. Using a Writer along with the Microsoft Volume Shadow Copy Service ensures a complete backup of your volume.
Note Microsoft Volume Shadow Copy Service is only supported on the Windows XP and Windows.NET platforms.
956
See your software documentation for information about Writers that may be provided by the softwares vendor. After making backup selections and then choosing the Advanced Open File Option, you can increase backup performance by configuring Backup Exec to use the snapshot technologies installed on your systems. Use the following table as a guide.
Open File Option
If you are running: VERITAS Advanced Open File Option
These are the available options: VERITAS Volume Snapshot Provider This is the Backup Exec default, as it is compatible with each of Microsofts operating environments (Windows NT 4.0, Windows 2000, Windows XP or Windows.NET).
VERITAS Volume Manager VERITAS Volume Manager version 3.0, along with Service Pack 1 with mirrored drives in a or greater, along with the FlashSnap Option. Windows 2000 environment Note The volumes you want to use with the FlashSnap Option must only first be snap-started through VERITAS Volume Manager, using the VERITAS Enterprise Administrator (VEA). For more information, see Snap Starting a VERITAS Volume Manager Volume on page 969. Vendor-specific, third party software, along with Windows XP or Windows.NET Microsoft Volume Shadow Copy Service Microsofts Volume Shadow Copy Service technology enables third party hardware and software vendors to create snapshot plugins for use with Microsofts technology.
Appendix F, VERITAS Backup Exec for Windows Servers - Advanced Open File Option
957
Requirements for Using the Advanced Open File Option

The following requirements must be in place in order to use the Advanced Open File Option with any snapshot technology. For remote Windows computers, and the volumes on those systems, you must purchase the Advanced Open File Option for each server or workstation that you want to protect. The media server must have:

Backup Exec for Windows Servers installed Pentium class processor If the Advanced Open File Option is to be used locally, then the media server must also have: Advanced Open File Option installed
The remote computer you want to back up with the Advanced Open File Option must have:

Windows NT 4, Windows 2000, Windows XP or Windows.NET Pentium class processor Advanced Open File Option installed Backup Exec for Window Servers Remote Agent installed (AOFO automatically installs the Remote Agent)
The volumes you want to back up with the Advanced Open File Option must have:

Enough free disk space to start the AOFO operation. Free diskspace should at least equal the size of the backup job in MBs being backed up. An NTFS, FAT32, or FAT file system
Note The Advanced Open File Option cannot be used on CD-ROM, floppy diskettes, or removable media. If you are installing the Advanced Open File Option locally to protect the media servers data, you are entitled to move the Remote Agent that was included with the Advanced Open File Option installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the Advanced Open File Option is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to move it to another Windows server. For instructions on moving the Remote Agent to another Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
Installing the Advanced Open File Option

The Advanced Open File Option is enabled from the Backup Exec server by entering your Advanced Open File Option serial number or numbers.
Open File Option
Installing Advanced Open File Option will install the VERITAS Snapshot Provider only; to use the VERITAS Volume Manager FlashSnap Option, you must purchase VERITAS Volume Manager, along with its FlashSnap Option; for Microsoft Volume Shadow Copy Service, you must be using the Windows XP and Windows.NET platforms. To use snapshot technologies with Backup Exec, you must first purchase the Advanced Open File Option. Caution Backup Exec for Windows Servers will not use older versions of the Open File Option. You must upgrade the Advanced Open File Option by purchasing and re-installing it on the local server and all remote computers on which it currently resides. Note You will need to reboot the computer on which you are installing AOFO after completing the installation. To install the Advanced Open File Option on a local media server, see Installing Backup Exec Options on a Local Server on page 49. To install the Advanced Open File Option on a remote media server, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. Note You can also install and uninstall the Advanced Open File Option on remote servers using the Windows command line. See Installing and Uninstalling the Advanced Open File Option to Remote Windows Servers Using the Command Line on page 960. See also: Upgrading Backup Exec Options on Remote Computers on page 71
959
Installing and Uninstalling the Advanced Open File Option to Remote Windows Servers Using the Command Line
You can also install the Advanced Open File Option using silent mode on a remote server using the Windows command line. Note Silent mode runs the installation operation without the benefit of a user interface.
To install the Advanced Open File Option on a remote server using the Windows command line: 1. Move to a remote server. 2. Map a drive letter to the Backup Exec for Windows Servers media server RANT32 directory using the following path: \Program Files\VERITAS\Backup Exec\NT\Agents\RANT32 3. Open a command prompt and enter the drive letter you mapped in step 2. 4. Run the following command: setup.exe /AOFO: -s Note The -s parameter is used to run the install operation in silent mode, without the benefit of a user interface. The parameter -boot is used to automatically reboot of 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 Advanced Open File Option files are installed on the remote server in the following directory: \Program Files\VERITAS\Backup Exec\RANT 6. The Advanced Open File Option installation log file is installed in \WINNT\bkupinst.log. After the installation finishes, reboot the system at your convenience in order to activate the Advanced Open File Option.
960
To uninstall the Advanced Open File Option from a remote server using the Windows command line: 1. At the remote server, open a command prompt.
Open File Option
2. Change directories to the Advanced Open File Option install directory using the following path: \Program Files\VERITAS\Backup Exec\RANT 3. Run the following command: setup.exe /AOFO: -s -u Note 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 parameter -boot is used to automatically reboot of 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 de-activate the Advanced Open File Option. The Advanced Open File Option is uninstalled from the remote server. After the uninstall finishes, reboot the system at your convenience in order to de-activate the Advanced Open File Option.
Uninstalling the Advanced Open File Option

If you uninstall Backup Exec, the Advanced Open File Option is uninstalled as well. Or, you can choose to remove only the Advanced Open File Option from a computer.
To uninstall the Backup Exec Advanced Open File Option: 1. From the Start menu, point to Settings, then click Control Panel. 2. Double-click Add/Remove Programs. 3. Select VERITAS Backup Exec for Windows Servers, and then click Change/Remove. Under Windows NT, click Add/Remove. 4. Click Additional Options and then click Next. 5. Click Continue on the VERITAS Backup Exec Serial Numbers dialog box.
961
Changing the Advanced Open File Option Default Settings
6. In the Destination pane of the VERITAS Backup Exec Features dialog box, select the computer from which you want to remove the Advanced Open File Option. 7. In the List pane, click the icon preceding the Advanced Open File Option and click This feature will not be available. 8. Click Continue. 9. Click Finish.

Defaults are provided for all the configurable elements in Advanced Open File Option. It is recommended that you allow Backup Exec to automatically calculate the size and location of the static volume for each backup. If you need to change the default settings, use the Advanced Open File Option wizard in the Backup Exec administration console. Note The Advanced Open File Option Wizard only enables you to change the configuration options for the VERITAS Volume Snapshot Provider. Note If the amount of data that you have selected to back up is significantly less (30%) than the total amount of data on the volume, the backup may run faster if you use the Advanced Open File Option Wizard to decrease the size of the static volume, rather than letting Backup Exec calculate it automatically. Use caution when you manually enter a specific size for the static volume 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.
To change the Advanced Open File Option default settings using the Advanced Open File Option Wizard: 1. On the Tools menu, select Wizards, and then click Advanced Open File Option Wizard. 2. Follow the on-screen prompts. When the Static Volume Setting screen appears, you can specify an alternate location for the static volume or volumes. It is highly recommended that you do not change the defaults.
962
3. On the Open File Option Configuration screen, enter new defaults using the following table.
Static Volume Settings for VERITAS Volume Snapshot Provider
Open File Option
Item Have Backup Exec calculate the initial and maximum size of the static volume
Description Enables Backup Exec to automatically calculate the initial and maximum size of the static volume for each backup.
Initial size of the static Sets the initial size of the static volume. volume (1 - 100 percent): If you choose not to use the default, then type the percentage of free space you want Advanced Open File Option to use to create the static volume and for incremental growth of the backup. Increase this percentage if you receive an error message stating that Advanced Open File Option is out of disk space. This increase enables additional free space to be allocated on the volume, which then can be used during the backup. Maximum size that the static volume can grow to: Sets the maximum size of the static volume. If you choose not to use the default, then type the maximum percentage that you allow for the static volume. If the static volume exceeds the percentage indicated, the job will fail and the error will be listed in the job log. Sets the minimum length of quiet time in seconds, in which the application waits for disk inactivity before the static volume is created. Decrease this setting if you have an active system so that the static volume 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. Number of seconds that the application tries to obtain the minimum quiet time, after which the job fails Sets the maximum length of quiet time in which the application waits for disk inactivity before creating the static volume. Increase this setting if a backup fails repeatedly. Increasing this setting maximizes the length of time used to create the static volume. The default is 2,000 seconds.
Number of seconds during which there can be no disk activity before the static volume is created
963
Using the Advanced Open File Option

You can use the Advanced Open File Option for specific backup jobs, or you can set the Advanced Open File Option as the default to be used for every backup job. If the volume selected for backup does not meet the requirements for using the Advanced Open File Option, then other options for backing up open files will apply to the backup. For example, if the option to back up open files with a lock is selected on the Advanced Backup dialog box, that option applies to a backup job if the Advanced Open File Option cannot run on the volume. After each job is completed, check the Job Log to make sure the Advanced Open File Option was used during the backup.
Selecting the Advanced Open File Option for a Single Backup Job
To set the Advanced Open File Option for a single backup job: 1. On the navigation bar, click Backup. 2. Select the data you want to back up from the Backup Selections tree or choose an existing selection list using the Load Selections from Existing List button. 3. On the Properties pane, under Settings, click Advanced Open File. 4. Select Use Advanced Open File Option. Selecting this option activates the Advanced Open File Option for use with the job. Note Backing up files and directories by following junction points is supported only if you are using the Advanced Open File Option on a Windows 2000 volume, and you are using the VERITAS Volume Snapshot Provider.
964
Select the appropriate option from the following:

Advanced Open File options Item Use Advanced Open File Option Open file configuration Automatically select open file technology VERITAS Volume Snapshot Provider Enables Backup Exec to select the best open file technology to use for the type of data being backed up. Backup Execs default open file option technology. It is compatible with each of Microsofts operating environments (Windows NT 4.0, Windows 2000, Windows XP or Windows.NET). VERITAS Volume Manager version 3.0, along with Service Pack 1 or greater, along with the FlashSnap Option. For use with VERITAS Volume Manager in a Windows 2000 environment only. Note The volumes you want to use with the FlashSnap Option must first be snap-started through VERITAS Volume Manager, using the VERITAS Enterprise Administrator (VEA). For more information, see Snap Starting a VERITAS Volume Manager Volume on page 969. Microsoft Volume Shadow Copy Service For use with vendor-specific, third party software, along with Windows XP or Windows.NET Microsofts Volume Shadow Copy Service technology enables third party hardware and software vendors to create snapshot plugins for use with Microsofts technology. Use Intelligent Image Option Used in conjunction with the Advanced Open File Option, this option enables Backup Exec to create a backup job as an image, rather than as a file-by-file backup set. For more information, see The Intelligent Image Option on page 948. Enables Backup Exec to use third party copy support if your storage hardware supports it and you are running in a SAN environment. For more information, see The ServerFree Option on page 939. Description Activates the Advanced Open File Option for use with Backup Exec for Windows Servers.
Open File Option
VERITAS Volume Manager FlashSnap Option
Use ServerFree Option
5. Start the backup job or select other backup options from the Properties pane.
965
6. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then expand the job you want to view. 7. Check the Job Log to make sure the Advanced Open File Option is being used during the backup. See also: Selecting the Advanced Open File Option for a Single Backup Job on page 964 Selecting Data to Back Up on page 259 Using Selection Lists on page 267 Creating a Manual Backup Job by Configuring Job Properties on page 236 Setting Advanced Open File Option as the Default Setting for All Backup Jobs on page 966 Checking the Job Log When Using the Advanced Open File Option on page 968 Advanced Open File Option Error Messages on page 970
Setting Advanced Open File Option as the Default Setting for All Backup Jobs
You can set the Advanced Open File Option as the default to be used for all backup jobs. If the volume selected for backup does not meet the requirements for using the Advanced Open File Option, then any other selected options for backing up open files apply to the backup. For example, if the option to back up open files With a lock has been selected on the Backup Job properties dialog box under the Advanced node, that option will apply to all backup jobs if the Advanced Open File Option cannot run on the volume. Note Jobs saved before the Advanced Open File Option was installed will continue to use the previous settings for backing up open files. In order to use the Advanced Open File Option with these jobs, you must edit the job and select Use Advanced Open File Option.
To set the Advanced Open File Option as the default: 1. On the Tools menu, click Options. 2. Under Settings, click Advanced Open File.
966
Using the Advanced Open File Option Options-Set Application Defaults for Advanced Open File Option
Open File Option
3. Select Use Advanced Open File Option. Selecting this option causes Backup Exec to use the Advanced Open File Option for all backup jobs. Note Remember, the Backup Open Files options (Never; If closed within 30 seconds; With a lock; Without a lock) only apply if the volume selected for backup does not meet the requirements for using the Advanced Open File Option. Note Backing up files and directories by following junction points is supported only if you are using the Advanced Open File Option on a Windows 2000 volume, and you are using the VERITAS Volume Snapshot Provider. 4. Select any other appropriate options, and then click OK. See also: Selecting the Intelligent Image Option for a Single Backup Job on page 950 Checking the Job Log When Using the Advanced Open File Option on page 968 Advanced Open File Option Error Messages on page 970 Setting Default Backup Options on page 312
967
Checking the Job Log When Using the Advanced Open File Option
If a backup completes successfully while using the Advanced Open File Option, information is displayed in the Job Log.
Job Log Example
If the backup included more than one volume, this information is repeated for each volume. If the Advanced Open File Option fails on initialization, the backup still runs but it is marked as failed in the job log. If the Advanced Open File Option fails during the backup of a device, that backup set is terminated and is reported as an error.
968
Snap Starting a VERITAS Volume Manager Volume
Snap Starting a VERITAS Volume Manager Volume
To Snap Start a volume:
Open File Option
1. Start VERITAS Enterprise Administrator (VEA). 2. Expand the Volumes object in the left pane, and then right-click the volume to Snap Start. 3. On the short cut menu, select Snap, and then select Snap Start. 4. On the Snap Start Volume screen, select either Auto select disks or Manually select disks. Note Auto select disks enables Volume Manager to make the disk selection for you, while Manually select disks enables you to make the selection. 5. Click OK to close the Volume Manager. During the Backup Exec backup job, the volume is snapshot (split from the original) in preparation for the backup operation on the local host. These operations are done automatically by the Volume Manager components during the backup job. After the backup job completes, the snapshot is resynchronized to the original volume. Note Snap Starting a volume only needs to be done once. The Snap Start procedure takes a considerable amount of time because it creates a mirror. To make backup selections from the volume, see Selecting Data to Back Up on page 259. Caution 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. For more information, see VERITAS Backup Exec - Agent for Microsoft SQL Server on page 975 and VERITAS Backup Exec - Agent for Microsoft Exchange Server on page 1067.
969
Advanced Open File Option Error Messages
Advanced Open File Option Error Messages

The following table lists common AOFO error messages and their solutions.
Advanced Open File Option error messages Error Message Microsoft Volume Shadow Copy Service error: Bad State Problem This is a VERITAS Volume Snapshot Provider internal error. More details may be available in the Windows Event Log. Solution Restart VERITAS Volume Snapshot Provider and Backup Exec for Windows Servers services. If this fails to solve the issue, the VERITAS Volume Snapshot Provider may need to be re-installed. Install or re-install the snapshot provider. Reboot the computer.
Microsoft Volume Shadow Copy Service error: Snapshot Provider not registered.
Backup Exec for Windows Servers detected that the underlying Snapshot provider is either not installed or is not working.
Microsoft Volume The volume specified by the user is Check the Windows Event Log for Shadow Copy Service not supported for snapshot. details on how to correct the error: problem. Volume not supported for snapshot Microsoft Volume Shadow Copy Service error: Cannot add anymore volumes since the maximum limit has been exceeded. Maximum number of volumes that Split the job so that fewer volumes can be supported by the Microsoft are involved per job. Volume Shadow Copy Service has been reached. The maximum number of volumes supported is 64.
Microsoft Volume Volume is currently locked by some Shadow Copy Service other process and cannot be Error: snapped. Volume is in use. Microsoft Volume Out of disk space during the Shadow Copy Service snapshot. error: Insufficient storage
Check for the process that has locked the file. Either quiescence it or wait until it is done, and then re-submit the job. Make sure that at least one volume has enough space to save the snapshot cache file.
970
Advanced Open File Option Error Messages Advanced Open File Option error messages (continued) Error Message Snapshot ran out of memory Problem This should never been seen. Solution Check the Windows Virtual Page file size and available disk space. You may need to increase both. Check the Windows Event Log for more details. Also check to determine if the volume can be mounted manually. Ensure that the Snapshot version number is one supported by Backup Exec. Check the VERITAS website for compatibility (www.veritas.com). Check the Windows Event Log for more details. Also determine if the volume is locked by another process. You can also verify that the volume can be mounted manually. Either increase the quite time using the Advanced Open File Option wizard, or submit the job when there is less activity on the volume.
Open File Option
Snapshot reports unable to mount
Snapshot open file option or the provider could not mount the volume specified.
Snapshot version error
Snapshot version number is not supported by Backup Exec for Windows Servers.
Snapshot timed out mounting volume
Snapshot exceeded the time limit allowed for mounting a volume.
Snapshot cannot meet minimum quiet time
Snapshot cannot meet the minimum quiet time specified by the user on the target machine. The default is five (5) seconds.
Snapshot unable to read real disk
The snapshot provider indicates Check that the disk is readable. that the real disk could not be read. Make sure that the mount points are valid and browsable. Volume specified for snapshot is not Remove virtual volumes from your a physical volume. Advanced Open job and provide the physical volume File Option does not support virtual name instead. volumes.
Snapshot is not able to create a snapshot of a virtual snap volume
Snapshot not taken The evaluation period has expired You need to either extend the because the for Backup Exec and the Advanced evaluation period or purchase the evaluation period has Open File Option. Advanced Open File Option. expired
971
Advanced Open File Option Error Messages Advanced Open File Option error messages (continued) Error Message Problem Solution There must be enough free disk space on one volume to create the Microsoft Volume Shadow Copy Service cache file.
Microsoft Volume Out of disk space. Shadow Copy Service Snapshot CacheFileBroker was unable to allocate cache files Snapshot job specified has incompatible snapshot types. VERITAS Volume Snapshot Provider and Volume Manager cannot be used for shadow copy backups. The specified backup job includes shadow copy components. These components cannot be snapped using either VERITAS Volume Snapshot Provider and Volume Manager
Use Microsofts Volume Shadow Copy Service for shadow copy component backup. Volume Shadow Copy Service is available only on Windows XP and Windows.NET servers.
The Advanced Open The AOFO option was upgraded File Option will not be from a previous version of Backup available until the Exec. system is rebooted. Static file has grown The static file has outgrown the to maximum size and maximum size specified for the cannot be Advanced Open File Option. incremented anymore.
Reboot the system to load the updated AOFO driver.
On the AOFO Wizard Advanced Open File Option Configuration dialog, select the option Have Backup Exec calculate the initial and maximum size of the static volume. This allows Backup Exec to automatically calculate the initial and maximum size of the static volume for each backup. Or, using the AOFO Wizard, increase the space in the Initial size of the static volume (1-100 percent).
Volume name is invalid or not available.
A location for the static file was Enter a valid drive and path for the entered, but the drive does not exist static volume. For more or is not a local or valid drive. information, see Changing the Advanced Open File Option Default Settings on page 962.
972
Advanced Open File Option Error Messages Advanced Open File Option error messages (continued) Error Message Data read error on physical volume. Problem Solution
You may have cross link clusters or Fix the disk errors using scan disk, other disk errors. and then restart the backup for that volume. The Advanced Open File Option files may have been installed incorrectly, or may have been deleted after installation. A software component that is incompatible with the Advanced Open File Option has been loaded. An error occurred within AOFO. Reinstall the Advanced Open File Option on the machine that failed.
Open File Option
Driver failed to load.
Driver version is incompatible.
Reinstall the Advanced Open File Option on the machine that failed.
Error during backup. Set has been terminated. Error while writing to static volume.
Check job log for a more detailed error.
A disk error has occurred.
Fix the disk errors using scan disk, and then restart the backup for that volume. Use the AOFO wizard to change the location of the static volume to a path that exists on the drive. This is not a file system supported by Advanced Open File Option. Contact your reseller.
A Win32 error has occurred.
The temporary drive mapping to the static volume does not exist.
File system is not NTFS or FAT.
This is not a file system supported by Advanced Open File Option.
Evaluation period has The evaluation period has been been exceeded. exceeded. Incompatible major version. A software component that is incompatible with the Advanced Open File Option has been loaded.
The AOFO version is mismatched with Backup Exec. Reinstall the version of AOFO that came with the Backup Exec installation CD. The AOFO version is mismatched with Backup Exec. Reinstall the version of AOFO that came with the Backup Exec installation CD.
Incompatible minor version.
A software component that is incompatible with the Advanced Open File Option has been loaded.
973
Advanced Open File Option Error Messages Advanced Open File Option error messages (continued) Error Message Initialization failure on: Device name Problem During initialization of the Advanced Open File Option, an error occurred. Solution Read the accompanying detailed message for more information on this particular error.
IO attach error has occurred. Not available on specified volume. Not enough disk space for work volume.
This is a network error. A server Check your server or check with may not be available or responding. your network administrator. The volume being backed up is a CD-ROM drive or floppy diskette. This is not currently supported.
The static volume has exceeded the Check the amount of free space amount of free space available. available; you may need to add more free space. Restart the backup for that volume. Volume Manager 3.x can only snapshot dynamic volumes; it cannot snapshot basic volumes. Do not select basic volumes directly or indirectly (via mount points) for backup with Volume Manager. Jobs with mount points will also fail Instead, back up dynamic volumes by assigning drive letters to the with the same error message. volumes.
OFO: Volume specified is not snappable. Possible reasons: Volume has NOT been Snap Started or is a non-dynamic (basic) volume. Unable to get minimum quiet time window for physical volume.
In order to create the static volume, there can be no disk activity for six seconds. Each time the static volume grows, another six seconds of disk inactivity is required.
The backup runs, but without using the Advanced Open File Option. Reduce the traffic on this volume, or wait and run the backup when there is less disk activity on the volume.
974
VERITAS Backup Exec - Agent for Microsoft SQL Server
G
SQL Agent
The VERITAS Backup Exec for Windows Servers - 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. Continue reading for information about using the SQL Agent with SQL 2000 installations, or for information about using the SQL Agent with SQL 7.0 installations, see About the Agent for SQL 7.0 on page 1024. In SQL 2000 installations, the SQL Agent provides support for:

Backups of multiple instances. Database, transaction log, differential, and filegroup backups, as well as database recovery and replacement. Database Consistency Checks (DBCC) for each backup and restore job, including a fast database consistency check of only the physical consistency of the database. Restores of transaction logs to a specific point in time or to a named transaction when log marks are used. 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. 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 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.
975
Requirements for Using the SQL Agent with SQL 2000
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 database read-only and able to restore additional transaction logs to create and maintain a standby database.

An automated restore of the master database. The Intelligent Disaster Recovery option, which automates the disaster recovery process of SQL 2000.
See also: Installing the SQL Agent on page 977
Requirements for Using the SQL Agent with SQL 2000

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 option Automate master database restore 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.
976
Installing the SQL Agent

The VERITAS Backup Exec Agent for Microsoft SQL Server is installed as a separate, add-on component of Backup Exec for Windows Servers, and can be installed locally or remotely to back up SQL Server databases. Whenever the SQL Agent is installed on the media server, the Backup Exec Remote Agent is included as part of the SQL Agent installation. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server that you want to back up. You cannot select resources from a remote server for backup until a Remote Agent has been installed.
SQL Agent
If you are using the SQL Agent to protect databases on the local media server only, you are entitled to install the Remote Agent that was included with the SQL Agent installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the SQL Agent is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to install it on another Windows server. For instructions on installing the SQL Agent on the local media server, see Installing Backup Exec Options on a Local Server on page 49. For instructions on installing the SQL Agent on a remote resource, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
Appendix G, VERITAS Backup Exec - Agent for Microsoft SQL Server
977
Using Backup Exec Logon Accounts for SQL 2000 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.
The Backup Exec logon account containing the Windows credentials is applied to the Windows server that SQL is installed on
978
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.
The Backup Exec logon account containing the SQL user account credentials is applied to the SQL instance
SQL Agent
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. See also: Changing Logon Accounts for Resources on page 266 Configuring Logon Accounts on page 347
979
Backup Strategies for SQL 2000
Backup Strategies for SQL 2000

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. When developing a SQL backup strategy, consider the following:
Recommendations for backing up SQL 2000 SQL Server backup strategies: Protect the entire SQL Server. Description:
To make sure SQL is completely protected, back up the following on a regular basis: The system drive that SQL is on. The Windows registry and System State. SQL databases or filegroups. You do not need to back up both. Transaction logs.
980
Backup Strategies for SQL 2000 Recommendations for backing up SQL 2000 (continued) SQL Server backup strategies: Back up both system and user databases and transaction logs regularly. Description:
Copies of the master and model databases are automatically created by Backup Exec whenever you back up the master and model databases. If these databases become corrupted or are missing, and SQL cannot be started, you can replace them with the copies of the master and model databases, and then start SQL. After SQL is running again, you can restore the latest copy of the master database using Backup 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.
SQL Agent
When you upgrade, run If you upgrade SQL, run new full database backups. You may not be new full database able to restore backups from one version or service pack level of SQL to backups. other versions. If you have filegroups, back them up instead of databases. Do not back up filegroups and databases. Run consistency checks after backups. 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.
We recommend that you run a consistency check after a backup. If a database, transaction log, or filegroup contains errors when it is backed up, the backup will still contain the errors when it is restored, if it is restorable at all. These consistency checks include: A full consistency check, including indexes. This check will have significant impacts on SQL performance; therefore, it should be performed in off-peak hours. A full consistency check with no index check. While not as thorough as a full consistency check that includes indexes, this check is faster and can be done during peak hours with little impact on system performance. A physical only check. 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.
981
Consistency Checks for SQL 2000 Recommendations for backing up SQL 2000 (continued) SQL Server backup strategies: Description:
Back up the master Back up the master database whenever procedures are run that change database whenever data information in the database, especially after: is changed in the New databases are created. master database. Files are added to an existing database. Usernames or passwords are added or changed. If changes are not backed up before the master database must be restored, the changes are lost. Run one backup at a time. Do not schedule more than one backup to occur simultaneously against a database or its transaction log, or a filegroup.
Consistency Checks for SQL 2000

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. It is strongly recommended 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. CHECKFILEGROUP is performed for filegroup-related operations. For more information concerning these utilities, see your Microsoft SQL documentation. See also: Setting Backup Options for SQL 2000 on page 984
982
Using the Advanced Open File Option with SQL 2000
Using the Advanced Open File Option with SQL 2000

The VERITAS Backup Exec for Windows Servers - Advanced Open File Option (AOFO) is installed as a separate, add-on component of Backup Exec for Windows Servers. The Advanced Open File Option uses advanced open file and image technologies designed to alleviate issues that are sometimes encountered during backup operations, such as protecting open files and managing shortened backup windows. The AOFO supports only SQL Server 2000. When using the AOFO with SQL backups, note the following:

AOFO is only available to perform full database backups; differential backups and transaction log backups are not supported. It is recommended that SQL backup jobs be run separately from AOFO Volume Shadow Copy Service and Volume Snapshot Provider backup jobs. If you select Microsoft Volume Shadow Copy Service or VERITAS Volume Snapshot Provider, the SQL databases may freeze for several minutes while the snapshot is initiated. All activity on the SQL Server 2000 is stopped while the snapshot is being made. Volume Shadow Copy Service and Volume Snapshot Provider backups also incur additional overhead to the SQL backups. VERITAS Volume Manager FlashSnap Option will freeze the SQL databases for only a few seconds.
SQL Agent
SQL backups made with the AOFO are considerably bigger than regular SQL backups. SQL filegroups can be backed up using AOFO but only one filegroup per database can be backed up in a job. For the Intelligent Disaster Recovery Option to work with SQL 2000, copies are made of the master and model databases. Copies are only made when non-AOFO backups of master and model are run. If you are using AOFO for SQL backups, make at least one backup of the master and model databases without using AOFO. If SQL 2000 is upgraded, refresh the copies with another non-AOFO backup.
SQL backups made using the AOFO will fail if:
Multiple databases are selected for backup and SQL Service Pack 2 is not installed. If SQL Service Pack 2 is installed, you can select multiple databases at the same time for backup. A differential or transaction log backup method is selected.
See also: VERITAS Backup Exec for Windows Servers - Advanced Open File Option on page 955
Appendix G, VERITAS Backup Exec - Agent for Microsoft SQL Server 983
Setting Backup Options for SQL 2000

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 on page 235.
To select backup job properties for SQL 2000: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click SQL.
984

Backup job properties for SQL Item Backup method: Description Full - Back up entire database or filegroup. Select this to back up the entire database or filegroup. See Backing Up SQL 2000 Databases on page 988. This option is selected by default. Log - Back up transaction log. Select this 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 or Standby under Enable SQL 2000 advanced log backup options. See Backing Up SQL 2000 Transaction Logs on page 992. 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 2000 Transaction Logs on page 992. Differential - Back up database or filegroup changes only. Select this 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.
SQL Agent
985
Setting Backup Options for SQL 2000 Backup job properties for SQL (continued) Item Consistency check before backup Description Select a consistency check to run before a backup. None. Select this if you do not want a consistency check to run before a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000 only). Select this 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. Continue with backup if Select this to continue with the backup operation even if the consistency check fails 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.
986
Setting Backup Options for SQL 2000 Backup job properties for SQL (continued) Item Description
Consistency check after Select a consistency check to run after a backup. Because database backup transactions can occur during or after the consistency check, but before the backup runs, consider running a consistency check after the backup to ensure the data was consistent at the time of the backup. None. Select this if you do not want a consistency check to run after a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000). Select this 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. Enable SQL 2000 advanced log backup options This option is available only when the selected backup method is Log - Back up transaction log. 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. Select this option to put the database in a loading state when the log file backup completes. Users cannot connect to or query the database while it is in a loading state. Select this option to put the database in standby mode when the log file backup completes. Users can connect to and query the database when it is in standby mode, but cannot update it. Convert a standby database to a live database by restoring the latest transaction log and specifying the recovery completion state Leave database operational. No additional transaction logs can be restored.
SQL Agent
No recover - Place database in loading state Standby - Place database in standby state
987
Setting Backup Options for SQL 2000 Backup job properties for SQL (continued) Item Guide Me Description Click this to start a wizard that helps you select backup job properties for SQL.
See also: Selecting Data to Back Up on page 259 Using Selection Lists on page 267 Consistency Checks for SQL 2000 on page 982
Backing Up SQL 2000 Databases

Backup Exec includes two methods for backing up databases: full and differential. 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. A differential backup is smaller and faster than a full backup, so differential backups can be run more often than full backups. Because differential backups allow the restore of a system only to the point that the differential backup was created, you should also create multiple log backups between the differential backups. Using transaction log backups allows you to recover the database to the exact point of failure. Consider using differential backups when only a relatively small amount of data changes between full backups, or if the same data changes often. Differential backups may also work well in your environment if you are using the simple recovery model and need backups more often, but cannot spare the time to do frequent full backups. If you are using the full or bulk-logged recovery models, you can use differential backups to decrease the time it takes to roll forward log backups when restoring a database. If you want to run database backups only, instead of a mix of database and log backups, 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. 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. 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 2000 databases: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL 2000 Resources on page 978. 3. 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 checkbox preceding the SQL icon, or you can select specific databases by clicking the SQL icon, and then selecting individual databases.
SQL Agent
989
4. To select the SQL backup job properties, on the Properties pane, under Settings, click SQL. 5. After selecting job options, start the backup job or select other backup options from the Properties pane. See also: Backing Up Data on page 233 Backing Up SQL 2000 Transaction Logs on page 992 Setting Backup Options for SQL 2000 on page 984
Backing Up SQL 2000 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 allows 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. Before filegroups are displayed on the backup selections pane, you must enable an option on the SQL applications default dialog box.
To display filegroups on the backup selections pane: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click SQL. 3. Select the option Display filegroups when creating new backup jobs.
990
To back up SQL 2000 filegroups: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL 2000 Resources on page 978. 3. 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. Expand the SQL container and select specific filegroups.
SQL Agent
991
4. To select SQL backup job properties, on the Properties pane, under Settings, click SQL. 5. After selecting job options, start the backup job or select other backup options from the Properties pane.
See also: Backing Up Data on page 233 Setting Backup Options for SQL 2000 on page 984.
Backing Up SQL 2000 Transaction Logs

Backup Exec includes two methods for backing up transaction logs: Log and Log No Truncate. Use the Log method to back up only the data contained in the transaction log. After the transaction log is backed up, committed transactions are removed (truncated). Do not use this method when the following has occurred:

The transaction log has been truncated, unless you run a full or differential backup after the transaction log truncation occurs and before running a log backup. Files are added or deleted from the database. You should immediately run a full backup instead.
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 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.
992
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.
To back up SQL 2000 transaction logs: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL 2000 Resources on page 978. 3. 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. 4. To select SQL backup job properties, on the Properties pane, under Settings, click SQL. 5. After selecting job options, start the backup job or select other backup options from the Properties pane.
SQL Agent
See also: Setting Backup Options for SQL 2000 on page 984 About Restoring SQL 2000 Databases and Filegroups on page 999 Restoring from SQL 2000 Transaction Logs Up to a Point in Time on page 1002 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1003
993
Restore Options for SQL 2000

This procedure details how to select restore job properties for SQL, and provides definitions for SQL-specific restore options. For details on how to create a restore job, and for definitions of all other restore options see Restoring Data on page 395.
To select restore job properties for SQL 2000: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click SQL.
994

Restore job properties for SQL Item Description
Recovery completion state Leave database operational. No additional transaction logs can be restored. (With Recovery) Select this option when restoring the last database, differential, or log backup in the restore sequence in order to have the restore operation roll back all uncompleted transactions. After the recovery operation, the database is ready for use. If Leave database operational is not performed, the database is left in an intermediate state and is not usable. If Leave database operational is selected when an intermediate backup is being applied, you cannot continue to restore backups. You must restart the restore operation from the beginning. Select this option during a restore if you have additional Leave database nonoperational but able differential or transaction log backups to be restored in another restore job. to restore additional transaction logs (No Recovery) Leave database read-only and able to restore additional transaction logs (Standby) Replace databases or filegroups Select this checkbox to replace a database or filegroup, even if another database or filegroup with the same name already exists on the server. If Replace Databases or Filegroups 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 the REPLACE option is not selected. 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.
SQL Agent
995
Restore Options for SQL 2000 Restore job properties for SQL (continued) Item Automate master database restore Description Select this checkbox to enable Backup Exec to 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 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 logon account used has administrator rights to the Windows server that the SQL instance is installed on. Consistency check after restore None. Select this if you are doing sequential restores. Do not run a consistency check after a restore until all sequential restores have been done. If a consistency check is selected during a restore, the restore will complete but the consistency check will not be done. Check the job log for this information. If you need to recover the database after restores are complete, select one of the following consistency checks when you select the Leave database operational option. Full check, excluding indexes. Select this 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 to include indexes in the consistency check. Any errors are logged. This option is selected by default. Physical check only (SQL 2000 only). Select this 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.
996
Restore Options for SQL 2000 Restore job properties for SQL (continued) Item Description
Default drive for Use this option to select a default drive to which SQL database files restoring database files: can be restored if the drive where one or more of the database files previously resided no longer exists. 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. Restore all database files to default drive Select this checkbox to restore all database files to their original directory path on the default drive, even if the drive where they originally resided exists. To make this option available, select a drive letter in Default drive for restoring database files. Note 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. Restore all database Select this checkbox to restore files to the default data and log files to the target directories of the destination instance. For example, if you are instances data location 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. Note 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.
SQL Agent
997
Restore Options for SQL 2000 Restore job properties for SQL (continued) Item Description
Point in time log restore Select this checkbox 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 Select this checkbox to restore transactions from a transaction log named transaction (SQL up to a named transaction (or named mark) in the transaction log; 2000) 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. Include the named transaction Select this checkbox to include the named transaction in the restore; otherwise the restore will stop immediately before the named transaction is restored. Select this checkbox 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. Click this to start a wizard that helps you select restore job properties for SQL.
Found after
Guide Me
See also: About Restoring SQL 2000 Databases and Filegroups on page 999. Restoring from SQL 2000 Transaction Logs Up to a Point in Time on page 1002 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1003 Restoring from SQL 2000 Filegroup Backups on page 1004
998
About Restoring SQL 2000 Databases and Filegroups

You can restore a database using one job or using multiple jobs to restore all of the backup sets, depending on the types of backup used to protect the database or filegroup. To restore a database using one job, select all the backup sets that you want to apply, including the full backup, any differential backups, and any log backups, and select the option Leave database operational. No additional transaction logs can 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
SQL Agent
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. Restoring a nonprimary filegroup. After running a Log No Truncate backup, separate restore jobs must be used to restore the missing filegroup from full and differential backups of the filegroups, and to restore the transaction logs.
If you use multiple jobs to restore a database, make sure that you specify the recovery completion state Leave database nonoperational but able to restore additional transaction logs for all the jobs except the last one, for which you should specify the recovery completion state Leave database operational. 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.
999
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 2000 on page 1009. Note SQL 7.0 database backups can be restored to SQL 2000, but SQL 2000 backups cannot be restored to SQL 7.0. See also: Restoring Data on page 395 Restoring from SQL 2000 Transaction Logs Up to a Point in Time on page 1002 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1003 Restoring from SQL 2000 Filegroup Backups on page 1004 Redirecting Restores for SQL 2000 on page 1009
1000
Restoring from SQL 2000 Database Backups

If the database is using the simple recovery model, there are no transaction log backups to restore. You only need to restore the most recent full database backup and if you were running differential database backups, restore the most recent differential database backup. For details on all other restore options, see Restoring Data on page 395.
To restore from full and differential database backups: 1. On the navigation bar, click Restore.
SQL Agent
2. On the Properties pane, under Source, click Selections. 3. 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. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational. No additional transaction logs can be restored. For information on other SQL restore options, see Restore Options for SQL 2000 on page 994. 6. Start the restore job or select other restore options from the Properties pane. See also: Restoring Data on page 395 About Restoring SQL 2000 Databases and Filegroups on page 999
1001
Restoring from SQL 2000 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 up to and including a point in time. 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. 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. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational. No additional transaction logs can be restored. 6. Select Point in time log restore, and then select a date and time. For information on selecting other options, see Restore Options for SQL 2000 on page 994. 7. Start the restore job or select other restore options from the Properties pane.
See also: Restoring Data on page 395 About Restoring SQL 2000 Databases and Filegroups on page 999
1002
Restoring from SQL 2000 Transaction Logs Up to a Named Transaction

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.
SQL Agent
Restore up to and including a named transaction. 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. 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. 4. On the Properties pane, under Settings, click SQL. 5. On Restore Job Properties for SQL, select the recovery completion state Leave database operational. No additional transaction logs can be restored. 6. 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.
1003
7. To include the named transaction in the restore, select Include the named transaction. 8. To specify a particular named transaction in the log, select Found after and then select a date and time. If a date and time are not entered, recovery from the transaction log is stopped at the first transaction with the specified name. For information on other SQL restore options, see Redirecting Restores for SQL 2000 on page 1009. 9. Start the restore job or select other restore options from the Properties pane. See also: Restoring Data on page 395 About Restoring SQL 2000 Databases and Filegroups on page 999
Restoring from SQL 2000 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. 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.
1004
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 Backup Exec v9.0.
To restore the entire database, a missing primary filegroup, or a filegroup containing a deleted or changed table:
SQL Agent
Note Use separate restore jobs to restore the primary filegroup, the rest of the filegroup backup sets, and the transaction logs. 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. In the restore selections list, select the backup set containing the primary filegroup. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database nonoperational but able to restore additional transaction logs. For information on other SQL restore options, see Redirecting Restores for SQL 2000 on page 1009. 6. Start the restore job. 7. After the primary filegroup is restored, select the rest of the filegroup backup sets containing the latest full and differential backups. 8. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database nonoperational but able to restore additional transaction logs, and then start the restore job.
9. When the full and differential backups are restored, select the backup set containing the transaction logs.
1005
10. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational and restore all of the transaction logs, or select Point in time log restore or Restore log up to named transaction. 11. Start the restore job or select other restore options from the Properties pane. For information on other restore options, see Restoring Data on page 395.
To restore a missing or corrupted filegroup: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections. 3. In the backup selections list, select the database. 4. On the Properties pane, under Settings, click SQL. 5. Select the backup method Log No Truncate, select None for a consistency check, and then start the backup job. 6. 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. 7. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational. No additional transaction logs can be restored. 8. Start the restore job or select other restore options from the Properties pane. See also: Restoring Data on page 395
1006
Restoring the SQL 2000 Master Database

If the master database is damaged, symptoms may include:

An inability to start SQL. Segmentation faults or input/output errors. A report generated by SQL Database Consistency Checker utility (DBCC).
If you can still start SQL, you can restore the latest copy of the master database backup using the Automate master database restore option in Backup 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.
SQL Agent
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. In a default installation of SQL 2000, the databases are in: C:\Program Files\Microsoft SQL Server\MSSQL\Data\*.*. In a named instance of SQL 2000, the databases are in: C:\Program Files\Microsoft SQL Server\MSSQL$Instance_Name\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. Open a command prompt window, and delete the original master and model databases and their transaction logs.
1007
For example: C:\Program Files\Microsoft SQL Server\MSSQL\Data> del master.mdf mastlog.ldf model.mdf modellog.ldf 3. Rename the copies of the databases back to their original names. Type the following C:\Program Files\Microsoft SQL Server\MSSQL\Data>rename master$4idr master.mdf C:\Program Files\Microsoft SQL Server\MSSQL\Data>rename mastlog$4idr mastlog.ldf C:\Program Files\Microsoft SQL Server\MSSQL\Data>rename model$4idr model.mdf C:\Program Files\Microsoft SQL Server\MSSQL\Data>rename modellog$4idr modellog.ldf 4. Use the SQL Service Control Manager to start SQL Server. 5. Continue with the next procedure to restore the latest changes to the master database.
To restore the master database: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. On the restore selections list, select the backup set containing the last master database backup. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select Automate master database restore. All existing users are logged off, and SQL Server is put into single-user mode. When this option is selected, only the master database can be restored; if this option is selected for any other database, those jobs will fail. If Backup Exec does not have access to the SQL registry keys HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server and HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer, then a restore to the default directory may not work, and the option Automate master database restore on
1008
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. 6. Select a consistency check to be run after the restore. 7. Start the restore job. After the restore, SQL is restarted in multi-user mode. See also: Restoring Data on page 395
SQL Agent
Redirecting Restores for SQL 2000

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. One or more filegroups in a backup to a different server or instance. Filegroups can be redirected to a different server, but the database file paths cannot be changed. For example, if the filegroup was backed up from G:\SQLDATA, then it must be restored to G:\SQLDATA, even if it is redirected to another server. Filegroups must be restored to the same drive letter and path that they were backed up from.
Single-job restores and multiple-job restores can both be used in redirected restore operations.
To redirect a restore: 1. Follow the instructions for the appropriate restore: Restoring from SQL 2000 Database Backups on page 1001. Restoring from SQL 2000 Transaction Logs Up to a Point in Time on page 1002. Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1003. Restoring from SQL 2000 Filegroup Backups on page 1004.
2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click SQL Redirection.
1009
3. Select the appropriate options as follows, and then start the redirected restore job or select other restore options from the Properties pane:
Restore job properties for redirected SQL sets Item Redirect Microsoft SQL Server sets Restore to server Description Select this checkbox to enable redirection of SQL backup sets.
To redirect this restore to a different server, type the target server name. You can redirect a full database backup to a different server or database; however, if the drive configuration is different from when the database backup was created, you must select either Default drive for restoring database files or Restore all database files to the target instances data location on the Restore Job Properties for SQL dialog box (see Restore Options for SQL 2000 on page 994).
1010
About Restoring SQL 2000 Databases and Filegroups Restore job properties for redirected SQL sets (continued) Item Server logon account Description To restore to a server, use a Backup Exec logon account that stores the credentials of a Windows user account. The Windows user account must have been granted the System Administrator role on the SQL instance. The default logon account is displayed. To use another logon account, click Change. For more information about logon accounts, see Using Backup Exec Logon Accounts for SQL 2000 Resources on page 978. If you are using SQL Server Authentication, use a Backup Exec logon account that stores the credentials of the SQL user account. Apply the Backup Exec logon account for the Windows user account to the Windows server that SQL is installed on, and then apply the logon account for the SQL user account to the SQL instance. To use another logon account, click Change. To remove the SQL logon account displayed in this field, click Clear. For more information about logon accounts, see Using Backup Exec Logon Accounts for SQL 2000 Resources on page 978. Restore to named instance (SQL 2000) To redirect this restore to a named instance, type the instance name. If you are restoring to the default instance, leave the field empty. To redirect the restore to a different database on the target server, type the target database name; otherwise, leave the field blank. You can redirect a full database backup to a different server and/or database; however, if the drive configuration is different from when the database backup was created, you must select either Default drive for restoring database files or select Restore all database files to the target instances data location on the Restore Job Properties for SQL dialog box (see Redirecting Restores for SQL 2000 on page 1009). If you are restoring a differential or log backup, and the associated database backup was restored to a different server, enter the new database name.
SQL logon account
SQL Agent
Restore to database
See also: Restoring Data on page 395 About Restoring SQL 2000 Databases and Filegroups on page 999
1011
Setting Default Backup and Restore Options for SQL 2000

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 change backup and restore defaults for SQL: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click SQL.
1012

Options - set application defaults for SQL Item Backup Backup method Full - Back up entire database or filegroup. Select this to back up the entire database or filegroup. See Backing Up SQL 2000 Databases on page 988. This option is selected by default. Description
SQL Agent
Log - Back up transaction log. Select this 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 2000 Transaction Logs on page 992. 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 2000 Transaction Logs on page 992. Differential - Back up database or filegroup changes only. Select this 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 2000 Databases on page 988.
1013
Setting Default Backup and Restore Options for SQL 2000 Options - set application defaults for SQL Item Consistency check before backup Description Select a consistency check to run before a backup. None. Select this if you do not want a consistency check to run before a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000 only). Select this 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. Continue with backup if consistency check fails Select this 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.
1014
Setting Default Backup and Restore Options for SQL 2000 Options - set application defaults for SQL Item Consistency check after backup Description Select a consistency check to run after a backup. Because database transactions can occur during or after the consistency check, but before the backup runs, consider running a consistency check after the backup to ensure the data was consistent at the time of the backup. None. Select this if you do not want a consistency check to run after a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000 only). Select this 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. Display filegroups when Select this checkbox if filegroups exist that you want to select for creating new backup jobs backup. If this checkbox is not selected, filegroups are not displayed as backup selections.
SQL Agent
1015
Setting Default Backup and Restore Options for SQL 2000 Options - set application defaults for SQL Item Restore Recovery completion state Leave database operational. No additional transaction logs can be restored (With Recovery). Select this option when restoring the last database, differential, or log backups in the restore sequence in order to have the restore operation roll back all uncompleted transactions. After the recovery operation, the database is ready for use. If Leave database operational is not performed, the database is left in an intermediate state and is not usable. If Leave database operational is selected when an intermediate backup is being applied, you cannot continue to restore backups. You must restart the restore operation from the beginning. This option is selected by default. Leave database nonoperational but able to restore additional transaction logs (No Recovery). Select this option during a restore if you have additional differential or transaction log backups to be restored in another restore job. Leave database read-only and able to restore additional transaction logs (Standby). 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. Replace databases or filegroups Select this checkbox to replace a database or filegroup, even if another database or filegroup with the same name already exists on the server. If Replace databases or filegroups 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 the REPLACE option is not selected. Description
1016
Setting Default Backup and Restore Options for SQL 2000 Options - set application defaults for SQL Item Consistency check after restore Description None. Select this if you are doing sequential restores. Do not run a consistency check after a restore until all sequential restores have been done. If a consistency check is selected during a restore, the restore will complete but the consistency check will not be done. Check the job log for this information. If you need to recover the database after restores are complete, select one of the following consistency checks when you select the Leave database operational option. Full check, excluding indexes. Select this 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 to include indexes in the consistency check. Any errors are logged. This option is selected by default. Physical check only (SQL 2000 only). Select this 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.
SQL Agent
1017
Preparing for Disaster Recovery of SQL 2000

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 the C: drive, 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. Caution For the Intelligent Disaster Recovery Option to work with SQL 2000, copies are made of the master and model databases. Copies are only made when non-AOFO backups of master and model are run. If you are using AOFO for SQL backups, make at least one backup of the master and model databases without using AOFO. If SQL 2000 is upgraded, refresh the copies with another non-AOFO backup.
To prepare for disaster recovery, 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. In a default installation of SQL 2000, the databases are in: C:\Program Files\Microsoft SQL Server\MSSQL\Data\*.*. In a named instance of SQL 2000, the databases are in: C:\Program Files\Microsoft SQL Server\MSSQL$Instance_Name\Data\*.* The copies of the master and model databases are named: Master$4idr Mastlog$4idr Model$4idr Modellog$4idr
1018
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 created. Backing up the system drive that SQL is on also backs up all the executables and registry settings needed for SQL to run.
Back up the master database whenever any changes are made to SQL. Keep records of any service packs that have been installed. Review Disaster Preparation of the Windows Computer on page 533 to make sure you are prepared to recover the entire server, not just SQL.
To perform a recovery, you will need:

SQL Agent
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.
1019
Disaster Recovery of SQL 2000

You can restore either the entire server, including the SQL databases, from full system backups, or restore only the SQL databases to a newly installed or other available SQL server. Restoring the entire server including the SQL databases Restoring the entire server, including the SQL databases has the added benefit of recovering other applications and data that may have resided on the server at the time of failure, and can be accomplished using one of the following methods:
Manual recovery of the Windows server, and then manual recovery of the SQL databases. This method involves manually restoring the Windows server from full system backups, and then recovering the SQL databases. The Intelligent Disaster Recovery Option. This option provides an automated method of restoring the Windows server as well as the SQL databases from full system backups. See Microsoft SQL Server Recovery Notes on page 909.
Restoring only the SQL databases
To restore only the SQL databases to a newly-installed or other available server, the server must be running on the same hardware platform (cross-platform restores are not supported), and the same version of SQL with the same service pack level as the original server. To restore SQL databases to an existing installation of SQL with other active databases, see Redirecting Restores for SQL 2000 on page 1009.
Manual Recovery of SQL 2000

If necessary, restore the Windows computer by following the instructions in Manual Disaster Recovery of Windows Computers on page 540. 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.
1020
Run the Rebuild Master utility (\Program Files\Microsoft SQL Server\80\Tools\Binn\rebuildm.exe) to rebuild the master database. Reinstall SQL.
This topic only details how to restart SQL by using the copies of the master and model databases made by Backup Exec. For more information on the Rebuild Master utility, or on reinstalling SQL, refer to your Microsoft SQL documentation. If you are restoring to a new SQL installation, start with To restore the master database: on page 1008.
To restart SQL using database copies:
SQL Agent
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 2000, the databases are in: C:\Program Files\Microsoft SQL Server\MSSQL\Data\*.*. In a named instance of SQL 2000, the databases are in: C:\Program Files\Microsoft SQL Server\MSSQL$Instance_Name\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. Open a command prompt window, and delete the original master and model databases and their transaction logs. Type the following: C:\program files\microsoft sql server\mssql\data> del master.mdf mastlog.ldf model.mdf modellog.ldf 3. Rename the copies of the databases back to their original names. Type the following C:\program files\microsoft sql server\mssql\data> rename master$4idr master.mdf C:\program files\microsoft sql server\mssql\data> rename mastlog$4idr mastlog.ldf C:\program files\microsoft sql server\mssql\data> rename model$4idr model.mdf
1021
C:\program files\microsoft sql server\mssql\data> rename modellog$4idr modellog.ldf 4. Use the SQL Service Control Manager to start SQL Server. 5. Continue with the next procedure to restore the latest changes to the master database.
To restore the master database: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. On the restore selections list, select the backup set containing the last master database backup. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select Automate master database restore. All existing users are logged off, and SQL Server is put into single-user mode. When this option is selected, only the master database can be restored; if this option is selected for any other database, those jobs will fail. If Backup Exec does not have access to the SQL registry keys HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server and HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer, then a restore to the default directory may not work, and the option Automate master database restore on the restore job properties for SQL will not work. To ensure that Backup Exec has access rights, verify that the account that Backup Exec uses has administrator rights to the computer that is running SQL. 6. Select a consistency check to run after the restore. 7. Start the restore job. After the restore, SQL is restarted in multi-user mode. 8. Continue with the next procedure, restoring the remaining SQL databases.
1022
Restore the remaining SQL databases: Note Do not select the master database for restore at this time. If you are restoring the SQL databases from filegroup backups, go to Restoring from SQL 2000 Filegroup Backups on page 1004. 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. Select all the backup sets that you want to apply, including the full backup, any differential backups, and any log backups. 4. On the Properties pane, under Settings, click SQL. 5. Select the option Leave database operational. No additional transaction logs can be restored. 6. Select the option Replace Databases or Filegroups. 7. In the Consistency Check After Database Restore field, select Full check, including indexes. 8. Start the restore job or select other options from the Properties pane. If the restore is being redirected, see Redirecting Restores for SQL 2000 on page 1009. When all of the restore operations have completed successfully, then the recovery of the SQL databases is complete. After the recovery has been completed, it is strongly recommended that a full database backup be performed as soon as possible. See also: Restoring Data on page 395
SQL Agent
1023
About the Agent for SQL 7.0
About the Agent for SQL 7.0

The VERITAS Backup Exec for Windows Servers - Agent for Microsoft SQL Server enables network administrators to perform backup and restore operations on installations of SQL 7.0 that are connected to a network. SQL database backups can be integrated with network backups without separate administration or dedicated hardware. Continue reading for information about the Agent for SQL 7.0 installations, or for information about the Agent for SQL 2000 installations, see VERITAS Backup Exec Agent for Microsoft SQL Server on page 975. The SQL Agent provides support for:

Database, transaction log, differential, and filegroup backups, as well as database recovery and replacement. Database Consistency Checks (DBCC) before and after each backup job. Restores of transaction logs to a specific point in time. 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 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 database read-only and able to restore additional transaction logs to create and maintain a standby database.
An automated restore of the master database. The Intelligent Disaster Recovery option, which automates the disaster recovery process of SQL 7.0.
See also: Installing the SQL Agent on page 1026
1024
Requirements for Agent for SQL 7.0
Requirements for Agent for SQL 7.0

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 option Automate master database restore on the restore job properties for SQL will not work.
SQL Agent
To ensure that Backup Exec has access rights, verify that the Backup Exec 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.
1025

The VERITAS Backup Exec Agent for Microsoft SQL Server is installed as a separate, add-on component of Backup Exec for Windows Servers, and can be installed locally or remotely to back up SQL Server databases. Whenever the SQL Agent is installed on the media server, the Backup Exec Remote Agent is included as part of the SQL Agent installation. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server that you want to back up. You cannot select resources from a remote server for backup until a Remote Agent has been installed. If you are using the SQL Agent to protect databases on the local media server only, you are entitled to install the Remote Agent that was included with the SQL Agent installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the SQL Agent is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to install it on another Windows server. For instructions on installing the SQL Agent on the local media server, see Installing Backup Exec Options on a Local Server on page 49. For instructions on installing the SQL Agent on a remote resource, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
1026
Using Backup Exec Logon Accounts for SQL 7.0 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, apply that Backup Exec logon account to the Windows server that SQL is installed on, not to the actual SQL instance.
SQL Agent
The Backup Exec logon account containing the Windows credentials is applied to the Windows server that SQL is installed on
1027
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 Backup Exec logon account for the SQL user account to the SQL instance.
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. See also: Changing Logon Accounts for Resources on page 266 Configuring Logon Accounts on page 347
1028
Backup Strategies for SQL 7.0
Backup Strategies for SQL 7.0

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 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.
SQL Agent
The trade-off with running fewer full backups and running more differential backups occurs at recovery time when you must recover using the full database backup as well as the last differential database backup and all log backups made after the last differential database backup. What will work best for you will be based on the size of your environment, the number of transactions processed each day, and the expectations of your users when a recovery is required. When developing a SQL backup strategy, consider the following:
Recommendations for backing up SQL 7.0 SQL backup strategies: Description: Protect the entire SQL Server. To make sure SQL is completely protected, back up the following on a regular basis: The system drive that SQL is on. The Windows registry and System State. SQL databases or filegroups. You do not need to back up both. Transaction logs.
1029
Backup Strategies for SQL 7.0 Recommendations for backing up SQL 7.0 (continued) SQL backup strategies: Description: Create a copy of the master and model databases, and place the copies in the same directory that the databases are in. 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 C: drive, it will automatically replace the damaged databases with the copies of the master and model databases that you made. For details, see To create copies of the master and model databases: on page 1062. When you upgrade, run 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 new full database other versions. backups. 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. Run consistency checks after backups. 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. We recommend that you run a consistency check after a backup. If a database, transaction log, or filegroup contains errors when it is backed up, the backup will still contain the errors when it is restored, if it is restorable at all. These consistency checks include: A full consistency check, including indexes. This check will have significant impacts on SQL performance; therefore, it should be performed in off-peak hours. A full consistency check with no index check. While not as thorough, this check is faster and can be done during peak hours with little impact on system performance.
1030
Consistency Checks for SQL 7.0 Recommendations for backing up SQL 7.0 (continued) SQL backup strategies: Description: Back up the master Back up the master database whenever procedures are run that change database whenever data information in the database, especially after: is changed in the New databases are created. master database. 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.
SQL Agent
Run one backup at a time.
Do not schedule more than one backup to occur simultaneously against a database or its transaction log, or a filegroup.
Consistency Checks for SQL 7.0

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. It is strongly recommended 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
CHECKDB and CHECKCATALOG are performed for database-related operations. CHECKFILEGROUP is performed for filegroup-related operations. For more information concerning these utilities, see your Microsoft SQL documentation. See also: Setting Backup Options for SQL 7.0 on page 1032
1031
Setting Backup Options for SQL 7.0

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 on page 235.
To select backup job properties for SQL 7.0: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click SQL.
1032
3. Select the appropriate options as follows:.

Backup job properties for SQL 7.0 Item Backup Method Description Full - Back up entire database or filegroup. Select this to back up the entire database or filegroup. See Backing Up SQL 7.0 Databases on page 1035. This option is selected by default. Log - Back up transaction log. Select this 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 7.0 Transaction Logs on page 1039. 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 7.0 Transaction Logs on page 1039. Differential - Back up database or filegroup changes only. Select this 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. Consistency check before backup Select a consistency check to run before a backup. None. Select this if you do not want a consistency check to run before a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged.
SQL Agent
1033
Setting Backup Options for SQL 7.0 Backup job properties for SQL 7.0 Item Description
Continue with backup if Select this checkbox to continue with the backup operation even if consistency check fails 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. Consistency check after Select a consistency check to run after a backup. Because database backup transactions can occur during or after the consistency check, but before the backup runs, consider running a consistency check after the backup to ensure the data was consistent at the time of the backup. None. Select this if you do not want a consistency check to run after a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged. Guide Me Click this to start a wizard that helps you select backup job properties for SQL.
See also: Backing Up SQL 7.0 Databases on page 1035 Backing Up SQL 7.0 Filegroups on page 1037 Backing Up SQL 7.0 Transaction Logs on page 1039
1034
Backing Up SQL 7.0 Databases

Backup Exec includes two methods for backing up databases: full and differential. 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. 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.
SQL Agent
Consider using differential backups when only a relatively small amount of data changes between full database backups, or if the same data changes often. Differential backups may also work well in your environment if you need backups more often, but cannot spare the time to do frequent full database backups. If you want to run database backups only, instead of a mix of database and log backups, 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. This helps prevent transaction logs from becoming full since the logs are not cleared after a database backup. 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 7.0 databases: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL 7.0 Resources on page 1027. 3. 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.
1035
To select all databases in SQL, click the checkbox preceding the SQL icon, or you can select specific databases by clicking the SQL icon, and then selecting individual databases.
4. To select the SQL backup job properties, on the Properties pane, under Settings, click SQL. 5. Select options for the backup job. For details on these options, see Setting Backup Options for SQL 7.0 on page 1032. 6. Start the backup job. For details on running or scheduling the job, as well as other backup options, see Backing Up Data on page 233.
1036
Backing Up SQL 7.0 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 allows you to recover the filegroup to the exact point of failure. 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. Before filegroups are displayed on the backup selections pane, you must enable an option on the SQL applications default dialog box.
SQL Agent
To display filegroups on the backup selections pane: 1. On the Backup Exec menu bar, click Tools, and then click Options.
2. On the Properties pane, under Job Defaults, click SQL to display the SQL application defaults dialog box. 3. Select the option Display filegroups when creating new backup jobs.
To back up SQL 7.0 filegroups: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up.
1037
For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL 7.0 Resources on page 1027. 3. 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. Expand the SQL container and select specific filegroups.
4. To select SQL backup job properties, on the Properties pane, under Settings, click SQL. 5. After selecting job options, start the backup job or select other backup options from the Properties pane. See also: Backing Up Data on page 233 Setting Backup Options for SQL 7.0 on page 1032
1038
Backing Up SQL 7.0 Transaction Logs

Backup Exec includes two methods for backing up transaction logs: Log and Log No Truncate. Use the Log method to back up only the data contained in the transaction log. After the transaction log is backed up, committed transactions are removed (truncated). Do not use this method when the following has occurred:

The transaction log has been truncated, unless you run a full or differential backup after the transaction log truncation occurs and before running a log backup. Files are added or deleted from the database. You should immediately run a full backup instead.
SQL Agent
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 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 to be able to restore a database. 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. The SQL database option select into/bulkcopy 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 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.
1039
To back up SQL 7.0 transaction logs: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL 7.0 Resources on page 1027. 3. 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. 4. To select SQL backup job properties, on the Properties pane, under Settings, click SQL. 5. After selecting job options, start the backup job or select other backup options from the Properties pane. 6. Start the backup job. For details on other backup options, see See also: Setting Backup Options for SQL 7.0 on page 1032 Restoring from SQL 7.0 Transaction Logs Up to a Point in Time on page 1048
1040
Restore Options for SQL 7.0

This procedure details how to select restore job properties for SQL and provides definitions of SQL-specific restore options. For details on how to create a restore job, and for definitions of all other restore options see Restoring Data on page 395.
To select restore job properties for SQL 7.0: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click SQL.
SQL Agent
1041

Restore job properties for SQL 7.0 Item Description
Recovery completion state Leave database operational. No additional transaction logs can be restored (With Recovery) Select this option when restoring the last database, differential, or log backup in the restore sequence in order to have the restore operation roll back all uncompleted transactions. After the recovery operation, the database is ready for use. If Leave database operational is not performed, the database is left in an intermediate state and is not usable. If Leave database operational is selected when an intermediate backup is being applied, you cannot continue to restore backups. You must restart the restore operation from the beginning. This option is selected by default. Leave database Select this option during a restore if you have additional nonoperational but able differential or transaction log backups to be restored in another to restore additional restore job. transaction logs (No Recovery) Leave database read-only and able to restore additional transaction logs (Standby) Replace databases or filegroups Select this checkbox to replace a database or filegroup, even if another database or filegroup with the same name already exists on the server. If Replace Databases or Filegroups 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 the REPLACE option is not selected. 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.
1042
Restore Options for SQL 7.0 Restore job properties for SQL 7.0 Item Automate master database restore Description Select this checkbox to enable Backup Exec to 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 data, 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 logon account used has administrator rights to the Windows server that the SQL instance is installed on. Consistency check after restore None. Select this if you are doing sequential restores. Do not run a consistency check after a restore until all sequential restores have been done. If a consistency check is selected during a restore, the restore will complete but the consistency check will not be done. Check the job log for this information. If you need to recover the database after restores are complete, select one of the following consistency checks when you select the Leave database operational option. Full check, excluding indexes. Select this 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 to include indexes in the consistency check. Any errors are logged. This option is selected by default.
SQL Agent
1043
Restore Options for SQL 7.0 Restore job properties for SQL 7.0 Item Description
Default drive for Use this option to select a default drive to which SQL database files restoring database files can be restored if the drive where one or more of the database files previously resided no longer exists. 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. Restore all database files to default drive Select this checkbox to restore all database files to their original directory path on the default drive, even if the drive where they originally resided exists. To make this option available, select a drive letter in Default drive for restoring database files. Note 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. Restore all database Select this checkbox to restore files to the default data and log files to the target directories of the destination instance. For example, if you are instances data location 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. Note 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.
1044
About Restoring SQL 7.0 Databases or Filegroups Restore job properties for SQL 7.0 Item Description
Point in time log restore Select this checkbox 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.
SQL Agent
Guide Me
Click this to start a wizard that helps you select restore job properties for SQL.
See also: About Restoring SQL 7.0 Databases or Filegroups on page 1045 Restoring from SQL 7.0 Transaction Logs Up to a Point in Time on page 1048 Restoring from SQL 7.0 Filegroup Backups on page 1049
About Restoring SQL 7.0 Databases or Filegroups

You can restore a database using one job or using multiple jobs to restore all of the backup sets, depending on the types of backup used to protect the database or filegroup. To restore a database using one job, select all the backup sets that you want to apply, including the full backup, any differential backups, and any log backups, and select the option Leave database operational. No additional transaction logs can be restored. Single-job restores and multiple-job restores can both be used in redirected restore operations. Some restore operations must be completed using separate restore jobs to recover data. These operations include
Restoring a database or a primary filegroup from a filegroup backup. Separate restore jobs must be used to restore the database backup or the primary filegroup backup, 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.
1045
Restoring a nonprimary filegroup. After running a Log No Truncate backup, separate restore jobs must be used to restore the missing nonprimary filegroup from full and differential backups of the filegroups, and to restore the transaction logs.
If you use multiple jobs to restore a database, make sure that you specify the recovery completion state Leave database nonoperational but able to restore additional transaction logs for all the jobs except the last one, for which you should specify the recovery completion state Leave database operational. 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 Restoring Data on page 395. Note SQL 7.0 database backups can be restored to SQL 2000, but SQL 2000 backups cannot be restored to SQL 7.0.
1046
Restoring from SQL 7.0 Database Backups

If the SQL database option truncate log on checkpoint is set for the database, 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.
To restore from full and differential database backups: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. 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. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational. No additional transaction logs can be restored. For information on other SQL restore options, see Restore Options for SQL 7.0 on page 1041. 6. Start the restore job or select other restore options from the Properties pane. See also: Restoring Data on page 395 About Restoring SQL 7.0 Databases or Filegroups on page 1045
SQL Agent
1047
Restoring from SQL 7.0 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 up to and including a point in time. 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. 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. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational. No additional transaction logs can be restored. 6. Select Point in time log restore, and then select a date and time. For information on selecting other options, see Restore Options for SQL 7.0 on page 1041. 7. Start the restore job or select other restore options from the Properties pane.
See also: Restoring Data on page 395 About Restoring SQL 7.0 Databases or Filegroups on page 1045
1048
Restoring from SQL 7.0 Filegroup Backups

With filegroup backups, you can restore a primary filegroup, a filegroup containing a deleted or changed table, and a nonprimary filegroup. Caution SQL 7.0 databases cannot be restored using only filegroups and log backups. SQL 7.0 databases must have at least one full database backup in order to be restored. If the database has been deleted or does not exist, restore the full database backup, and then restore all the filegroup and log backups. The following are conditions for filegroup restores:
All filegroups must be restored to the same point in time. For example, if a table is deleted from a filegroup, you cannot restore that filegroup to a point in time before the table was deleted and then leave it at that time; you must continue restoring the filegroup to the same point in time shared by all existing filegroups. To be able to restore a filegroup to the same point in time as the other filegroups, run one of the following log backups: If the database is intact, run a Log backup. If any files or filegroups are missing, run a Log - No Truncate backup.
SQL Agent
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.
Previous versions of Backup Exec cannot restore filegroup backups made with Backup Exec v9.0.
To restore a primary filegroup, or a filegroup containing a deleted or changed table: Note Use separate restore jobs to restore the primary filegroup, the rest of the filegroup backup sets, and the transaction logs.
1049
1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. In the restore selections list, select the backup set containing the primary filegroup. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database nonoperational but able to restore additional transaction logs. For information on other SQL restore options, see Redirecting Restores for SQL 7.0 on page 1053. 6. Start the restore job. 7. After the primary filegroup is restored, select the rest of the filegroup backup sets containing the latest full and differential backups. 8. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database nonoperational but able to restore additional transaction logs, and then start the restore job.
9. When the full and differential backups are restored, select the backup set containing the transaction logs. 10. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational. No additional transaction logs can be restored and restore all of the transaction logs, or select Point in time log restore or Restore log up to named transaction, and then start the restore job. 11. Start the restore job or select other restore options from the Properties pane. For information on other restore options, see Restoring Data on page 395.
To restore a missing or corrupted nonprimary filegroup: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selection. 3. In the backup selections list, select the database. 4. On the Properties pane, under Settings, click SQL. 5. Select the backup method Log No Truncate, select None for a consistency check, and then start the backup job.
1050
6. After the Log No Truncate backup is complete, restore the missing filegroup by selecting the filegroup backup sets containing the latest full and differential backups, and the transaction log backups. 7. On the Restore Job Properties for SQL dialog box, select the recovery completion state Leave database operational. No additional transaction logs can be restored. 8. Start the restore job or select other restore options from the Properties pane. See also: Restoring Data on page 395
SQL Agent
Restoring the SQL 7.0 Master Database

If the master database is damaged, symptoms may include:

An inability to start SQL. Segmentation faults or input/output errors. A report generated by SQL Database Consistency Checker utility (DBCC).
If you can still start SQL, you can restore the latest copy of the master database backup using the Automate master database restore option in Backup Execs Restore Job Properties for SQL, 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 you created as part of your disaster recovery preparation plan. 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 Rebuild Master utility (\MSSQL7\binn\Rebuildm.exe) to rebuild the master database and start SQL. For more information, refer to your Microsoft SQL documentation. 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.
1051
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. 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. Open a command prompt window, and delete the original master and model databases and their transaction logs. Type the following: C:\ mssql7\data> del master.mdf mastlog.ldf model.mdf modellog.ldf 3. Rename the copies of the databases back to their original names. Type the following: C:\ mssql7\data> rename master$4idr master.mdf C:\ mssql7\data> rename mastlog$4idr mastlog.ldf C:\ mssql7\data> rename model$4idr model.mdf C:\ mssql7\data> rename modellog$4idr modellog.ldf 4. Use the SQL Server Service Manager to start SQL. 5. Continue with the next procedure to restore the latest changes to the master database.
To restore the master database: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click SQL. 3. On the restore selections list, select the backup set containing the last master database backup. 4. On the Restore Job Properties for SQL dialog box, select Automate master database restore. All existing users are logged off, and SQL Server is put into single-user mode.
1052
When this option is selected, only the master database can be restored; if this option is selected for any other data, 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 logon account used has administrator rights to the Windows server that the SQL instance is installed on. 5. Select a consistency check to be run after the restore.
SQL Agent
6. Start the restore job. After the restore, SQL is restarted in multi-user mode. See also: Restoring Data on page 395.
Redirecting Restores for SQL 7.0

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. One or more filegroups in a backup to a different server or instance. Filegroups can be redirected to a different server, but the database file paths cannot be changed. For example, if the filegroup was backed up from G:\SQLDATA then it must be restored to G:\SQLDATA, even if it is redirected to another server. Filegroups must be restored to the same drive letter and path that they were backed up from.
Single-job restores and multiple-job restores can both be used in redirected restore operations.
To redirect a restore: 1. Follow the instructions for the appropriate restore: Restoring from SQL 7.0 Database Backups on page 1047. Restoring from SQL 7.0 Transaction Logs Up to a Point in Time on page 1048. Restoring from SQL 7.0 Filegroup Backups on page 1049.
1053
2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click SQL Redirection.
Restore job properties for redirected SQL sets Item Redirect Microsoft SQL Server sets Restore to server Description Select this checkbox to enable redirection of SQL backup sets.
To redirect this restore to a different server, type the target server name. You can redirect a full database backup to a different server or database; however, if the drive configuration is different from when the database backup was created, you must select either Default drive for restoring database files or Restore all database files to the target instances data location on the Restore Job Properties for SQL dialog box (see Restore Options for SQL 7.0 on page 1041).
1054
About Restoring SQL 7.0 Databases or Filegroups Restore job properties for redirected SQL sets (continued) Item Server logon account Description 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 by default. To use another logon account, click Change. For more information about logon accounts, see Using Backup Exec Logon Accounts for SQL 7.0 Resources on page 1027. If you are using SQL Server Authentication, use a Backup Exec logon account that stores the credentials of the SQL user account. Apply the Backup Exec logon account for the Windows user account to the Windows server that SQL is installed on, and then apply the logon account for the SQL user account to the SQL instance. To use another logon account, click Change. To remove the SQL logon account displayed in this field, click Clear. For more information about logon accounts, see Using Backup Exec Logon Accounts for SQL 7.0 Resources on page 1027. Restore to database To redirect the restore to a different database on the target server, type the target database name in this field; otherwise, leave the field blank. You can redirect a full database backup to a different server and/or database; however, if the drive configuration is different from when the database backup was created, you must select either Default drive for restoring database files or select Restore all database files to the target instances data location on the Restore Job Properties for SQL dialog box (see Redirecting Restores for SQL 7.0 on page 1053). If you are restoring a differential or log backup, and the associated database backup was restored to a different server, enter the new database name.
SQL logon account
SQL Agent
See also: Restoring Data on page 395 About Restoring SQL 7.0 Databases or Filegroups on page 1045
1055
Setting Default Backup and Restore Options for SQL 7.0

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 change backup and restore defaults for SQL: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click SQL.
1056

Options - Set Application Defaults for SQL Item Backup Backup method Full - Back up entire database or filegroup. Select this to back up the entire database or filegroup. See Backing Up SQL 7.0 Databases on page 1035. This option is selected by default. Log - Back up transaction log. Select this 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 7.0 Transaction Logs on page 1039. 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 7.0 Transaction Logs on page 1039. Differential - Back up database or filegroup changes only. Select this 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. See Backing Up SQL 7.0 Databases on page 1035. Description
SQL Agent
1057
Setting Default Backup and Restore Options for SQL 7.0 Options - Set Application Defaults for SQL (continued) Item Consistency check before backup Description Select a consistency check to run before a backup. None. Select this if you do not want a consistency check to run before a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged. Continue with backup if consistency check fails Select this checkbox to continue with the backup operation even if the consistency check fails. You may want to continue with the backup when the consistency check fails if you think that a backup of the database in its current state is better than no backup at all, or if you are backing up a very large database with only a small problem in a table. Select a consistency check to run after a backup. Because database transactions can occur during or after the consistency check, but before the backup runs, consider running a consistency check after the backup to ensure the data was consistent at the time of the backup. None. Select this if you do not want a consistency check to run after a backup. It is strongly recommended 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 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 to include indexes in the consistency check. Any errors are logged. Display filegroups when Select this checkbox if filegroups exist that you want to select for creating new backup jobs backup. If this checkbox is not selected, filegroups exist are not displayed as backup selections.
Consistency check after backup
1058
Setting Default Backup and Restore Options for SQL 7.0 Options - Set Application Defaults for SQL (continued) Item Restore Recovery completion state Leave database operational. No additional transaction logs can be restored (With Recovery). Select this when restoring the last database, differential, or log backups in the restore sequence in order to have the restore operation roll back all uncompleted transactions. After the recovery operation, the database is ready for use. If Leave database operational is not performed, the database is left in an intermediate state and is not usable. If Leave database operational is selected when an intermediate backup is being applied, you cannot continue to restore backups. You must restart the restore operation from the beginning. This option is selected by default. Leave database nonoperational but able to restore additional transaction logs (No Recovery). Select this option during a restore if you have additional differential or transaction log backups to be restored in another restore job. Leave database read-only and able to restore additional transaction logs (Standby). 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. Replace databases or filegroups Select this checkbox to replace a database or filegroup, even if another database or filegroup with the same name already exists on the server. If Replace databases or filegroups 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 the SQL 7.0 REPLACE option is not selected. Description
SQL Agent
1059
Setting Default Backup and Restore Options for SQL 7.0 Options - Set Application Defaults for SQL (continued) Item Consistency check after restore Description None. Select this if you are doing sequential restores. Do not run a consistency check after a restore until all sequential restores have been done. If a consistency check is selected during a restore, the restore will complete but the consistency check will not be done. Check the job log for this information. If you need to recover the database after restores are complete, select one of the following consistency checks when you select the Leave database operational option. Full check, excluding indexes. Select this 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 to include indexes in the consistency check. Any errors are logged. This option is selected by default.
1060
Preparing for Disaster Recovery of SQL 7.0

Backup Exec provides a quicker method for restoring SQL rather than running the Rebuild Master utility or reinstalling SQL. You can make copies of the master and model databases (as instructed in the following procedures), and then replace the corrupted or missing databases with those copies, and 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. You can then restart SQL, and restore the latest master database backup and any other databases that are necessary. To prepare for disaster recovery, do the following:
SQL Agent
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 master and model databases: on page 1062). Back up both system and user databases and transaction logs regularly. Back up the system drive that contains SQL. Backing up the system drive that SQL is on also backs up all the executables and registry settings needed for SQL to run.
Back up the master database whenever any changes are made to SQL. Keep records of any service packs that have been installed. Review Disaster Preparation of the Windows Computer on page 533 to make sure you are prepared to recover the entire server, not just SQL.
To perform a recovery, you will need:

The latest backup of the SQL directory (\Program Files\Microsoft SQL Server\MSSQL7), and the Windows registry. The most recent SQL database or filegroup backup, and the most recent (if any) differential and log backups. An Administrator logon account (or an Administrator equivalent) during the recovery.
1061
To create copies of the master and model databases: 1. Use the SQL Server Service Manager to stop the SQL services. 2. Open a command prompt window, and copy the original master and model databases and their transaction logs to the specified file names. In a default installation of SQL 7.0, the databases are in C:\MSSQL7\Data. Type the following: C:\ mssql7\data> copy master.mdf master$4idr C:\ mssql7\data> copy mastlog.ldf mastlog$4idr C:\ mssql7\data> copy model.mdf model$4idr C:\ mssql7\data> copy modellog.ldf modellog$4idr
1062
Disaster Recovery of SQL 7.0

You can restore either the entire server, including the SQL databases, from full system backups, or restore only the SQL databases to a newly installed or other available SQL server. Restoring the entire server including the SQL databases Restoring the entire server, including the SQL databases has the added benefit of recovering other applications and data that may have resided on the server at the time of failure, and can be accomplished using one of the following methods:
SQL Agent
Manual recovery of the Windows server, and then manual recovery of the SQL databases. This method involves manually restoring the Windows server from full system backups, and then recovering the SQL databases. The Intelligent Disaster Recovery Option. This option provides an automated method of restoring the Windows server as well as the SQL databases from full system backups. See Microsoft SQL Server Recovery Notes on page 909.
Restoring only the SQL databases
To restore only the SQL databases to a newly-installed or other available server, the server must be running on the same hardware platform (cross-platform restores are not supported), and the same version of SQL with the same service pack level as the original server. To restore SQL databases to an existing installation of SQL with other active databases, see Redirecting Restores for SQL 7.0 on page 1053.
1063
Manual Recovery of SQL 7.0

If necessary, restore the Windows computer by following the instructions in Manual Disaster Recovery of Windows Computers on page 540. 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 that replace the master and model databases and move them to the same directory that the original master and model databases are in. After the master and model databases are present on the SQL server, you must restart SQL, restore the master database with the Automate master database restore option, and then restore all other databases. Run the Rebuild Master utility (\MSSQL7\binn\rebuildm.exe) to rebuild the master database and start SQL. Reinstall SQL.
This topic only details how to restart SQL by using the copies of the master and model databases made by Backup Exec. For more information on the Rebuild Master utility, refer to your Microsoft SQL documentation. If you are restoring to a new SQL installation, start with To restore the master database: on page 1065.
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. 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. Open a command prompt window, and delete the original master and model databases and their transaction logs. Type the following: C:\ mssql7\data> del master.mdf mastlog.ldf model.mdf modellog.ldf
1064
3. Rename the copies of the databases back to their original names. Type the following: C:\ mssql7\data> rename master$4idr master.mdf C:\ mssql7\data> rename mastlog$4idr mastlog.ldf C:\ mssql7\data> rename model$4idr model.mdf C:\ mssql7\data> rename modellog$4idr modellog.ldf 4. Use the SQL Server Service Manager to start SQL. 5. Continue with the next procedure to restore the latest changes to the master database.
SQL Agent
To restore the master database: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. In the restore selections list, select the backup set containing the last master database backup. 4. On the Properties pane, under Settings, click SQL. 5. On the Restore Job Properties for SQL dialog box, select Automate master database restore. All existing users are logged off, and SQL Server is put into single-user mode. When this option is selected, only the master database can be restored; if this option is selected for any other data, 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 logon account used has administrator rights to the Windows server that the SQL instance is installed on. 6. Select a consistency check to run after the restore. 7. Start the restore job. After the restore, SQL is restarted in multi-user mode.
1065
8. Continue with the next procedure, restoring the remaining SQL databases.
Restore the remaining SQL databases: Note Do not select the master database for restore at this time. If you are restoring the SQL databases from filegroup backups, go to Restoring from SQL 7.0 Database Backups on page 1047. 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. Select all the backup sets that you want to apply, including the full backup, any differential backups, and any log backups. 4. On the Properties pane, under Settings, click SQL. 5. Select the option Leave database operational. No additional transaction logs can be restored. 6. Select the option Replace Databases or Filegroups. 7. In the Consistency Check After Database Restore field, select Full check, including indexes. 8. Start the restore job or select other options from the Properties pane. If the restore is being redirected, see Redirecting Restores for SQL 7.0 on page 1053. When all of the restore operations have completed successfully, then the recovery of the SQL databases is complete. After the recovery has been completed, it is strongly recommended that a full database backup be performed as soon as possible. See also: Restoring Data on page 395
1066
VERITAS Backup Exec - Agent for Microsoft Exchange Server
The VERITAS Backup Exec for Windows Servers - Agent for Microsoft Exchange Server (Exchange Agent) enables network administrators to perform backup and restore operations on installations of Exchange Server that are connected to a network. Exchange database backups can be integrated with network backups without separate administration or dedicated hardware. Continue reading for information about using the Exchange Agent with Exchange 2000 installations or for information about using the Exchange Agent with Exchange 5.5 installations, see About Using the Exchange Agent with Exchange 5.5 on page 1105. In Exchange 2000 installations, the Exchange Agent provides support for:

Exchange Agent
Selecting storage groups for backup and restore, or selecting one or more databases within the storage group for backup and restore. Increased performance of mailbox backups through: Incremental and differential backups. Individual mailbox backup and restore. The ability to globally exclude or include specified subfolders in each mailbox for backup and restore operations. Single-instance storage for message attachments. The ability to back up only a single instance of a message attachment.
Individual public folder backup and restore with the same capabilities that are available for mailbox backup and restore.
See also: Installing the Exchange Agent on page 1068 Backup Strategies for Exchange 2000 on page 1070 Recommended Configurations for Exchange 2000 Server on page 1073
1067
Requirements for Using the Exchange Agent with Exchange 2000
Requirements for Using the Exchange Agent with Exchange 2000

The following are required for the Exchange Agent in an Exchange 2000 installation:

The media server must have access to the Exchange Server. To use Backup Exec's Resource Discovery feature, which allows detection of new backup resources within a Windows domain, you must install Microsoft's Exchange System Manager utility on the media server. The media server must be running Windows 2000.
See also: Using Resource Discovery to Search for New Resources on page 295
Installing the Exchange Agent

The VERITAS Backup Exec Agent for Microsoft Exchange Server is installed as a separate, add-on component of Backup Exec for Windows Servers, and can be installed locally or remotely to back up Exchange Server databases. Whenever the Exchange Agent is installed on the media server, the Backup Exec Remote Agent is included as part of the Exchange Agent installation. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server that you want to back up. You cannot select resources from a remote server for backup until a Remote Agent has been installed. If you are using the Exchange Agent to protect databases on the local media server only, you are entitled to install the Remote Agent that was included with the Exchange Agent installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the Exchange Agent is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to install it on another Windows server. For instructions on installing the Exchange Agent on the local media server, see Installing Backup Exec Options on a Local Server on page 49. For instructions on installing the Exchange Agent on a remote resource, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
1068
Using Backup Exec Logon Accounts with Exchange 2000 Resources
Using Backup Exec Logon Accounts with Exchange 2000 Resources

In order to back up and restore Exchange Server resources, you must use a Backup Exec logon account that stores the credentials of a user account that has local administrator rights on every Exchange server that you want to back up. In order to back up and restore individual Exchange mailboxes and public folders, use Microsofts System Manager utility to grant the Exchange Administrator role to the user account at the Administrative Group level (for all Administrative Groups if there is more than one). Additionally, Backup Exec must have access to a uniquely named mailbox within the Exchange organization. When selecting mailboxes or public folders for backup, Backup Exec will attempt to find a mailbox with the same name as the username stored in the Backup Exec logon account used to connect to the Exchange server. If you use a Backup Exec logon account that stores the credentials of a user account that is unique and has a corresponding mailbox of the same name, then you are not prompted for an additional logon account when selecting mailboxes or public folders. 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 is one that does not exist in the organization as a subset of characters in another mailbox name. For example, if EXCH1 has been entered as the mailbox name, and there are other mailbox names such as EXCH1BACKUP, or BACKUPEXCH1, then Backup Exec will not accept the name and you are prompted to choose another mailbox name. If you cannot create a unique mailbox name, you must create a Backup Exec logon account and enter the fully qualified name in the username field of the logon account. For example: /O=Company/OU=Orlando/CN=Test/CN=EXCH1 See also: Backing Up Exchange 2000 Mailboxes and Public Folders on page 1080 Configuring Logon Accounts on page 347
Exchange Agent
Appendix H, VERITAS Backup Exec - Agent for Microsoft Exchange Server
1069
Backup Strategies for Exchange 2000

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, down to 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 not only recover from the full backup but from each incremental backup as well.
What will work best for you is based on the size of your environment, number of transactions processed each day, and the expectations of your users when a recovery is required. Consider the following backup strategies:

Full backups run as frequently as possible, no less than once a day. Full backups daily with differential backups used at regular periods throughout the day. Full backups every few days (no less than weekly) with frequent incremental backups in between each full backup.
1070
We strongly recommend that in addition to backing up Exchange storage groups, you also back up the following on a regular basis:
Backup selections for Exchange 2000 configuration data Recommended backup selections for configuration data File system Description
Back up folders and drives containing files for Windows and Exchange. Usually, this is the root drive C:\ and the virtual drive created by Exchange during installation, which by default is M:\ but may be different in each environment. Note Back up the C:\ drive, but do not back up the virtual drive created by Exchange. It is intended only to provide Explorer access to the Exchange data, but all files system functions may not be replicated. Backup and restore operations are not recommended or supported. As a general practice, we recommend that you exclude the Exchange database and log files from the file system backup. The .EDB files, as well as any active .LOG files, are not backed up when the file system is backed up because they are opened for exclusive use by the Exchange system. These files appear as in use - skipped during the file system backup; however, these files are backed up when the Exchange databases are selected for backup.
Exchange Agent
Windows NT registry System State
For Windows NT, 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 Active Directory For more information on backing up System State, see Selecting Data to Back Up on page 259. If the entire server must be restored, you must restore System State to the server before you can restore Exchange 2000.
Key Management Back up the Key Management Service database by selecting the KMS Service (KMS) database icon in Backup Selections, and then running a full backup. Local or remote backups can be performed on the KMS database. Site Replication Services (SRS) database If Exchange 2000 is running in an Exchange 5.5 environment, back up the Site Replication Services (SRS) database by selecting the SRS icon in Backup Selections, and then running a full backup. This data is used for interoperability with Exchange 5.5.
1071
Backup Strategies for Exchange 2000 Backup selections for Exchange 2000 configuration data (continued) Recommended backup selections for configuration data Active Directory Description
To back up Active Directory, select System State on the domain controllers and run a full backup. When there are configuration changes on Exchange 2000, 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.
Mailboxes and public folders
When you back up the Exchange server databases, mailboxes and public folders are included in the backup. However, to make restores easier, you can also select one or more mailboxes or public folders for backup separately from the databases. You can also enable features in Backup Exec to make mailbox and public folder backups faster. See Recommendations for backing up Exchange 2000 mailboxes and public folders on page 1081.
See also: Backup Options for Exchange 2000 on page 1074 Backing Up Exchange 2000 on page 1078 Backing Up Exchange 2000 Mailboxes and Public Folders on page 1080 Setting Default Backup and Restore Options for Exchange 2000 on page 1097 Preparing for Disaster Recovery of Exchange 2000 on page 1101
1072
Recommended Configurations for Exchange 2000 Server

Before starting backups for Exchange, read the following recommendations for configuring Exchange 2000 in order to make it easier to recover using the backups:
Avoid making the Exchange Server a domain controller. For disaster recovery purposes, it is much easier to restore Exchange if you dont have to first restore the Active Directory. Install Exchange into a domain that has at least two domain controllers. 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. Locate transaction log files on a separate physical disk from the database. This is the single most important configuration affecting the performance of Exchange. This configuration also has recovery implications, since transaction logs provide an additional recovery resource.
Exchange Agent
Disable Write Cache on the SCSI controller. Windows does not use buffers, so when Exchange (or other applications) 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. Disable circular logging if possible. 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.
See also: Reviewing Circular Logging for Exchange 2000 on page 1079
1073
Backup Options for Exchange 2000

This procedure details how to select backup job options for Exchange Server and provides definitions for Exchange backup options. For details on how to create a backup job, and for definitions of all other backup options, see Backing Up Data on page 233.
To select backup job properties for Exchange 2000 Server: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click Exchange.
1074

Backup job properties for Exchange Server Item Exchange server backup method Description FULL - Database & Logs (flush committed logs). Select this 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 that have all transactions committed to the database are then deleted. This option is selected by default. COPY - Databases & Logs. Select this 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 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from differential backups, the last differential backup and the last full backup are required. INCREMENTAL - Logs (flush committed logs). Select this 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from incremental backups, the last full backup and all incremental backups done since are required. Guide Me Click Guide Me to start a wizard that helps you choose backup job properties for backing up Exchange 2000.
Exchange Agent
1075
Backup Options for Exchange 2000 Backup job properties for Exchange Server (continued) Item Mailbox backup method Description FULL - Back up messages. Reset archive bit. Select this to back up all messages in the selected mailboxes. This option is set by default. A time/date stamp placed in each folder indicates the messages have been backed up. COPY - Back up messages. Select this 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 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 placed on the folders during the last full backup is used to determine which messages have been modified since, but the time/date stamp is not updated during the differential backup. INCREMENTAL - Back up changed messages. Reset archive bit. Select this 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 placed on the folders during the last full or incremental backup is used to determine which messages have been modified since, and the time/date stamp is updated during the differential backup.
1076
Backup Options for Exchange 2000 Backup job properties for Exchange Server (continued) Item Enable single instance backup for message attachments (for mailbox and public folder backups only) Description Select this 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 and 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. Disable this option if you want each identical copy of a message attachment backed up and kept in order on the backup set.
Caution If the backup job does not run to completion, the message attachments 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 messages and attachments. You must run a full or copy backup to ensure that all messages and attachments are backed up completely.
Guide Me Click Guide Me to start a wizard that helps you choose backup job properties for recreating user accounts and mailboxes.
Exchange Agent
See also: Backing Up Exchange 2000 on page 1078 Backing Up Exchange 2000 Mailboxes and Public Folders on page 1080 Reviewing Circular Logging for Exchange 2000 on page 1079
1077
Backing Up Exchange 2000

To back up Exchange Server 2000, you can select:

Multiple storage groups Individual storage groups Individual databases (not recommended)
We recommend that you select individual storage groups for backup rather than selecting individual databases in storage groups. While 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.
To back up Exchange storage groups: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069. 3. To select Exchange data from local or remote selections, click the domain name icon or icons that contain the Exchange installations, and then click the actual Windows computer icon that contains the Exchange installation. If you are using a server cluster, make backup selections from the virtual server. A list of shared network directories appears, along with an icon that represents the Exchange installation. To select all storage groups in Exchange, click the checkbox preceding the Microsoft Information Store, or you can select specific storage groups by expanding the Exchange icon, and then individually selecting storage groups.
1078
4. To select the Exchange server backup method, on the Properties pane, under Settings, click Exchange. For details on these options, see Backup Options for Exchange 2000 on page 1074. Note To perform incremental and differential backups of storage groups, make sure that circular logging is not enabled on the storage group. 5. Select other backup options from the Properties pane or start the backup job. See also: Backup Strategies for Exchange 2000 on page 1070 Backing Up Exchange 2000 Mailboxes and Public Folders on page 1080 Reviewing Circular Logging for Exchange 2000 on page 1079 Backing Up Data on page 233
Reviewing Circular Logging for Exchange 2000

Exchange Agent
When circular logging is enabled, incremental and differential backups of Exchange databases and storage groups cannot be performed because these types of backups rely on a complete history of logs. When circular logging is enabled, transaction log files that have already been committed to the database are overwritten, preventing the accumulation of logs. The log files are overwritten whether or not a full or incremental backup has been run, and a history of previous logs since the last full or incremental backup is not maintained. When circular logging is disabled, transaction log files accumulate on the disk until a full or incremental backup is performed, after which the log files that have all transactions committed to the database are deleted.
To review the circular logging setting for Exchange 2000: 1. Open the Exchange System Manager utility. 2. Expand the tree to the storage group for which you want to review the circular logging setting. 3. Right-click the storage group and choose Properties.
1079
Backing Up Exchange 2000 Mailboxes and Public Folders
4. On the General tab, review the Enable circular logging setting. 5. If you want to perform incremental and differential backups on databases, make sure that circular logging is not enabled. See also: Backup Strategies for Exchange 2000 on page 1070

Mailboxes and public folders are already included in the Exchange server database backups, but if you want to make the restore of a mailbox or folder easier, you can also select one or more mailboxes or public folders for backup separately from the databases. Although mailbox backups will take longer to run than database backups, you can enable features in Backup Exec to make mailbox and public folder backups faster. These features are described in Recommendations for backing up Exchange 2000 mailboxes and public folders on page 1081. 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 - only from backups of the Information Store. Consider using the Exchange System Manager utility to adjust the deletion settings in each Stores properties so that deleted items are retained for a period of time, allowing them to be recovered rather than restored. See your Microsoft Exchange Server documentation for details.
1080
To obtain the most efficiency and greatest performance in mailbox and public folder backups, consider the following:
Recommendations for backing up Exchange 2000 mailboxes and public folders Recommendation Description
Use full and incremental Consider running full backups of mailboxes or public folders on a backups regular basis, supplemented with incremental or differential backups throughout your schedule to keep backup run time to a minimum. Exclude unwanted or unnecessary folders from the backup When you select a mailbox or public folder for backup, by default all folders and subfolders are included. You can easily exclude specific folders and subfolders from the backups by using the ** wildcard in the file selection path on the Advanced File Selection dialog box when making backup selections (see Including or Excluding Files for Backup Using Advanced File Selection on page 262). 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\* If you also want to exclude all subfolders of the specified folders from the backup, check the Include Subfolders checkbox in the Advanced File Selection dialog. Use single-instance storage 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, and 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.
Exchange Agent
1081
Backing Up Exchange 2000 Mailboxes and Public Folders Recommendations for backing up Exchange 2000 mailboxes and public folders (continued) Recommendation Do not back up special system mailboxes created by Exchange Description While these special system mailboxes can be backed up, it is not necessary or useful. The following are common examples of special system mailboxes, but there may be others depending on the Exchange 2000 server configuration and environment. System Attendant Any mailbox name starting with SMTP or System Mailbox Also, when selecting objects from the mailbox tree, all objects are displayed as messages. Some non-message objects can be identified by the subject line. For example, if you create a Calendar event named Appointment1, that name is displayed in the subject line for that object. However, some objects such as Forms and Views do not have a subject line (even though they can be named) and may not be easily identifiable. Select public folders The same public folders may be displayed for multiple Exchange from only one Exchange servers since public folders can be replicated. Selecting public folders server. on multiple Exchange servers will only increase the time and media required for the backup and does not provide any additional protection.
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, however, may be displayed on more than one server since public folders can be replicated to many servers. Note 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 created using a site-centric view. If the mailboxes are all selected from the same server, they are placed together in one backup set on the storage media. If the mailboxes are selected from more than one server, then the mailboxes are placed in separate backup sets according to the server.
To back up Exchange mailboxes or public folders: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections.
1082
3. To select Exchange mailboxes or public folders from local or remote selections, click the domain name icon or icons that contain the Exchange mailboxes, and then click the actual Windows computer icon that contains the Exchange mailboxes. If you are using a server cluster, make backup selections from the virtual server. 4. Expand the Microsoft Exchange Mailbox icon that contains the mailboxes or public folders you want to back up. You can select all mailboxes or individual messages, mailboxes, and folders 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.
Exchange Agent
1083
5. If prompted, select a logon account that will allow you to connect to the Exchange mailboxes or public folders. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069. 6. To select the mailbox or public folders backup method, on the Properties pane, under Settings, click Exchange. For details on these options, see Backup Options for Exchange 2000 on page 1074. 7. Select other backup options from the Properties pane or start the backup job. See also: Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069 Recommendations for backing up Exchange 2000 mailboxes and public folders on page 1081 Backing Up Data on page 233
1084
Restore Options for Exchange 2000

This procedure details how to select restore job properties for Exchange 2000 and provides definitions for Exchange 2000-specific restore options. For details on how to create a restore job, and for definitions of all other restore jobs, see Restoring Data on page 395.
To select restore job properties for Exchange 2000: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click Exchange.
Exchange Agent
1085

Restore job properties for Exchange 2000 Item Exchange Server options Automatically recreate user accounts and mailboxes Select this checkbox to recreate the user accounts and their mailboxes if they do not already exist on the target server. Otherwise, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this checkbox is selected, the password you entered on the Exchange Options - Set Application Defaults dialog box is used as the password for accounts that are recreated. To change the password, on the Tools menu click Options, and then in the Properties pane under Job Defaults, click Exchange. Select Automatically recreate user accounts and mailboxes, and then click Change password. Note This option 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. Exchange 2000 No loss restore (do not delete existing transaction logs) Select this checkbox to preserve the existing transaction logs on the Exchange 2000 server. Transaction logs from the storage media are then restored and added to the existing set of transaction logs on the Exchange 2000 server. When the restore operation finishes, Exchange 2000 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 checkbox should be selected. If this checkbox is not selected, uncommitted transactions for other databases in the storage group may be lost. Description
1086
Restore Options for Exchange 2000 Restore job properties for Exchange 2000 Item Temporary location for log and patch files Description 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. Commit after restore completes If your selection contains the last backup set to be restored, select this checkbox to direct 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 selected 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). Mount database after restore Select this checkbox to mount the database so that it is available to users. This checkbox 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 2000.
Exchange Agent
Guide Me
See also: Restoring Exchange 2000 Mailboxes and Public Folders on page 1089
1087
Restoring Exchange 2000
Restoring Exchange 2000

Following are requirements for restoring Exchange 2000:

Use the Exchange System Manager utility to dismount any databases that are being restored. Check the temporary location for log and patch files to make sure it is empty before you starting the restore. 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.
Before starting the restore job, review Restoring Data on page 395 for information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs.
To restore Exchange 2000 databases: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. In the restore selections list, select the backup sets you want to restore. Restore the last full backup, or Restore the last full backup and the last differential backup, or Restore the last full backup and all subsequent incremental backups.
4. On the Properties pane, under Settings, click Exchange. 5. Select the appropriate options. For details, see Restore Options for Exchange 2000 on page 1085. Do not select the Commit after restore completes checkbox and the Mount database after restore checkbox on the Restore Job Properties dialog box for Exchange unless your selections include the last backup set to be restored. These selections direct the Exchange server to replay transactions, roll back uncommitted transactions, and mount the databases to make them available for use after the restore.
1088
Restoring Exchange 2000 Mailboxes and Public Folders
6. Start the restore job or select other restore options from the Properties pane. 7. Run a full backup of the restored databases. See also: Restoring Data on page 395 Backing Up Data on page 233 Restoring Exchange 2000 Mailboxes and Public Folders on page 1089 Redirecting Exchange 2000 Storage Group and Database Restores on page 1091 Redirecting Mailbox and Public Folder Restores in Exchange 2000 on page 1093

How you restore mailbox or public folder data depends on the types of backup used to protect the data, and the type of data you want restored. You can restore individual mailboxes, messages, and public folders from backup sets created when individual mailboxes were backed up from the Microsoft Exchange Mailboxes selection, or when individual public folders were backed up from the Microsoft Exchange Public Folders selection. You cannot restore individual mailboxes, messages, or public folders from storage group or database backups. If you need to restore mailboxes that have been deleted back to their original location, you can choose to have the user account and mailbox automatically recreated. A password that you specify is assigned to the recreated user account. If the mailbox restore is being redirected, the mailbox must already exist on the target server. Following are notes about restoring mailboxes or public folders:
Exchange Agent
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 will restore normally. Mailboxes that resided on other servers must be redirected to those servers.
If you restore mailboxes from a backup created with a version of Backup Exec prior to 8.5, and mailboxes with duplicate Display Names reside on the server, select those mailboxes for restore separately and follow the instructions in Redirecting Mailbox and Public Folder Restores in Exchange 2000 on page 1093.
1089
When messages in mailboxes or public folders are restored to a location where a message with the same name already exists, the restored message does not replace the existing message, but is added to the destination folder; therefore, duplicate messages may result in the destination folder. The option Restore Over Existing Files in the Advanced Restore Job Properties does not apply to mailboxes or public folders. If other selections are restored in addition to mailboxes or public folders, and the option Restore Over Existing Files is selected, it applies only to the other selections; mailboxes and public folders are not restored over existing objects. For details on this option, see General settings options for restore job on page 409. 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 2000 server configuration and environment. System Attendant Any mailbox name starting with SMTP or System Mailbox
To restore Exchange mailboxes and public folders: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. In the restore selections list, navigate to and select the data you want to restore. 4. On the Properties pane, under Settings, click Exchange. On the Restore Job Properties dialog box, if the user accounts and their mailboxes that are being restored do not already exist on the target server, and they are being restored to their original location, select Automatically recreate user accounts and mailboxes. If this option is not selected, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this checkbox is selected, the password entered on the Exchange Options - Set Application Defaults dialog box is used as the password for accounts that are recreated. To change the password, on the Tools menu click Options, and then in the Properties pane under Job Defaults, click Exchange. Select Automatically recreate user accounts and mailboxes, and then click Change password.
1090
5. Start the restore job or select other restore options from the Properties pane. 6. After the restore is complete, run a full backup of the restored mailboxes. See also: Restore Options for Exchange 2000 on page 1085 Redirecting Mailbox and Public Folder Restores in Exchange 2000 on page 1093
Redirecting Exchange 2000 Storage Group and Database Restores

Following are requirements for redirecting restores:

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 target server must have the same Organization and Administrative Group name as the source server. The target 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.
Exchange Agent
You cannot redirect the restore of:

A version of Exchange server database to a different version of the database. 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.
Before starting the restore job, review Restoring Data on page 395 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.
To redirect a restore of storage groups or databases: 1. Follow the instructions for the restore in Restoring Exchange 2000 on page 1088. 2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Exchange Redirection.
1091
3. Select the appropriate options as follows, and then start the redirected restore job or select other restore options from the Properties pane. After completing the restore, it is recommended that a full backup of the restored databases be performed.
Restore job properties for redirected Exchange sets Item Redirect Exchange sets Description Select this checkbox to enable the Restore to server and Server logon account fields. Type the name of the computer to which you are restoring, using the format \\server name. To restore to a server, use a Backup Exec logon account that stores the credentials of a Windows user account. The default logon account is displayed by default. To use another logon account, click Change. For more information about logon accounts, see Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069.
Restore to server
Server logon account
1092
Redirecting Mailbox and Public Folder Restores in Exchange 2000

You can redirect the restore of individual mailboxes and public folders from backup sets created when individual mailboxes were backed up from the Microsoft Exchange Mailboxes selection, or when individual public folders were backed up from the Microsoft Exchange Public Folders selection. You cannot restore individual mailboxes or public folders from storage group or database backups. If you select a single mailbox, or one or more messages or folders from a single mailbox, you can redirect that restore to another existing mailbox on the same or a different server. If any of the folders in the original mailbox do not exist in the destination mailbox, they will be created during the restore. If you select more than one mailbox, or folders and messages from more than one mailbox, you can only redirect the restore to another server. Mailboxes with the same names as those selected must already exist on the target server. Following are requirements for redirecting the restore of mailboxes:
If the mailboxes 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 on the server that you are redirecting messages or mailbox restores to, click the destination server in the backup selections list, select Microsoft Exchange Mailboxes and verify that the target mailbox is displayed in the list of mailboxes. If you are prompted for a logon account, use a logon account that stores the credentials of a user account that is unique and has a corresponding mailbox of the same name. See Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069. 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]).
Exchange Agent
1093
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, if you back up Mailbox 1, which consists of Top of Information Store, Inbox, and Folders 1 and 2, each containing some mail messages, and then you restore Mailbox 1 to the existing Mailbox 2, then all of Mailbox 1, including the Top of Information Store, Inbox, Folders 1 and 2, and messages, are restored to Mailbox 2. Note that Mailbox 1 itself is not created under Mailbox 2.
Redirecting the restore of Mailbox 1 to Mailbox 2
1094
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.
Redirecting Mailbox 1\Top of Information Store\Folder 2 to Mailbox 2
Exchange Agent
To redirect a mailbox restore: 1. Follow the instructions for the restore in Restoring Exchange 2000 Mailboxes and Public Folders on page 1089. 2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Exchange Redirection. 3. Select the appropriate options as follows, and then start the redirected restore job or select other restore options from the Properties pane. After completing the restore, it is recommended that a full backup of the restored mailboxes be performed.
Restore job properties for redirected Exchange sets Item Redirect Exchange sets Description Select this checkbox to enable the Restore to server and Server logon account fields. Type the name of the computer to which you are restoring, using the format \\server name. 1095
Restore to server
Restoring Exchange 2000 Mailboxes and Public Folders Restore job properties for redirected Exchange sets (continued) Item Server logon account Description To restore to a server, use a Backup Exec logon account that stores the credentials of a Windows user account. The default logon account is displayed by default. To use another logon account, click Change. For more information about logon accounts, see Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069. Type the name of the target mailbox exactly as it appears when browsing to the mailbox in the backup selections pane, including the brackets surrounding the mailbox directory identifier (for example, Mailbox Name [mailboxname]). The mailbox must already exist before you can restore to it. See Redirecting Mailbox and Public Folder Restores in Exchange 2000 on page 1093. To restore a mailbox or public folder, use a Backup Exec logon account that stores the credentials of the mailbox user account. To use another logon account, click Change. To clear the displayed logon account and use the same logon account specified in the Server logon account field, click Clear. For more information about logon accounts, see Using Backup Exec Logon Accounts with Exchange 2000 Resources on page 1069.
Restore to mailbox
Mailbox logon account
1096
Setting Default Backup and Restore Options for Exchange 2000

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. You can also change the defaults for any specific backup or restore job.
To change backup and restore defaults for Exchange 2000: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Exchange.
Exchange Agent
1097

Options - Set Application Defaults for Exchange 2000 Item Backup Exchange method FULL - Database & Logs (flush committed logs). Select this 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 that have all transactions committed to the database are then deleted. This option is selected by default. COPY - Databases & Logs. Select this 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 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from differential backups, the last differential backup and the last full backup are required. INCREMENTAL - Logs (flush committed logs). Select this 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from incremental backups, the last full backup and all incremental backups done since are required. Description
1098
Setting Default Backup and Restore Options for Exchange 2000 Options - Set Application Defaults for Exchange 2000 (continued) Item Mailbox method: Description FULL - Back up messages. Reset archive bit. Select this to back up all messages in the selected mailboxes. This option is set by default. A time/date stamp placed in each folder indicates the messages have been backed up. COPY - Back up messages. Select this 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 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 placed on the folders during the last full backup is used to determine which messages have been modified since, but the time/date stamp is not updated during the differential backup. INCREMENTAL - Back up changed messages. Reset archive bit. Select this 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 placed on the folders during the last full or incremental backup is used to determine which messages have been modified since, and the time/date stamp is updated during the differential backup.
Exchange Agent
1099
Setting Default Backup and Restore Options for Exchange 2000 Options - Set Application Defaults for Exchange 2000 (continued) Item Enable single instance backup for message attachments (for mailbox and public folder backups only) Description Select this 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 and 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. Disable this option if you want each identical copy of a message attachment backed up and kept in order on the backup set.
Restore - Exchange 2000 Temporary location for log and patch files Type a location where the associated log and patch files are to be kept until the database is restored. The default location is \temp. If storage groups are being restored, a subdirectory in \temp is created for each storage group. The log and patch files for each storage group are kept in the corresponding subdirectory. If Commit after restore completes is selected for the restore job, the log and patch files in the temporary location are applied to the database, and then the current log files are applied. After the restore is complete, the log and patch files are automatically deleted from the temporary location (including any subdirectories). To select Commit after restore completes, on the navigation bar, click Restore, and then on the Properties pane, under Settings, click Exchange. Note Make sure the temporary location for log and patch files is empty before you start a restore job. If a restore job fails, check the temporary location (including subdirectories) to make sure any previous log and patch files from a previous restore job were deleted.
1100
Preparing for Disaster Recovery of Exchange 2000 Options - Set Application Defaults for Exchange 2000 (continued) Item Automatic recreation Automatically recreate user accounts and mailboxes Select this checkbox to recreate the user accounts and their mailboxes if they do not already exist on the target server. Otherwise, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this checkbox is selected, the password you entered on the Exchange Options - Set Application Defaults dialog box is used as the password for accounts that are recreated. To change the password, see To restore Exchange mailboxes and public folders: on page 1090. Note This option 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. Description
Exchange Agent
Change password...
Click this to specify a password to use when user accounts and mailboxes are automatically recreated on the target server.
See also: Restoring Exchange 2000 on page 1088
Preparing for Disaster Recovery of Exchange 2000

A disaster preparation plan is an absolute necessity for restoring Exchange efficiently and effectively in the event of a catastrophic failure. Because Exchange uses Windows security for authentication, disaster recovery of Exchange cannot be separated from the disaster recovery of Windows. Planning ahead reduces the time needed to recover. It is critical to build a kit that includes items such as:

An operating system configuration sheet A hard drive partition configuration sheet Any RAID configuration A hardware configuration sheet EISA/MCA configuration disks An Exchange configuration sheet
1101
Disaster Recovery for Exchange 2000
A Windows emergency repair diskette
To perform the actual recovery, you will need:

An installed copy of Backup Exec for Windows Servers The latest full, incremental, and differential backups of the Exchange databases you want to recover The Microsoft Exchange Server Installation CD Any service packs which were applied to the original installation

This procedure guides you through a complete restoration of Exchange 2000 using Backup Exec. You should have already performed all the appropriate preparation as detailed in Preparing for Disaster Recovery of Exchange 2000 on page 1101. 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 Microsoft Exchange 2000 Server documentation for details on recovering those databases. Always log in to Windows using the Administrator account (or an Administrator equivalent) during this procedure. If you purchased the Intelligent Disaster Recovery option, see Microsoft Exchange Recovery Notes on page 909 for directions on using Intelligent Disaster Recovery to recover the Exchange server.
To perform disaster recovery for an Exchange 2000 Server: 1. Recover the Windows server first. For instructions, see Disaster Preparation of the Windows Computer on page 533. Note Make sure you restore the Exchange 2000 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 2000 server. 2. From the Services applet, verify the Microsoft Exchange Information Store service is started. 3. Start Backup Exec.
1102
4. Catalog the media that contains the latest full, incremental, and differential backups of the Exchange 2000 storage groups you want to recover. 5. On the navigation bar, click Restore. 6. On the Properties pane, under Source, click Selections. 7. Select the latest full backups of each storage group for restore. Note 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. 8. 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. 9. On the Properties pane, under Settings, click Exchange.
Exchange Agent
10. Clear the Exchange 2000 option No loss restore (do not delete existing transaction logs). 11. In the field Temporary location for log and patch files, type a location where the associated log and patch files are to be kept until the database is restored. Note Make sure the temporary location for log and patch files is empty before you start a restore job. If a restore job fails, check the temporary location (including subdirectories) to make sure any previous log and patch files from a previous restore job were deleted. 12. If your selection contains the last backup set to be restored, select Commit after restore completes. Do not select this checkbox if you still have backup sets to restore. If Commit after restore completes is selected 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).
1103
13. If you want the databases to be immediately available to users after the recovery, select Mount database after restore. This checkbox is only available if Commit after restore completes is selected. 14. Start the restore job or select other restore options on the Properties pane. 15. After completing the restore, it is recommended that a full backup of the restored databases be performed.
1104
About Using the Exchange Agent with Exchange 5.5
About Using the Exchange Agent with Exchange 5.5

The Exchange Agent enables network administrators to perform backup and restore operations on installations of Exchange Server 5.5 that are connected to a network. Exchange database backups can be integrated with network backups without separate administration or dedicated hardware. Continue reading for information about using the Exchange Agent with Exchange 5.5 installations, or for information about using the Exchange Agent with Exchange 2000 installations, see VERITAS Backup Exec - Agent for Microsoft Exchange Server on page 1067. In Exchange 5.5 installations, the Exchange Agent provides support for:
Increased performance of mailbox backups through: Incremental and differential backups. Individual mailbox backup and restore. The ability to globally exclude or include specified subfolders in each mailbox for backup and restore operations.
Exchange Agent
The ability to back up only a single instance of a message attachment.
Individual public folder backup and restore with the same capabilities that are available for mailbox backup and restore.
See also: Installing the Exchange Agent on page 1106 Recommended Configurations for Exchange 5.5 Server on page 1109 Backup Strategies for Exchange 5.5 on page 1107
Requirements for Using the Exchange Agent with Exchange 5.5

The following are required for the Exchange Agent in an Exchange 5.5 installation:

The media server must have access to the Exchange Server. To use Backup Exec's Resource Discovery feature, which allows detection of new backup resources within a Windows domain, you must install Microsoft's Exchange Administrator utility on the media server.
See also: Using Resource Discovery to Search for New Resources on page 295
1105

The VERITAS Backup Exec Agent for Microsoft Exchange Server is installed as a separate, add-on component of Backup Exec for Windows Servers, and can be installed locally or remotely to back up Exchange Server databases. Whenever the Exchange Agent is installed on the media server, the Backup Exec Remote Agent is included as part of the Exchange Agent installation. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server that you want to back up. You cannot select resources from a remote server for backup until a Remote Agent has been installed. If you are using the Exchange Agent to protect databases on the local media server only, you are entitled to install the Remote Agent that was included with the Exchange Agent installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the Exchange Agent is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to install it on another Windows server. For instructions on installing the Exchange Agent on the local media server, see Installing Backup Exec Options on a Local Server on page 49. For instructions on installing the Exchange Agent on a remote resource, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823.
Using Backup Exec Logon Accounts with Exchange 5.5 Resources

In order to back up and restore Exchange Server resources, you must use a Backup Exec logon account that stores the credentials of a user account that has local administrator rights on every Exchange server that you want to back up. In order to back up and restore individual Exchange mailboxes and public folders, use Microsofts Exchange Administrator utility to grant the Admin role to the user account at the Site level (for all Sites if there is more than one). Additionally, Backup Exec must have access to a uniquely named mailbox within the Exchange organization. When selecting mailboxes or public folders for backup, Backup Exec will attempt to find a mailbox with the same name as the username stored in the Backup Exec logon account used to connect to the Exchange server. If you use a Backup
Backup Strategies for Exchange 5.5
Exec logon account that stores the credentials of a user account that is unique and has a corresponding mailbox of the same name, then you are not prompted for an additional logon account when selecting mailboxes or public folders. 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 is one that does not exist in the organization as a subset of characters in another mailbox name. For example, if EXCH1 has been entered as the mailbox name, and there are other mailbox names such as EXCH1BACKUP, or BACKUPEXCH1, then Backup Exec will not accept the name and you are prompted to choose another mailbox name. If you cannot create a unique mailbox name, you must create a Backup Exec logon account and enter the fully qualified name in the username field of the logon account. For example: /O=Company/OU=Orlando/CN=Test/CN=EXCH1 See also: Backing Up Exchange 5.5 on page 1114 Backing Up Exchange 5.5 Mailboxes and Public Folders on page 1115 Configuring Logon Accounts on page 347
Exchange Agent

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, down to the individual database, mailbox, message, or 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 not only recover from the full backup but from each incremental backup as well.
1107
What will work best for you will be based on the size of your environment, number of transactions processed each day, and the expectations of your users when a recovery is required. For fastest recoveries, consider the following backup options listed in recovery priority sequence:

Full backups run as frequently as possible, no less than once a day. Full backups daily with differential backups used at regular periods throughout the day. Full backups every few days (no less than weekly) with frequent incremental backups in between each full backup.
You should also read about best practices for configuring Exchange to provide the fastest and safest recovery in Recommended Configurations for Exchange 5.5 Server on page 1109. In addition to the Information Store and Directory Store, we strongly recommend that you also back up the following on a regular basis:
Backup selections for Exchange 5.5 configuration data Recommended backup selections for configuration data File system Description
Back up folders and drives containing files for Windows and Exchange. Usually, these are on drive C:\ unless a different location was specified during installation. For Windows NT, back up the registry by running a full backup of the \WINNT directory. For Windows 2000, back up the registry by selecting System State and running a full backup.
Windows registry
Key Management To back up the KMS database, stop the Key Management Server service Service (KMS) database if it is running, and then back up the contents of the directory stored in EXCHSRVR\KMSdata. This directory contains security data that includes encryption keys needed to decipher encrypted mail messages. Without these keys, all previously encrypted messages cannot be opened by recipients. Directory Store for each The Directory Store for each Exchange Server is unique, so it is critical Exchange Server to have a backup of the Directory Store for each Exchange Server.
1108
Recommended Configurations for Exchange 5.5 Server

Before starting backups for Exchange, read the following recommendations for configuring Exchange 5.5 in order to make it easier to recover using the backups:
Locate transaction log files on a separate physical disk from the database. This is the single most important configuration affecting the performance of Exchange. This configuration also has recovery implications, since transaction logs provide an additional recovery resource. Disable Write Cache on the SCSI controller. Windows does not use buffers, so when Exchange (or other applications) 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. Disable circular logging if possible. 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 databases are disabled, and recovery is only possible up to the point of the last full or copy backup.
Exchange Agent
See also: Reviewing Circular Logging for Exchange 5.5 on page 1115
1109
Backup Options for Exchange 5.5

This procedure details how to select backup job options for Exchange Server and provides definitions for Exchange backup options. For details on how to create a backup job, and for definitions of all other backup options, see Backing Up Data on page 233.
To select backup job properties for Exchange 5.5 Server: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click Exchange.
1110

Backup job properties for Exchange Server Item Exchange server backup method Description FULL - Database & Logs (flush committed logs). Select this 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 that have all transactions committed to the database are then deleted. This option is selected by default. COPY - Databases & Logs. Select this 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 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from differential backups, the last differential backup and the last full backup are required. INCREMENTAL - Logs (flush committed logs). Select this 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from incremental backups, the last full backup and all incremental backups done since are required. Guide Me Click Guide Me to start a wizard that helps you choose backup job properties for backing up Exchange 5.5.
Exchange Agent
1111
Backup Options for Exchange 5.5 Backup job properties for Exchange Server (continued) Item Mailbox backup method Description FULL - Back up messages. Reset archive bit. Select this to back up all messages in the selected mailboxes. This option is set by default. A time/date stamp placed in each folder indicates the messages have been backed up. COPY - Back up messages. Select this 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 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 placed on the folders during the last full backup is used to determine which messages have been modified since, but the time/date stamp is not updated during the differential backup. INCREMENTAL - Back up changed messages. Reset archive bit. Select this 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 placed on the folders during the last full or incremental backup is used to determine which messages have been modified since, and the time/date stamp is updated during the differential backup.
1112
Backup Options for Exchange 5.5 Backup job properties for Exchange Server (continued) Item Enable single instance backup for message attachments (for mailbox and public folder backups only) Description Select this 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 and 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. Disable this option if you want each identical copy of a message attachment backed up and kept in order on the backup set.
Guide Me Click Guide Me to start a wizard that helps you choose backup job properties for recreating user accounts and mailboxes.
Exchange Agent
See also: Backup Strategies for Exchange 5.5 on page 1107 Backing Up Exchange 5.5 Mailboxes and Public Folders on page 1115 Reviewing Circular Logging for Exchange 5.5 on page 1115
1113
Backing Up Exchange 5.5
Backing Up Exchange 5.5
To back up Exchange 5.5: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections, and then select the data you want to back up. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts with Exchange 5.5 Resources on page 1106. 3. To select Exchange data from local or remote selections, click the domain name icon or icons that contain the Exchange installations, and then click the actual Windows computer icon that contains the Exchange installation. If you are using a server cluster, make backup selections from the virtual server. A list of shared network directories and resources appears. 4. Click the check boxes preceding the Microsoft Exchange Information Store and Microsoft Exchange Directory. 5. To select the Exchange server backup method, on the Properties pane, under Settings, click Exchange. For details on these options, see Backup Options for Exchange 5.5 on page 1110. Note To perform incremental and differential backups of storage groups, make sure that circular logging is not enabled on the storage group. See also: Backup Strategies for Exchange 5.5 on page 1107 Backing Up Exchange 5.5 Mailboxes and Public Folders on page 1115 Reviewing Circular Logging for Exchange 5.5 on page 1115
1114
Backing Up Exchange 5.5 Mailboxes and Public Folders
Reviewing Circular Logging for Exchange 5.5

When circular logging is enabled, incremental and differential backups of the Exchange databases cannot be performed because these types of backups rely on a complete history of logs. When circular logging is enabled, transaction log files that have already been committed to the database are overwritten, preventing the accumulation of logs. The log files are overwritten whether or not a full or incremental backup has been run, and a history of previous logs since the last full or incremental backup is not maintained. When circular logging is disabled, transaction log files accumulate on the disk until a full or incremental backup is performed, after which the log files that have all transactions committed to the database are deleted.
To review the circular logging setting for Exchange 5.5: 1. Run the Exchange Administrator utility. 2. Select the server you want to check by clicking Site, then Configuration, and then clicking Servers. 3. From the File menu, click Properties. 4. Click the Advanced tab. You can set circular logging separately for the Information Store and the Directory Store. 5. If you want to perform incremental and differential backups of the stores, make sure that circular logging is not enabled on the stores.
Exchange Agent

Mailboxes and public folders are already included in the Information Store database backups, but if you want to make the restore of a mailbox or folder easier, you can also select one or more mailboxes or public folders for backup separately from the databases. Although mailbox backups will take longer to run than database backups, you can enable features in Backup Exec to make mailbox and public folder backups faster. These features are described in Recommendations for backing up mailboxes and public folders on page 1116. 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 - only from backups of the Information Store.
Appendix H, VERITAS Backup Exec - Agent for Microsoft Exchange Server 1115
Consider using the Exchange Administrator utility to adjust the deleted item retention settings for the Public and Private Information Stores properties so that deleted items are retained for a period of time, allowing them to be recovered rather than restored. See your Microsoft Exchange Server documentation for details. To obtain the most efficiency and greatest performance in mailbox and public folder backups, consider the following:
Recommendations for backing up mailboxes and public folders Recommendation: Description:
Use full and incremental Consider running full backups of mailboxes or public folders on a backups regular basis, supplemented with incremental backups throughout your schedule to keep backup run time to a minimum. Exclude unwanted or unnecessary folders from the backup When you select a mailbox or public folder for backup, by default all folders and subfolders are included. You can easily exclude specific folders and subfolders from the backups by using the ** wildcard in the file selection path on the Advanced File Selection dialog box when making backup selections (see Including or Excluding Files for Backup Using Advanced File Selection on page 262). 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\* If you also want to exclude all subfolders of the specified folders from the backup, check the Include Subfolders checkbox in the Advanced File Selection dialog. Use single-instance storage 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, and 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. However, if the backup is incomplete, the attachments may not be included on the backup set. The backup should be rerun until it is successfully completed.
1116
Backing Up Exchange 5.5 Mailboxes and Public Folders Recommendations for backing up mailboxes and public folders (continued) Recommendation: Do not back up special system mailboxes created by Exchange Description: While these special system mailboxes can be backed up, it is not necessary or useful. The following are common examples of special system mailboxes, but there may be others depending on the Exchange 5.5 server configuration and environment. Microsoft Schedule+Free/Busy Connector System Attendant Directory Service 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. Select public folders The same public folders may be displayed for multiple Exchange from only one Exchange servers since public folders can be replicated. Selecting public folders server. on multiple Exchange servers will only increase the time and media required for the backup and does not provide any additional protection.
Exchange Agent
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, however, may be displayed on more than one server since public folders can be replicated to many servers. Note In versions of Backup Exec prior to 8.6, mailboxes could be selected for backup from a site-centric view, which listed all mailboxes that resided on Exchange Servers in the same Exchange site, 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 created using a site-centric view.
To back up Exchange 5.5 mailboxes or public folders: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections. 3. To select Exchange mailboxes or public folders from local or remote selections, click the domain name icon or icons that contain the Exchange mailboxes, and then click the actual Windows computer icon that contains the Exchange mailboxes. If you are using a server cluster, make backup selections from the virtual server.
1117
4. Expand the Microsoft Exchange Mailbox icon that contains the mailboxes or public folders you want to back up. You can select all mailboxes or individual messages, mailboxes, and folders 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.
5. If prompted, select a logon account that will allow you to connect to the Exchange mailboxes or public folders. For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts with Exchange 5.5 Resources on page 1106. 6. To select the mailbox or public folders backup method, on the Properties pane, under Settings, click Exchange. For details on these options, see Backup Options for Exchange 5.5 on page 1110.
Restore Options for Exchange 5.5
7. Select other backup options from the Properties pane or start the backup job. See also: Backing Up Data on page 233

This procedure details how to select restore job properties for Exchange 5.5 and provides definitions for Exchange 5.5-specific restore options. For details on how to create a restore job, and for definitions of all other restore options, see Restoring Data on page 395.
To select restore job properties for Exchange 5.5: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click Exchange.
Exchange Agent
1119
3. Select the appropriate options as follows.

Restore Job Properties for Exchange 5.5 Item Exchange Server options Automatically recreate Select this checkbox to recreate the user accounts and their user accounts and mailboxes if they do not already exist on the target server. mailboxes during restore Otherwise, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this checkbox is selected, the password you entered on the Exchange page in the Options - Set Application Defaults dialog box is used as the password for accounts that are recreated. To change the password, on the Tools menu click Options, and then in the Properties pane under Job Defaults, click Exchange. Select Automatically recreate user accounts and mailboxes, and then click Change password. Note This option 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. Exchange v5.5 No loss restore (Do not delete existing transaction logs) Select this to preserve the existing transaction logs on Exchange 5.5. Transaction logs on the storage media are then restored and added to the existing set of transaction logs on Exchange 5.5. When the restore operation finishes, Exchange 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. Select this 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. Select this 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. Description
Restore private mailboxes
1120
Restoring Exchange 5.5 Restore Job Properties for Exchange 5.5 (continued) Item Guide Me Description Click Guide Me to start a wizard that helps you choose restore job properties for restoring Exchange 5.5 Directory and Information Store data.
Restoring Exchange 5.5

How you restore data depends on the types of backup used to protect the data:

Restore the last full backup, or Restore the last full backup and the last differential backup, or Restore the last full backup and all subsequent incremental backups.
Note 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 restarted. Following are requirements for running a restore job for Exchange 5.5 Server:
Exchange Agent
The Exchange System Attendant service is 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. If you are restoring the Exchange Directory, the target server must have access to the original Security Account Manager (SAM) information. 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.
Note Restoring an Exchange 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. Before starting the restore job, review Restoring Data on page 395 for information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs.
1121
Restoring Exchange 5.5
To restore Exchange 5.5: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. In the restore selections list, select the backup sets you want to restore. Restore the last full backup, or Restore the last full backup and the last differential backup, or Restore the last full backup and all subsequent incremental backups.
4. On the Properties pane, under Settings, click Exchange. 5. Select the appropriate options. For details, see Restore Options for Exchange 5.5 on page 1119. 6. Start the restore job or select other restore options from the Properties pane. 7. 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 Pre/Post Commands for Restore Jobs on page 416. 8. When the Exchange Server is back online, run the Directory Store/Information Store (DS/IS) consistency adjuster in order to resolve any inconsistencies. Results of the consistency adjustment can be found in the Windows Event Log. For more information concerning the DS/IS consistency adjuster, refer to your Exchange documentation. 9. After the restore is complete, it is recommended that you run a full backup of the restored databases. See also: Restoring Data on page 395
1122
Restoring Exchange 5.5 Mailboxes and Public Folders

You can restore mailbox and public folder data from backup sets created when individual mailboxes were backed up from the Microsoft Exchange Mailboxes selection, or when individual public folders were backed up from the Microsoft Exchange Public Folders selection. You cannot restore individual mailboxes or public folders from database backups. If you need to restore mailboxes that have been deleted back to their original location, you can choose to have the user account and mailbox automatically recreated. A password that you specify is assigned to the recreated user account. If the mailbox restore is being redirected, the mailbox must already exist on the target server. Please note the following before starting a mailbox or public folder restore job:
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 will restore normally. Mailboxes that resided on other servers must be redirected to those servers.
Exchange Agent
If you restore mailboxes from a backup created with a version of Backup Exec prior to 8.5, and mailboxes with duplicate Display Names reside on the server, select those mailboxes for restore separately and follow the instructions in Redirecting Mailbox and Public Folder Restores in Exchange 5.5 on page 1127. When messages in mailboxes or public folders are restored to a location where a message with the same name already exists, the restored message does not replace the existing message, but is added to the destination folder; therefore, duplicate messages may result in the destination folder. The option Restore over existing files in the Restore Job Properties dialog box 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. To display the Restore Job Properties dialog box, on the navigation bar click Restore, and then on the Properties pane, click Settings.
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 5.5 server configuration and environment. Microsoft Schedule + Free/Busy Connector System Attendant Directory Service
1123
To restore Exchange mailboxes and public folders: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Source, click Selections. 3. In the restore selections list, navigate to and select the data you want to restore. 4. On the Properties pane, under Settings, click Exchange. On the Restore Job Properties dialog box, if the user accounts and their mailboxes that are being restored do not already exist on the target server, and they are being restored to their original location, select Automatically recreate user accounts and mailboxes. If this option is not selected, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this checkbox is selected, the password entered on the Exchange page of the Options - Set Application Defaults dialog box is used as the password for accounts that are recreated. To change the password, on the Tools menu click Options, and then in the Properties pane under Job Defaults, click Exchange. Select Automatically recreate user accounts and mailboxes, and then click Change password. 5. Start the restore job or select other restore options from the Properties pane. 6. After the restore is complete, run a full backup of the restored mailboxes. See also: Restoring Data on page 395 Restore Options for Exchange 2000 on page 1085 Setting Default Backup and Restore Options for Exchange 2000 on page 1097
1124
Redirecting Exchange 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 5.5 database restores:
Restrictions for redirecting restores of Exchange 5.5 databases Restriction Description
The Site and Organization Backup Exec does not prevent redirection of an Information names of the original and Store when the Site and Organization names differ. If the Site destination servers must match. and Organization names are different, the redirected restore may appear to complete successfully but the IS service will fail to start afterward.
Exchange Agent
The No loss restore option cannot be selected.
The No loss restore option must be cleared so that any transaction logs on the destination server are removed to avoid an incompatibility that would prevent the Information Store service from starting. The No loss restore option appears on the Restore Job Properties for Exchange 5.5 dialog box. To access this option, on the navigation bar, click Restore, and then in the Properties pane under Settings, click Exchange.
The Directory Store cannot be restored through redirection.
You cannot redirect a restore job in which you have selected to restore one or more Exchange 5.5 Directory databases.
To redirect an Information Store restore: 1. Follow the instructions for the restore in Restoring Exchange 5.5 on page 1121. 2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Exchange Redirection.
1125
Restore job properties for redirected Exchange sets Item Redirect Exchange sets Description Select this checkbox to enable the Restore to server and Server logon account fields. Type the name of the computer to which you are restoring, using the format \\server name. To restore to a server, use a Backup Exec logon account that stores the credentials of a Windows user account. The default logon account is displayed by default. To use another logon account, click Change. For more information about logon accounts, see Using Backup Exec Logon Accounts with Exchange 5.5 Resources on page 1106.
Restore to server
1126
4. 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 412. 5. When the Exchange server is back online, run the Directory Store/Information Store (DS/IS) consistency adjuster in order to resolve any inconsistencies. Results of the consistency adjustment can be found in the Windows Event Log. For more information concerning the DS/IS consistency adjuster, refer to your Exchange documentation. 6. After the restore is complete, it is recommended that you run a full backup of the restored databases. See also: Restoring Data on page 395
Redirecting Mailbox and Public Folder Restores in Exchange 5.5

You can redirect the restore of individual mailboxes and public folders from backup sets created when individual mailboxes were backed up from the Microsoft Exchange Mailboxes selection, or when individual public folders were backed up from the Microsoft Exchange Public Folders selection. You cannot restore individual mailboxes or public folders from database backups. If you select a single mailbox, or one or more messages or folders from a single mailbox, you can redirect that restore to another existing mailbox on the same or a different server. If any of the folders in the original mailbox do not exist in the destination mailbox, they will be created during the restore. If you select more than one mailbox, or folders and messages from more than one mailbox, you can only redirect the restore to another server. Mailboxes with the same names as those selected must already exist on the target server. Following are requirements for redirecting the restore of mailboxes:
Exchange Agent
If the mailboxes 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.
1127
To ensure that Backup Exec can access mailboxes on the server that you are redirecting messages or mailbox restores to, click the destination server in the backup selections list, select Microsoft Exchange Mailboxes and verify that the target mailbox is displayed in the list of mailboxes. If you are prompted for a logon account, use a logon account that stores the credentials of a user account that is unique and has a corresponding mailbox of the same name. See Using Backup Exec Logon Accounts with Exchange 5.5 Resources on page 1106. 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, if you back up Mailbox 1, which consists of Top of Information Store, Inbox, and Folders 1 and 2, each containing some mail messages, and then you restore Mailbox 1 to the existing Mailbox 2, then all of Mailbox 1, including the Top of Information Store, Inbox, Folders 1 and 2, and messages, are restored to Mailbox 2. Note that Mailbox 1 itself is not created under Mailbox 2.
Redirecting the restore of Mailbox 1 to Mailbox 2
1128
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.
Redirecting Mailbox 1\Top of Information Store\Folder 2 to Mailbox 2
Exchange Agent
To redirect a restore: 1. Follow the instructions for the restore in Restoring Exchange 5.5 Mailboxes and Public Folders on page 1123. 2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Exchange Redirection.
1129
3. Select the appropriate options as follows, and then start the redirected restore job or select other restore options from the Properties pane. After completing the restore, it is recommended that a full backup of the restored mailboxes be performed.
Restore job properties for redirected Exchange sets Item Redirect Exchange sets Description Select this checkbox to enable the Restore to server and Restore to mailbox fields. Type the name of the computer to which you are restoring, using the format \\server name. To restore to a server, use a Backup Exec logon account that stores the credentials of a Windows user account. The default logon account is displayed. To use another logon account, click Change. For more information about logon accounts, see Using Backup Exec Logon Accounts with Exchange 5.5 Resources on page 1106.
Restore to server
1130
Restoring Exchange 5.5 Mailboxes and Public Folders Restore job properties for redirected Exchange sets (continued) Item Restore to mailbox Description Type the name of the target mailbox exactly as it appears when browsing to the mailbox in the backup selections pane, including the brackets surrounding the mailbox directory identifier (for example, Mailbox Name [mailboxname]). The mailbox must already exist before you can restore to it. See Redirecting Mailbox and Public Folder Restores in Exchange 5.5 on page 1127. To restore a mailbox or public folder, use a Backup Exec logon account that stores the credentials of the mailbox user account. To use another logon account, click Change. To clear the displayed logon account and use the same logon account specified in the Server logon account field, click Clear. For more information about logon accounts, see Using Backup Exec Logon Accounts with Exchange 5.5 Resources on page 1106.
Mailbox logon account
Exchange Agent
1131
Setting Default Backup and Restore Options for Exchange 5.5

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. You can also change the defaults for any specific backup or restore job.
To change backup and restore defaults for Exchange: 1. On the Backup Exec menu bar, click Tools, and then click Options. 2. On the Properties pane, under Job Settings, click Exchange.
1132

Options - Set Application Defaults for Exchange Item Backup Exchange method FULL - Database & Logs (flush committed logs). Select this 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 that have all transactions committed to the database are then deleted. This option is selected by default. COPY - Databases & Logs. Select this 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 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from differential backups, the last differential backup and the last full backup are required. INCREMENTAL - Logs (flush committed logs). Select this 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. Note If circular logging is enabled, incremental and differential backups cannot be performed. To restore from incremental backups, the last full backup and all incremental backups done since are required. Description
Exchange Agent
1133
Setting Default Backup and Restore Options for Exchange 5.5 Options - Set Application Defaults for Exchange (continued) Item Mailbox method: Description FULL - Back up messages. Reset archive bit. Select this to back up all messages in the selected mailboxes. This option is set by default. A time/date stamp placed in each folder indicates the messages have been backed up. COPY - Back up messages. Select this 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 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 placed on the folders during the last full backup is used to determine which messages have been modified since, but the time/date stamp is not updated during the differential backup. INCREMENTAL - Back up changed messages. Reset archive bit. Select this 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 placed on the folders during the last full or incremental backup is used to determine which messages have been modified since, and the time/date stamp is updated during the differential backup.
1134
Setting Default Backup and Restore Options for Exchange 5.5 Options - Set Application Defaults for Exchange (continued) Item Enable single instance backup for message attachments Description Select this 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 and 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. Disable this option if you want each message attachment backed up and kept in order on the backup set.
Restore 5.5 No loss restore (do not delete existing transaction logs) Select this to preserve the existing transaction logs on Exchange 5.5. Transaction logs on the storage media are then restored and added to the existing set of transaction logs on Exchange 5.5. When the restore operation finishes, Exchange 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. Select this 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.
Exchange Agent
1135
Setting Default Backup and Restore Options for Exchange 5.5 Options - Set Application Defaults for Exchange (continued) Item Restore private mailboxes Description Select this 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. Automatic recreation Automatically recreate user accounts and mailboxes Select this checkbox to recreate the user accounts and their mailboxes if they do not already exist on the target server. Otherwise, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this checkbox is selected, the password you entered on the Exchange page on the Options - Set Application Defaults dialog box is used as the password for accounts that are recreated. To change the password, see To restore Exchange mailboxes and public folders: on page 1124. Note This option 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. Password Click this to specify a password to use when user accounts and mailboxes are automatically recreated on the target server.
See also: Restore Options for Exchange 5.5 on page 1119 Restoring Data on page 395
1136
Preparing for Disaster Recovery of Exchange 5.5
Preparing for Disaster Recovery of Exchange 5.5

A disaster preparation plan is an absolute necessity for restoring Exchange efficiently and effectively in the event of a catastrophic failure. Because Exchange uses Windows security for authentication, disaster recovery of Exchange cannot be separated from the disaster recovery of Windows. Planning ahead reduces the time needed to recover. It is critical to build a kit that includes items such as:

An operating system configuration sheet A hard drive partition configuration sheet Any RAID configuration A hardware configuration sheet EISA/MCA configuration disks An Exchange configuration sheet A Windows emergency repair diskette
Exchange Agent
An Exchange Performance Optimizer settings sheet
To perform the actual recovery, you will need:

An installed copy of Backup Exec for Windows Servers The latest full, incremental, and differential backups of the Exchange databases you want to recover The Microsoft Exchange Server Installation CD Any service packs which were applied to the original installation
1137
Disaster Recovery for Exchange Server 5.5

This procedure guides you through a complete restoration of Exchange 5.5 using Backup Exec. You should have already performed all the appropriate preparation as detailed in Preparing for Disaster Recovery of Exchange 5.5 on page 1137. Always log in to Windows using the Administrator account (or an Administrator equivalent) during this procedure. To properly recover Exchange, the Directory Store needs to be restored to a server that has the same computer name, and Domain, Organization, and Site name as the original. If these conditions are not met, the recovery will not be successful. Even if the only Directory Store backup available is of the original Directory Store, restore it, and then backfill changes from another server in the site. If you purchased Intelligent Disaster Recovery, see Microsoft Exchange Recovery Notes on page 909 for directions on using Intelligent Disaster Recovery to recover your Exchange server.
To perform disaster recovery for Exchange 5.5: 1. Recover the Windows server first. For instructions, see Disaster Recovery of a Local Windows NT Computer on page 541 or Disaster Recovery of a Remote Windows 2000/XP/.NET Computer (includes non-authoritative restore of Active Directory for a domain controller) on page 549. Note Make sure you restore the Exchange Server files that existed on all disk partitions. When the Windows server disaster recovery procedure is complete (after the last reboot), recover the Exchange server. 2. Do one of the following: Note This step is necessary because the Microsoft Exchange Directory service may hang when there is no database to use because you have not restored it yet. However, if you have tools that can kill a process such as KILL or PVIEWER, then kill the DSAMAIN.EXE process and go to step 4 on page 1139. a. For Windows 2000, click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools, and then double-click Services. Right-click Microsoft Exchange Directory service, and then click Properties. On the General tab, under Startup, click Disabled, and then click OK. b. For Windows NT, click Start, point to Settings, and then click Control Panel, and then double-click Services. Double-click Microsoft Exchange Directory service, change the Startup Type to Disabled, and then click OK.
1138
3. Restart the computer. Note Upon reboot, a message is displayed stating that not all services could be started. 4. Double-click the Microsoft Exchange Directory service, and then change the Startup Type to Automatic. 5. Click OK. 6. Verify that the Exchange System Attendant service is started. 7. Start Backup Exec. 8. Catalog the tapes that contain the latest full, incremental, and differential backups of the Exchange Stores you want to recover. 9. On the navigation bar, click Restore. 10. On the Properties pane, under Source, click Selections.
Exchange Agent
11. On the restore selections list, select the latest full backups of the Directory and Information Stores for restore. 12. 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. 13. On the Properties pane, double-click Settings, and then click Exchange. 14. Select the Exchange 5.5 options Restore Public Folder and Restore Private Mailboxes. 15. Clear the checkbox for the Exchange 5.5 option No loss restore (do not delete existing transaction logs). 16. Start the restore job.
1139
17. 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 following directory on the Exchange CD: \setup\<your processor type>\bootenv to the following directory on your hard drive: \exchsrvr\mtadata For example, assuming your Exchange installation is on drive C, your CD-ROM drive is drive D, and your processor type is Intel, you would type the following in a command window: copy d:\setup\i386\bootenv\*.* c:\exchsrvr\mtadata Note If you use File Manager or Windows Explorer to copy the files, you must remove the READ ONLY file attribute from the files after you copy them. If you do not remove this file attribute, the Microsoft Exchange Message Transfer Agent service will not start. 18. 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. 19. Do one of the following: a. For Windows 2000, click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools, and then double-click Services. b. For Windows NT, click Start, point to Settings, and then click Control Panel, and then double-click Services. 20. Start ALL of the Exchange services that have Automatic as a Startup Type. This should include: 1140
Microsoft Exchange Directory Microsoft Exchange Information Store Microsoft Exchange Message Transfer Agent Microsoft Exchange System Attendant
21. 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. 22. After completing the restore, it is recommended that a full backup of the restored databases be performed.
Exchange Agent
1141
1142
VERITAS Backup Exec - Library Expansion Option
Using a robotic library with Backup Exec 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 licenses for additional robotic library drives, you must purchase the optional VERITAS Backup Exec for Windows Servers - Library Expansion Option (LEO). This option allows concurrent processing on multi-drive robotic libraries. See also: Using Robotic Libraries with Backup Exec on page 132 Configuring Multi-drive Robotic Libraries on page 1145
Setting Up Robotic Library Hardware

Before installing Backup Exec, you will need to make sure the robotic library hardware is configured properly.
Library Expansion
Make sure the robotic arm is set to Random mode. Please refer to your robotic library documentation for more information. If you have a multi-LUN robotic library, make sure your controller card is set to support multiple LUNs (if supported). The SCSI ID of the robotic arm must precede the SCSI address of the drives in the robotic library. The following illustration shows an example of a standalone drive and robotic library configuration.
1143
Setting Up Robotic Library Hardware Standalone drive and robotic library configuration
SCSI Address:
2 Standalone drive
3 Standalone drive
4 Robotic Arm
5 and 6 Media drives in the robot
1144
Setting Up Robotic Library Hardware
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 addresses 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 addresses to match the sequence of the drive element addresses. For example, if your robotic library has two drives, the drive with the lowest drive element address should be assigned the lower SCSI address.
Example configuration for a Multi-drive robotic library Data Transfer Element (Storage Devices) Robotic Arm Storage Device 0 Storage Device 1 SCSI ID Drive Element Address
4 5 6
N/A 00008000 00008001
Library Expansion
Appendix I, VERITAS Backup Exec - Library Expansion Option
1145
Installing the Library Expansion Option
Installing the Library Expansion Option

Backup Execs optional Library Expansion Option installation requires:
Purchasing an Library Expansion Option serial number 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. To install the Library Expansion Option, follow the installation steps described in Installing Backup Exec Options on a Local Server on page 49, adding the Library Expansion Option serial number.
Starting Backup Exec After Installing the Library Expansion Option

Information is displayed about the configuration of your storage devices when one of the following occurs:

Backup Exec is started for the first time following the Library Expansion Option installation. The Confirm Backup Device Availability item is selected from the Backup Exec Assistant. From the Tools menu, you point to Wizards, and then select Device Configuration Wizard.
This item displays several dialogs, including the Welcome screen:
The Detected Hardware dialog box shows all of the devices attached to the media server. If a drive attached to your media server does not appear in the list, click Configure Devices to install the appropriate driver for the device. The Drive Configuration dialog box shows how the devices appear to Backup Exec.
1146
Starting Backup Exec After Installing the Library Expansion Option Detected Hardware dialog box
Devices in the robotic library Robotic library
Drive Configuration dialog box
Library Expansion
Make sure that each device in the robotic library is properly associated with the robotic library. Make sure the drives in the library appear in the device configuration wizard under the robotic library in the order matching their drive element address. The drive having 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, you can correct the association by clicking and dragging the drive over the robotic library entry. If this does not work, make sure the SCSI addresses of the robotic library and the storage device are configured properly.
Appendix I, VERITAS Backup Exec - Library Expansion Option 1147
Note During startup, Backup Exec expects the storage devices in the robotic library to be empty. If there is media in the device, Backup Exec tries to return the media to its original magazine slot. If, for any reason, it cannot return the media to the slot, an error message appears requesting that the media be ejected from the storage device. See also: Setting Up Robotic Library Hardware on page 1143 Using the Backup Exec Assistant on page 82 Viewing Drive Configuration Properties on page 119
Viewing Robotic Libraries

The following is an example of how robotic libraries are depicted when Devices is selected from the navigation bar:
Robotic libraries in the Devices view
Robotic library Robotic library drive
All slots Individual slots
Depending upon your robotic library configuration, the first slot could be numbered 1 or 0. If your robotic library uses a zero-based slot configuration you can reassign how the slots are displayed in Backup Exec, by right clicking the Robotic Library in the left pane, selecting Properties, and then selecting Configuration. Depending on whether your robotic library begins slot numbering at 0 or 1, specify the appropriate number in the Slot Base field.
1148
Starting Backup Exec After Installing the Library Expansion Option Changer properties for Library|Configuration tab
After completing the configuration of your robotic library, you should perform an Inventory operation to update Backup Execs media database. See also: Inventorying Media in Devices on page 165
Library Expansion
Appendix I, VERITAS Backup Exec - Library Expansion Option
1149
1150
VERITAS Backup Exec - Agent for Oracle Server
The Backup Exec Agent for Oracle Server (Oracle Agent) is installed as a separate, add-on component of Backup Exec for Windows Servers. The Oracle Agent provides a complete solution for backing up and restoring database servers running single or multiple Oracle databases. When using the Oracle Agent, the Oracle databases do not have to be taken offline or shut down to be backed up. Database users can continue using the databases while the backup is run. This is called an Online Database Backup. The Oracle Agent simplifies the process of backing up an Oracle database by automatically backing up the databases tablespace data files and the database control file, along with all of the Oracle archived logfiles when you perform a full database backup. The Oracle Agent also gives you a tablespace view of the database from within Backup Exec, which allows you to select individual tablespaces for backup. This feature allows you to schedule the frequency of individual tablespace backups. For example, if your Oracle database has a tablespace that rarely changes, you can schedule its backup to occur less frequently than a tablespace that continuously changes. Because each tablespace is backed up automatically when the entire Oracle database is backed up, the individual data files that comprise a tablespace or an entire database do not need to be manually selected in order to protect the database. If new tablespaces have been added to the Oracle database since the last backup operation was performed, these new tablespaces are automatically detected and backed up during the next full backup operation of the selected Oracle database. When an online tablespace is backed up, the tablespace is placed in Backup Mode and its associated data files are backed up. After backup, the tablespace is placed back online, if it was previously online. When all selected tablespaces have been backed up, the archive redo logfiles are backed up to the same backup set. Backing up the archive redo logfiles after the tablespace is placed online again gives you the ability to restore the tablespace to the state at which the tablespace backup was completed. Note The Oracle Agent takes advantage of the Oracle Database Services ability to create a copy of a databases control file while the database is online. Using this feature, the agent can back up the copy of the databases control file while the database is actually being backed up online.
Oracle Agent
1151
Requirements for Using the Oracle Agent
Requirements for Using the Oracle Agent

You need to have the following software installed before you can use the Oracle Agent:

Windows NT 4.0, Windows 2000, Windows XP, and Windows.NET Backup Exec for Windows Servers 9.x or later. One of the following supported databases: Oracle Database Server Version 8.0.5, 8i, or 9i, and Oracle Application Server 9i.
Backup Strategies for An Oracle Database Server

Use the Backup Exec Oracle Agent to back up the database frequently. The more frequently you back up the database, the less time it takes to recover it in the event of data loss. In addition to these regularly scheduled backups, it is recommended that you perform a Closed Database Backup whenever you alter the structure of the database. Closed database backups take place while a database is shut down. When the database is shut down, all data files and control files comprising the database are available for backup by a file system backup operation. Performing a closed database backup of the Oracle server is recommended after making structural changes to the database. A closed database backup speeds the recovery of the database in a disaster situation. One method of performing a closed database backup is to shut down the database and back up the entire volume (disk) where the Oracle database is located. An alternative method is to select only the directories and files that make up the database. When you perform your normal file system backups using the normal Backup Exec methods, make sure the Oracle database control and data files are excluded from the backup set. Because these database files are both locked and unreadable when the database is open, they will appear as Skipped in the Backup Exec Job History job log if you attempt to back them up during your normal file system backup jobs.
1152
Backup Strategies for An Oracle Database Server
Types of Oracle Database Data You Can Protect

Within the Backup Selections in Backup Exec, each Oracle database agent contains a list of one or more database instances. These instances appear as subdevices of the Oracle Agent and contain logical views of the Oracle databases.
Oracle Databases You Can Protect Oracle Database Agent Oracle Database Instances Archived Logfiles Directory Database Control File Directory Oracle Tablespaces
Oracle Database Data Types You Can Protect Item Tablespace Data Description Tablespaces appear as subdirectories within the listed database instances. Data files that comprise the tablespace appear as files within the appropriate tablespace directory entry. The datafile path is stored as part of the file name, so Backup Exec changes the display of the file names so that backslashes (\) display as forward slashes (/) and colons (:) display as vertical bars (|). For Oracle 8.1.x and above, do not select a temporary tablespace with local extent management for backup. There is no need to back up temporary tablespaces with local extent management because they are used by Oracle only for the duration of a session and are not recognized during media recovery. Archived Logfiles The Oracle Agent creates a directory entry named {Archived Logfiles} in the root directory of the agent device. During a backup operation the Backup Exec administration console does not display any files within this directory. However, the Backup Exec job server has access to the actual Oracle archived redo logfiles when a backup operation takes place.
Oracle Agent
Appendix J, VERITAS Backup Exec - Agent for Oracle Server
1153
Requirements for Configuring the Oracle Agent Oracle Database Data Types You Can Protect (continued) Item Control File Backup Description The Oracle Agent creates a directory named {Database Control File} in the root directory of the agent device. The Backup Exec administration console does not display any files within this directory, but the Backup Exec job server will see and back up the file called Becf<Sid_Name>.bak from this directory. When this file is restored from the storage media, it is automatically placed in the Oracle datafile directory on your database server. By default, it is \Orant\Database.
Requirements for Configuring the Oracle Agent

Before you install and configure the Oracle Agent, you should verify that the following conditions are met for each Oracle SID (database) that you want to protect:

The Backup Exec Oracle Agent has an Oracle user account assigned to it that it can use to log on to the Oracle database. The Oracle Servers Database Log Mode is set to ARCHIVELOG. The Oracle Servers Automatic Archival is enabled in the Oracle parameter initialization file (default name: Init<SID>.ora, where <SID> is the name of the instance). There is a directory on the Oracle Server where Oracle will generate the Archived Logfiles.
See also: Creating a New Oracle User Account for the Oracle Agent on page 1154 Verifying ARCHIVELOG Mode and Automatic Archival Settings on page 1155
Creating a New Oracle User Account for the Oracle Agent

A user account with appropriate database rights must exist for the Oracle Agent to access the database. You can use either an existing user account that has the required rights, or you can create a new user account with the required rights. To create an Oracle user account specifically for use by the Backup Exec Oracle Agent, use the Oracle Server Manager application and type the following commands at the prompt.
1154
Note Make sure you are connected as a DBA. Be sure to replace USERNAME with the assigned login user name and PASSWORD with the appropriate password. create user USERNAME identified by PASSWORD; grant dba to USERNAME; After all of the commands have been entered, the assigned user will have the appropriate rights needed to protect the database.
Verifying ARCHIVELOG Mode and Automatic Archival Settings

Before Oracle databases can be backed up, each databases Oracle Database Log Mode setting must be set to ARCHIVELOG and each databases Automatic Archival setting must be enabled. ARCHIVELOG must be enabled so the Oracle Agent can put each tablespace in Backup Mode prior to running the backup operation. Note Archivelogs can be replicated to another machine for safe storage and duplication. For more information on Archivelog replication, please see the Oracle documentation.
To verify the Database Log is in ARCHIVELOG mode and Automatic Archival is enabled: 1. Type the following from the Server Manager command prompt: archive log list; You should see: Database Log Mode ARCHIVE LOG Automatic Archival ENABLED If either parameter is not set correctly, shut down the database and set it correctly. 2. Close the database by typing the command: shutdown; 3. Start the database service without mounting the database. Type the following command: startup nomount; 4. Open the database and mount it in exclusive mode. Type the following command:
Oracle Agent
1155
alter database mount exclusive; 5. Enable ARCHIVELOG mode by typing the command: alter database archivelog; 6. Open the database and mount it for general use. Type the following command: alter database open; 7. IMPORTANT: To enable Automatic Archival, you must edit the Oracle instance initialization parameter file (default Init<SID>.ora where <SID> is the name of the instance). The following item must be specified: log_archive_start = true 8. You may also specify the directory where Oracle will create the Archived log files (LOG_ARCHIVE_DEST). If this parameter is not specified in the Oracle parameter initialization file, Oracle will use the default value of $Oracle_Home\RDBMSxx. You can specify the archive redo logfile location by setting LOG_ARCHIVE_DEST to the appropriate path. log_archive_dest = \orant\database\logs Note Each time a tablespace is backed up, an archive redo logfile is created and backed up. Over time, you may want to delete older archived redo logfiles to help save hard drive space. By default the Oracle installation maintains two instances of redo logs, but recommends three copies of them. Please see the Oracle documentation for more information.
Shutting Down and Restarting the Database

In order for Automatic Archival to be enabled, each database you want to protect must be shut down and restarted. Before shutting down the databases, make sure that:

A user with appropriate rights exists for the Oracle Agent. The Database Log Mode is set to ARCHIVELOG. Automatic Archival is enabled in the Oracle initialization file. A directory has been created (or already exists) for the archive redo log files.
1156
To shut down and start up the Oracle databases: 1. Type the following command from the Server Manager prompt: shutdown; 2. After each database has been shut down, type the following command to bring each of them back online: startup; 3. Verify that Automatic Archival is enabled and the database log is in ARCHIVELOG mode by typing the following command: archive log list; You should see: Database Log Mode ARCHIVE LOG Automatic Archival ENABLED If either parameter is not set correctly, shut down the database and set it correctly.
Running Multiple Database Instances on a Single Server

If you are running multiple database instances on your database server, it is important that you configure each database instance to use different Archive Redo Logfile destination directories. All Oracle databases have instance initialization parameter files associated with them. Each initialization parameter file is named Init<SID>.ora, where <SID> is the name of the instance. This file controls the destination where Oracle creates the archive redo logfiles. Because each database instance requires its own archive redo logfile directory, you must edit the Oracle instance initialization parameter file and change or add the new archive redo logfile directory path.
Oracle Agent
1157
Using Fully Specified Paths for Oracle Data Files

All Oracle data files must be defined with fully specified paths. If you browse an Oracle tablespace folder through the Backup Exec administration console and notice that data files are missing, check the datafile definitions to make sure they use fully specified paths. Use the following SQL command from the SQLDBA program to check the datafile definitions: SVRMGR> SELECT * FROM V$DATAFILE; The "NAME"- field values must all contain fully specified filename paths. If data files are defined and do not specify full paths for the data file name, then you must rename the data files to use full paths. See also: Renaming Data Files From a Single Tablespace on page 1158
Renaming Data Files From a Single Tablespace

Follow these steps to rename Oracle data files to use full paths.
To rename data files from a single tablespace: 1. Take the non-SYSTEM tablespace that contains the data file offline. 2. Use either the Rename Datafile dialog box of Enterprise Manager/GUI or the SQL command ALTER TABLESPACE with the RENAME DATAFILE option to change the filenames within the database. For example, the following statement renames the datafile 'FILENAME' to 'D:\Orant\Database\Filename' in the tablespace USERS: ALTER TABLESPACE users RENAME DATAFILE filename TO 'd:\orant\database\filename'; 3. Place the tablespace back online.
1158
Understanding the Oracle Agent Configuration Utility

The Oracle Agent configuration utility automatically configures the agent as a Windows system service. After running the Oracle Agent Configuration Utility, you can use the Windows Services control panel to verify that the Backup Exec Oracle Agent is running. The agent service is configured so that it will be automatically started when the system is started. The Oracle Agent uses the application event log to record events that are important to the agents operation. Events recorded by the agent include information such as the agent service starting and stopping, as well as any error conditions encountered by the agent. If an error is encountered while interacting with the Oracle database server program, the Oracle error number is also recorded in the application event log. The Oracle Agent does not attempt to log on to the Oracle database server until a Backup Exec administration console or Backup Exec Job Server attempts to access the agent. If the agent is unable to log on to the Oracle server, the agent will not have access to the Oracle tablespace information. There are a number of reasons why the agent cannot log on to the Oracle database service. They include the following:

The Oracle database has been shut down. The Oracle database has not finished starting up. An invalid Oracle user account was specified in the agents configuration utility. The Oracle database server has not been installed on the system.
When the agent is unable to log on to Oracle in order to access the Oracle tablespace information, the Backup Exec Backup Source view will display only the {Archived Logfiles} and {Database Control File} directories in the root of the Oracle database server. Note If you have multiple Oracle SIDs (databases) on an Oracle database server, and you want to protect them all, you must run the Oracle Agent Configuration Utility and add a configuration definition for each Oracle SID that resides on the Oracle database server. Oracle SIDs are limited to four characters in length in Oracle 8.0.x and to eight characters in Oracle 8i and 9i.
Oracle Agent
1159
Installing the Oracle Agent

The Oracle Agent is installed as a separate, add-on component of Backup Exec for Windows Servers, and can be installed locally or remotely to back up Oracle databases. Whenever the Oracle Agent is installed on the media server, the Backup Exec Remote Agent is included as part of the Oracle Agent installation. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server that you want to back up. You cannot select resources for backup from a remote server until a Remote Agent has been installed. If you are using the Oracle Agent to protect databases on the local media server only, you are entitled to install the Remote Agent that was included with the Oracle Agent installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the Oracle Agent is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to install it to another Windows server. In order to use the Backup Exec Oracle Agent, you must install and enable the agent on the media server, and then install the agent on the Oracle database server. After the agent is installed, you must configure it. For instructions on installing the Oracle Agent on the local media server, see Installing Backup Exec Options on a Local Server on page 49. For instructions on installing the Oracle Agent on a remote resource, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823. Note The Oracle Agent must be installed on the media server. If Backup Exec is not already installed, see Installing Backup Exec on page 41.
To install the Oracle Agent on the Oracle database server: 1. At the Oracle database server, map a drive letter to the volume on the media server that contains the Backup Exec Oracle Agent software. The default location for the agent is: \Program Files\VERITAS\Backup Exec\NT\Agents\Oracle\<Lang>
1160
2. Double-click Setup.exe. 3. Follow the instructions on the screen. When the installation is complete, the Readme file is displayed along with the Backup Exec Oracle Agent Configuration Utility. You can now configure the Oracle Agent. See also: Installing the Remote Agent to Remote Windows Servers on page 823
Configuring the Oracle Agent
To configure the Oracle Agent: Note The Oracle Agent Configuration Utility displays automatically after you install the Backup Exec for Windows Servers Agent for Oracle Server. If you closed the Configuration utility before setting it up, you can reopen it. To open the Oracle Agent Configuration Utility at the Oracle database server, click Start, and then point to Programs. Then click VERITAS Agent for Oracle Server Configuration Utility. 1. Select the appropriate items as follows:
General tab Item Password Description Password used to access the Oracle Agent. When attempting to access the Oracle Agent from the Backup Exec administration console, the password supplied at the administration consoles password prompt must match the password entered here.
Oracle Agent
Confirm
Retype the password you typed in the Password field. You must provide exactly the same password in the password Confirm field as you did in the Password field.
1161
Installing the Oracle Agent General tab (continued) Item Configured Media Servers Description Lists the Backup Exec media servers on your network that will have access to this Oracle Agent. At least one media server should be listed. All Backup Exec media servers that appear in this list can be used to process backup and restore jobs from the Oracle database server running the Oracle Agent. When entering a media server, click Add and then type either a media servers host name or its TCP/IP address. To remove a media server from the list, click the host name or the address of the machine you want to remove, and then click Remove.
2. Click Database. 3. Click Add to add the Oracle SID (unique identifier) of the databases residing on your Oracle database server.
SID Information dialog box
1162
Item SID Name
Definition The SID of an Oracle database residing on the database server. The SID can be up to four characters in Oracle 8.0.x and up to eight characters in Oracle 8i and 9i. Oracle SIDs refer to the unique identifier or name of each Oracle Database on the Oracle Server. The Oracle Agent requires the exact Oracle SID identifier to be configured in order to connect to and backup the Oracle databases. The Oracle user account name you want the agent to use when logging in to the Oracle server. Note The user account must have specific rights for the agent to function properly. For more information, see Creating a New Oracle User Account for the Oracle Agent on page 1154.
User
Password
The password for the user account you want the Oracle Agent to use when logging on to the Oracle database server. Retype the password to verify it. The path of the Archive Logfile location for this SID. Make sure the directory you choose actually exists. You can click Browse to set the archived logfile path. The path where the backup copy of the Database Control File is created. Make sure the directory you choose exists.
Confirm Archived Logfile Location
Control File Backup Location
5. Click OK.
Oracle Agent
1163
Adding Media Servers to Use with the Oracle Agent

Follow these steps to add media servers on your network that will have access to the Oracle Agent.
To configure a media servers host name or IP address for use with the Oracle Agent: 1. At the Oracle database server, click Start, point to Programs, and then click VERITAS Agent for Oracle Server Configuration Utility. 2. Click the General tab. 3. Click Add.
Adding Media Server dialog box
4. Type either the media servers name or its TCP/IP address. 5. Click OK. To add additional media servers, repeat steps 3-5. 6. Click the Database tab and add one or more SID definitions. 7. Click OK to save your configuration information and configure the Oracle Agent as a system service. Following configuration, the service is started. The Oracle Agent is now ready for use.
1164
Backing Up Data Using the Oracle Agent

With the Oracle Agent you can back up three types of data:

An entire online database. This includes the databasess tablespace data files and the database control file. It also includes all of the Oracle archived log files. Individual online tablespaces. Use this to protect individual, online tablespaces within an Oracle database. A closed database. This type of backup takes place while a database is shut down, so all data files and control files comprising the database are available for backup by a file system backup operation. This type of backup is recommended after making structural changes to the database.
See also: Backing Up an Entire Online Database on page 1165 Backing Up Individual Online Tablespaces on page 1167 Backing Up a Closed Database on page 1168
Backing Up an Entire Online Database

When you back up an entire online database, the Oracle Agent automatically backs up the databases tablespace data files and the database control file, along with all of the Oracle archived log files. Note For Oracle 8.1.x and above, do not select a temporary tablespace with local extent management for backup. There is no need to back up temporary tablespaces with local extent management because they are used by Oracle only for the duration of a session and are not recognized during media recovery.
To back up an entire Oracle online database:
Oracle Agent
1. At the media server, start Backup Exec. 2. On the navigation bar, click Backup. 3. In the Backup Selections pane, expand Remote Selections, and then expand Backup Exec Agents. 4. Expand Oracle Agent. A list of database servers running the Backup Exec Oracle Agent appears.
1165
5. Expand the Oracle database server that you want to back up. If you have previously password-protected the Oracle Agent, a Backup Exec Attach To dialog box appears. Type the password and click Attach. 6. In the Results pane, click the check box preceding the Oracle database you want to back up.
Oracle Database Selection
A check mark appears in the box, indicating that the complete database, including all tablespaces, control files, and archived logfile data will be backed up. 7. Complete the backup settings as normal. For more information, see Creating a Backup Job on page 235.
1166
Backing Up Individual Online Tablespaces

If you have tablespaces that are modified more frequently than others, you can use the Oracle Agent to create backup jobs to protect individual, online tablespaces within an Oracle database. Individual tablespaces can be scheduled for backup at a frequency that reflects the rate at which the tablespaces data is modified. For example, if you have a tablespace that is modified much more frequently than the other tablespaces, then you could schedule that tablespace for more frequent backups. Alternatively, if your database contains a tablespace that rarely changes, you may want to reduce the frequency of its backups. Caution When backing up an individual tablespace, make sure you also select the ARCHIVED LOGFILES folder for backup. Note For Oracle 8.1.x and above, do not select a temporary tablespace with local extent management for backup. There is no need to back up temporary tablespaces with local extent management because they are used by Oracle only for the duration of a session and are not recognized during media recovery.
To back up individual online tablespaces: 1. At the media server, start Backup Exec. 2. On the navigation bar, click Backup. 3. In the Backup Selections pane, expand Remote Selections, and then expand Backup Exec Agents. 4. Expand Oracle Agent to display a list of Oracle database servers. 5. Expand the Oracle database server that contains the database you want to back up. If you have previously password-protected the Oracle Agent, a Backup Exec Attach To dialog box appears. Enter the password and click Attach. 6. Expand the Oracle database that contains the tablespace you want to back up. A list of tablespaces, along with the Database Control File folder and the Archived Logfiles folder appears. 7. Click the box preceding the tablespace folders you want to back up. Make sure you also select the {Archived Logfiles} folder.
Oracle Agent
1167
Backing Up Data Using the Oracle Agent Individual Tablespace Selection
A check mark appears in the box, indicating that only the specified tablespaces, along with the Archived Logfile data, will be backed up. 8. Complete the backup settings as normal.
Backing Up a Closed Database

Closed database backups take place while a database is shut down. When the database is shut down, all data files and control files comprising the database are available for backup by a file system backup operation. Performing a closed database backup of the Oracle server is recommended after making structural changes to the database. A closed database backup also speeds the recovery of the database in a disaster situation. One method of performing a closed database backup simply requires you to shut down the database and back up the entire volume (hard drive) where the Oracle database is located. Another method is to select only the directories and files that make up the database.
1168
Restoring the Oracle Database Using the Oracle Agent

You can restore full databases, individual tablespaces, and the database control file if they become corrupted or are accidentally deleted. If you need to restore full databases, they can be either online or closed. Caution When creating Oracle database restore jobs, you must always select the option Restore Over Existing Files. To access this option, on the navigation bar, click Restore. And then under Settings, click General.
Restore Job Properties
Oracle Agent
1169
Restoring an Online Oracle Database

Note This procedure assumes that the Oracle Database Server is operational, and that database administration can be performed. It also assumes that all the tablespaces you want to restore have been defined, and that the Oracle Agent has been started on the database server. The following procedure is used when the database is operational, but you want to restore the entire database to a prior state for which you have an online backup. Restoring an online database requires you to run two separate restore jobs. First, restore the databases Archived Logfiles directory. Second, restore each of the databases tablespaces, which completes the database recovery. After each tablespace is restored, the Oracle Agent automatically attempts to perform media recovery for the tablespace. If the media recovery is unsuccessful, the agent creates an application event log entry with the specific Oracle error code. Note A databases system tablespace cannot be restored while the database is online. The system tablespace can only be restored to a closed database.
Restoring the Archived Logfiles data (1st restore operation): 1. Make sure that the Backup Exec Oracle Agent has been loaded and is running on the Oracle database server. 2. At the media sever, start Backup Exec. 3. On the navigation bar, click Restore. 4. Expand the All Resources icon. A list of previously backed up systems appears. 5. Determine which system you want to restore and expand the view to reveal backup sets that contain either tablespaces and/or logfiles. 6. Click the box preceding the {Archived Logfiles} directory from the appropriate backup set. 7. Submit the restore job to restore the {Archived Logfiles} data.
1170
Restoring the databases tablespaces (2nd restore operation): 1. After restoring the {Archived Logfiles} directory, on the navigation bar, click Restore. 2. Expand the All Resources icon. A list of previously backed up systems appears. 3. Determine which system you want to restore and expand the view to reveal backup sets that contain either tablespaces and/or logfiles. Clicking a backup set in the left pane reveals the sets contents in the right pane. 4. Click the backup set from which you restored the {Archived Logfile} directory. 5. Select each tablespace by clicking the preceding box. A check mark appears within each box. Do not select the {Archived Logfiles} directory. 6. Submit the restore job to restore the tablespaces. After each tablespace is restored, the Oracle Agent automatically attempts to perform media recovery for the tablespace. If the media recovery is unsuccessful, the agent creates an application event log entry with the specific Oracle error code.
Restoring a Closed Oracle Database

Use this section to guide you through the process of restoring a closed Oracle database.
To restore a closed Oracle database: 1. Close the database by typing the following command: shutdown;
Oracle Agent
Note If you cannot close the database using the normal shutdown command, you can close the database using the Oracle Enterprise Manager Shutdown Abort mode of the Shutdown Database dialog box, or the SHUTDOWN command with the ABORT option. 2. From the Backup Exec navigation bar, click Restore. 3. Expand the All Resources icon. A list of previously backed up systems appears.
1171
4. Determine which system you want to restore and expand the view to reveal backup sets that contain either tablespaces and/or logfiles. Clicking a backup set in the restore selections pane reveals the sets contents in the results pane. 5. Determine which backup set contains the entire Oracle database you want to restore. 6. Create a restore job by clicking the check box preceding the backup set you want to restore. 7. Submit the restore job to restore the entire Oracle database.
Restoring Individual Tablespaces

If one or more tablespace data files become corrupted or deleted, a single tablespace can be recovered easily with the Oracle Agent. Caution Do not restore individual tablespaces if an entire database becomes corrupted. Instead, restore the entire database, along with the pertinent transaction logs. See your Oracle Administrators Manual or call your Oracle Technical Support Center. A corrupted or deleted tablespace usually results in the following error when the database is initialized:
Corrupted or Deleted Tablespace Error
Tablespace recovery can also be performed with the Oracle Agent when either of the following conditions exist:

An empty copy of the missing data file cannot be created because the original file was created after the logfiles had been reset. An old version of the data file cannot be found and restored using a closed database restore procedure.
1172
To restore individual tablespaces: 1. At the Oracle database server, start the Oracle Server Manager. For logon information, type the following: Username = System Password = The password assigned to the System account Service (if applicable) = The name of the non-default database Connect as = sysdba 2. Make sure the database is mounted using an exclusive mount, but is not open. 3. Move to the media server and start Backup Exec. 4. On the navigation bar, click Restore. 5. Expand the All Resources icon. 6. Click the database backup set from which you want to restore. 7. Select the tablespaces you want to restore. 8. Restore as normal. 9. When the restore job completes, move back to the Oracle database server. 10. Start the Oracle Server Manager and connect as System, as a SYSDBA. 11. Type Recover. 12. After the recovery of the database completes, shut down and restart the database.
Oracle Agent
Restoring the Database Control File

When restoring the database control file Becf<SID>.bak from your storage media, keep in mind that it is automatically placed in the Oracle datafile directory on your database server. By default, it is \Orant\Database. After restoring the file, see the Restore Section Loss of Non-Mirrored Control Files in your Oracle Administrators Guide for more information on recovery of the database control file.
1173
Disaster Recovery Using the Oracle Agent

The ability to recover your Oracle databases after a catastrophic failure requires you to implement a plan of protection before a failure happens. When developing a pre-disaster plan, you should use the following recommended backup strategies:

Have at least one closed database backup of your database. Make a backup of the Windows directory on the Oracle database server, making sure that you also include the Windows Registry. Perform a full closed database backup if the structure of the database is altered. For example, if you create a new tablespace or drop an old one, a complete closed database backup is recommended. Schedule regular full online backups of your Oracle database server.
See also: Recovering a Remote Oracle Database Server from a Disaster on page 1175 Recovering a Combination Oracle Database Server/Media Server on page 1176
Disaster Recovery Prerequisites

You should perform the following before a disaster occurs. The following items are needed to fully recover your Oracle database server in the event of a disaster.
Make a full Oracle database server file system backup using Backup Exec. When making this backup, include both the Oracle database directory and the Windows system directory. However, do not include the Oracle database tablespace data files in this backup.
Using the Oracle Agent, make a second backup containing the Oracle database tablespace data files.
After creating these backups, you can now recover your Oracle database server in case a disaster occurs. See also: Backing Up Individual Online Tablespaces on page 1167
1174
Recovering a Remote Oracle Database Server from a Disaster
If your remote Oracle database server experienced a disaster, such as a hard drive failure, use this procedure to recover your Oracle databases: 1. Re-install Windows on the Oracle database server. During the re-install process, install Windows into a temporary directory that you can delete after your Oracle database server is running. 2. At the media server and using the storage media containing the full Oracle database server file system backup, restore the entire contents of the media to the Oracle database server using Backup Exec. 3. After restore completes, reboot your Oracle database server. Because the full system backup was restored, your computer is now booted using its original version of Windows. The system now contains the original version of Windows, the Backup Exec Oracle Agent, the Oracle databases minus the tablespaces, and any other files contained on the full backup media. If you have a full closed Oracle database backup, continue with step 4. If you do not have a full closed database backup, ignore step 4 and proceed with step 5. 4. Restore your last full closed Oracle database backup and start your database. Your database is now operational. To bring your database up-to-date, restore your most recent online Oracle database backup.
If you could not run step 4, continue from here: 5. At the media server, run another restore operation. This time, use the Oracle Agent to restore the storage media containing all of the Oracle tablespace data files. 6. When the restore operation completes, move to the Oracle database server and start the Oracle Server Manager. 7. Connect as System, as a SYSDBA. 8. Type recover database using backup controlfile. 9. After the recovery of the database completes, type alter database open resetlogs. 10. After the command completes, shut down and restart the database. Your Oracle database server should now be restored to full working order.
Oracle Agent
1175
11. Delete the temporary directory containing the copy of Windows that was used to initially boot the computer. Disaster recovery of the Oracle database server is now complete. See also: Restoring an Online Oracle Database on page 1170 Restoring Individual Tablespaces on page 1172
Recovering a Combination Oracle Database Server/Media Server

Use this section to guide you through the process of recovering a computer running both an Oracle database and a Backup Exec media server.
To recover a combination Oracle database and media server: 1. Re-install Windows on the Oracle database server/media server. During the re-install process, install Windows into a temporary directory that you can delete after your Oracle database server/media server is back up and running. 2. Re-install Backup Exec. 3. After re-installing Backup Exec, recatalog the media. 4. Restore the entire contents of the media containing the full server file system backup. This restore operation restores your original Windows system, along with any services required to run your Oracle databases. 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 Backup Exec Oracle Agent, the Oracle databases minus the tablespaces, and any other files contained on the full backup media. 6. Run another restore operation. This time, use the Oracle Agent to restore the media containing all of the Oracle tablespace data files. 7. When the restore operation completes, start the Oracle Server Manager. 8. Connect as System, as a SYSDBA. 9. Type Recover.
1176
Oracle Agent Error Message Chart
10. After the recovery of the database completes, shut down and restart the database. Your Oracle database server/media server should now be restored to full working order. 11. Delete the temporary directory containing the copy of Windows that was used to initially boot the computer. Disaster recovery of the Oracle database server is now complete. See also: Disaster Recovery Prerequisites on page 1174 Restoring Individual Tablespaces on page 1172
Oracle Agent Error Message Chart

The following chart lists possible Oracle Agent error messages and solutions. Because the Backup Exec Oracle Agent runs as a system service on the Oracle database server, any error message generated is written to the Oracle database servers Event Application Log.
Oracle Agent Error messages Application Log Error Message Unable to access database control file backup location = %1 Solution Verify that the specified directory is correct and exists. If the specified directory is incorrect, use the Oracle Agent Configuration Utility to set the correct location for the backup copy of the database control file. Unable to access archived log file location = %1 Verify that the specified directory is correct and exists. If the specified directory is incorrect, use the Oracle Agent Configuration Utility to set the correct location of the archive redo logfiles. System service error %1 The Oracle Agent was not installed correctly or its system service control parameters have been corrupted. Uninstall and then re-install the Oracle Agent.
Oracle Agent
1177
Oracle Agent Error Message Chart Oracle Agent Error messages Application Log Error Message (continued) (ALTER TABLESPACE %1 BEGIN BACKUP) failed. Oracle Status = %2 (ALTER TABLESPACE %1 OFFLINE IMMEDIATE) failed. Oracle Status = %2 (ALTER TABLESPACE %1 END BACKUP) failed. Oracle Status = %2 (ALTER TABLESPACE %1 ONLINE) failed. Oracle Status = %2 Solution (continued) The Oracle Agent was unable to complete the command. Check the Oracle database server code documentation for information about the particular status code.
Unable to access Oracle datafile (%1). Oracle The Oracle Agent is unable to access the named data files must be defined using a full path datafile. specification! Verify that the datafile was defined using a fully specified path. Unable to logon to the Oracle server. Oracle user account name %1 Make sure that the Oracle user name and password are valid for this Oracle account. This event will also occur if another instance of Backup Exec for Windows Servers attempts to access the Oracle Agent when the Oracle database instance is shut down. Unable to resolve the Oracle service name for Verify that the Oracle SQL Net configuration SID = %1 (Tnsnames.ora) has been set up properly for the named SID.
1178
VERITAS Backup Exec - Agent for Lotus Domino
The VERITAS Backup Exec for Windows Servers Agent for Lotus Domino (Lotus Domino Agent) is installed as a separate, add-on component of Backup Exec for Windows Servers. The Lotus Domino Agent allows you to back up and restore Lotus Domino versions R5 and later databases and transaction logs on local media servers and on remote computers. You can integrate Lotus Domino database backups with regular server backups without separately administering them or using dedicated hardware.
The Lotus Domino Agent provides support for:

Full, incremental, and differential online backups of Lotus Domino databases and transaction logs using Lotus Domino APIs. Restores of Lotus Domino databases and transaction logs and point in time restores. Recycling of Lotus Domino transaction logs after a successful backup. Flexible scheduling capabilities. Backup and restore of partitioned and clustered Lotus Domino servers.
See also: Installing the Lotus Domino Agent on the Media Server on page 1181
Lotus Domino Agent
1179
Lotus Domino Agent Requirements
Lotus Domino Agent Requirements

The Lotus Domino Agent supports Lotus Domino R5 and later. Caution If transaction logging is enabled and you have Lotus Domino Release 5.0.3 or earlier, the transaction log to which the Lotus Domino server is actively writing transactions cannot be completely backed up. This may result in data loss during a restore operation. Following are the requirements for backing up Lotus Domino database files residing on the media server, or for remote Windows computers and workstations. If the Lotus Domino files you want to back up are on the local media server, the server must have:

Backup Exec for Windows Servers An Intel-compatible processor The Lotus Domino data directory on the Lotus Domino server
If the Lotus Domino files you want to back up are on a remote computer, the remote computer must have:

Windows operating system Backup Exec Remote Agent for Windows Servers An Intel-compatible processor Corresponding Windows Administrative Share for each volume that contains Lotus Domino databases The Lotus Domino data directory on the Lotus Domino server
Following are requirements for backing up Lotus Domino transaction logs:

Transaction logging must be enabled to perform differential and incremental backups and to perform point in time recovery. The Lotus Domino logging style must be set to archive if you want to back up the transaction logs.
See also: Viewing and Selecting Lotus Domino Databases on page 1182
1180
Installing the Lotus Domino Agent on the Media Server
Installing the Lotus Domino Agent on the Media Server

The VERITAS Backup Exec Agent for Lotus Domino is installed as a separate, add-on component of Backup Exec for Windows Servers, and can be installed locally or remotely to back up Lotus Domino databases. Whenever the Lotus Domino Agent is installed on the media server, the Backup Exec Remote Agent is included as part of the Lotus Domino Agent installation. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. Because a Remote Agent is also a Client Access License (CAL), you must install the Remote Agent on any remote Windows server that you want to back up. You cannot select resources from a remote server for backup until a Remote Agent has been installed. If you are using the Lotus Domino Agent to protect databases on the local media server only, you are entitled to install the Remote Agent that was included with the Lotus Domino Agent installation to one remote Windows server so that resource can be protected by Backup Exec. However, if the Lotus Domino Agent is protecting a remote resource, the Remote Agent is necessary in order to perform remote backup and restore operations, and you are not entitled to install it on another Windows server. For instructions on installing the Lotus Domino Agent on the local media server, see Installing Backup Exec Options on a Local Server on page 49. For instructions on installing the Lotus Domino Agent on a remote resource, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the Remote Agent to Remote Windows Servers Using the Command Line on page 823. See also: Configuring Default Lotus Domino Options on page 1184 Backing Up Lotus Domino Databases on page 1185 Restoring Lotus Domino Databases on page 1189
Lotus Domino Agent
Appendix K, VERITAS Backup Exec - Agent for Lotus Domino
1181
Viewing and Selecting Lotus Domino Databases

After installing the Lotus Domino Agent, you can view and select existing Lotus Domino databases in the selections pane. To view databases created while Backup Exec is running, select Refresh from the View menu or press <F5>. To back up the newly-created database, select it from the volume level, unless the entire volume is already selected for backup.
To view Lotus Domino databases on the local server:
On the navigation bar, click Backup, and then 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
Note 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.
1182
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. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections.
Lotus Domino Agent
1183
Configuring Default Lotus Domino Options
3. Click Remote Selections, and then click Microsoft Windows Network. 4. 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. See also: Backing Up Lotus Domino Databases on page 1185 Restoring Lotus Domino Databases on page 1189 Preparing for Disaster Recovery on a Lotus Domino Server on page 1195
Configuring Default Lotus Domino Options

You can configure default settings for Lotus Domino databases for all new jobs you create. When you create a job, you can use the default settings or modify the Domino properties for the job.
To configure default Domino options for all new jobs: 1. On the Tools menu, click Options. The Options - Set Application Defaults dialog box appears. 2. On the Properties pane, under Job Defaults, click Domino. 3. Select Lotus Domino backup default options. For more information, see the Backup job properties for Lotus Domino databases table in the Backup Options for Lotus Domino Databases on page 1187 section. 4. Select Lotus Domino restore default options. For more information, see the Restore job properties for Domino databases table in the Restore Options for Lotus Domino Databases on page 1192 section. 5. Click OK to save the options or select other options from the Properties pane.
1184
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. See also: Lotus Domino Transaction Logs on page 1186 Backup Options for Lotus Domino Databases on page 1187 Restore Options for Lotus Domino Databases on page 1192
Supported Lotus Domino Database Configurations

You can back up the following types of Lotus Domino database configurations using the Lotus Domino Agent:
Domino Server Databases. Domino Server databases can be Logged or Unlogged. They are located in a folder in the Domino data directory, typically Lotus\Domino\Data, but may also be linked to the Domino data directory using Lotus Linked Databases. Logged Domino Server Databases. A logged Domino Server database logs transactions for one or more Lotus databases. If transaction logging is enabled on the server, all database transactions go into a single transaction log. Unlogged Domino Server Databases. An unlogged Domino Server database does not have transaction logging enabled, or the transaction logging has been disabled for specific server databases. Unlogged Domino Server databases will be backed up in their entirety when a full, differential, or incremental backup is performed, but the database can only be restored to the point of the latest database backup.
Lotus Domino Agent
1185
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 R5 backup methods. The database can be restored only to the point of the latest database backup.
Lotus Domino Transaction Logs

Lotus Domino has the ability to log transactions for one or more Lotus Domino databases. Lotus Domino databases are logged by default when transaction logging is enabled on the Lotus Domino server and the database is in the Domino data directory. When transaction logging is enabled on the server, each Lotus Domino database is assigned a database instance ID (DBIID). Each transaction recorded in the log includes the DBIID, which is used to match transactions to the database during a restore. A new DBIID may be assigned to the database when some Lotus Domino operations are performed. When the new DBIID is assigned, all new transactions recorded in the log use the new DBIID; however, previous transactions have the old DBIID and will not match the new DBIID for the database. To prevent data loss, it is recommended that a full backup be performed when a database receives a new DBIID since transactions with the old DBIID cannot be restored to the database. A full backup includes all current transactions on the database and ensures that only the transactions with the new DBIID are needed to restore the database. You can select only one logging style when transaction logging is enabled on the server. Following are the two styles of logging for Lotus Domino databases:
Archive logging. This logging style produces a transaction log that is limited only by the capacity of your mass storage. Archive logging is the recommended logging style to be used with the Lotus Domino Agent since all the transaction logs can be backed up and marked for recycling. When the transaction logs are recycled the Lotus Domino server reuses the existing transaction logs after they are backed up to create space for new transaction logs. Circular logging. This logging style reuses the log file after a specific log file size is reached. By reusing the log file you are saving resources; however, you are also limiting your recovery options because the database can only be recovered to the point of the last full backup. If the incremental or differential backup method is selected for a backup job, a full backup of the changed databases is performed since transaction logs cannot be backed up.
Caution When circular logging is enabled, the circular transaction log cannot be backed up, which could result in the loss of changes made to the database since the last backup was performed.
1186
Backup Options for Lotus Domino Databases
Backup Options for Lotus Domino Databases

This procedure details how to select backup job properties for Lotus Domino databases and provides definitions for Domino-specific backup options. You should back up Lotus Domino databases during off-peak hours and disable Lotus Domino agents before running the backup. The transaction logs will automatically be included in the backup job. For details on how to create a backup job, and for definitions of all other backup options see Creating a Backup Job on page 235. 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 back up a Lotus Domino server simultaneously from multiple media servers.
To select backup job properties for Lotus Domino databases: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click Domino.
Lotus Domino Agent
1187
Backup Options for Lotus Domino Databases Backup Job Properties for Lotus Domino

Backup job properties for Lotus Domino databases Item Backup method: Description 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. 1188 Administrators Guide
Restoring Lotus Domino Databases Backup job properties for Lotus Domino databases (continued) Item Mark archive logs for recycling Description 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. 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. Note This option may not work for Lotus Domino versions prior to 5.0.7. For more information about this limitation of Lotus Domino, go to the Lotus Domino web site.
4. Start the backup job or select other backup options from the Properties pane. See also: Backing Up Data on page 233
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. You must close the databases that you want to replace. 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.
Lotus Domino Agent
1189
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.
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 R5 Backup Job Contains Lotus Domino database files
Contains Lotus Domino transaction logs
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.
1190
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.
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.
Transaction Logs backup set for Differential Backup 0002.
Lotus Domino Agent
1191
Restore Options for Lotus Domino Databases
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 R5 backup set to restore, all database files and necessary transaction logs are automatically restored. You can also choose to restore specific database files.
To select restore job properties for Lotus Domino databases: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click Domino.
1192
Restore Options for Lotus Domino Databases Restore Job Properties for Lotus Domino

Restore job properties for Lotus Domino databases Option Seconds to wait for the database to go offline Description 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.
Database Identification Retain original IDs Select this option to restore the original database IDs.
Assign new database ID Select this option to assign new IDs to the database. Assign new database ID Select this option to assign new IDs to the database. A replica ID is and replica ID 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. Appendix K, VERITAS Backup Exec - Agent for Lotus Domino 1193
Lotus Domino Agent
Restore Options for Lotus Domino Databases Restore job properties for Lotus Domino databases (continued) Option Point in time restore Description 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.
Caution If your Lotus Domino database is replicated, the databases on each machine 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. 4. Start the restore job or select other options from the Properties pane. See also: Restoring Data on page 395 Lotus Domino Transaction Logs on page 1186
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.
To redirect the restore of a Lotus Domino database: 1. Select the media that contains the data you want to restore. 2. On the navigation bar, click Restore. 3. Select the Lotus Domino databases. 4. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click File Redirection.
1194
Preparing for Disaster Recovery on a Lotus Domino Server
5. Select Redirect file sets. 6. 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. 7. Enter the logon account for the server in Server logon account. 8. Enter the path to which you are restoring in Restore to path. 9. Enter the logon account for the path in Path logon account. 10. Start the redirection job or select other restore options from the Properties pane. See also: Restoring Data on page 395 Configuring Logon Accounts on page 347

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.
Lotus Domino Agent
1195
Disaster Recovery of a Lotus Domino Server

Before restoring your Lotus Domino server, you must first completely recover the Windows computer and then recover or re-install Lotus Domino to the same location as before the disaster occurred. All of the Lotus Domino system data must be recovered, including log.nsf, names.nsf, template files, notes.ini, mail.box, and ID files. Note If transaction logging is enabled on the Lotus Domino server, go to the section that contains the steps for disaster recovery for the style of logging selected on the server. System recovery can be performed manually (see Disaster Preparation and Recovery on page 531) or with Backup Execs Intelligent Disaster Recovery option (see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855). After rebuilding the server, you can restore the databases from your most recent backup.
To recover a Lotus Domino server and databases: 1. Restore or re-install the Lotus Domino server program directory to the same location as before the disaster occurred. 2. Restore the notes.ini, cert.id, and server.id files from the last full backup of the Lotus Domino server program directory. 3. Use the Lotus Domino Agent to restore the databases to the Domino data directory. 4. Start the Lotus Domino Server. See also: Disaster Recovery of a Lotus Domino Server Using Circular Logging on page 1198 Disaster Recovery of a Local Windows NT Computer on page 541 Restoring Data on page 395 Restore Options for Lotus Domino Databases on page 1192
1196
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. If all of the transaction logs are lost, in order to recover the database you must have an up-to-date Notes.ini file from the Lotus Domino server, the backups of the database, and archived log extents. The following steps provide instructions for recovering the Lotus Domino server, databases, and transaction logs.
To recover the Lotus Domino server, databases, and transaction logs when archive logging is enabled: 1. Restore or re-install the Lotus Domino server program directory (excluding the notes.ini, cert.id, and server.id files) to the same location as before the disaster occurred. 2. Reboot the server. 3. Check that the transaction 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. 4. Restore the last transaction logs from the last backup to the logdir directory. Caution Do not start the Lotus Domino server after performing the previous steps. 5. Restore the notes.ini, cert.id, and server.id files from the last full backup of the Lotus Domino server program directory. 6. To have Lotus Domino create the control file when the server starts, set the following parameter in the Notes.ini file: translog_recreate_logctrl=1 Note If you enter the translog_recreate_logctrl=1 parameter on the last line in the Notes.ini file, you must press <Enter> after the parameter. 7. Use the Lotus Domino Agent to restore the databases to the Domino data directory.
Lotus Domino Agent
1197
8. Start the Lotus Domino server. After the Lotus Domino server is restarted, run a full backup of the server since new DBIIDs have been assigned. See also: Restore Options for Lotus Domino Databases on page 1192 Restoring Data on page 395
Disaster Recovery of a Lotus Domino Server Using Circular Logging

If circular logging is enabled and the transaction log is lost, the Lotus Domino databases can only be recovered to the point of the last backup.
To recover the Lotus Domino server and databases when circular logging is enabled: 1. Restore or re-install the Lotus Domino server program directory (excluding the notes.ini, cert.id, and server.id files) to the same location as before the disaster occurred. 2. Check that the log directory (logdir) is created and does not contain old files. If the log directory was not created, recreate the directory to the same location as before the disaster occurred. Caution Do not start the Lotus Domino server after performing the previous steps. 3. Restore the notes.ini, cert.id, and server.id files from the last full backup of the Lotus Domino server program directory to the same location as before the disaster occurred. 4. To have Lotus Domino create the circular log file in the log directory (created in step 2) when the server starts, set the following parameter in the notes.ini file: translog_path=logdir 5. Use the Lotus Domino Agent to restore the databases to the Domino data directory. See also: Restoring Data on page 395 Restore Options for Lotus Domino Databases on page 1192
1198
R/3 Agent
VERITAS Backup Exec - Agent for R/3 for Oracle Server
The Backup Exec for Windows Servers Agent for R/3 for Oracle Server (Backup Exec R/3 Agent) is installed as a separate, add-on component of Backup Exec for Windows Servers. The Backup Exec R/3 Agent allows you to submit backup, restore, and archive jobs of SAP R/3 for Oracle for Windows NT/2000 using the R/3 BACKINT interface to the Backup Exec for Windows Servers. It follows the BC-BRI BACKINT Interface for ORACLE Databases specification, version 3.0. You can use the R/3 tools and the BACKINT interface, along with the Backup Exec R/3 Agent to connect to a Backup Exec server and perform backup and restore on individual files, entire databases, or individual tablespaces in either online or offline mode, as well as archive offline redo logs. The BACKINT implementation acts as a client for Backup Exec. You use the R/3 tools to run the BACKINT executable, which provides command line options that describe the operation to perform, such as backup, restore, or archive. A file is also provided (biparam.ini) in which you set Backup Exec parameters for jobs that you submit from the SAPDBA or CCMS console, such as specifying a server or device to use for the job, or specifying the backup compression mode. The BACKINT executable connects to the specified Backup Exec server, and the requests become Backup Exec operations. Jobs submitted from the SAPDBA or CCMS console, via BACKINT, to Backup Exec are treated as run now jobs. Jobs may be placed in a Backup Exec job queue as queued if all drives are busy. After the jobs are in the queue, the Backup Exec administrator can edit or cancel the job. Note You must always use SAPDBA or CCMS to run database-related operations. When the job is complete, the Backup Exec server writes a standard job log, as it does for any submitted job. You can view this job log using the standard Backup Exec administration console (remote or local). The BACKINT executable also sends the results of the operations to the SAP R/3 tools. When a job is initiated by SAPDBA or CCMS, a job log with an eight-character name is created to represent that job. The R/3 system stores that job log in a directory:
<x>:\Oracle\<SID>\sapbackup
1199
where <x> is the database installation drive and <SID> represents the system ID of the Oracle instance. This file is a plain ASCII text file that you can view with any text editor. A file called Backint.mdb that correlates the R/3 catalog with the Backup Exec catalog is maintained in the Usr\<SID>\sys\exe\run directory. You must be able to restore this file in order to restore data to the R/3 server using the Backup Exec R/3 Agent. The Backup Exec R/3 Agent is capable of supporting multiple media servers running on the same network. See also: Backup Exec R/3 Agent Security on page 1200
Backup Exec R/3 Agent Security

The BACKINT interface functions as a client to the Backup Exec server. As such, all Windows security limitations that apply to the Backup Exec administration console also apply to the BACKINT interface. You must have the appropriate privileges on both the R/3 and media servers to be able to perform both backup and restore operations. The Backup Exec service account must have:

Access to selections in jobs submitted by the BACKINT interface Rights to the volumes on which the selections are contained
See also: Changing Windows Security on page 44.
Backup Exec Alerts and the BACKINT Interface

Backup Exec generates alerts in some conditions. The BACKINT interface handles these alerts in one of two modes - unattended mode or interactive mode:
Unattended mode. In this mode, any alert that requires a response from you causes the job to fail. If such an alert occurs, it appears on the R/3 system console. Any alerts that contain only informative text also appear on the R/3 system console. You can start the operation in attended mode by setting Confirm backup parameters to Yes on the Backup Database screen of SAPDBA.
Interactive mode. In this mode, all alerts appear on the R/3 console. You must respond to these alerts as prompted for the job to continue.
1200
R/3 Agent
Requirements for Backup Exec R/3 Agent

Windows NT version 4.0 with Service Pack 4, or Windows 2000, Windows XP, or Windows.NET Oracle Enterprise Server version 7.3.x SAP R/3 version 3.1h, 4.08, 4.6c and 4.6d All R/3 databases to be backed up must be placed in the ARCHIVE_LOG mode and Automatic Archival must be enabled using the database administration tools. For more information on how to check or perform this operation, consult the R/3 User Manual or your R/3 Database Administrator's Guide. All Oracle databases to be protected must be managed by the R/3 system. To protect Oracle databases not managed by R/3, purchase the VERITAS Backup Exec for Windows Servers Agent for Oracle Server.
Note The Backup Exec R/3 Agent does not support data stored on RAW partition types. See also: Installing the Backup Exec R/3 Agent on page 1201 Backup Exec R/3 Agent Security on page 1200
Installing the Backup Exec R/3 Agent

Note Before you install the agent, verify that the R/3 system environment variables are set correctly for the server you plan to protect. The Backup Exec R/3 Agent's default directory is the R/3 database's home Usr\<SID>\sys\exe\run directory. If this is the initial installation of Backup Exec, see Installing Backup Exec on page 46. To install the Backup Exec R/3 Agent, see Installing Backup Exec Options on a Local Server on page 49.
Appendix L, VERITAS Backup Exec - Agent for R/3 for Oracle Server
1201
Using the R/3 Agent to Back Up the R/3 Database

Use the Backup Exec R/3 Agent to frequently back up the database. The more frequently you back up the database, the less time it takes to recover it in the event of data loss. In addition to these regularly scheduled backups, it is recommended that you close the R/3 database and do a file level backup whenever you alter the structure of the database. The following backup strategies are highly recommended in order to recover your R/3 database server after a catastrophic failure.
Have at least one closed database backup of your database (see your R/3 Database Administrators Guide for details). Do this by using Backup Exec to make a full R/3 database server file system backup. If the structure of the database is altered, you should perform a full closed database backup. When you perform your full file system backups, make sure the R/3 database control and data files are excluded from the backup set. Because these database files are both locked and unreadable when the database is open, they will appear as Skipped in the Backup Exec Job History job log if you attempt to back them up during your full file system backup jobs. Create a backup of the Windows directory on the R/3 database server, making sure that you also include the Windows registry. Always include the Backint.mdb file (in the Usr\<SID>\sys\exe\run directory) in your regular backups of the R/3 database server. This file correlates the R/3 catalog with the Backup Exec catalog. You must have this file in order to restore data. Use the Backup Exec R/3 Agent to perform regularly-scheduled offline and online backups of the R/3 database server. Create regular backups of the rest of the data that resides on the server.
Note All scheduled jobs must be handled by the R/3 database management system. Any attempt to schedule jobs not using the R/3 database management system can potentially damage your database. For more information on how to check or perform this operation, consult the R/3 User Manual or your Oracle Server Administrator's Guide.
Specifying Backup Exec Parameters

The BACKINT interface specifications provide for a file that you can use to specify Backup Exec parameters for backup jobs that you submit from the SAPDBA or CCMS console. This backup utility parameter file is maintained in Windows .ini file format, and is called Biparam.ini. A template of this file, named Biparam.ini, is included with the installation.
1202
R/3 Agent
The backup utility parameter file is used for every backup job submitted to Backup Exec from the SAPDBA or CCMS console. If you are directing the backup job to a remote media server, you must edit the backup utility parameter file and change the Server entry to reference the media server. If a Server entry is not supplied, the backup will be submitted to the local server. You can also create a new .ini file to use with specific jobs. You specify which .ini file is to be used when you submit the job from the SAPDBA or CCMS console. Any valid file name or location can be specified as long as you enter the complete file specification. Note All Backup Exec options not specified in the .ini file will use the values and defaults specified by the media server.
To edit the backup utility parameter file: 1. Open the Biparam.ini file, located in the Usr\<SID>\sys\exe\run directory (or any .ini file you created for a specific job) and make any changes. 2. Edit any of the following options in the Biparam.ini file to configure the media server.:
Options in the Biparam.ini file Use this option: Server=<server name> For this operation: To specify a Backup Exec server to perform this backup job. Note Restore jobs are automatically directed to the Backup Exec server from where the original backup was executed. The default is the local machine. Device=<device name> To specify a device, by name, for use in backup operations. The default is the first available device. Note The device name must match the device exactly as it appears in Backup Exec for Windows Servers. Media=<media name> To specify a name for new media. Note This option is only effective when new media is used for the backup, otherwise the original media name is retained. The default is a media name automatically specified by Backup Exec, which is a date and time stamp of when the media is created; for example, Media created 07/24/98 10:51:59 PM.
1203
Using the R/3 Agent to Back Up the R/3 Database Options in the Biparam.ini file (continued) Use this option: For this operation:
Description=<backup set To specify a name for the next backup set description. name> The default is a backup set description automatically specified by Backup Exec, which is an incremental number of the backup sets created since the installation of Backup Exec; for example, Backup 0020. Compression = <backup compression mode> To specify the backup compression mode. Allowable values are: Best - Use hardware compression; if not available, then use software compression. Hardware - Use hardware compression; if not available, then use no compression. Software - Use software compression. None - Use no compression. The default is Hardware. Auto Verify=<> To toggle the Verify after backup option. Note Because Verify after backup is not directly supported by the R/3 tools, the results are not sent back to the R/3 system. This option is available for user information only when the backup job is viewed through the Backup Exec administration console. The default is on. Print Log=<> To toggle the printing of job history job log information after a backup job completes. The default is off.
See also: Backing Up the R/3 Database on page 1205 Restoring the R/3 Database on page 1206 Backup Exec Alerts and the BACKINT Interface on page 1200
1204
R/3 Agent
Backing Up the R/3 Database

You must have the appropriate privileges on both the R/3 and media servers to be able to perform both backup and restore operations. Before you submit a backup operation, you must:

Enter configuration information for your Backup Exec server in the Biparam.ini file found in your Usr\<SID>\sys\exe\run directory. Place all SAP R/3 databases to be backed up in the ARCHIVE_LOG mode and enable Automatic Archival using the SAPDBA or CCMS console. For more information on how to check or perform this operation, consult the R/3 User Manual or your Oracle Server Administrator's Guide.
Note The Backup Exec R/3 Agent does not support concurrent backup or restore operations. Attempting to back up or restore the same R/3 database from more than one media server at a time causes the operations to fail.
To submit a backup job to Backup Exec: Note If the BACKINT interface is in unattended mode, any alert that requires a response from you causes the backup job to fail. You can start the backup job in attended mode by setting Confirm backup parameters to Yes in the Backup Database screen of SAPDBA. 1. From the SAPDBA console, select the appropriate backup option (database or archive logs). 2. Select Backup Device Type, and then select util_file for an offline database backup or select util_file_online for an online database backup. 3. Select Backup utility parameter file, and then enter the full path to the Biparam.ini file (or any other .ini file you created), including the file name. 4. Press <Enter>. 5. Verify that you have selected the correct backup type for the utility file type you specified (online, offline, etc.). 6. Start the job.
1205
Restoring the R/3 Database
Restoring the R/3 Database

You must have the appropriate privileges on both the R/3 and media servers to be able to perform both backup and restore operations.
To submit a restore job to Backup Exec: 1. From the SAPDBA console, select the Restore Database option. 2. Select Restore Type, and then select the catalog that you want to restore. 3. Start the job. Note Restore jobs are automatically directed to the Backup Exec server from where the original backup was executed. 4. When the restore operation completes, open the SAPDBA or CCMS console, and select Check and Repair Database. 5. Select Automatic Recovery, and then follow the online prompts.
Disaster Recovery Using the Backup Exec R/3 Agent

The ability to recover your R/3 database server after a catastrophic failure requires you to implement a plan of protection before a failure happens. When developing a pre-disaster plan, the following backup strategies are highly recommended and should be followed:
Have at least one flat file database backup of your database and make regular offline backups using SAPDBA or CCMS (see your R/3 Database Administrators Guide for details) Back up the Windows directory on the R/3 database server, making sure that you also include 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, a complete offline database backup is recommended
1206
R/3 Agent
Always include the Backint.mdb file (in the Usr\<SID>\sys\exe\run directory) in your regular flat file backups of the R/3 database server. This file correlates the R/3 catalog with the Backup Exec catalog. You must have this file in order to restore data. Schedule full online backups of your R/3 database server regularly.
See also: Disaster Recovery Prerequisites on page 1207 Recovering a Remote R/3 Database Server from a Disaster on page 1208 Recovering a Combination R/3 Database Server/Media Server on page 1209
Disaster Recovery Prerequisites

The following backups are required in order to fully recover your R/3 database server in the event a disaster occurs.
Create a FULL R/3 database server file system backup using Backup Exec. When creating this backup, include both the R/3 database directory and the Windows system directory. However, if the database must remain open, do not include the R/3 database tablespace data files in this backup.
Create a second backup containing the R/3 database tablespace data files (see your R/3 Database Administrators Guide for details).
After creating these backups, you can now recover your R/3 database server in case a disaster occurs. See also: Backing Up Data on page 233 Recovering a Remote R/3 Database Server from a Disaster on page 1208 Recovering a Combination R/3 Database Server/Media Server on page 1209
1207
Recovering a Remote R/3 Database Server from a Disaster
To recover a remote R/3 database server: 1. Re-install Windows on the R/3 database server. During the re-install process, install Windows into a temporary directory that you can delete after your R/3 database server is back up and running. 2. At the media server, and using the storage media containing the FULL flat file R/3 database server file system backup, restore the entire contents of the media to the R/3 database server using Backup Exec. 3. After restore completes, reboot your R/3 database server. Because the full system backup was restored, your computer should now boot using its original version of Windows. The system should now contain the original version of Windows, the Backup Exec R/3 Agent, the R/3 database minus the tablespaces, and any other files contained on the full backup media. 4. If you have a full offline R/3 database backup, restore your last full offline R/3 database backup and start your database. If you do not have a full offline database backup, skip this step and proceed to step 5. Your database is now operational. 5. Restore the Backint.mdb file from the latest full server backup. This file correlates the R/3 catalog with the Backup Exec catalog. 6. To bring your database up-to-date, restore your most recent online or offline R/3 database backup. 7. At the media server, run another restore operation. This time, use the Backup Exec R/3 Agent to restore the storage media containing all of the R/3 tablespace data files. 8. When the restore operation completes, open the SAPDBA or CCMS console, and select Check and Repair Database. 9. Select Automatic Recovery, and then follow the online prompts. Disaster recovery of the R/3 database server is now complete. See also: Disaster Recovery Prerequisites on page 1207 Recovering a Combination R/3 Database Server/Media Server on page 1209
1208
R/3 Agent
Recovering a Combination R/3 Database Server/Media Server

1. Re-install Windows on the R/3 database server/media server. During the re-install process, install Windows into a temporary directory that you can delete after your R/3 database server/media server is back up and running. 2. Re-install Backup Exec. 3. Recatalog the media containing the full flat file R/3 database server file system backup, and the media containing the R/3 database tablespace data files. 4. Restore the entire contents of the media containing the full flat file server file system backup. This restores your original Windows system, along with any services required to run your R/3 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 Backup Exec R/3 Agent, the R/3 database minus the tablespaces, and any other files contained on the full backup media. 6. Restore the Backint.mdb file from the latest full server backup. This file correlates the R/3 catalog with the Backup Exec catalog. 7. Run another restore operation. This time, use the Backup Exec R/3 Agent to restore the media containing all of the R/3 tablespace data files. 8. When the restore operation completes, open the SAPDBA or CCMS console, and select Check and Repair Database. 9. Select Automatic Recovery, and then follow the online prompts. Disaster recovery of the R/3 database server is now complete. See also: Disaster Recovery Prerequisites on page 1207 Recovering a Remote R/3 Database Server from a Disaster on page 1208
1209
1210
SharePoint Agent
VERITAS Backup Exec - Agent for Microsoft SharePoint Portal Server
The SharePoint Agent enables network administrators to perform backup and restore operations on SharePoint Portal Server installations that are connected to a network. SharePoint backups can be integrated with network backups without separate administration or dedicated hardware. 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, which include database files, log files, and backup patch files Microsoft Search Service (MSSearch) system resources, which include the property store, subscriptions store, full-text index files, and propagated indexes SharePoint Portal Server configuration information, including Web Storage System configuration information, content source information, server properties, and access accounts The Applications folder, which contains a subfolder for each workspace on the server Shortcuts or content sources that reference the local file system Individual documents that are contained in the workspaces
SharePoint Agent does not back up the following data:
Content source crawls (a content source is a URL that SharePoint Portal Server uses as a starting point to search, or crawl, for content in documents stored outside the workspace) scheduled using Microsoft Windows 2000 Scheduled Tasks Scheduled tasks for processing subscriptions
1211
Requirements for the SharePoint Agent
Gatherer logs Lotus Notes configuration information
For more information about the various types of data stored on SharePoint Portal Server, see your Microsoft SharePoint Portal Server documentation. Note SharePoint Portal Server is available only for Windows 2000. See also: Requirements for the SharePoint Agent on page 1212 Installing the SharePoint Agent on page 1213 Backing Up a SharePoint Portal Server or Workspace on page 1213 Restoring SharePoint Portal Servers and SharePoint Portal Workspaces on page 1215 Redirecting SharePoint Portal Server Restore Jobs on page 1217 Disaster Recovery of a SharePoint Portal Server on page 1221
Requirements for the SharePoint Agent

The SharePoint Agent must be installed on the media server. The Backup Exec Remote Agent for Windows Servers must be installed on each remote SharePoint Portal Server that will be protected. The credentials specified by the logon account used for backing up and restoring SharePoint Portal Server data must have local administrative rights on the server where SharePoint is installed. Additionally, to backup and restore individual documents in workspaces, the account must be granted the Coordinator role in SharePoint on all folders to be accessed in the workspace. For more information on granting permissions on folders in the workspace, see your SharePoint Portal Server documentation.
1212
Installing the SharePoint Agent
Installing the SharePoint Agent

The SharePoint Agent must be installed on the media server. If Backup Exec is not already installed, see Installing Backup Exec on page 41.
SharePoint Agent
To install the SharePoint Agent, see Installing Backup Exec Options on a Local Server on page 49. To install the Backup Exec for Windows Servers Remote Agent, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54.
Backing Up a SharePoint Portal Server or Workspace

There are no SharePoint-specific options to configure when you back up a SharePoint Portal Server. When backing up a SharePoint Portal Server, a full backup will be performed, which backs up the entire SharePoint Portal Server database and all relevant data from other dependent data stores. See also: Creating a Manual Backup Job by Configuring Job Properties on page 236
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 a folder and document objects from a SharePoint Portal Workspace: 1. Start Backup Exec for Windows Servers. 2. On the navigation bar, click Backup. 3. From the Backup Selections pane, and under Local Selections, expand Microsoft SharePoint Portal Workspaces. If SharePoint Portal Server is installed remotely, expand Remote Selections. 4. Select the folders and/or documents in the workspace that you want to back up.
Appendix M, VERITAS Backup Exec - Agent for Microsoft SharePoint Portal Server
1213
Backing Up a SharePoint Portal Server or Workspace Backup Job Properties dialog box
5. Start the backup job or select other backup options from the Properties pane. 6. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job you want to view.
1214
Restoring SharePoint Portal Servers and SharePoint Portal Workspaces

With the SharePoint Agent, you can restore the entire SharePoint Portal Server or, if they were backed up separately, just the individual documents that are contained in the SharePoint Portal Workspaces. You can redirect the restore of a SharePoint Portal Server to a different server than the one from which it was backed up. In addition, you can redirect the restore of SharePoint Portal Workspaces to an alternate workspace or file share. There are some limitations on what information can be restored in SharePoint Portal Workspaces. The Microsoft SharePoint Portal Workspaces interface in Backup Exec is intended to provide backup and restore of individual documents stored in the Documents subfolder for each workspace and should not be used as a substitute for SharePoint Portal Server database backup. Many of the other files and folders contained in the workspace are controlled by the SharePoint Portal Server software and may not restore successfully into the workspace even though they are available for backup. In addition, when restoring individual documents, the creation date and modification date properties do not restore. Note SharePoint Portal Server must be installed on the target server before you can restore a SharePoint Portal Server. Caution When you restore a SharePoint Portal Server database, all SharePoint data on the target server is overwritten. See also: Creating a Manual Restore Job by Configuring Job Properties on page 404
SharePoint Agent
Restoring a SharePoint Portal Server
To restore a SharePoint Portal Server: 1. Place the media containing the data you want to restore in the storage device. 2. On the navigation bar, click Restore. 3. Navigate to and select the SharePoint Portal Server database you want to restore.
1215
4. On the Properties pane, set the appropriate options. 5. Start the restore job. 6. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job you want to view.
Restoring a SharePoint Portal Workspace
To restore SharePoint Portal workspace data: 1. Place the media containing the data you want to restore in the storage device. 2. On the navigation bar, click Restore. 3. Navigate to and select the SharePoint workspace data you want to restore. 4. On the Properties pane, set the appropriate options. 5. Start the restore job. 6. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job you want to view. See also: Backing Up Folders and Documents from a SharePoint Portal Workspace on page 1213 Redirecting SharePoint Portal Server Restore Jobs on page 1217
1216
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.
SharePoint Agent
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: 1. Place the media containing the data you want to restore in the storage device. 2. On the navigation bar, click Restore. 3. Navigate to and select the SharePoint Portal Server database you want to restore. 4. On the Properties pane, under Destination, click SharePoint Redirection. 5. Check the box labeled Redirect SharePoint Portal Server sets. 6. In the Restore to server field, enter the name of the SharePoint server to which you are restoring. Use the following format: \\servername.
Restore Job Properties -Sharepoint Redirection
7. Use the default logon account as indicated, or click Change to select a different one.
1217
8. On the Properties pane, select other job properties that might be appropriate for your environment. 9. Start the restore job. 10. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job you want to view. After the restore completes, it is recommended that you perform a full backup of the restored SharePoint Portal Server databases. See also: Backing Up a SharePoint Portal Server or Workspace on page 1213 Restoring a SharePoint Portal Server on page 1215
Redirecting SharePoint Portal Workspace Restore Jobs

Before redirecting the restore of SharePoint Portal workspace data, the SharePoint Portal Server software must be installed on the target server. Caution When you restore SharePoint Portal workspace data, all documents that exist in the target location are overwritten by those being restored.
Restoring Workspace Data To Another Workspace
To redirect SharePoint Portal workspace data to another workspace: 1. Place the media containing the data you want to restore in the storage device. 2. On the navigation bar, click Restore. 3. Navigate to and select the SharePoint Portal workspace data you want to restore. 4. On the Properties pane, under Destination, click SharePoint Redirection. 5. Check the box labeled Redirect SharePoint Portal document sets. 6. In the Restore to server field, enter the name of the SharePoint server to which you are restoring. Use the following format: \\servername.
1218
7. In the Restore to workspace field, enter 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.
Restore Job Properties - Sharepoint Redirection
SharePoint Agent
8. Use the default logon account as indicated, or click Change to select a different one. 9. On the Properties pane, select other job properties that might be appropriate for your environment. 10. Start the restore job. 11. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job you want to view. See also: Backing Up Folders and Documents from a SharePoint Portal Workspace on page 1213 Restoring a SharePoint Portal Workspace on page 1216
1219
Restoring Workspace Data to a File Path
To redirect SharePoint Portal Workspace data to a file path: 1. Place the media containing the data you want to restore in the storage device.
2. On the navigation bar, click Restore. 3. Navigate to and select the SharePoint Portal Server data you want to restore. 4. On the Properties pane, under Destination, click SharePoint Redirection. 5. Check the box labeled Redirect SharePoint Portal document sets, and then select Redirect to path. 6. Enter the drive letter and path to which you want to direct the restore in the Restore to drive and Restore to path fields, or click the ellipsis (...) button to browse to the desired location. Note You can also enter a UNC path (\\servername\share) in the Restore to drive field.
Restore Job Properties - Sharepoint Redirection
7. Use the default logon account as indicated, or click Change to select a different one.
1220
Disaster Recovery of a SharePoint Portal Server
8. On the Properties pane, select other job properties that might be appropriate for your environment. 9. Start the restore job.
SharePoint Agent
10. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job you want to view. See also: Backing Up Folders and Documents from a SharePoint Portal Workspace on page 1213 Restoring a SharePoint Portal Workspace on page 1216

Because SharePoint Portal Server uses Windows 2000 security for authentication, disaster recovery of a SharePoint Portal Server cannot be separated from the disaster recovery of Windows 2000. If you purchased the Intelligent Disaster Recovery (IDR) option, see VERITAS Backup Exec - Intelligent Disaster Recovery Option on page 855 for directions on using IDR to recover a Windows 2000 server. For specific notes on using IDR with SharePoint Portal Server, see SharePoint Portal Server Recovery Notes on page 909. You must recover the Windows 2000 server first. For more information, see Manual Disaster Recovery of Windows Computers on page 540. 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. Use the following procedures to complete the recovery of a SharePoint Portal Server and the associated SharePoint data. Always log on to the Windows 2000 server using the Administrator account (or an Administrator equivalent) during this procedure. You need:

A copy of Backup Exec for Windows Servers with the SharePoint Agent installed The latest backup of the SharePoint Portal Server you want to recover The SharePoint Portal Server CD Any SharePoint Portal Server service packs that were applied to the original installation
Caution You cannot completely recover a SharePoint Portal Server database using backups of individual workspaces. You must use a backup of the SharePoint Portal Server database to complete the disaster recovery.
Appendix M, VERITAS Backup Exec - Agent for Microsoft SharePoint Portal Server 1221
Uninstalling and Reinstalling the SharePoint Portal Server Software
To uninstall/reinstall the SharePoint Portal Server software: 1. Use Add/Remove Programs in the Windows Control Panel to uninstall the SharePoint Portal Server software. Restart the server when the uninstall operation completes. 2. Insert the SharePoint CD and install the SharePoint Portal Server software to the desired location using the appropriate options for your environment. When the New Workspace Wizard starts, click Cancel. 3. If applicable, install any SharePoint Portal Server service packs that were applied to the original installation.
Restoring SharePoint Portal Server Data
To restore SharePoint Portal Server data: 1. Place the media containing the data you want to restore in the storage device. 2. On the navigation bar, click Restore. 3. Navigate to and select the SharePoint data you want to restore. 4. On the Properties pane, set the appropriate options. 5. Start the restore job. 6. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job you want to view. After the restore completes, it is recommended that you perform a full backup of the restored SharePoint Portal Server database.
1222
VERITAS Backup Exec - Remote Agent for NetWare
N
NetWare Agent
The Backup Exec Remote Agent for NetWare allows network administrators for Windows servers to perform backup and restore operations on NetWare servers that are connected to their network. The Backup Exec Remote Agent for NetWare supports NetWare v4.2, NetWare v5.x, or NetWare 6.x. Because the Remote Agent for NetWare 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 for NetWare is a NetWare Loadable Module (NLM) called BEREMOTE.NLM, and is 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. The Remote Agent for NetWare consists of NLMs that execute Target Service Agents (TSAs) to provide backup support on the NetWare server. When the Remote Agent for NetWare is installed, the most current versions of the NLMs needed by Backup Exec to process NetWare-specific requests are copied to the NetWare server.
1223
Requirements for the Remote Agent for NetWare
Requirements for the Remote Agent for NetWare

The following are required to install the Remote Agent for NetWare:

The NetWare server on which the installation is being performed must have access to the media server. You must be a user with admin object rights to both the directory tree and the NetWare server. On the media server, you must run one of the following: Microsoft Client Services for NetWare Gateway Services for NetWare Novell Client for Windows NT/2000. This is required if the NetWare server is IP-only.
See also: Maximizing Remote Agent Performance on the NetWare Server on page 1224 Installing the Remote Agent for NetWare on page 1225
Maximizing Remote Agent Performance on the NetWare Server

When using Remote Agent on NetWare 5.x or later servers, TCP/IP provides the fastest backups. You also can increase backup speed by running modified backups, such as differential and incremental. During modified backups, file selection is performed locally by the Remote Agent instead of across the network, which is the method used by traditional network backup applications. Tip Your network hardware can have a major impact on performance. For example, an 8-bit Network Interface Card (NIC) in the server does not provide the performance of a 16- or 32-bit NIC. Bandwidth also plays a major role. For example, 100 Mbps Ethernet provides much better performance than 10 Mbps Ethernet when running concurrent remote backups.
Note When configuring 100 Mbps NICs, ensure that all of the components on the network are using the same duplex setting. Having your NIC cards at full duplex on a switch that is set to half duplex will severely impact performance.
1224
Installing the Remote Agent for NetWare

When you install the Remote Agent for NetWare on the NetWare server, the following occurs:
A directory called BKUPEXEC is created in the selected 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. Older versions of the NLMs are renamed with a .ORG extension. For example, if an older version of the TSA500.NLM file was found on the NetWare server, the installation program would rename it to TSA500.ORG and copy the newer TSA500.NLM from the installation CD.
NetWare Agent
If you already have the latest tested or most recent version of the NLMs installed on your server, they are not replaced.
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 Backup Exec must already be installed before you can install options to remote systems. The Remote Agent for NetWare is installed remotely from the Windows media server. If you have previously installed the Remote Agent for NetWare 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 for NetWare, see Installing Backup Exec Remote Agents and Options on Remote Servers on page 54. When Backup Exec is installed, both the TCP/IP and NetWare IPX/SPX protocols are selected for use by default. You can change the default settings through the Options-Set Application Defaults dialog box. For more information, see Default Settings for the Remote Agent for NetWare on page 1235. See also: Installing Backup Exec Remote Agents and Options on Remote Servers on page 54 Using NetWare 5.x and 6.x in a TCP/IP Only Environment on page 1226 Adding BESTART to the AUTOEXEC.NCF File on the NetWare Server on page 1226
Appendix N, VERITAS Backup Exec - Remote Agent for NetWare
1225
Using NetWare 5.x and 6.x in a TCP/IP Only Environment

If your network is not configured to allow the use of Service Location Protocol (SLP), or if you are using Microsoft Client Services for NetWare or Gateway Services for NetWare, you must ensure the server names and IP addresses are in your networks Domain Naming Services (DNS) database. If these names and IP addresses are not in DNS, then you must manually add the names and IP addresses to the media servers HOSTS file, which usually is found in the Drivers\ETC subdirectory under your SYSTEM32 directory. In addition, you must manually add the server names to Backup Execs server list through the Options - Set Application Defaults dialog box (see Default Settings for the Remote Agent for NetWare on page 1235).
Adding BESTART to the AUTOEXEC.NCF File on the NetWare Server

After installing the Remote Agent for NetWare on the NetWare server, you should load the latest Novell patches. You can also add the BESTART command, which loads the Remote Agent for NetWare 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 for NetWare is automatically started each time the NetWare server is booted. 2. After saving the AUTOEXEC.NCF file, reboot the NetWare server in order for the changes to take effect.
1226
Unloading the Remote Agent for NetWare

If you added BESTART as the last line in the AUTOEXEC.NCF file on the NetWare server, the Remote Agent for NetWare 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:
At the NetWare servers console prompt:, type: unload beremote <Enter>
NetWare Agent
or bestop <Enter> (which unloads all NLMs associated with the Agent) You can still use the Remote Agent for NetWare to back up the NetWare server when the Remote Agent is unloaded, but the speed of the backup will be significantly less.
1227
About Backing Up NetWare Servers

The first time you access the NetWare servers for backup, you may be prompted for a username and password. The usernames and passwords you enter to gain initial access to remote servers and workstations are kept in a password database. This database prevents you from having to type usernames and passwords each time you need to access remote devices and also allows Backup Exec to log on to servers and attach to agent workstations for unattended jobs. To back up the NetWare File System, you must have an account on the NetWare server with the following rights:
Necessary rights for NFS backup To do this: 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
1228
To back up, and restore when necessary, the NDS Tree, you must have a user account on the NetWare server that has the following rights to the [Root] object of the NDS Tree:
Necessary rights for NDS backup To do this: Backup/ Restore You need these rights: Object rights Supervisor Browse Create Delete Rename Inheritable Property rights, All properties Supervisor Compare Read Write Add Self Inheritable
NetWare Agent
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.
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. 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.
1229
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.
1230
Backing Up NetWare Servers
To back up a NetWare server: 1. On the navigation bar, click Backup.

Backup Selections
NetWare Agent
2. Doubleclick the NetWare computer icon for the NetWare server you want to back up. NetWare servers should be selected from the Novell Storage Management Services node. If they are not selected from this node, NDS objects and file attributes will not be backed up. 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. 3. Click the checkbox preceding the volume icon to select the directories that you want to back up, or double-click the volume to select directories.
1231
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 (TRINITY) that has both the file system and the NetWare Directory Services selected for backup:
Backup Selections for NetWare server
4. If you want to change the Backup default, on the Properties pane, under Settings, click NetWare SMS. 5. Select or clear the Backup 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. 6. Continue creating the job by following the procedures in Creating a Manual Backup Job by Configuring Job Properties on page 236.
1232
About Restoring NetWare Servers
About Restoring NetWare Servers

Before restoring your NetWare server, you may want to read about restore operations in general in Restoring Data on page 395. 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.
NetWare Agent
Restoring NetWare Servers
To restore files to a NetWare server: 1. On the navigation bar, click Restore. 2. Select the data you want to restore. For details on how to select data, see Selecting Data to Restore on page 428. 3. If you want to change the Restore option default, on the Properties pane, under Settings, click NetWare SMS. 4. Select or clear the Restore volume restriction option. If you select this option, Backup Exec restores NetWare volume restrictions. Restoring volume restrictions is not recommended unless you are performing disaster recovery. 5. (Optional) If you want to redirect the restore to another server, under Destination, click File Redirection and complete the options as described in Files destination options on page 437.
1233
About Restoring NetWare Servers Restore Redirection Job Properties
If you are redirecting a restore operation, please 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 NT volume; again, NDS objects cannot be redirected.
6. Complete the restore job by following the procedures described in Creating a Manual Restore Job by Configuring Job Properties on page 404.
1234
Default Settings for the Remote Agent for NetWare

By default, Backup Exec enables agents using either the TCP/IP or IPX/SPX protocols. You can change the default protocols and ensure that the correct protocol is enabled on the Options - Set Application Defaults dialog box. Also through this dialog box, you can set network defaults for all backup and restore operations performed on the NetWare servers by Backup Exec. You can override these defaults each time you create a backup or restore job.
To enable the protocol on the media server:
NetWare Agent
1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Network.
Network default options
Note If using TCP/IP with a NetWare 5.x server, ensure that Enable agents using TCP/IP protocol is selected. Otherwise, select Enable agents using NetWare IPX/SPX protocol. For more information about setting default network options, see Specifying the Default Backup Network on page 325.
1235
3. Select the protocols you want to use, then click OK. 4.
Restart Backup Exec.
To change backup and restore defaults for the NetWare server: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click NetWare SMS.
NetWare SMS default options
1236

NetWare SMS options Item General 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 advertise using the Server Advertising Protocol (if IPX/SPX is being used) and the Service Location Protocol (if TCP/IP is being used) can be seen. Backup Exec displays these servers in this field. You can manually add or delete servers to or from this list. As soon as a server is added, all of the servers that were displayed from the wildcard default are deleted. Only the servers that are added display in the network resources. If you are using an IP-only environment and your network is not configured to allow the use of Service Location Protocol, you must manually add the servers names. For more information, see Using NetWare 5.x and 6.x in a TCP/IP Only Environment on page 1226. For these changes to take effect, you must restart the Backup Exec administration console. Backup Back up compressed files in decompressed form Click this to decompress, or expand, compressed files as they are backed up. If you select this option, the server may run out of memory or disk space. Also, the backup job will take longer due to the extra time involved in file decompression. In most cases, this option should not be selected. Restore Restore volume restrictions Click this to restore NetWare volume restrictions. Restoring volume restrictions is not recommended unless you are performing a disaster recovery job. Description
NetWare Agent
1237
Saving Configuration Information for the NetWare Server
4. To manually add a server to the server list: a. Click Add. b. Type the name of the server you want to add, and then click OK. 5. To delete a server from the server list: a. Select the server you want to delete. b. Click Delete. 6. After all servers have been added or deleted, and the NetWare SMS default options have been selected, click OK.
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. Note You can use the following options when loading BEDIAG.NLM: (for example, load bediag /c) /c - outputs the file to the screen /s - gathers information for SCSI devices only /n - exclude information for SCSI devices 2. View the BEDIAG.FAX file with a text editor or word processor. The information in this file includes: The contents of your CONFIG.SYS and AUTOEXEC.BAT files. Contents of the STARTUP.NCF file. The amount of memory available.
1238
Disaster Recovery of NetWare Servers
The contents of your AUTOEXEC.NCF file. A listing of the NLMs that are currently loaded on your server, including the version numbers and the date stamp. Configuration settings for your server, including volumes and individual namespace support.
3. On the print-out of the BEDIAG.FAX, write the Supervisor user and password. Note Keep this print-out locked in a safe place.
NetWare Agent

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

Reinstall NetWare. Reinstall the Backup Exec Remote Agent for NetWare. 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. For more information, see Getting Started with IDR on page 859
Tip
1239
1240
VERITAS Backup Exec - Tivoli Storage Manager Option
The Backup Exec for Windows Servers Tivoli Storage Manager (TSM) Option is installed as a separate, add-on component of Backup Exec for Windows Servers. Using the TSM Option, you can combine the speed and localized control of Backup Exec with the TSM policy-based system of centralized storage management. The TSM Option enables the TSM servers storage resources to appear as a tape robotic library in a list of target devices on the Backup Exec server. Backup Exec administrators can then direct the output of any Backup Exec job to the TSM server by selecting the name of the TSM robotic library as the destination when submitting the job. See also: Requirements for the TSM Option on page 1241 Backup Exec as a TSM Client on page 1242 TSM Backup Exec Components on page 1243
Tivoli Option
Requirements for the TSM Option

Familiarity with TSM terminology and operation, and the operating system on which the server resides. TSM versions 3.7 though 5.1 Backup Exec for Windows Servers 9.x or later installed on the media server. TCP/IP installed on the media server.
Note The Backup Exec TSM Option does not support the following communication protocols: SPX, NetBEUI, NetBIOS or any mainframe protocols such as SNA The Tivoli Storage Manager Administrators Guide and Administrators Reference Guide may also be helpful.
1241
Backup Exec as a TSM Client

Backup Execs TSM Option enables computers running Backup Exec for Windows Servers to become clients of a Tivoli Storage Manager server. As a TSM client, Backup Exec can use the TSM server as storage volumes for its backup jobs. To become a TSM client, each computer runs Backup Exec for Windows Servers, along with the appropriate TSM option. Note The TSM server must be prepared using the BEX.MAC macro before becoming a TSM client.
TSM Example
- AIX, AS/400, HP-UX, MVS, OS/390, z/OS, Sun Solaris, VM, and Windows - Tivoli Storage Manager Tivoli Storage Manager
Corporate Network
TSM client
TSM client
Windows NT 4 (SP 6a, Windows 2000, Windows XP, Windows.NET Exchange Server (optional) SQL Server (optional) Backup Exec for Windows Server v9.x or later Backup Exec for Tivoli Storage Manager option
After establishing communication with the TSM Server, Backup Exec recognizes the TSM server as a virtual single tape drive robotic library and stores the contents of its backup jobs on it. Because the TSM option is implemented within Backup Exec as an add-on logical device driver, all standard robotic library features are available except LABM. You can also configure a variable number of logical media slots within the virtual tape robotic library.
1242
Backup Exec Architecture and the TSM Server

Device Driver Backup Exec Scheduler and Job Engine Backup Exec Device Handling Layer Device Driver Device Driver Device Driver Tape Device
Tape Device
Tape Loader
Virtual Tape Loader
TCP/IP Protocol
Tivoli Option
TSM Server
See also: TSM Backup Exec Components on page 1243 Requirements for the TSM Option on page 1241
TSM Backup Exec Components

To prepare the TSM server to receive and store Backup Exec jobs, a new policy domain and policy set are created for Backup Exec on the TSM server. A separate policy domain for Backup Exec is used to distinguish Backup Exec administration console data from other policy domains used by client data. Then, a storage pool and two management classes are created in the new policy domain to help manage the data sent by Backup Exec. Data sent to the TSM server by Backup Exec is contained in two data streams:
The position information (PI) data stream is bound to the new management class named MC_PI. The PI data stream is directed to the newly-created, disk-based storage pool, named backupexec_pi.
Appendix O, VERITAS Backup Exec - Tivoli Storage Manager Option
1243
Backup Exec uses the backupexec_pi storage pool to retain position information about each backup set that it sends to the TSM servers BACKUPPOOL storage pool. Migration is turned off, and should remain off, for the backupexec_pi storage pool so that the position information for each stored file is not migrated off the disk to tape, but is always immediately available to Backup Exec. If the position information data were migrated to tape, performance in Backup Exec would be severely impaired. The virtual tape (VT) data stream is bound to the new management class MC_VT. The VT data stream contains the actual client backup data packaged as objects. This backup data can be stored on disk or migrated to tape, disk, or RCD and is managed automatically by the TSM database.
Note The VT data stream must first be written to a disk-based storage pool, then optionally migrated to tape. Configurations in which the VT data stream is sent directly to tape are not supported. Finally, a node named Backupexec is registered on the TSM server. All of the Backup Exec media servers can share this node, with backup sessions from the servers differentiated on the TSM server by the media servers file space name. VERITAS includes a TSM server preparation macro named BEX.MAC that automatically performs all steps necessary to prepare the TSM server. Regardless of your experience with TSM, it is extremely important that you use the instructions under Preparing the TSM Server and Running the BEX Macro to properly configure the TSM server. From the Backup Exec interface, you can direct output from Backup Exec jobs to the TSM server by selecting the name of the TSM robotic library as the destination. See also: Preparing the TSM Server on page 1245 BEX.MAC Macro Command Details on page 1253
1244
Preparing the TSM Server

This section explains the details necessary for preparing your TSM Server to accept the Backup Exec server as a TSM client. These details include:

Allocating storage space using the Volume Formatting Wizard. Creating a storage volume for the backupexec_pi storage pool. Running the BEX.MAC preparation macro.
Note Regardless of your experience with TSM, it is extremely important to install this TSM option using both the following instructions and the included macro, BEX.MAC. The TSM command conventions used within the BEX.MAC macro file may need to be adjusted to reflect the operating system conventions your TSM server is using. See also: Allocating Storage Space on page 1245 Creating The bexpi.dsm Storage Volume on page 1246 Running the BEX.MAC Macro on page 1248
Tivoli Option
Allocating Storage Space

The high-level macro named BEX.MAC contains commands that automate the process of preparing the TSM server. Note You must install the Backup Exec for Windows Servers TSM Option to obtain a copy of the BEX.MAC macro. During the install, the BEX.MAC macro is placed in the same directory where Backup Exec was installed. However, for the BEX.MAC macro to run correctly, you must first use the TSM DSMFMT utility to allocate space for the storage pool, backupexec_pi, used by the position information (PI) data stream. The TSM DSMFMT utility is delivered as part of the TSM server, and is used to pre-allocate the space needed when disk-based storage pools are created. For information on the DSMFMT utility parameters, see your TSM Administrators Reference Guide. See also: BEX.MAC Macro Command Details on page 1253
1245
Creating The bexpi.dsm Storage Volume
To format a file as a storage volume for the backupexec_pi storage pool using the Volume Formatting Wizard: 1. Using the Volume Formatting Wizard, in the Storage Management interface, create a 30MB database file named bexpi.dsm, which will act as the storage volume name for the storage pool backupexec_pi. For example, if you are using TSM on the Windows NT, Windows 2000 or Windows.NET platforms, and you want to format a 30MB file to be located in the root directory, select this location when using the wizard. Other paths can be used, but the other paths must be reflected in the BEX.MAC. 2. After formatting the bexpi.dsm file, edit the BEX.MAC macro to associate the backupexec_pi storage pool with the bexpi.dsm file. The macro also executes commands that complete the preparation of the TSM server. Note For the BEX.MAC macro to run correctly, the BACKUPPOOL storage pool must exist on the TSM server.
To manually format a file as a storage volume for the backupexec_pi storage pool: 1. From the command prompt on the TSM server, format a 30-MB file named bexpi.dsm as the storage volume for the storage pool backupexec_pi, by typing: [drive:][path]dsmfmt [drive:][path]bexpi.dsm 30 Note For TSM version 4.x, you must access the server command window under the Reports option.
TSM command variables Item Description The drive and directory location of the DSMFMT utility. The location of the DSMFMT utility may vary according to the operating system your TSM server is using.
[drive:][path]
dsmfmt
1246
Preparing the TSM Server TSM command variables (continued) Item Description The drive and directory location where you want to create the bexpi.dsm file. The DSMFMT utility specifies the bexpi.dsm file as a storage volume for the storage pool backupexec_pi. Important: The BEX.MAC macro looks for the bexpi.dsm file in the root or top-level directory, then associates it with the backupexec_pi storage pool. If you locate the bexpi.dsm file in a directory other than the root or top-level, you must edit the BEX.MAC macro and change the location of the bexpi.dsm file so it can be associated with the backupexec_pi storage pool. 30 Specifies that the size of the bexpi.dsm file is 30MB. (When using the Volume Formatting Wizard, this value is expressed in megabytes by default.) If you require the file to be a size other than 30MB, use the following formula to find the maximum filespace needed: (number of slots +1) x 64K = maximum space required per robotic library. Add the maximum space required for each robotic library to find the total space required by the bexpi.dsm file.
[drive:][path]
bexpi.dsm
Tivoli Option
For example, if you are using TSM on the Windows NT, Windows 2000, Windows XP, or Windows.NET platforms and you want to format a 30MB file to be located in the root directory, type: dsmfmt <path>bexpi.dsm 30 where <path> is the directory to create the file in. 2. After formatting the bexpi.dsm file, run the BEX.MAC macro to associate the backupexec_pi storage pool with the bexpi.dsm file. The macro also executes commands that complete the preparation of the TSM server. Note For the BEX.MAC macro to run correctly, the BACKUPPOOL storage pool must exist on the TSM server. See also: BEX.MAC Macro Command Details on page 1253
1247
Running the BEX.MAC Macro

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

To install and configure the TSM Option on a Windows computer, see Installing Backup Exec Options on a Local Server on page 49. Note During the installation, you will need to know both the TSM servers IP and port address settings. See also: Changing the Defaults for Backup Exec for Windows Servers on page 1249 Preparing the TSM Server on page 1245
Changing the Defaults for Backup Exec for Windows Servers

When the Backup Exec media server sends backup data to the TSM server, the management class names, node names and passwords used on the two servers must match. If the values on the TSM server do not match the values in the Backup Exec registry key, the TSM Option will not work. When the TSM Option is installed, the BEX.MAC macro contains the same default names that are in the Backup Exec server registry key: HKEY_LOCAL_MACHINE/SOFTWARE/VERITAS/BACKUP EXEC/ADSM If you change default names in the BEX.MAC macro, you must make the same changes on the Backup Exec server by editing fields in the registry key. If you do not use the BEX.MAC macro to prepare the TSM server, or if you register a node manually, either use the same values that are in the registry key, or change the registry key values to match whatever values you enter on the TSM server. After you make changes in the registry key, stop and restart the Backup Exec services. The following screen shows the registry key. The values appear in hexadecimal format.
Tivoli Option
1249
Changing the Defaults for Backup Exec for Windows Servers Registry Key Values For The TSM Option
Following is a description of the values in the registry key that can be changed. The values are given as decimal values:
Registry Key Values Item CommTimeout: Description This value must match the Communications Timeout entry in the DSMSERV.OPT file on the TSM server. Minimum: 1 second Maximum: 65535 seconds, Default: 60 seconds If the If closed with X seconds setting is selected in Backup Exec, (under Advanced node in the Backup Job Properties pane) its value should not exceed the Communications Timeout setting on the IBM TSM server. If the time-out value does exceed the TSM CommTimeout value, backups may fail with an I/O device error indicated for the TSM drive. The TSM CommTimeout value must be coordinated with the CommTimeout value on the TSM server, as described in the TSM installation documentation.
1250
Changing the Defaults for Backup Exec for Windows Servers Registry Key Values (continued) Item Enabled: Description Enables or disables TSM support. When this field is set to 0, TSM is disabled. Default: 1 (on) Changes the file space name of a media server for which you want to view or restore data. By default, the machine name is used as the file space name. Multiple Backup Exec servers can send backup data to the TSM server. If the media servers are sharing a node, which is the default, the TSM server uses the servers file space name to distinguish backup sessions. To be able to view or access backup data, you must use the same file space name that was used when the data was sent to the TSM server. For example, if you backed up data to the TSM server using the media server with the file space name of ACCT, but you are now on a media server with the file space name of PUBS, you can view or restore the backup data from ACCT by changing the file space name on PUBS to ACCT and cataloging the tapes/slots you want to view. Maximum length: 1023 characters Default: MachineName LoaderSlots: Sets the number of slots you can define in any given magazine Minimum: 1 slot, Maximum: 255 slots Default: 10 slots Sets the name of the node used to communicate with the TSM server. This name must match the node name registered for Backup Exec on the TSM server. Maximum length: 63 characters, Default: BackupExec
FileSpaceName:
Tivoli Option
NodeName:
1251
Changing the Defaults for Backup Exec for Windows Servers Registry Key Values (continued) Item ObjectMegSize: Description When Backup Exec sends data to the TSM server, it sends the data in blocks. For example, 50MB of data is sent to the TSM server in five 10MB blocks. This key is used to change the default block size. You may want to change the block size from the 10MB default according to your system performance. A recommendation is to set the object size to 1/100 of the available space in the BACKUPPOOL storage pool, if more than 100 MB are available in that pool. An indication that the object size is too large, or that the TSM server is running out of storage space, is if the following errors appear in the Event Log: 7106: Storage device TSM Storage reports an error on a request to write a file mark to media. The error reported is Hardware failure. 14000: An error occurs while processing an TSM command, ANS4311E (RC11) Server out of data storage space, and ANSO2661 (RC2302) The dsmEndTxn vote is ABORT. Check the reason field. Minimum: 0MB, Maximum: 3096MB, Default: 10MB PI_MgmtClass: Sets the name of the position information management class. This name must match the PI management class name on the TSM server. Maximum length: 29 characters, Default: MC_PI. Platform: Used to further identify a session on the TSM Client Console Monitor. Maximum length: 15 characters, Default: MachineName_01 VT_MgmtClass: Sets the name of the virtual tape management class. This name must match the VT management class name on the TSM server. Maximum length: 29 characters, Default: MC_VT.
See also: Changing Passwords on page 1253
1252
BEX.MAC Macro Command Details
Changing Passwords
To change the password for TSM on a Backup Exec server, run ADSMCFG.EXE, found in the Backup Exec program directory. For example: C:\PROGRAM FILES\VERITAS\BACKUP EXEC\NT. You are prompted to enter a new password, and then to re-enter it to confirm it. You must make the same password change on the TSM server or you will receive an authentication failure error when the next Backup Exec session starts. On a shared node, if the password is changed for one Backup Exec server, it must be changed for all servers sharing that node. The TSM server automatically expires node passwords after a specified amount of time. When the password expires, Backup Exec instructs the TSM server to reuse the previous password.

The high-level macro BEX.MAC automates the process of preparing the TSM server to run with Backup Exec. By using the BEX.MAC macro, you can save time and prevent errors. In brief, the macro:

Tivoli Option
Associates the storage pool backupexec_pi with the storage volume file bexpi.dsm. Creates a new policy domain named VERITAS. Creates a new policy set in the VERITAS domain named bex_backup. Creates a management class named MC_PI. Creates a management class named MC_VT, and modifies it to be the default management class for the policy set bex_backup. Creates a backup copy group (inside the MC_PI management class) with a destination pointing to the backupexec_pi storage pool. Creates a backup copy group (inside the MC_VT management class) with a destination pointing to the TSM servers BACKUPPOOL storage pool. Activates all the changes and additions. Registers a node on the TSM server named backupexec with a password of bex.
Note If you change any of the default names used in the BEX.MAC macro, you must make the same changes on the Backup Exec server.
1253
The following table describes the BEX.MAC macro commands:

BEX.MAC macro commands Item define stgpool backupexec_pi disk Description Creates a storage pool named backupexec_pi using the disk device class without migration capabilities. Backup Exec uses the backupexec_pi storage pool to store information about each file that it backs up and stores in the TSM servers BACKUPPOOL storage pool. Migration is turned off for the backupexec_pi storage pool so that the information in backupexec_pi will always be immediately available to Backup Exec. If the position information data in backupexec_pi were migrated to tape, performance in Backup Exec would be adversely affected. define volume backupexec_pi c:\bexpi.dsm access = READWrite define domain VERITAS define policyset VERITAS bex_backup define mgmtclass VERITAS bex_backup MC_PI SPACEMGTECHnique = NONE define mgmtclass VERITAS bex_backup MC_VT SPACEMGTECHnique = NONE Associates the file c:\bexpi.dsm with the storage pool named backupexec_pi.
Creates a policy domain named VERITAS. Creates a policy set in the domain VERITAS named bex_backup.
Creates a management class named MC_PI for the policy set bex_backup in the domain VERITAS with space management disabled. The MC_PI management class acts like a map for all the backup data files that are stored on the TSM server. It is written to and read from by Backup Exec during almost every operation. Creates a management class called MC_VT for the policy set bex_backup in the domain VERITAS. This class is where the bulk of the data being backed up resides. Backup Exec stores its data on the TSM server in chunks called objects. By default, the object size is 10MB, but the size can be changed. For details on how to change the object size, and when it might be necessary, see Changing the Defaults for Backup Exec for Windows Servers on page 1249. Modifies the management class MC_VT to be the default management class.
assign defmgmtclass VERITAS bex_backup MC_VT
1254
BEX.MAC Macro Command Details BEX.MAC macro commands (continued) Item define copygroup VERITAS bex_backup mc_pi DESTination = backupexec_pi VERExists = 1 VERDeleted = 0 RETExtra = 0 RETOnly = NOLimit define copygroup VERITAS bex_backup mc_vt DESTination = BACKUPPOOL VERExists = 1 VERDeleted = 0 RETExtra = 0 RETOnly = NOLimit Description Creates a backup copy group with a destination pointing to the backupexec_pi storage pool. The number of backup versions to keep is set to one because Backup Exec only recognizes one copy of backup data. Because Backup Exec does not use the Length of Time To Retain Only Backup Version feature, it is set to No Limit. Creates a backup copy group for the VT data stream with a destination pointing to the TSM servers BACKUPPOOL storage pool. Note The VT data stream must first be written to a disk-based storage pool, then optionally migrated to tape. Configurations in which the VT data stream is sent directly to tape are not supported.
Tivoli Option
activate policyset VERITAS Activates all the previously listed additions/modifications. bex_backup REGister Node backupexec bex DOMain = VERITAS BACKDELETE = YES Registers a node on the TSM server called backupexec with a password of bex, using the policy domain called VERITAS, and allowing the deletion of file spaces. If you are using individual nodes for each Backup Exec server, you can use this node registration for one server. You must manually register all other servers using a unique node name and password, and using the policy domain VERITAS. You must also change the default names on the Backup Exec server to match the new node registration. See Changing the Defaults for Backup Exec for Windows Servers on page 1249.
1255
Troubleshooting
Troubleshooting
If the TSM server and the Backup Exec server cannot communicate after the TSM Option has been installed, check the following:

Are all the necessary API and OPT files copied to the correct locations? Does the DSM.OPT file have the correct TCP/IP address and port number entered? Can you ping the TSM servers TCP/IP address? If you cannot ping the server, the support will not work.
See also: TSM Problem Resolutions for Backup Exec for Windows Servers on page 1257
Viewing TSM-related Errors

To view TSM-related errors in Backup Exec for Windows Servers, look in the application log in the Windows event viewer. The DSIERROR.LOG file is located in the directory from which Backup Exec runs. If the IBM client is loaded, you can also view error codes listed in a file named DSMRC.H, located in the TSM API client directory, \ADSM32\API\INCLUDE. The TSM API code also creates an error log file called DSIERROR.LOG. This file can also contain information useful for isolating any TSM-related problems when using Backup Exec. See also: TSM Problem Resolutions for Backup Exec for Windows Servers on page 1257
1256
TSM Problem Resolutions for Backup Exec for Windows Servers

Item: TSM Tape and Robotic Library Devices do not appear in the Devices view. 1. Verify the Registry entries for TSM Tape and Robotic Library Devices: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\ADAMM\Scsi\Scsi Port xx\Scsi Bus x\Target Id x\... Logical Unit Id 0 DeviceName: REG_SZ: MediumChanger40 Identifier: REG_SZ: ADSM Changer Device Type: REG_SZ: MediumChangerPeripheral Logical Unit Id 1 DeviceName: REG_SZ: Tape41 Identifier: REG_SZ: ADSM Tape Device Type: REG_SZ: TapePeripheral
Tivoli Option
2. Verify that TSM is enabled in the Registry: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\ADSM Enabled: REG_DWORD: 0x1 You may need to restart the Backup Exec services for the changes to take effect. 3. To restart the services, go to Control Panel - Settings. Select the Backup Exec services, and then click Stop. 4. Click Start.
Item: Hardware Error Detected message box says, No storage device has been detected. The Windows Event Viewer will contain an entry under Application Log.
1257
Possible error messages and corrective actions for this problem are listed in the following table:
TSM Troubleshooting Guide Error Message An error occurred while attempting to load the IBM ADSM32.DLL. The files ADSM32.DLL, BLKHOOK.DLL, DSCAMENG.TXT and DSM.OPT must reside in the same directory as Backup Exec. An error occurred while processing a TSM command. (610) Corrective Action Verify that these files are present.
The file DSCAMENG.TXT is missing. The file DSM.OPT is missing. Verify that TCP/IP is installed properly. Ensure the DSM.OPT entry for TCPServeraddress points to a valid TSM server.
An error occurred while processing a TSM command. Options file not found. An error occurred while processing a TSM command. Session rejected: TCP/IP connection failure.
An error occurred while processing a TSM command. Session rejected: Unknown or incorrect ID entered.
Ensure that the Backup Exec node exists on the TSM server.
Item: If the object size is set too large, or the TSM server is running out of storage space, the following errors appear in the Event Log:

7106: Storage device TSM Storage reports an error on a request to write a file mark to media. The error reported is Hardware failure. 14000: An error occurs while processing a TSM command, ANS4311E (RC11) Server out of data storage space, and ANSO2661 (RC2302) The dsmEndTxn vote is ABORT. Check the reason field.
1258
Glossary
ADAMM Advanced Device and Media Management, Backup Execs database that automates the tracking of media and storage devices and ensuring 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 system.
Glossary
Agent A component that allows workstations or other servers, for example your SQL server, to interact with the Backup Exec server. Alert An event that usually requires some form of user interaction or acknowledgment. Alert Category One of 35 classes or groups used by Backup Exec in which an alert fits. Examples of alert categories include job success, install warning, and database maintenance failure. Alert Source One of four areas that can generate an alert. Alert sources include job, media, device, and system. Alert Type Determined by the severity of the alert, an alert type has a corresponding colored icon. Backup Exec recognizes four types of alerts: Error, Warnings, Information, and Attention Required. Allocated Media Media that belongs to a user media set.
1259
Append Period The length of time that data may be added to the media. The append period starts when the first backup job is written to this media. Archive - Delete files after successful copy backup One of the available backup methods. Backs up 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. Archive Bit A file attribute that is set whenever a file is modified. For full and incremental backups that use archive bits, this bit is turned off after the backup completes, indicating to the system that the file has been backed up. If the file is changed again before the next incremental or full backup, the bit will be turned on and Backup Exec will back up the file. Backup A process where files on a server or workstation drive are copied and stored on a reliable form of media. Backup Exec Service Account A user account configured for Backup Execs system services that contains a user name and password and provides the rights to log on as a service and act as a Backup Exec administrator. Backup Folder A virtual device that Backup Exec treats as any real tape device. Backup folders can be part of drive pools, but not cascaded drive pools, and are created using Backup Execs backup-to-disk feature. Backup Job Template Attributes that define how and when Backup Exec processes a backup job. Templates specify the device, settings, and schedule options to use, but do not include the resource selections to be used for the backup job. Backup Method When you run a backup, you can specify how you want Backup Exec to use and set the files backup status. This is necessary when you incorporate a backup strategy. Backup Exec uses the following backup methods: FULL - Back Up Files - Reset Archive Bit. Backs up all selected data on a volume and resets the archive bit to indicate that the files have been backed up.
1260
COPY - Back Up Files. Includes all selected data, and does not affect any media rotation scheme because the archive bit is not reset. DIFFERENTIAL - Changed Files. Includes all files that have been changed (based on archive bit) since the last full or incremental backup, and does not affect any media rotation scheme because the archive bit is not reset. INCREMENTAL - Changed Files - 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. FULL - Back Up Files - Allow incrementals and differentials using modified time. Includes all of the selected data on a volume and allows the use of incrementals and differentials using the modified date and time stamp. DIFFERENTIAL - Using modified time. Includes all files since last full backup using the files last modified date and time stamp. INCREMENTAL - 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. DAILY - Files that Changed Today. Backs up files that were created or modified today. WORKING SET - All files last accessed in (x) days. Includes all files that were created or modified since the last full or incremental backup. If you select this backup method, you can then indicate that you want to include data that has been accessed in a specific number of days. ARCHIVE - Deletes files after successful copy backup. Backs up all selected files, 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 Set When a backup job is run, the data selected from a single resource, such as a Microsoft Exchange dataset, for the backup is placed together on media in a backup set. Files selected from multiple resources create multiple backup sets. Backup Strategy The procedures you implement for backing up your network. A good backup strategy allows minimal time to get a system up and running in the event of a disaster.
Glossary
Glossary
1261
Cascaded Drive Pool The grouping of drives of the same drive type so 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 defined in the group. Catalog A database for keeping track of the contents of media created during a backup or archive operation. You can only restore information from fully cataloged media. Cluster When two or four servers (called nodes) are linked in a network, and run cluster software that allows each node access to the shared disks. Copy Backup One of the available backup methods. Includes all selected data, and does not affect any media rotation scheme because the archive bit is not reset. Daily Backup One of the available backup methods. Backs up files that were created or modified today. Database Server In a shared storage environment, the server in which the shared Advanced Device and Media Management (ADAMM) database and the shared catalog resides. Differential - Changed Files Backup One of the available backup methods. Includes all files that have been changed (based on archive bit) since the last full or incremental backup, and does not affect any media rotation scheme because the archive bit is not reset. Differential - Using Modified Time Backup One of the available backup methods. Includes all files since the last full backup using the files last modified date and time stamp. Drive Pool A grouping of drives for Backup Exec operations. In a non-cascaded drive pool, jobs assigned to the drive pool are run on the first available drive. Event Action that occurs during a Backup Exec operation. For example, the canceling of a job.
1262
Failover When a node in a cluster becomes unavailable and cluster resources migrate to an available node. Fibre Channel A high speed storage network that can operate over copper wire or optical fiber and may support simultaneous transfer of many different data protocols, including SCSI, IPI, HiPPI, IP, and ATM. Fibre Channel Arbitrated Loop (FC-AL) A fibre channel configuration in which the devices are connected in a loop using a fibre channel hub. The bandwidth of the fibre channel is shared between the devices. Fibre Channel Hub A networking device used to connect the components of a Fibre Channel Arbitrated Loop (FC-AL). Fibre Channel Switch A networking device used to connect the components of a Fibre Channel Switched Fabric (FC-SW). Fibre Channel Switched Fabric (FC-SW) A fibre channel configuration in which the devices are connected in a network using a fibre channel switch. The full bandwidth of the fibre channel is available to all the devices. Fibre Channel Tape Controller Compaqs Fibre to SCSI Bridge. Fibre to SCSI Bridge A device that connects a Fibre Channel and a SCSI bus. Full - Back Up Files - Allows incrementals and differentials using modified time Backup One of the available backup methods. Includes all of the selected data on a volume and allows the use of incrementals and differentials using the modified date and time stamp. Full - Back Up Files - Reset Archive Bit Backup One of the available backup methods. Backs up all selected data on a volume and resets the archive bit to indicate that the files have been backed up.
Glossary
Glossary
1263
Hub A connecting device in a network that joins communication lines together. Imported Media Media created by a product other than this installation of Backup Exec. Incremental - Changed Files - Reset Archive Bit Backup 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 Incremental - Using modified time Backup Includes 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 Audit Log A running history of all user actions performed on jobs in the Backup Exec system. An entry into the log is created each time a job is modified by the user. Job History A report of what happened during the processing of the job (statistics, errors, and so on). Job Log Created when a job runs, the job log contains the results from the job. You can review the job log to review job errors and details. Local Device A disk or tape drive connected to a server and only available to the server to which it is attached.
1264
Media ID A unique internal label assigned by Backup Exec to individual media and used to keep statistics on each media. The media ID, unlike the media label, cannot be erased or changed. Media Label Used to identify media, the label can be assigned automatically by Backup Exec 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 consist of a pre-assigned bar code label. Media Location Location of your media. In Backup Exec, there are three categories available for tracking media: Online location. The online location lists media that reside in a storage device, robotic library slot, or backup-to-disk folder. It is defined by Backup Exec, so you cannot delete or rename it. In addition, you cannot add media to it. Offline location. The offline location displays all media that are onsite but are not in drives 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. User-defined media vault. A logical representation of the actual physical location of media. Media Overwrite Protection Level Set system-wide through the Media Overwrite dialog box, this option allows you to protect all, some, or no media from being automatically overwritten. Media Rotation A strategy that determines when media can be reused, or rotated back into use, by Backup Exec. Media Server The Windows server where Backup Exec was installed and the Backup Exec services are running. Media Set A group of media on which a backup job is targeted. The media set controls the overwrite protection period, the length of time that data is retained on a specific media before being overwritten, and the append period, the length of time that data can be appended to a media assigned to a media set.
Glossary
Glossary
1265
Media Vault A logical representation of the actual physical location of media. Node Servers operating in a cluster environment. A node can also be a selection in a tree view on the administration console (see Using the Administration Console on page 76). Overwrite Protection Period The length of time that data is retained on a specific media before being overwritten (unless the media is erased, formatted, moved to scratch media, or if the Media Overwrite Protection Level is set to None). The overwrite protection period is measured from the last time data was appended to the media. Partition A grouping of slots in a robotic library for use in Backup Exec operations. 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) run on remote computers. Remote Agent A Backup Exec system service that runs on Windows or NetWare remote servers and workstations and allows remote backup and restore of these systems and provides increased backup throughput. Resource Data files and databases, such as Windows shares and Microsoft SQL databases, that can be selected for backing up.
Resource Discovery A Backup Exec operation that allows detection of new backup resources within a Windows domain. Restore A process by which data that has been backed up to media is returned to disk.
1266
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 but backups will not run to it. Media must be retired before it can be deleted. If you want to use media that has been deleted, Backup Exec will recognize it as imported media. It must be cataloged before you can restore from it. Robotic Library A high-capacity data storage system for storing, retrieving, reading, and writing multiple magnetic tape cartridges. It contains storage racks for holding the cartridges and a robotic mechanism for moving the cartridge to the drive or drives. Scratch Media Media that do not belong to a media set and can be overwritten, including new or blank media, erased media, and media moved from another group to scratch media. SCSI Small Computer System Interface. A processor-independent standard for system level interfacing between a computer and peripheral devices such as printers, hard drives, and CD-ROMs. Selection List The data selected to be backed up or restored. Selection lists can be save and used for multiple jobs. Shared Device A disk or tape drive that can be accessed by multiple servers. Silent Mode Installation The process of installing Backup Exec from the command line using the setup.exe program on the Backup Exec installation CD. Static Volume A point in time view of a volume. System Media All media that has been introduced into the Backup Exec system, except those media that have been assigned to a media set.
Glossary
Glossary
1267
Wizard A series of instructional dialogs that guide you through the steps needed to accomplish a task, such as creating a backup job. Working Set Backup One of the available backup methods. Includes all files that were created or modified since the last full or incremental backup. If you select this backup method, you can then indicate that you want to include data that has been accessed in a specific number of days.
1268
Index
A active alerts defined 454 responding to 459 viewing 454 Active Alerts by Media Server Report 835 active alerts report 515 Active Directory, backing up in Exchange 2000 1072 active history report 515 active job viewing properties 370 active jobs canceling 373 removing hold 374 viewing 365 ADAMM, defined 1259 Admin Plus Pack advanced reporting capabilities 832 installing 827 overview 36, 827 scheduling report jobs 835 setting notification recipients for reports 835 administrating jobs using command line applet 614 administration console defined 1259 overview 76 role in backup process 39 Advanced Device and Media Management (ADAMM) database overview 911 device management overview 89 Devices view 90 media operations overview 218 Advanced File Selection options described 263 selecting files 262 Advanced Open File Option changing default settings 962 error messages 970 overview 36 requirements 958 uninstalling 961 using for all backup jobs 966 using for single backup job 964 wizard 962 Advanced options for backup 252 for duplicate job 303 for restore 412 Agent for Microsoft SharePoint Portal Server about backing up a SharePoint Server or Workspace 1213 about restoring a SharePoint Server or Workspace 1215 disaster recovery 1221 installing 1213 overview 1211 redirecting restore jobs 1217 system requirements 1212 agent, defined 1259 agent.cfg commands (UNIX Agent) 588 Agents, Backup Exec See also Exchange Server Agent, Lotus Domino Agent, NetWare Agent, Oracle Agent, R/3 for Oracle Server Agent, Remote Agent, SharePoint Agent, SQL Server Agent list of agents with descriptions 36 upgrading on remote computers 71 alert category, defined 1259
Index
1269
alert history defined 454 viewing 454 alert notification, printers 485, 487 alert source, defined 1259 alert switches for command line applet 619 alert type, defined 1259 alerts alert types 453 assigning recipients 491 clearing recipients 492 configuring 453 configuring default options 86 defined 453, 1259 filters 454 modifying alert category properties 492 notification methods 467 properties 457 responding to 453, 459 setting filter 456 using command line applet 619 viewing 454 viewing job log 460 views 454 alias backup, in backup job script file 608, 684, 711 all media, defined 190 allocated media defined 191, 1259 overwriting 195 append options for media 195 append period defined 185, 228, 1260 setting for media set 228 append to media option 244 Archive - delete files after successful copy, defined 1260 archive bit, defined 344, 1260 archive logging Lotus Domino 1186 recovery of Lotus Domino 1197 archiving freeing disk space 293 NTFS and VFAT file systems 294 using disk grooming 294 ARCserve media, restoring data from 426 ASR files, in IDR copy to diskette or CD 875
defined 855, 859 ASR See Automated System Recovery audit log logon accounts 356 report 517 AUTOEXEC.NCF file, NetWare Agent 1226 auto-inventory media after import job completes 181 Automated System Recovery 537 B backing up clusters database files 765 local disks 764 shared disks 764 Windows 2000 and Windows.NET 763 files and directories by following junction points 252 media server using one-button backup 292 R/3 database 1205 remote storage 253 BACKINT alerts 1200 implementation 1199 overview 1200 backup defined 1260 overview 233 Backup Exec installing command line installation 56 evaluation copy 553 installation requirements 46 overview 46 serialized copy, upgrading to 553 silent mode installation 56 uninstalling 66 upgrading 71 using Repair option 64 overview additional options 36 how it works 39 new features 33 system requirements 42 repairing 64
1270
running devices managed exclusively by 563 release devices 564 starting after installing Library Expansion Option 1146 upgrading options on remote computers 71 overview 71 Backup Exec Assistant, using 82 Backup Exec for Windows Servers Remote Agent hardware requirements 822 installing 823 serial numbers 822 stopping 824 Backup Exec for Windows Servers, described 31 Backup Exec Server in SAN 911 Backup Exec services account, defined 1260 Backup Exec Services Manager dialog box 65 commands 641 managing using command line applet 641 stopping and starting 65 Backup Exec Utility Database Tasks 809 aging the database 810 checking the database consistency 810 compacting the media server database 811 dumping a media server database 811 rebuilding a media server database indices 812 recovering a media server database 813 repairing a media server database 812 General Tasks adding new media servers 792 deleting a media server 794 deleting a media server group 795 deleting media servers from the All Media Servers subnode 794
running Backup Exec Diagnostics 796 viewing media server properties 797 Media Server Group Tasks 816 adding a media server 816 removing a media server 817 SAN SSO Tasks 804 configuring the SAN SSO 806 moving the primary SAN SSO Server 808 promotion to a primary SAN SSO Server 806 removing the primary SAN SSO Server 805 setting the primary SAN SSO Server 804 Services Tasks 798 changing service accounts 799 editing server configurations 801 starting services 799 stopping services 798 starting the Backup Exec Utility 788 Backup Exec Web Administrative Console accessing help 783 alerts 786 how it differs from Backup Exec for Windows Servers 782 installing 782 navigating 784 requirements 781 starting 782 tools 785 backup file defined 143 deleting 156 recreating a deleted file 157 renaming 155 viewing and changing properties 157 backup folder adding 144 changing the path 148 creating for removable media 147 creating more disk space 242 defined 143 deleting 149 designating location for 146 overview 143 pausing and resuming 151 recreating 150 1271
Index
Index
renaming 148 viewing properties 152 backup job Advanced options 252 alias backup in script file 608, 684, 711 choices for creating 233 copying to another server 831 creating from template 283 creating manually 236 creating using command line applet 596 creating using script file 660 creating using the wizard 236 Device and Media options 242 general options for new job from template 284 overview 235 pre/post commands 256 running from command line 596 scheduling 358 script file, creating and using 660 script file, saving and launching 704 selecting devices and data 259 Selections options 239, 407 switches for command line applet 596 tasks to do before 234 using command line applet to back up server drive 599 Backup Job Properties dialog box Exchange 2000 1074 Exchange 5.5 1110 SQL 2000 984 SQL 7.0 1032 backup job script file creating 660 saving and launching 704 backup job template copying to another server 831 creating 276 creating a copy 282 creating job using with command line applet 729 creating with command line applet 713 defined 276, 1260 editing 282 setting general options 278 backup job template script file creating 713 values 713 backup methods 1272
defined 1260 Intelligent Image Option (IIO) 948 selecting 248 selecting for template 279 setting default 313 using modified time 345 backup mode, Oracle Agent 1151 backup network changing for a backup job 328 configuring 325 overview 323 setting up 325 backup options backing up data in remote storage 253 contents of mounted local drives 252 NetWare network volumes 335 backup selections, changing order 265 backup set, defined 1261 Backup Size by Resource Job Report 839 backup strategies See also names of individual agents choosing devices to back up 338 defined 336, 1261 frequency of backups 337 increasing throughput with Backup Exec Remote Agent 821 length of data retention 338 multiple devices per job 339 one job per device 338 protecting against viruses 338 Backup Success Rate 837 backup types archive 344 copy 342 daily 342 differential 341 full 340 incremental 342 working set 343 Backup Wizard, launching 236 backup-to-disk properties General tab 158 Management tab 159 Statistics tab 160 renaming file 155 renaming folder 148 viewing folder properties 152
bar code labels and media ID 197 default 198 mixed media libraries 199 overview 198 robotic library support 198 bar code rules changing 201 deleting 202 setting up 199 BE Diagnostics, running from server properties 115 bediag.fax file 1238 bediag.nlm utility, saving configuration information 1238 bemcmd command, in command line applet 593 BESTART command, to start NetWare Agent 1226 BESTOP command, to stop NetWare Agent 1227 BEUtility.exe utility clusters, using in 751 BEWAC, See also Backup Exec Web Administrative Console biparam.ini options 1203 specifying Backup Exec parameters 1202 bjscript.txt 660 bjtemplatescript.txt 713 block size, setting for drives 122 Boot managers, restoring in IDR 891 bootable media for IDR CD image, creating 875 comparing types 856 floppy diskettes, creating 871 tape image, creating 877 types of media 856 buffer count, setting for drives 122 buffer size, setting for drives 122 build and version information, displaying 553 byte count, incorrect 564 C calendar display filters 369 view filters 369 viewing 368
cartridge tape drives, suggested types to use 558 cartridges, media 560 cascaded drive pools adding drives 108 creating 107 defined 89, 1262 deleting 110 deleting drives 109 overview 106 properties 111 renaming 111 requirements for using 107 using hardware compression in 107 catalog defined 40, 1262 levels 401 media in drive 397 removing unused after x days 401 searching 433 catalog database, in SAN Shared Storage Option 931 catalog operation errors DLT tape drive hangs 561 storage device hangs 560 CHECKCATALOG utility 982, 1031 CHECKDB utility 982, 1031 CHECKFILEGROUP utility 982, 1031 checkpoint restart on cluster failover enabling or disabling 747 overview 746 circular logging Exchange 2000, reviewing in 1079 Exchange 5.5, reviewing in 1115 Lotus Domino 1186 recovery of Lotus Domino server 1198 cleaning jobs, submitting for robotic libraries 178 cleaning properties for media 225 Cleaning tab for drive properties 128 client (or gateway) services for NetWare 335 clone CD image creating 828 overview 828 clone, using alias backup for a 608, 684, 711 clrest command 770 clusters adding or removing a failover node 750 all drives pool 745 1273
Index
Index
backing up database files 765 local disks 764 shared disks 764 Windows 2000 and Windows.NET 763 BEUtility 751 changing the order in which nodes fail over 749 clrest command 770 configurations four-node on a fibre channel SAN with the SAN SSO 760 overview 752 shared SCSI bus for tape devices 755 two-node on a fibre channel SAN with the SAN SSO 758 two-node with locally-attached storage devices 753 two-node with tape devices on a shared SCSI bus 754 creating drive pools 745 database server, designating new in SAN SSO 751 disaster recovery Backup Exec on a cluster using IDR 775 cluster data files 777 clustered Backup Exec 779 entire cluster manually 776 nodes using IDR 774 overview 773 shared disks 778 using IDR to prepare 774 error-handling rules 386 failover restart 740 installation additional options 743 Backup Exec in a cluster 742 requirements 741 Open File Option, and using 743 overview 762 Remote Agent, installing 742 restoring cluster quorum for Windows 2000 and Windows.NET 768 cluster quorum to node running Active Directory 769 specifying a new drive letter for the 1274
cluster quorum disk 771 Windows 2000 and Windows.NET 767 size 565 system state, backing up 764 troubleshooting 779 uninstalling Backup Exec 744 using with Backup Exec 739 virtual servers, backing up 765 combination R/3 database server/media server recovery 1209 command line applet administrating jobs 614 alert switches 619 alias backup 608, 684, 711 backup and restore script files 660 backup job switches 596 bemcmd command 593 defined 591 error-handling rules 623 job status messages 736 logon account switches 642 managing Backup Exec services 641 managing devices 624 media management switches 624 online help 594 report switches 643 requirements 592 restore job switches 618 setting default options 645 switches for administrating jobs 614 using 593 command line installation of Backup Exec 56 command line switches, used with all operations 594 commands See also names of individual commands completed jobs, job log overview 382 compression enable hardware compression option 121 in cascaded drive pools 107 setting backup defaults 315 configuration settings report 518 Configuration tab for drive properties 120 Configuration tab for robotic library 136 Configure Devices button 75
Configure SAN SSO, See Backup Exec Utility 806 configuring 1161 drives 119 holidays 364 media servers to use with Oracle Agent 1164 Oracle Agent, overview 1159 robotic library 133 consistency check options SQL 2000 981 SQL 7.0 1033 control file backup, Oracle Agent 1154 controller card 559 copy backups, defined 342, 1262 creating more disk space for backup folder 242 custom setup, when to use in IDR 898 D daily backups, defined 342, 1262 Daily Jobs by Resource Report 838 Daily Jobs Report 841 Daily Network Device Utilization Report 842 damaged media, removing 196 DAT, recommended driver 558 data compression, drive does not support 561 database files, backing up in a cluster 765 database log mode, Oracle Agent 1154 database maintenace configuring 389 database maintenance overview 389 database server defined 911, 1262 in clusters 751 Date Modified tab 435 default options backup and restore for Exchange 2000 1097 backup and restore for Exchange 5.5 1132 IDR, setting 863 NetWare network volumes 335 overview 39 restore 441 setting 84
setting for backup jobs 312 setting using command line applet 645 SQL 2000, backup and restore 1012 SQL 7.0, backup and restore 1056 default preferred configuration settings for drives 123 deleting drive pools 102 drives from pools 101 media 218 user-defined vault 213 device allocation in a shared storage environment 916 cleaning cartridge 560 managed by Backup Exec 563 selecting for backup job 242 Device and Media options for backup job 242 device management 89 Device Offline message 120 device operations See also robotic library cataloging media 397 ejecting media 177 Enable Hardware Compression Option 121 erasing media (quick or long) 168 formatting media 173 inventorying a drive 165 labeling media 174 overview of utility jobs 164 retensioning a tape 171 using with SAN Shared Storage Option 921 device summary report 519 Device Summary Report 918 devices configuring 93 Hot-swappable Device Wizard 94 managing using command line applet 624 pausing and resuming 94 release from Backup Exec 564 renaming 95 SCSI address 559 troubleshooting 934 viewing 90 1275
Index
Index
viewing with Library Expansion Option 1148 Devices view 90 Dfs See Distributed file system DHCP See Dynamic Host Configuration Protocol dialog boxes, overview 79 differential backups advantages and disadvantages 341 changed files, defined 1262 defined 341 using modified time, defined 1262 disable device for Backup Exec 120 disaster preparation Disaster Preparation Plan (DPP) 532 emergency repair disk 535 Exchange 2000 1101 Exchange 5.5 1137 hardware protection 532 Lotus Domino Agent 1195 off-site storage 532 overview 531 SQL 2000 1018 SQL 7.0 1061 disaster recovery See also names of individual agents clusters Backup Exec 779 Backup Exec on a cluster using IDR 775 data files 777 entire cluster manually 776 nodes using IDR 774 overview 773 shared disks 778 using IDR to prepare 774 data protected by Backup Exec agents 540 different types of computers, overview 540 Exchange 2000 1102 Exchange 5.5 1138 local Windows 2000 computers (non-authoritative) 546 local Windows NT computers 541 Lotus Domino Agent 1196 manual recovery of Windows system 540 NetWare Agent 1239 1276
Oracle Agent 1174 overview 540 remote Windows 2000 computers (non-authoritative) 549 remote Windows NT computers 543 disaster recovery alternate data path, in IDR 864 disaster recovery data path, in IDR 864 disaster recovery file (*.dr file) in IDR defined 855, 859 setting locations for 862 Disaster Recovery Wizard requirements 899 running 899 disk grooming, using for archive job 294 Disk Manager, using in IDR 902 Distributed file system (Dfs) backing up 261 restoring 424 DLT tape, drive hangs when cataloging 561 Domain Controller, using redirected restore to install from media 439 domains, host and target, defined 45 DPP See also Disaster Preparation Plan Drive Pool Properties dialog box 106 drive pools See also cascaded drive pools adding drives 98 creating 97 creating in a cluster 745 default for SAN Shared Storage Option 920 defined 89, 1262 deleting 102 deleting drives 101 overview 96 prioritizing drives 99 properties 105 renaming 104 SAN Shared Storage Option 916 using the default drive pool 96 viewing properties 106 drive properties Cleaning tab 128 Configuration tab 119 General tab 117 Media Types tab 130 SCSI Information tab 125 Statistics tab 126 Administrators Guide
viewing 116 drivers archive 558 download latest 559 Exabyte 558 if drive is not listed 558 Sony 558 Wangtek 558 drives block size 122 buffer count 122 buffer size 122 configuring 119 DAT 558 default settings 123 high water count 123 SCSI information 125 specifying media types for 130 statistics on usage 126 statistics since cleaning 128 types 558 using exclusively with Backup Exec 163 duplicate job advanced settings 303 general settings 302 duplicating backup data 300 Dynamic Host Configuration Protocol (DHCP) 576 E editing jobs created from templates 286 editions of Backup Exec, listed and described 31 See also names of individual editions eject media after job completes 244 from a drive 177 e-mail configuring MAPI notification 469 configuring SMTP notification 467 configuring VIM notification 470 emergency repair disk, creating 535 enabling bar code rules 137 device for Backup Exec option 120 hardware compression 121 Removable Storage (RSM) 137 robotic library for Backup Exec 137
robotic library initialization on startup 137 erase media operation, quick or long 168 Error Handling Rules Report 521 error-handling rules configuring 387 defined 386 overview 387 report 521 using command line applet 623 evaluation version Backup Exec, updating to serialized version 553 event logs report 522 Event Recipients Report 843 event, defined 1262 Exabyte 558 Exchange 2000 agent features 1067 agent installation 1068 agent requirements 1068 best practices 1073 disaster recovery 1102 logon accounts, overview 1069, 1106 Resource Discovery feature, using with 1068 Exchange 2000, backing up Active Directory 1072 Backup Job Properties dialog box 1074 backup methods 1075, 1098, 1111, 1133 circular logging, reviewing 1079 Guide Me wizard 1075, 1077 Internet Information Service (IIS) metabase 1071 Key Management Service (KMS) 1071 mailbox backup methods 1076 public folders 1080 recommended selections 1071 single instance backup for message attachments 1077 Site Replication Services (SRS) database 1071 storage groups 1078 strategies for 1070 system state 1071 Exchange 2000, restoring 1086 change password when recreating mailboxes 1101 1277
Index
Index
commit after restore completes option 1087 mailboxes and public folders, overview 1089 mailboxes and user accounts, recreating 1086 mount database after restore option 1087 no loss restore option 1086 redirecting mailboxes and public folders 1093 redirecting storage groups and databases 1091 Redirection dialog box 1091 requirements 1088 restore defaults 1097 Restore Job Properties dialog box 1085 restoring data to server 1085 temporary location for log and patch files 1087 Exchange 5.5 agent features 1105 agent installation 1106 agent requirements 1105 best practices 1109 logon accounts 1106 Resource Discovery feature, using with 1105 Exchange 5.5, backing up Backup Job Properties dialog box 1110 backup methods 1111 circular logging, reviewing 1115 Guide Me wizard 1111 Key Management Service (KMS) 1108 mailbox backup methods 1112 recommended selections 1108 single instance backup for message attachments 1113 strategies for 1107 Exchange 5.5, restoring 1120 change password when recreating mailboxes 1136 defaults 1135 DS/IS consistency adjuster after restore 1122, 1127 mailboxes and user accounts, recreating 1120 no loss restore option 1120 redirecting database restores 1125
redirecting mailboxes and public folders 1127 Redirection dialog box 1125 requirements 1121 Restore Job Properties dialog box 1119 restore private mailboxes option 1120 restore public folder option 1120 restoring data to server 1119 Exchange Server Agent, backing up backup job script file method, using 665, 705 command line for Exchange 2000 603 using for backup job 600 executing a command after backup 256 after restore 417 before backup 256 before restore 417 ExecView communication module, defined 391 components 392 information server, defined 391 launching console 394 overview 391 user preferences overview 393 exporting media 181 express setup, when to use in IDR 898 F failback, defined 740 Failed Backup Jobs Report 844 failover adding or removing a failover node 750 changing the order in which nodes fail over 749 defined 739 restart 740 FAT cluster size 565 partition 564 fatal tape format inconsistency message 560 father/son media rotation strategy 215 FC-AL See Fibre Channel Arbitrated Loop Fibre Channel Arbitrated Loop (FC-AL) defined 1263 in SAN SSO 911 fibre channel hub, defined 1263 fibre channel switch, defined 1263
1278
Fibre Channel Switched Fabric (FC-SW), defined 1263 fibre channel tape controller, defined 1263 fibre channel, defined 1263 fibre to SCSI bridge defined 1263 replacing 936 file permissions, restoring 420 filegroups backing up SQL 2000 990 SQL 7.0 1037 displaying 990, 1037 restoring SQL 2000 1004 SQL 7.0 1049 restoring nonprimary SQL 2000 999 SQL 7.0 1046 restoring primary SQL 2000 999 SQL 7.0 1045 files, processing open 254, 318 filters calendar 369 job monitor 365 jobs list 367 filters for alerts 454 finding media in a location or vault 210 format media 173 frequently asked questions about using Backup Exec 82 Full - Back Up Files - Allows incrementals and differentials using modified time defined 1263 Full - Back Up Files - Reset Archive Bit defined 1263 full backups advantages and disadvantages 340 defined 340 G General drive properties 117 general job defaults, setting 87 general media properties, viewing 220 general options backup job template 278 duplicate job 302 job created from template 284
restore jobs 409 General tab Backup-to-Disk folder 158 robotic library 135 grandfather media rotation strategy 216 groups, configuring recipients 487 H hardware compression in cascaded drive pools 107 creating profile 534 enable hardware compression option 121 error message 560 protection in case of disaster 532 high water count, setting for drives 123 host domain, defined 45 hub defined 1264 replacing 937 I IBM ADSM Option, overview 38 IBM computers, recovering with IDR 893 IDR Configuration Wizard 859 imported media defined 191, 1264 labeled by Backup Exec 198 overwriting 195 importing media 180 Incremental - Changed Files - Reset Archive Bit, defined 1264 Incremental - Using modified time, defined 1264 incremental backups advantages and disadvantages 342 defined 342 indows XP backing up 333 Information Desk, overview 79 installation parameter file creating 62 defined 62 using 62 installation requirements, Backup Exec 46 See also names of individual agents and options installing additional Backup Exec options on a cluster 743 1279
Index
Index
Backup Exec 47 Backup Exec in a cluster 742 Domain Controllers from media 439 Library Expansion Option 1146 locally additional options 49 using clone CD image 829 overview 41 Remote Administrator 67 remotely using clone CD image 830 SharePoint Agent 1213 storage devices 41 using installation program 47 using Repair option 64 Windows Management Instrumentation performance counter 499 Windows Management Instrumentation SNMP provider 499 Intelligent Disaster Recovery (IDR) alternate data path on a remote computer 864 ASR files 855, 859 boot managers 891 catalog entries, added to *.dr file 857 clusters recovering Backup Exec 775 recovering nodes 774 custom setup, using 898 disaster recovery diskettes, updating 881 disaster recovery file (*.dr file), defined 855, 859 express setup, using 898 First Time Startup Configuration Wizard 859 hard disk partitions, changing for Windows NT 900 hard drive partition, altering sizes using IDR 903 IBM computers 893 installing 858 Intelligent Image Option (IIO), used with 948 Microsoft Exchange Server, recovering 909 Microsoft SQL Server, recovering 909 Options - Set Application Defaults dialog box 863 OS/2 boot manager, restoring 891 1280
overview 36, 855 Recovery Wizard, running 899 requirements 858 restoring remote media server 902 Sharepoint Portal Server, recovering 909 System Commander boot manager, restoring 891 utility partitions, backing up 868 virtual devices, using in 858 Windows Automated System Recovery (ASR) files 855, 859 Intelligent Disaster Recovery Additional Client option, installing 858 Intelligent Image Option (IIO) caution about canceling a restore job 954 command line, running from 600, 611 encrypted files, backing up 948 installing 949 Intelligent Disaster Recovery (IDR), used with 948 job log example 952 open files, backup and restore of 948 overview 38 requirements 949 restoring IIO backup sets 954 selecting as backup method 951 single-pass restore 948 Internet Information Services (IIS) metabase, backing up 1071 inventory job creating 166 setting job priority 167 inventorying all drives on startup 85 all drives when Backup Exec starts 165 drives 165 J job audit log, defined 1264 Job Distribution by Device Report 845 job history defined 40, 1264 deleting report 511 saving report 510 viewing 378 viewing report 509 job log configuring default options 384 defined 1264
status overview 382 job monitor command line switches 614 filters 365 views 365 Job priority 167 job priority setting for cleaning jobs 179 setting for eject job 177 setting for erase job 171 setting for export job 182 setting for format job 173 setting for import job 180 setting for inventory job 167 setting for label media job 176 setting for retension job 172 specifying using command line applet 596 job progress indicators, displaying 86 Job Queue Status Report 845 job status messages, descriptions 736 Job Templates Report 846 jobs active, canceling 373 changing priority for scheduled 375 configuring default Lotus Domino options 1184 configuring default schedule 363 configuring error-hanlding rules 387 configuring new recipients 493 configuring schedule 358 defined 1264 deleting scheduled 377 edit recipients 493 editing schedule 360 holiday scheduling 364 Lotus Domino backup properties 1187 removing hold active jobs 374 scheduled jobs 375 run report 506 running scheduled job 374 running scheduled test job 376 scheduled, modifying 374 scheduled, viewing 374 scheduling 358 selecting recipients for notifications 492 setting general defaults 87 viewing active 365 Index
viewing and filtering calendar 368 jobs list 365 viewing and scheduling in a SAN 929 viewing completed 378 jobs list view filters 367 viewing 365 K Key Management Service (KMS) database, backing up 1071, 1108 L labeling media creating default labels 206 imported media label 198 in drive 174 renaming label 202 using bar code labels 198 last known good menu 533 Library Expansion Option overview 36, 1143 SCSI addresses for hardware 1143 setting up hardware 1143 library sharing configuring server for 923 linked drives See cascaded drive pools local device, defined 1264 local media server, breaking connection with 68 lock open files for backup 254, 318 lock robotic library panel 182 logon accounts changing default 355 changing for a resource being backed up 266 clearing audit log 356 command line applet switches 642 default, defined 348 deleting 354 editing 353 Exchange 2000 resources, and 1069, 1106 Exchange 5.5 resources, and 1106 overview 347 replacing 353 SQL 2000 resources 978 SQL 7.0 resources 1027 system logon account 349 viewing audit log 356 1281
Index
Lotus Domino Agent APIs 1185 archive logging 1186 backup job script method, using 666, 718 backup options 1187 circular logging 1186 command line, using for backup 606 configuring default options 1184 database backup overview 1185 database backup requirements 1180 disaster preparation 1195 disaster recovery archive logging 1197 circular logging 1198 of server 1196 overview 37 redirecting restore 1194 requirements 1180 restore overview 1189 selecting for restore 1190 selecting restore options 1192 supported configurations 1185 viewing databases 1182 M Machines Backed Up Report 847 Macintosh Agent, system requirements 578 mailboxes Exchange 2000 backup methods 1076 best practices 1081 change password when recreating 1101 exclude specific folders 1081 overview of backing up 1080 recreating mailboxes and user accounts 1086 redirecting restores 1093 restore overview 1089 Exchange 5.5 backup methods 1112 best practices 1116 change password when recreating mailboxes 1136 exclude specific folders 1116 overview of backing up 1115 redirecting restores 1127 restore overview 1123 majority node in a cluster 741
Management tab for backup-to-disk folder 159 manually update server list, for NetWare 1238 MAPI configuring recpients 474 MAPI e-mail notification method 469 master database backup SQL 2000 982 SQL 7.0 1031 master database restore SQL 2000 996, 1007 SQL 7.0 1043 media adding to the offline location or user-defined media vault 211 all media, defined 190 allocated, defined 191 append backup to 244 append options 195 cartridges 560 cleaning properties, viewing 225 creating default labels 206 damaged 196 deleting 218 deleting user-defined vault 213 displaying media ID 220 finding in a location or vault 210 general properties 220 hardware-compressed tape 561 how Backup Exec searches for overwritable media 193 imported, defined 191 management properties, viewing 222 managing using command line applet 624 moving to a media set 219 moving to a new location 212 overwrite for backup 244 overwrite options 192 overwriting allocated or imported 195 properties 220 recyclable, defined 191 retired, defined 191 scratch, defined 190 setting default options 203 sharing 931 statistical properties 223 system, defined 190 Administrators Guide
1282
testing integrity of 305 using with Removable Storage 162 with excessive errors 196 media capacity, testing before backup runs 311 media catalogs 911 media categories 190 media ID, defined 197, 1265 media label bar code rule changing 201 deleting 202 in mixed media libraries 199 bar codes 198 defined 1265 imported 198 overview 196 renaming 202 media location 209 media name, specifying during backup job 243 media operations deleting media 218 moving media 219 viewing media properties 220 media overwrite protection levels, defined 190, 1265 media overwrite protection, overview 185 Media Required for Recovery Report 848 media rotation in SAN 932 media rotation strategies father/son 215 grandfather 216 son 214 Media Rotation Wizard 217 media rotation, defined 1265 media server backing up using one-button backup 292 connecting 68 defined 1265 running diagnostics on 112 viewing properties 112 media servers configuring for robotic library sharing 923 media set creating 227 default 189 Index
defined 191, 1265 deleting 229 properties 230 renaming 230 selecting for backup job 243 shared storage environments, and 931 wizard, running 226 media sets report 523 media types, specifying for drives 130 media vault defined 209, 1265 finding media in a vault 210 user-defined creating 210 defined 209 renaming 211 media view 395 menu bar, overview 76 messages device offline 120 error 566 fatal tape format inconsistency 560 hardware error 560 Microsoft Cluster Server, using with Backup Exec 740 Microsoft Exchange Server See also Exchange Server Agent Microsoft SQL Server See alsoSQL Server Agent mirror, using alias backup for split mirror 608, 684, 711 mixed media library bar code labeling 199 mounted local drives, backing up files and directories 252 Move Media to Vault Report 849 moving media from user-defined vault 213 media to a media set 219 MSCS, using with Backup Exec 740 N Name & Location dialog box 434 named transaction include in restore, SQL 2000 998 restore up to, SQL 2000 998, 1003 navigation bar, overview 77 Net Send configuring recipients 482
Index
1283
NetWare client (or gateway) services 335 options 1237 NetWare Agent AUTOEXEC.NCF file 1226 installing 1225 overview 37 Remote Agent 1224 system requirements 1224 TCP/IP only environment 1226 NetWare Agent, backing up BEDIAG.NLM utility 1238 create BEDIAG.FAX 1238 decompressed files 1237 password database 1228 rights for backup 1228, 1229 single server backup strategies 1229 strategies for multiple administrators 1230 strategies for single administrator 1230 NetWare Agent, restoring 1233 network changing a backup network for a job 328 overview of backup networks 323 setting up a backup network 325 network options, restore job 445 network protocols, IPX/SPX 327 network shares, NetWare volumes 335 New Backup-to-Folder dialog box 145 nodes adding or removing a failover node 750 changing the order in which nodes fail over 749 configurations in a cluster 752 defined 739 disaster recovery using IDR 774 nonlogged operations occurring in SQL 7.0 1039 notification assigning recipients to alerts 491 defined 453 notifications assigning alert categories 491 clearing recipients 492 configuring MAPI e-mail 469 configuring pager 471 configuring SMTP e-mail 467 configuring SNMP 494 configuring VIM e-mail 470 1284
methods defined 467 modifying alert category properties 492 modifying recipient properties 489 scheduling recipients 488 selecting recipients for jobs 492 Novell Storage Management Services tree view 335 NTFS cluster size 565 partition 564 numbering, specify for media label 207 O offline media location adding media to 211 defined 209, 1265 offline, when devices display as 120 off-site storage of backups 532 one-button backup 292 online media location 209, 1265 Online Registration Wizard, using 63 online, putting device back 120 open files backing up 254 setting default for backing up 318 unable to back up 562 optimizing remote backups 253 options default for job log 384 Options - Set Application Defaults General 87 Preferences 85 options, additional Backup Exec options described 36 Oracle Agent 1161 adding media servers 1164 archived redo logfiles 1151 backup mode, described 1155 backup strategies 1152 error messages 1177 fully specified paths, using 1158 installing 1160 overview 37 renaming data files from a single tablespace 1158 shutting down and restarting the Oracle database 1156 system requirements 1152 troubleshooting 1177
types of data to protect 1153 user account, creating 1154 Oracle Agent, backing up closed database 1168 command line, using for backup 607 online database 1165 online tablespaces 1167 Oracle Agent, configuring Adding Media Server dialog box 1164 archived logfiles directory 1159 ARCHIVELOG mode 1155 automatic archival 1154, 1155 BECF.BAK 1154 control file backup 1154 control file backup location 1163 database control file 1159 database log mode 1154, 1155 Database tab 1164 General tab 1164 INIT.ORA 1157 INITORCL.ORA 1154 instance initialization parameter files 1157 list of configured media servers 1162 multiple database instances on a single database server 1157 Oracle account username 1163 Oracle Server using the Oracle Agent Configuration Utility 1159 overview 1159 removing configured media servers 1162 requirements 1154 server manager 1155 SID 1157 SID name 1163 tablespace data 1153 TCP/IP address 1164 Oracle Agent, disaster recovery file system backup 1174 Oracle database server and media server combination 1176 remote Oracle database server 1175 requirements 1174 tablespace data files 1174 Oracle Agent, restoring closed database 1171 database control file 1173 individual tablespaces 1172 online database 1170 Index
Oracle information manager 1173 over existing files 1169 Oracle server manager 1173 Overnight Summary Report 849 overview tab, using 79 overwritable media, how Backup Exec searches for it 193 overwrite default media label 206 overwrite media option, specifying for backup job 244 overwrite protection levels full 204 none 205 partial 205 overwrite protection period defined 185, 228, 1266 setting for media set 228 overwrite protection, disabling 205 P pager configuring recipients 479 notification method 471 parameter file, editing in R/3 Agent for Oracle Server 1203 partial overwrite protection 205 partition creating for robotic library 140 defined 1266 FAT 564 NTFS 564 redefining for robotic library 142 password database, NetWare Agent 1228 pausing a device 120 pausing device 95 performance, increasing during backups of remote systems 822 physical check, SQL 2000 987 PHYSICAL_ONLY utility 982 placing scheduled job on hold if test run fails 311 point in time log restore option SQL 2000 998, 1002 SQL 7.0 1045, 1048 portal support 181 post-job command setting for backup job 256 setting for restore job 416 pre/post command options for jobs 320
Index
1285
Pre/Post Commands 320 prefix, creating for media label 207 pre-job command setting for backup job 256 setting for restore job 416 preserve tree option for backup job 249 for backup template 280 for restores 411 primary navigation bar 784 primary server defined 911 printer, configuring recipients 485 priority changing for scheduled job 375 setting for backup job 247 setting for drives in pools 99, 121, 153 setting for restore job 410 Problem Files Report 850 product updates, receiving 70 prompt before overwriting allocated or imported media 205 properties active job 370 alerts 457 Lotus Domino 1187 media cleaning 225 general 220 management 222 statistical 223 report 512 protecting Windows XP and Windows.NET systems 333 public folders Exchange 2000 backing up 1080 best practices 1081 exclude specific folders 1081 redirecting restores 1093 restore overview 1089 Exchange 5.5 backing up 1115 best practices 1116 exclude specific folders 1116 redirecting restores 1127 restore overview 1123 restore public folder option 1120 published drives, defined 569 1286
Q Quick Start Edition of Backup Exec, described 32 R R/3 Agent backing up the R/3 database 1205 R/3 Agent for Oracle Server BACKINT implementation 1199 how it works 1199 installing 1201 requirements 1201 security 1200 R/3 Agent for Oracle Server, restoring disaster recovery requirements 1207 submitting restore jobs 1206 R/3 database server, restoring, remote recovery 1208 reapplying templates to jobs 286 reassigning how slots appear 137 Rebuild Master utility, SQL 7.0 1051 Recently Written Media Report 851 recipients assigning alert categories 491 clearing recipients 492 configuring 477 configuring groups 487 configuring MAPI e-mail 474 configuring Net Send 482 configuring new for jobs 493 configuring pager 479, 485 configuring SMTP 472 defined 472 modifying alert category properties 492 selecting for notifications 492 recovery completion state SQL 2000 995 SQL 7.0 1042 recovery requirements in IDR 891 recyclable media, defined 191, 1266 redirected restore See also names of individual agents using to install Domain Controllers from Media 439 redirecting scheduled job 103 registry, restoring 414 Remote Administrator defined 1266 running 68
system requirements 67 Remote Agent defined 1266 described 37 for NetWare 1224 installing on a cluster 742 Installing using the command line 823, 960 remote backup and restore 821 Uninstalling using the command line 824, 961 remote storage, back up data 253 Removable Storage feature, Microsofts monitoring Backup Exec 163 using with Backup Exec 161 using with the SAN SSO 162 Remove Primary SAN SSO Server 805 renaming cascaded drive pools 111 drive pools 104 media labels 202 robotic library or drive 95 user-defined vault 211 renaming libraries and drives in shared environment 921 reports active alerts 515 Active Alerts by Media Server 835 active history 515 audit log 517 Backup Size by Resource Job 839 Backup Success Rate Report 837 configuration settings 518 Daily Jobs 841 Daily Jobs by Resource 838 Daily Network Device Utilization 842 deleting in job history 511 device summary 519 Error Handling Rules 521 error-handling 521 event logs 522 Event Recipients 843 Failed Backup Jobs 844 Job Distribution by Device 845 Job Queue Status 845 Job Templates 846 Machines Backed Up 847 Media Required for Recovery 848 media sets 523 Index
Move Media to Vault 849 Overnight Summary 849 Problem Files 850 Recently Written Media 851 Resource Risk Assessment 852 Retrieve Media from Vault 853 Robotic Library Inventory 526 running 503 running job 506 saving 510 Scheduled Server Workload 853 scheduling report jobs 835 Scratch Media Availability 527 standard in Backup Exec 513 Template Definition Usage 854 using command line applet 643 viewing 502 viewing in job history 509 viewing properties 512 requirements Agent for Exchange 2000 1068 Agent for Exchange 5.5 1105 installation, for Backup Exec 46 Lotus Domino Agent 1180 R/3 Agent for Oracle Server 1201 SAN Shared Storage Option 914 system, for Backup Exec 42 TSM option 1241 Reset Cleaning Statistics 128 resource credentials, changing for restore job 430 order, changing 265 resource discovery creating job 295 defined 1266 Resource Risk Assessment Report 852 resource, defined 1266 responding to active alerts 459 restore job Advanced File Selection 430 advanced options 412 canceling 446 copying to another server 831 creating through dialog boxes 404 creating using script file 686 creating with wizard 403 file permissions 420 general options 409 Lotus Domino options 1192 1287
Index
over existing files 410 overview 403 pre/post commands 416 preserve tree option 411 R/3 Agent for Oracle Server 1206 redirecting 436 redirecting Lotus Domino 1194 running from command line 618 security 411 setting defaults 441 specifying network 445 Restore Job Properties dialog box Exchange 2000 1085 Exchange 5.5 1119 Exchange Redirection page 1091, 1125 SQL 2000 994 SQL 7.0 1041 restore job script file 686 saving and launching 704 Restore Selections dialog box 428 restore, defined 1266 restoring ARCserve tapes 426 byte count does not match 566 caution about canceling an IIO restore job 954 closed Oracle database 1171 clusters cluster quorum for Windows 2000 and Windows.NET 768 cluster quorum on node running Active Directory 769 Windows 2000 and Windows.NET 767 Distributed file system (Dfs) 424 Exchange 2000 1085 Exchange 5.5 1119 individual Oracle tablespaces 1172 Intelligent Image Option backup sets 954 Lotus Domino Agent 1190 media view 395 media with hardware compression 561 NetWare Agent volume restrictions 1237 online Oracle database 1170 Oracle database control file 1173 registry 414 resource view 395 searching for files 433 selecting data 428 1288
single-pass restore with Intelligent Image Option 948 using the media view 428 using the resource view 428 resuming a drive 95 retarget job 103 retensioning a tape 171 retired media defined 191, 1267 moving damaged media 196 Retrieve Media from Vault Report 853 returning to a previous configuration 533 rjscript.txt 660 robotic library cleaning jobs 178 configuring 133 configuring partitions 140 creating partitions 140 defined 1267 displaying storage devices 1146 example configuration 1145 exporting media 181 importing media 180 lock front panel 182 portal support 181 problem with not displaying 559 redefining partitions 142 setting up hardware 1143 unlock front panel 183 using with Backup Exec 132 viewing 1148 viewing properties 134 Robotic Library Inventory Report 526 robotic library properties Configuration tab 136 General tab 135 SCSI Information tab 138 Status tab 139 robotic library sharing between Windows and NetWare servers 922 prerequisites 922 S SAN Shared Storage Option (SSO) device allocation 916 device operations 921 installing 915 overview 37
requirements 914 schedule 364 schedule script file using with device and media operations 730 values 730 scheduled jobs changing priority 375 configuring 358 configuring default options 363 deleting 377 editing 360 modifying 374 removing hold 375 running immediately 374 running test job 376 viewing 374 Scheduled Server Workload Report 853 scheduling notification recipients 488 SAN SSO jobs 929 scratch media creating 195 defined 190, 1267 Scratch Media Availability Report 527 SCSI address 559 address for devices 559, 1143 configuring devices 559 controller card 559 defined 1267 information about drives 125 information about robotic library 138 modes 560 setting address for robotic library drives 1143 SCSI bus, configuring for tape devices in a cluster 755 SCSI pass-through mode, setting for drives 123 search catalogs 433 secondary navigation bar 784 security changing for Windows systems 44 R/3 Agent for Oracle Server 1200 restoring 411 select into/bulk copy option, SQL 7.0 1039 selecting devices and data to back up 259 selection lists Index
copying to another server 831 creating 267 creating using script file 704 defined 267, 1267 deleting 272 editing 273 excludes 273 merging and replacing 271 script file using in command line applet 704 values for 705 using for backup job 270 selections deleting 272 editing 274 user-defined, adding 275 user-defined, using TCP/IP addresses 275 Selections options for backup job 239 serial numbers Backup Exec for Windows Servers Remote Agent 822 Backup Exec, adding and removing 48, 53 See also names of individual agents and options serialized copy, Backup Exec 553 server clusters See alsoclusters server list adding and removing servers 65 manually update for NetWare 1238 server properties viewing 112 viewing server information 113 viewing system properties 114 Server tab 113 ServerFree Option installing 944 overview 38 service account changing 65 described 46 services starting and stopping 65 starting and stopping on multiple servers 933 Set Application Defaults, Preferences 85 Set Primary SAN SSO Server, See also
Index
1289
Backup Exec Utility Set Remote Agent Priority 253 Shadow Copy Components backing up 333 selecting for backup 333 shared catalogs, using 911 shared device, defined 1267 SharePoint Agent 1211 backing up a SharePoint Portal Server or Workspace 1213 disaster recovery 1221 installing 1213 overview 38, 1211 redirecting restore jobs 1217 restoring SharePoint Portal Servers and Workspaces 1215 system requirements 1212 SharePoint Portal Server command line, backing up from 605 disaster recovery 1221 redirecting restore jobs 1217 sharing media 911, 931 silent mode installation 46, 56, 1267 simple recovery model, SQL 2000 975 single block mode, setting for drives 123 single instance backup for message attachments Exchange 2000 1077 Exchange 5.5 1113 single instance backup for NTFS volumes 252 Site Replication Services (SRS) database, backing up 1071 size, cluster 565 slot base configuration 137, 1148 Small Business Server Edition of Backup Exec, described 32 SMTP configuring e-mail recipients 472 SMTP e-mail notification method 467 SNMP configuring notification 494 configuring system service for Windows 2000 498 configuring system service for Windows NT 497 installing WMI provider 499 object identifier prefix 494 traps, defined 494 1290
WMI 499 software license agreement 47, 67 son media rotation strategy 214 Sony, recommended driver 558 Specified Backup Network feature configuring 325 described 323 splash screen, show at startup 85 SQL 2000 agent features 975 agent installation 977 agent requirements 976 Backup Job Properties dialog box 984 consistency check, recommendations 981 Database Consistency Check (DBCC), recommendations 981 disaster recovery preparation 1018 logon accounts 978 overview 975 SQL 2000, backing up backup job script file method 719 backup methods 985 command line 604 consistency check after backup 987 consistency check recommendations 981 databases 988, 989 disaster recovery preparation 1018 filegroups 991 Guide Me wizard 988 loading state 987 standby mode 987 strategies for 980 transaction logs 993 Windows registry 980 SQL 2000, restoring automate master database restore 996 create standby database 995 database files to target instance 997 disaster recovery 1020 filegroups 1004 Guide Me wizard 998 Intelligent Disaster Recovery (IDR) option 1018 master database 1007 named transaction, include 998 named transaction, to a 998, 1003 point in time log restore option 1002 primary and nonprimary filegroups 999 Administrators Guide
recovery completion state 995 redirecting restores 1009 Redirection dialog box 1009 restore defaults 1012 Restore Job Properties dialog box 994 very large databases 999 SQL 7.0 agent features 1024 agent installation 1026 agent requirements 1025 consistency check, recommendations 1030 Database Consistency Check (DBCC), recommendations 1030 disaster recovery preparation 1061 logon accounts 1027 SQL 7.0, backing up Backup Job Properties dialog box 1032 backup job script file method 665, 707 backup methods 1033 command line 602 command line, using for standby or recover 605 consistency check after backup 1058 consistency check options 1033 consistency check recommendations 1030 continue with backup if consistency check fails 1058 databases 1035 disaster recovery preparation 1061 filegroups 1037 Guide Me wizard 1034 nonlogged operations occurring 1039 select into/bulk copy option 1039 transaction logs 1040 truncate log on checkpoint option 1035, 1039 Windows registry 1029 SQL 7.0, restoring automate master database restore 1043 create standby database 1042 disaster recovery 1063 filegroups 1049 Guide Me wizard 1045 primary and nonprimary filegroups 1045 Rebuild Master utility 1051 recovery completion state 1042, 1059 Index
redirecting restores 1053 Redirection dialog box 1054 restore database files to target instance 1044 restore defaults 1056 restore job properties 1041 Restore Job Properties for SQL dialog box 1041 Standby database 1059 SQL 7.0., backing up strategies for 1029 standby database SQL 2000 975 SQL 7.0 1024 standby database, creating SQL 2000 995 SQL 7.0 1042 starting Backup Exec 74 services 933 static volume, defined 1267 statistical properties for media 223 statistics drive usage 126 drives since cleaning 128 Statistics tab for backup-to-disk folder 160 Status tab for a robotic library 139 stopping services 933 storage devices installing 41 not being displayed 559 system logon account 349 system media, defined 190, 1267 system requirements See also names of individual agents and options Backup Exec 42 System State backing up on remote systems 825 restoring 421 System Summary, overview 80 System tab 114 T tablespace data, Oracle Agent 1153 tape driver, recommended use 558 tape drives, cartridge 558 tapes See also media
Index
1291
DLT tape drive 561 target domain, defined 45 task pane, overview 77 TCP/IP adding for user-defined shares 275 enabling protocol 327 required for UNIX Agent 584 Template Definition Usage Report 854 test run job creating 307 defined 307 running for scheduled job 376 setting defaults 310 Tivoli Storage Manager (TSM) Option, overview 38 transaction logs Lotus Domino DBIID 1186 overview, Lotus Domino 1186 recycling, Lotus Domino 1189 viewing Lotus Domino 1182 transaction logs, backing up SQL 2000 992 SQL 7.0 1039 troubleshooting clusters 779 Oracle Agent 1177 TSM option 1256 truncate log on checkpoint option, SQL 7.0 1035, 1039 TSM Option Backup Exec as TSM client 1242 commands management classes created by bex.mac macro 1254 MC_PI management class created by bex.mac macro 1254 MC_VT management class created by bex.mac macro 1254 objects, default size 1254 objects, defined 1254 password for backupexec node, default 1255 policy domain VERITAS, default 1254 policy set bex_backup, default 1254 registering nodes 1255 time to retain only backup version, setting 1255
VERITAS policy domain, default 1254 components Backup Exec default node name 1255 Backup Exec default node registration 1255 backupexec_pi storage pool associated with bexpi.dsm file 1254 backupexec_pi storage pool, defined 1244 backuppool 1244, 1254 bex.mac macro, command details 1254 bex.mac macro, defaults created by 1254 bex.mac macro, defined 1245, 1253 bex.mac macro, errors while executing 1248 bex.mac macro, using with shared or individual nodes 1248 bex_backup policy set, default 1254 bexpi.dsm file, as used in bex.mac macro 1254 creating backupexec_pi storage pool 1245 creating the bexpi.dsm file 1246 diserror.log error log 1256 dsmfmt utility, defined 1245 dsmfmt utility, using to create a storage volume 1246 dsmrc.h file 1256 MC_PI management class 1243 MC_VT management class in theory of operation 1244 Position Information (PI) data stream, defined 1243 setting backup versions to keep 1255 storage volume, creating with dsmfmt utility 1246 theory of operation 1243 error logs 1256 individual nodes 1248 registering nodes 1249 registry keys 1249 changing default number of slots in robotic library 1251 changing default password 1253 communications timeout, changing default 1250 Administrators Guide
1292
file space name, changing in Backup Exec 1251 MC_PI management class in Backup Exec 1252 MC_VT management class, changing default name 1252 node name for Backup Exec 1251 objects in Backup Exec 1252 shared nodes 1248 system requirements 1241 troubleshooting 1256 Virtual Tape (VT) data stream, defined 1244 U unattended backup jobs 106 uninstalling Backup Exec 66 Backup Exec from a cluster 744 using command line 61 Windows Management Instrumentation SNMP provider 500 UNIX Agent advertise to media server 589 back up symbolic links 582, 588, 589 configuring 588 described 584 installation overview 584 system requirements 584 UNIX Agent commands agent.cfg commands 588 exclude directories/files 590 identify exported paths 589 include remote file systems 589 password-protect published path 589 password-protect workstation 588 preserve ctime 590 publish directory tree 589 write-protect published path 589 unlocking robotic library panel 183 user account, Oracle Agent 1154 user-defined media vault 209, 1265 adding media to 211 creating 210 deleting 213 renaming 211 user-defined selections, adding 275 utility jobs, overview 164 utility partitions
backing up 334 backing up in IDR 868 restoring 423 restoring in IDR 871 selecting data for backup 259 V verify after backup completes 249, 280 after duplicate backup completes 303 verify job creating 305 defined 305 VERITAS Backup Exec for Windows Servers, described 31 VERITAS update 70 version and build information, displaying 553 view filter, setting 456 viewing active alerts 454 active job properties 370 alert history 454 alert job log 460 alert properties 457 alerts 454 calendar 368 completed job 378 job monitor 365 jobs 929 jobs list 365 Lotus Domino databases 1182 Lotus Domino transaction logs 1182 scheduled jobs 374 views, alerts 454 VIM configuring recipients 477 VIM, e-mail notification method 470 virtual devices, using in IDR 858 virtual servers, backing up in a cluster 765 virus, effect on data storage requirements 338 volume restrictions, NetWare Agent 1237 W Windows 2000 remote systems, backing up with Backup Exec Remote Agent 825 System State, backing up on remote systems 825 1293
Index
Index
Windows 98/Me Agent installing 571 password-protecting published folders 575 publishing drives and directories 574 set directories as read-only 575 system requirements 570 Windows 98/Me Agent, configuring allow registry restore 573 current status 573 disable and enable network backup 573 overview 572 publish directories 574 set up network protocol 576 set workstation password 573 using DHCP 576 Windows Automated System Recovery (ASR) files, in IDR, defined 855, 859 Windows Change Journal option to use for backup job 249 using to determine backed up status 346 Windows Explorer, backups creating 286 enabling 85 overview 286 specifying or changing settings 287 submitting 290
Windows Management Instrumentation (WMI), adding WMI capability 499 Windows NT disaster recovery 541 drivers list 558 Windows registry, backing up SQL 2000 980 SQL 7.0 1029 Windows XP disaster recovery 537 Windows.NET backing up 333 disaster recovery 537 support in Backup Exec 33 wizards accessing using the Assistant 82 defined 1268 WMI installing performance counter provider 499 installing SNMP provider 499 performance counters 499 uninstalling SNMP provider 500 WMI See Windows Management Instrumentation working set backups, defined 343, 1268 write checksums to media 244
1294

Be Admin

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Be Admin

Hochgeladen von

Copyright:

Verfügbare Formate

VERITAS Backup Exec for Windows Servers

October 2002 N096948

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

Appendix J. VERITAS Backup Exec - Agent for Oracle Server

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Using Backup Exec Documentation

Steps Text that you type

Numbered steps are listed as 1.,

Text that you replace

Items on the interface

Introducing Backup Exec

Small Business Server

QuickStart Edition (OEM release only)

See also: Backup Exec Options on page 36

Whats New in This Release

Whats New in This Release

Updated graphical user interface

Automatic discovery of new resources Error handling rules

Chapter 1, Introducing Backup Exec

Whats New in This Release

Tracking of media by location Media capacity tracking Dynamic product update

Whats New in This Release

Enhanced reporting capabilities

Hot-swappable Device Wizard

Advanced Open File Option

Admin Plus Pack Option

Chapter 1, Introducing Backup Exec

Backup Exec Options

Backup Exec Options

Backup Exec Options

Chapter 1, Introducing Backup Exec

Backup Exec Options

How Backup Exec Works

How Backup Exec Works

Backup Exec database

storage devices and media

Backup Exec media server running the Backup Exec engine

Backup Exec workstation and server agents

Chapter 1, Introducing Backup Exec

How Backup Exec Works

Installing Backup Exec

Chapter 2, Installing Backup Exec

Changing Windows Security

Changing Windows Security

If You Are Backing Up Servers (only) in One Domain:

Changing Windows Security

Chapter 2, Installing Backup Exec

Installing Backup Exec

Installing Backup Exec

The Backup Exec Service Account

Installing Backup Exec

Installing Backup Exec Using the Installation Program

Chapter 2, Installing Backup Exec

Installing Backup Exec

Installing Backup Exec

Installing Backup Exec Options on a Local Server