279401

Symantec Backup ExecTM 10d for Windows Servers
Administrators Guide
N180788 September 2005
Disclaimer The information contained in this publication is subject to change without notice. Symantec 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. Symantec 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. Symantec Legal Notice Copyright 2005 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 http://www.symantec.com Third-Party Copyrights
Douglas C. Schmidt and his research group at Washington University and University of California, Irvine
ACE (TM) is copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved.
Apache Software Foundation

Apache Tomcat 4.0, Apache Xerces C++ 1.2.0 and 1.3.0 Apache Software License Version 1.1 Copyright (c) 2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appears. 4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>. Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.
Crystal Decisions, Inc. (formerly Seagate Software Information Management Group, Holdings, Inc.
Crystal Reports 8.5 Use, duplication, reproduction, or transfer of this commercial software and accompanying documentation is restricted in accordance with FAR 12.212 and DFARS 227.7202 and by a license agreement. Contact: Crystal Decisions, Inc., Attn: Contracts Department, 895 Emerson Street, Palo Alto, CA 94301.
Nebiru Software Inc. (dba DomAPI)

DomAPI LIbrary 5.0 Copyright 2001-2003
Boris Fornitchev
STLPort 3.2.1 Copyright 1999,2000 Boris Fomitchev This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. The Licensee may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. The Licensee may distribute original or modified STLport sources, provided that: (i) The conditions indicated in the above permission notice are met; (ii) The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: Copyright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems, Inc. Copyright 1997 Moscow Center for SPARC Technology. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett- Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC Technology makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Carnegie Mellon University and The Regents of the University of California

ucd-snmp 4.1.1 Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work -Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Ronald L. Rivest
Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved. License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work. RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided "as is" without express or implied warranty of any kind. These notices must be retained in any copies of any part of this documentation and/or software.
Wei Dai
Compilation Copyright (c) 1995-2003 by Wei Dai. All rights reserved. This copyright applies only to this software distribution package as a compilation, and does not imply a copyright on any particular file in the package. The following files are copyrighted by their respective original authors, and their use is subject to additional licenses included in these files. mars.cpp - Copyright 1998 Brian Gladman. All other files in this compilation are placed in the public domain by Wei Dai and other contributors. I would like to thank the following authors for placing their works into the public domain: Joan Daemen - 3way.cpp Leonard Janke - cast.cpp, seal.cpp Steve Reid - cast.cpp Phil Karn - des.cpp Michael Paul Johnson - diamond.cpp Andrew M. Kuchling - md2.cpp, md4.cpp Colin Plumb - md5.cpp, md5mac.cpp Seal Woods - rc6.cpp Chris Morgan - rijndael.cpp Paulo Baretto - rijndael.cpp, skipjack.cpp, square.cpp Richard De Moliner - safer.cpp Matthew Skala - twofish.cpp Permission to use, copy, modify, and distribute this compilation for any purpose, including commercial applications, is hereby granted without fee, subject to the following restrictions: 1. Any copy or modification of this compilation in any form, except in object code form as part of an application software, must include the above copyright notice and this license. 2. Users of this software agree that any modification or extension they provide to Wei Dai will be considered public domain and not copyrighted unless it includes an explicit copyright notice.
3. Wei Dai makes no warranty or representation that the operation of the software in this compilation will be error-free, and Wei Dai is under no obligation to provide any services, by way of maintenance, update, or otherwise. THE SOFTWARE AND ANY DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT EXPRESS OR IMPLIED WARRANTY INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL WEI DAI OR ANY OTHER CONTRIBUTOR BE LIABLE FOR DIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 4. Users will not use Wei Dai or any other contributor's name in any publicity or advertising, without prior written consent in each case. 5. Export of this software from the United States may require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting. 6. Certain parts of this software may be protected by patents. It is the users' responsibility to obtain the appropriate licenses before using those parts. If this compilation is used in object code form in an application software, acknowledgement of the author is not required but would be appreciated. The contribution of any useful modifications or extensions to Wei Dai is not required but would also be appreciated.
Maarten Hoeben
ReportCtrl.h 2.0.1
Stac Electronics
Copyright (C) Stac Electronics 1993, including one or more U.S. patents No. 4701745, 5016009, 5126739 and 5146221 and other pending patents.
Administrators Guide - Table of Contents

Using Backup Exec Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Chapter 1. Introducing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Whats New in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Whats New in Backup Exec Agents and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Backup Exec Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 How Backup Exec Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Chapter 2. Installing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Microsoft SQL Server 2000 Desktop Engine (MSDE) Components Installed with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Changing Windows Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 The Backup Exec Environment Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Installing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Installing Backup Exec Using the Installation Program . . . . . . . . . . . . . . . . . . . . . . 67 Installing Backup Exec Options to the Local Computer . . . . . . . . . . . . . . . . . . . . . . 71 Installing Backup Exec to Remote Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Installing Backup Exec Agents to Remote Computers . . . . . . . . . . . . . . . . . . . . . . . 77 Installing Backup Exec Using the Command Line (Silent Mode) . . . . . . . . . . . . . . 81 Installing the Remote Administrator Using the Command Line . . . . . . . . . . . . . . 85 Push-Installing the Remote Agent for Windows Servers and the Advanced Open File Option Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . 87 Uninstalling Backup Exec Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . . 88 Registering Backup Exec Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Repairing Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Starting and Stopping Backup Exec Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Uninstalling Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7
Uninstalling Backup Exec Options from the Local Media Server . . . . . . . . . . . . . . 94 Installing the Backup Exec Remote Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Using a Clone CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Creating a Clone CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Installing Locally Using a Clone CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Installing to a Remote System Using a Clone CD Image . . . . . . . . . . . . . . . . . . . . . 99 Using VERITAS Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Viewing Installed Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Viewing License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Upgrading from Previous Versions of Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Upgrading Backup Exec Options on Remote Computers . . . . . . . . . . . . . . . . . . . . . . . 105 Chapter 3. Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Before Starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Starting Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 First Time Startup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Using the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Using Backup Exec Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Using the Overview View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Using the Backup Exec Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Backup Exec Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Changing Default Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Changing General Job Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Chapter 4. Managing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Viewing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Viewing Media Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Configuring Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Hot Swap for Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 VERITAS device driver Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
8 Administrators Guide
Pausing, Resuming, and Renaming Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Using Device Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Creating Device Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Adding Devices to a Device Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Setting Priorities for Devices in a Device Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Deleting Devices from a Device Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Deleting Device Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Retargeting Jobs from a Deleted Device Pool or Media Set . . . . . . . . . . . . . . . . . . 137 Renaming a Device Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Viewing Device Pool Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Using Cascaded Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Requirements for Using Cascaded Drive Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Creating a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Adding Drives to a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Deleting Drives from a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Deleting a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Renaming a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Viewing Properties of a Cascaded Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Viewing Media Server Properties and Running Server Diagnostics . . . . . . . . . . . . . 144 Viewing Media Server General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Viewing Media Server System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Viewing Media Server Advanced Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Viewing Media Server License Information Properties . . . . . . . . . . . . . . . . . . . . . 150 Viewing and Using Device Properties and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Viewing General Device Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Viewing Drive Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Viewing Drive SCSI Information Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Viewing Drive Statistics Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Viewing Drive Cleaning Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Viewing and Specifying a Devices Media Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Administrators Guide - Table of Contents 9
Using Robotic Libraries with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Configuring a Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Viewing Properties of a Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Creating Robotic Library Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Redefining Robotic Library Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Using Backup-to-Disk Folders and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Adding a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Renaming a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Changing the Path of a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Deleting a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Recreating a Backup Folder and Its Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Pausing and Resuming a Backup Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Viewing Backup Folder Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Viewing Backup Folder General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Viewing Backup Folder Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Renaming a Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Deleting a Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Recreating a Deleted Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Using Microsofts Removable Storage Feature with Backup Exec . . . . . . . . . . . . . . . 189 Using Media in Drives Managed by Removable Storage . . . . . . . . . . . . . . . . . . . . 190 Creating Utility Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Inventorying Media in Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Erasing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Erasing Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Retensioning a Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Formatting Media in a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 Labeling Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Ejecting Media from a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Setting Up Cleaning Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Importing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Exporting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Locking the Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Unlocking the Robotic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Exporting Expired Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Chapter 5. Managing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Media Overwrite Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Default Media Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Creating Media Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Running the Media Set Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Deleting a Media Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Renaming a Media Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 General Media Set Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Vault Rule Properties for Media Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Media Overwrite Protection Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Media Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Media Overwrite Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Media Append Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Overwriting Allocated or Imported Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Removing Damaged Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Media Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Imported Media Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Bar Code Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Renaming Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Setting Default Media Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Media Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Creating Media Vaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Finding Media in a Location or Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Renaming a Media Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Adding Media to the Offline Location or a Media Vault . . . . . . . . . . . . . . . . . . . . . 245
11
Update Media Vaults by Using a Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Moving Media by Dragging and Dropping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Deleting a Media Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Media Rotation Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Son Media Rotation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Father/Son Media Rotation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Grandfather Media Rotation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Media Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Deleting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Moving Media to a Media Set or Media Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Viewing General Media Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Viewing Statistics for Media Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Chapter 6. Backing Up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259 Creating a Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Using the Backup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Creating a Manual Backup Job by Configuring Job Properties . . . . . . . . . . . . . . . 262 Selecting Data to Back Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 About Selecting Distributed File System (Dfs) Links for Backup . . . . . . . . . . . . . 287 Including or Excluding Files for Backup Using Advanced File Selection . . . . . . 288 Changing the Order for Processing Backup Selections . . . . . . . . . . . . . . . . . . . . . 291 Changing and Testing Logon Accounts for Resources . . . . . . . . . . . . . . . . . . . . . . 292 Using Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Creating Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Using Selection Lists to Create a Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Holding Jobs That Back Up a Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Merging and Replacing Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Deleting Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Editing Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 About the Excludes Selection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
12
Setting Priority and Availability Windows for Selection Lists . . . . . . . . . . . . . . . 301 Creating Multiple Selection Lists from a Single Selection List . . . . . . . . . . . . . . . 303 Searching Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Setting Up User-defined Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Using Backup Execs Windows Explorer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Submitting a Backup Job from Windows Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Running a One-button Backup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Archiving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Archiving Data Using Disk Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Using Resource Discovery to Search for New Resources . . . . . . . . . . . . . . . . . . . . . . . 311 Excluding Computers from a Resource Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 Duplicating Backed Up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Verifying a Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Creating a Test Run Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Setting Test Run Default Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Setting Default Backup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Setting Default Pre/Post Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Specifying Backup Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Specifying Default Backup Network and Firewall Options . . . . . . . . . . . . . . . . . . 336 Changing the Backup Network for a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Using Backup Exec with Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Browsing Systems Through a Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Protecting Windows Server 2003 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 About the Backup Exec Shadow Copy Components File System . . . . . . . . . . . . . . 344 Protecting Upgraded Windows Server 2003 Resources . . . . . . . . . . . . . . . . . . . . . 347 Backing Up Utility Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Backing Up EFI System Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 About Backup Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Choosing a Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 Understanding Backup Methods and Their Advantages . . . . . . . . . . . . . . . . . . . . 354
Understanding the Archive Bit and Backup Methods . . . . . . . . . . . . . . . . . . . . . . . 357 Understanding Modified Time and Backup Methods . . . . . . . . . . . . . . . . . . . . . . . 358 Chapter 7. Policies and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361 Creating a New Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Editing a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Deleting a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Using an Example Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Using Templates in Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Migrating Templates from Previous Versions of Backup Exec . . . . . . . . . . . . . . . 367 Adding a Backup Template to a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Setting the Schedule for a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Adding an Export Media Template to a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Importing a Template into a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Editing a Template in a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Deleting a Template from a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Setting Template Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Changing Template Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Deleting Template Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Creating Jobs Using Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Viewing the Policies that Protect Selection Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Editing the Next Occurrence of a Policy-based Job . . . . . . . . . . . . . . . . . . . . . . . . . 379 Deleting a Job Created from a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Renaming a Job Created from a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 About Duplicate Backup Set Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Adding a Duplicate Backup Template to a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Chapter 8. Administrating Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385 Configuring Logon Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Default Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Backup Exec System Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Creating a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Editing a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Replacing a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Deleting a Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Changing Your Default Backup Exec Logon Account . . . . . . . . . . . . . . . . . . . . . . . 392 Creating a New Backup Exec System Logon Account . . . . . . . . . . . . . . . . . . . . . . . 392 Copying Jobs, Selection Lists, and Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 Copy Configuration Settings and Logon Information . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Scheduling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Editing the Job Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 Configuring Default Schedule Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 Configuring Holiday Scheduling for Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Viewing and Filtering Jobs in the Job List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Managing Custom Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 Viewing and Filtering Jobs in the Calendar View . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Viewing and Changing Active Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Viewing and Changing Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Viewing and Changing Completed Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Using Audit Logs to Review Activity Performed in Backup Exec . . . . . . . . . . . . . . . . 437 Configuring the Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Error-Handling Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Custom Error-handling Rule for Recovered Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Cluster Failover Error-Handling Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Setting Thresholds to Recover Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 Configuring Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Chapter 9. Restoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Restore Operations and the Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 Cataloging Media in a Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
15
Setting Catalog Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 Catalog Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Restoring Data to a Server or Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Using the Restore Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 Creating a Manual Restore Job by Configuring Job Properties . . . . . . . . . . . . . . . 458 Restoring File Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Restoring System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472 Restoring Windows Server 2003 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Restoring Utility Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 Restoring EFI System Partition Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Restoring Distributed File System (Dfs) Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 Restoring Media Created With Other Backup Software . . . . . . . . . . . . . . . . . . . . . 476 Selecting Data to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Using the Resource View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Using the Media View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 Changing and Testing Resource Credentials for Restore Jobs . . . . . . . . . . . . . . . 481 Using Advanced File Selection to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Searching for Files to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483 Restore Operations and Media Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 Redirecting a Restore Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Using Redirected Restore for Active Directory, Active Directory Application Mode, and Install from Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Setting Restore Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Specifying the Restore Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 Canceling a Restore Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 Catalog Icon Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Chapter 10. Alerts and Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .501 Viewing and Filtering Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502 Viewing Alert Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 Responding to Active Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Viewing the Job Log for Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 Clearing Informational Alerts from the Active Alerts Pane . . . . . . . . . . . . . . . . . . . . 510 Enabling or Disabling Alerts from the Active Alerts Pane . . . . . . . . . . . . . . . . . . . . . . 510 Configuring Alert Category Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 Deleting Alerts from the Alert History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 Configuring E-mail and Pager Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . 514 Configuring SMTP E-Mail for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 Configuring MAPI E-Mail for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 Configuring VIM E-Mail for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 Configuring a Pager for Alert Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 Configuring Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Configuring SMTP Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Configuring MAPI Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 Configuring VIM Mail for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 Configuring a Pager for a Person Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 Configuring a Net Send Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 Configuring a Printer Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 Configuring a Group Recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 Scheduling Notification for Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 Editing Recipient Notification Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 Editing Recipient Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 Removing Recipients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 Assigning Recipients to Alert Categories for Notification . . . . . . . . . . . . . . . . . . . . . . 533 Selecting Recipients for Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534 Configuring SNMP Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 Adding Windows Management Instrumentation Capability . . . . . . . . . . . . . . . . . . . . 540 Uninstalling WMI Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541 Chapter 11. Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
17
Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 Running and Viewing a New Report Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 Scheduling Report Jobs and Setting Notification Recipients . . . . . . . . . . . . . . . . 553 Viewing Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 Available Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Active Alerts Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Active Alerts by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Alert History Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 Alert History by Media Server Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 Audit Log Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 Backup Job Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564 Backup Resource Success Rate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565 Backup Set Details by Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 Backup Sets by Media Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 Backup Size By Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Configuration Settings Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569 Current Job Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 Daily Network Device Utilization Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Device Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 Device Usage by Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Error-Handling Rules Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 Event Logs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 Event Recipients Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 Failed Backup Jobs Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 Job Distribution by Device Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577 Jobs Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 Machines Backed Up Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579 Managed Media Servers Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579 Media Required for Recovery Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 Media Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Media Vault Contents Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 Missed Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Move Media to Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Operations Overview Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 Overnight Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 Policy Jobs by Resource Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 Policy Jobs Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590 Policy Properties Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591 Policy Protected Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 Problem Files Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 Recently Written Media Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 Resource Backup Policy Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 Resource Risk Assessment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 Restore Set Details by Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597 Retrieve Media from Vault Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 Robotic Library Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 Scheduled Server Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600 Scratch Media Availability Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 Test Run Results Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602 Chapter 12. Disaster Preparation and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605 Key Elements of a Disaster Preparation Plan (DPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 606 Disaster Preparation of the Windows Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607 Returning to the Last Known Good Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 607 Creating a Hardware Profile Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608 Creating an Emergency Repair Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609 Using Windows Automated System Recovery and System Restore to Recover a Windows XP or Windows Server 2003 System . . . . . . . . . . . . . . . . . . . 610 Manual Disaster Recovery of Windows Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
19
Manual Disaster Recovery of a Local Windows 2000/XP/Server 2003 Computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611 Disaster Recovery of a Remote Windows 2000/XP/Server 2003 Computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615 Chapter 13. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .619 Hardware-related Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 Backup Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624 Restore Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626 Improving Backup Exec Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626 Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 Before Calling Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628 Finding Version and Revision Information for Your Backup Exec Installation 629 Backup Exec Diagnostic Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629 Using Symantec DirectAssist for Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 633 Chapter 14. Symantec Backup Exec - Workstation Agents . . . . . . . . . . . . . . . . . . . . . . . .635 The Backup Exec Windows 98 and Windows Me Agents . . . . . . . . . . . . . . . . . . . . . . . 636 Requirements for Running the Backup Exec Windows 98/Me Agent . . . . . . . . . 636 Installing the Backup Exec Windows 98/Me Agent on the Workstation . . . . . . 637 Configuring the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . 637 Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639 Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641 The Backup Exec Macintosh Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642 Requirements for Running the Backup Exec Macintosh Agent . . . . . . . . . . . . . . 643 Installing and Configuring the Macintosh Agent on a Mac OS X Computer . . . 643 Modifying the NetInfo Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648 About the Backup Exec 8.x and 9.x Agent for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Requirements for Running the Backup Exec 8.x and 9.x Agent for Unix . . . . . . 649 Installing the Backup Exec 8.x and 9.x Agent for Unix on the Workstation . . . 650 Configuring the Backup Exec 8.x and 9.x Agent for Unix . . . . . . . . . . . . . . . . . . . . 653 Loading the Backup Exec 8.x and 9.x Agent for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . 656 Troubleshooting Workstation Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 Chapter 15. Using Symantec Backup Exec with Server Clusters . . . . . . . . . . . . . . . . . . 657 How Backup Exec Works in a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . 658 Requirements for Installing Backup Exec on a Microsoft Cluster Server . . . . . . . . . 659 Installing Backup Exec on a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . 660 Upgrading Backup Exec on a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661 Installing Additional Backup Exec Options on a Microsoft Cluster . . . . . . . . . . . 662 Uninstalling Backup Exec From a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . 663 Creating Device Pools for Microsoft Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 Using Checkpoint Restart on Microsoft Cluster Server Failover . . . . . . . . . . . . . . . . 665 Enabling or Disabling Checkpoint Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667 Specifying a Different Failover Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668 Designating a New SAN SSO Primary Server and Central Administration Server in a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669 Configurations for Backup Exec and Microsoft Cluster Servers . . . . . . . . . . . . . . . . . 670 Two-node Cluster with Locally Attached Storage Devices . . . . . . . . . . . . . . . . . . . 671 Two-node Cluster with Tape Devices on a Shared SCSI Bus . . . . . . . . . . . . . . . . . 672 Multi-node Clusters on a Fibre Channel SAN with the SAN SSO . . . . . . . . . . . . . 675 Using the Central Admin Server Option with Microsoft Clusters and SAN SSO . . . 678 Backing Up Microsoft Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680 Backing Up Windows 2000 and Windows Server 2003 Features in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681 Backing Up Local Disks in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682 Backing Up Shared Disks in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 682 Backing Up Database Files in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 683 Restoring Data to a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Restoring Windows 2000 and Windows Server 2003 Features to a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684 Restoring the Cluster Quorum for Windows 2000 and Windows Server 2003 Computers to a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685 Restoring the Cluster Quorum to a Windows 2000 or Windows Server 2003 Node Running Active Directory to a Microsoft Cluster . . . . . . . . . . 686 Specifying a New Drive Letter for the Cluster Quorum Disk . . . . . . . . . . . . . . . . . 688 Using Backup Exec with a VERITAS Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 689 Requirements for Installing Backup Exec on a VERITAS Cluster Server . . . . . . . . . 690 Installing Backup Exec on a VERITAS Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . 691 Backing Up VERITAS Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692 Backing Up Windows 2000 and Windows Server 2003 Features in a VERITAS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693 Backing Up Local Disks in a VERITAS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694 Backing Up Shared Disks in a VERITAS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 694 Backing Up Database Files in a VERITAS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 695 Restoring Data to VERITAS Cluster Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696 Restoring Windows 2000 and Windows Server 2003 Features to a VERITAS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696 Using Backup Job Failover with VERITAS Cluster Servers . . . . . . . . . . . . . . . . . . . . . 696 Disaster Recovery of a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697 Using IDR to Prepare for Disaster Recovery of a Cluster . . . . . . . . . . . . . . . . . . . . 698 Recovering Nodes on the Cluster Using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698 Recovering Backup Exec on a Microsoft Cluster Using IDR . . . . . . . . . . . . . . . . . 700 Recovering the Entire Cluster Using a Manual Disaster Recovery Procedure . 700 Recovering the Microsoft Cluster Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702 Recovering All Shared Disks in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . 703 Recovering All Shared Disks in a VERITAS Cluster . . . . . . . . . . . . . . . . . . . . . . . . 704 Recovering Backup Exec in a Microsoft Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705 Troubleshooting Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
22
Chapter 16. Symantec Backup Exec - Web Administration Console . . . . . . . . . . . . . . . 709 Requirements for BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Installing BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 Setting Internet Explorer Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 Starting BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 Differences Between BEWAC and Backup Exec for Windows Servers . . . . . . . . . . . . 711 Accessing Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712 Navigating in BEWAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Viewing, Clearing, and Responding to Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Chapter 17. Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Starting the Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719 Completing Tasks using the Backup Exec Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 Running Backup Exec Utility General Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Add a New Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722 Create a New Media Server Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723 Delete a Media Server from the All Media Servers Node . . . . . . . . . . . . . . . . . . . . 724 Delete a Media Server Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725 Run Backup Exec Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726 Enable Debug Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726 View Media Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 Running Backup Exec Utility Services Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733 Stop Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734 Start Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734 Change Service Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736 Editing Media Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737 Copy Media Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742 Apply Copied Media Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
23
Update Configuration for New Media Server Name . . . . . . . . . . . . . . . . . . . . . . . . 743 Running Backup Exec Utility CASO Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745 Set Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746 Remove Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747 Enable CASO Job Delegation on a Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748 Disable CASO Job Delegation on Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748 Move Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749 Change Catalog Storage Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750 Running Backup Exec Utility SAN SSO Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751 Set the Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752 Remove the Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752 Configure the SAN SSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 Promote a Media Server to a Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . 754 Move the Primary SAN SSO Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755 Running Database Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756 Check the Database Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757 Age the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757 Compact a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758 Dump a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758 Rebuild Media Server Database Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759 Repair a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759 Recover a Media Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760 Change the SQL Server sa Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761 Change Database Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762 New Backup Exec Database Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763 Copy Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764 Running Media Server Group Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765 Add Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765 Remove a Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766 Set Central Administration Server for the Media Server Group . . . . . . . . . . . . . 766
Running Cluster Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768 Edit Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768 Chapter 18. Symantec Backup Exec - Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . 771 Requirements for the TSM Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771 Backup Exec as a TSM Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772 TSM Backup Exec Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773 Preparing the TSM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775 Allocating Storage Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775 Creating The bexpi.dsm Storage Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776 Running the BEX.MAC Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778 Enabling TSM Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 Changing the Defaults for Backup Exec for Windows Servers . . . . . . . . . . . . . . . . . . 779 BEX.MAC Macro Command Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786 Viewing TSM-related Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786 TSM Problem Resolutions for Backup Exec for Windows Servers . . . . . . . . . . . . 786 Appendix A. Symantec Backup Exec - Remote Agent for Windows Servers . . . . . . . . . 789 Requirements for the Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791 Backing Up Data in a Mixed Environment Using the Remote Agent . . . . . . . . . . . . . 792 Installing the Remote Agent to Remote Windows Computers . . . . . . . . . . . . . . . . . . 793 Installing the Remote Agent on a 64-bit Computer Using the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793 Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794 Installing and Uninstalling the 64-bit Remote Agent and Advanced Open File Option Using a Command Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795 Stopping and Starting the Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797 The Remote Agent Monitor for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797 Setting Defaults for the Remote Agent Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799 Viewing Remote Agent Monitor Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Enable Advertising for the Remote Agent for Windows Servers . . . . . . . . . . . . . 800 Enable Debug Logging for Remote Windows Computers . . . . . . . . . . . . . . . . . . . . 802 Appendix B. Symantec Backup Exec - Remote Agent for Linux or Unix Servers . . . . . .803 Requirements for the Remote Agent for Linux or Unix . . . . . . . . . . . . . . . . . . . . . . . . 803 Installing the Remote Agent for Linux or Unix Servers . . . . . . . . . . . . . . . . . . . . . . . . 804 Creating the BEOPER Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804 Installing RALUS Using the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805 The ralus.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808 Using the Remote Agent for Linux or Unix Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . 810 Making Backup Selections with RALUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810 Uninstalling the Remote Agent for Linux or Unix Servers . . . . . . . . . . . . . . . . . . . . . 813 Manual Install and Uninstall of RALUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814 Manually Installing RALUS from a TAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814 Manually Uninstalling RALUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815 Manually Starting the RALUS Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815 Manually Stopping the RALUS Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816 RALUS and the Backup Exec 8.x and 9.x Agent for Unix . . . . . . . . . . . . . . . . . . . . . . . 816 Appendix C. Symantec Backup Exec - Central Admin Server Option . . . . . . . . . . . . . . . .819 About the Central Admin Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819 The Central Admin Server Option Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820 How the Central Admin Server Option Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821 Features of the Central Admin Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825 Requirements for Installing the Central Admin Server Option . . . . . . . . . . . . . . 828 Getting Started with the Central Admin Server Option . . . . . . . . . . . . . . . . . . . . . . . . 829 Installing the Central Admin Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832 Installing Managed Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832 Installing Managed Media Servers Behind a Firewall . . . . . . . . . . . . . . . . . . . . . . . 835 Upgrading a Backup Exec Media Server to a Central Administration Server . . 836 Setting a Central Administration Server for Stand-alone Media Servers . . . . . 837
Migrating from Network Storage Executive v8.6 (NSE) . . . . . . . . . . . . . . . . . . . . . 838 Uninstalling Backup Exec from the Central Administration Server . . . . . . . . . . 839 Uninstalling Backup Exec from a Managed Media Server . . . . . . . . . . . . . . . . . . . 839 Configuring the Central Admin Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840 Configuring Device Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840 Configuring Managed Media Server Time Thresholds and Catalog Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840 Setting Job Log and Job History Options for Managed Media Servers . . . . . . . . . 844 Configuring CASO Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845 Configuring CASO Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847 Running Managed Media Server Operations from the Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848 Pausing and Resuming a Managed Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 848 Disabling and Enabling Communications with the Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849 Stopping and Starting Backup Exec Services on the Managed Media Server from the Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850 Remotely Connecting to a Managed Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . 851 Deleting a Managed Media Server from the Media Servers View . . . . . . . . . . . . . 852 Viewing Managed Media Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852 CASO Changes to Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853 The CASO Media Servers View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853 Changes to the Job Monitor/Job History View with CASO . . . . . . . . . . . . . . . . . . . 856 CASO Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856 Backing Up with the Central Admin Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857 Setting Media Server Property Options for CASO Backup Jobs . . . . . . . . . . . . . . 857 Setting the Default Network Interface for Delegated Jobs . . . . . . . . . . . . . . . . . . . 858 Device and Media Options for CASO Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860 Restoring Data Using the Central Administration Server . . . . . . . . . . . . . . . . . . . . . . 860 CASO Restore Operations and Centralized Catalogs . . . . . . . . . . . . . . . . . . . . . . . . 861 Requirements for Restore When Using the Central Administration Server . . . 862
27
How Centralized Restore Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862 How CASO Restores Data That Resides on Multiple Storage Devices . . . . . . . . . 863 Using the Device and Media Property with Centralized Restore Jobs . . . . . . . . . 865 Using Media Server Pools in CASO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866 Creating a Media Server Pool and Adding Managed Media Servers . . . . . . . . . . 867 Adding Additional Managed Media Servers to a Media Server Pool . . . . . . . . . . 868 Renaming a Media Server Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869 Deleting a Media Server Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869 Removing a Managed Media Server from a Media Server Pool . . . . . . . . . . . . . . 870 Configuring Device Pools for Use with CASO Media Server Pools . . . . . . . . . . . . 870 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871 Recovering Failed Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871 Pausing Storage Devices on Managed Media Servers from the Central Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873 Backup Duplicate Data and Synthetic Backup Templates Considerations . . . . . 873 Disaster Recovery Using Intelligent Disaster Recovery (IDR) with CASO . . . . . . . . 874 Appendix D. Symantec Backup Exec - Advanced Disk-based Backup Option . . . . . . . .875 Installing the Advanced Disk-based Backup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . 875 About the Synthetic Backup Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876 Requirements for Synthetic Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878 Best Practices for Synthetic Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879 Collecting Additional Information for Synthetic Backup . . . . . . . . . . . . . . . . . . . 879 Creating A Synthetic Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880 Creating a Synthetic Backup By Using the Policy Wizard . . . . . . . . . . . . . . . . . . . 881 Creating a Synthetic Backup By Copying the Example Policy for Synthetic Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881 Creating a Synthetic Backup By Adding Templates to a Policy . . . . . . . . . . . . . . 883 About the Offhost Backup Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888 Requirements for Offhost Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
28
Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890 Best Practices for Using Offhost Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891 Setting Offhost Backup Options for Backup Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . 892 Browsing Remote Computers for Installed Snapshot Providers . . . . . . . . . . . . . . 894 Restoring Offhost Backup Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895 Troubleshooting the Offhost Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896 Appendix E. Symantec Backup Exec - Intelligent Disaster Recovery Option . . . . . . . 901 Requirements for Using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902 Installing the IDR Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903 Using an Evaluation Version of the IDR Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903 Preparing Computers for IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904 Getting Started with IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906 Manually Setting Data Paths for the *.dr Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 About Creating and Updating Recovery Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912 Requirements for Running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . . 913 Running the IDR Preparation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914 Creating Recovery Media After a Disaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915 Creating A Full Set of Diskettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917 Creating a Bootable CD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920 Creating a Bootable Tape Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924 Creating the Intelligent Disaster Recovery Diskettes Only . . . . . . . . . . . . . . . . . . 927 Updating Bootable Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929 Updating the Full Set of Disaster Recovery Diskettes . . . . . . . . . . . . . . . . . . . . . . . 931 Updating the Intelligent Disaster Recovery Diskettes Only . . . . . . . . . . . . . . . . . 934 Preparing IDR Media Via Other Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937 Preparing to Recover from a Disaster Using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939 Changing Hardware in the Computer to be Recovered . . . . . . . . . . . . . . . . . . . . . . 940 Using IDR To Recover IBM Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941 Using IDR To Recover Windows 2000 Computers . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Recovering a Computer Using IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942 Using the Disaster Recovery Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945 Altering Hard Drive Partition Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949 Recovering Computers Requiring OEM-Specific SCSI Drivers . . . . . . . . . . . . . . . 950 Performing a Manual Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951 Performing Remote IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952 Microsoft SQL Server Recovery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953 Microsoft Exchange Recovery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954 SharePoint Portal Server Recovery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954 Citrix Metaframe Recovery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954 Using IDR with the Central Admin Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . 955 Using IDR with VERITAS Storage Foundation for Windows . . . . . . . . . . . . . . . . 955 About Recovering 64-bit Itanium Computers with IDR . . . . . . . . . . . . . . . . . . . . . 955 Best Practices for IDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956 Appendix F. Symantec Backup Exec - SAN Shared Storage Option . . . . . . . . . . . . . . . . .957 Requirements for the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959 Installing the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960 About Devices in the Shared Storage Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 961 Monitoring Drives in the Shared Storage Environment . . . . . . . . . . . . . . . . . . . . 962 Viewing Media in the Shared Storage Environment . . . . . . . . . . . . . . . . . . . . . . . . 962 Using Drive Pools with the SAN Shared Storage Option . . . . . . . . . . . . . . . . . . . . 963 Using Device Operations with the SAN Shared Storage Option . . . . . . . . . . . . . . 964 Sharing Robotic Libraries Between Backup Exec for NetWare Servers and Backup Exec for Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965 Scheduling and Viewing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970 Sharing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971 Cataloging Media in SAN SSO Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971 Media Rotation in SAN SSO Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972 Designating a New Database Server and Setting Up Servers . . . . . . . . . . . . . . . . . . . 973 Tips for Maintaining the Database Server
and the ADAMM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973 Creating a Standby Primary Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974 Starting and Stopping Backup Exec Services on Multiple Servers . . . . . . . . . . . . 975 Troubleshooting and Recovering Failed Components . . . . . . . . . . . . . . . . . . . . . . . . . 976 Checklist for Troubleshooting Devices That Have Gone Offline . . . . . . . . . . . . . 976 Resetting the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978 Bringing Devices Online After an Unsafe Device Removal Event . . . . . . . . . . . . 978 Best Practices for SAN SSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979 Appendix G. Symantec Backup Exec - ServerFree Option . . . . . . . . . . . . . . . . . . . . . . . . 981 Understanding ServerFree Backup Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981 ServerFree Backup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984 Installing the ServerFree option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986 Running the ServerFree Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987 Restoring A ServerFree Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989 Appendix H. Symantec Backup Exec - Advanced Open File Option . . . . . . . . . . . . . . . . 991 Understanding the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991 Supported Snapshot Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994 Requirements for Using the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . 995 Installing the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996 Installing and Uninstalling the Advanced Open File Option to Remote Windows Computers Using the Command Line . . . . . . . . . . . . . . . . . . . . 997 Uninstalling the Advanced Open File Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999 Setting Defaults for the Advanced Open File Option for Backup Jobs . . . . . . . . . . . . 999 Using Snap Start on a VERITAS Storage Foundation for Windows Volume . . 1005 Best Practices for Using the Symantec Volume Snapshot Provider . . . . . . . . . 1006 Symantec Volume Snapshot Provider Cache File Location . . . . . . . . . . . . . . . . . 1007 Changing the Default Settings for the Symantec Volume Snapshot Provider . . . 1008 Checking the Job Log When Using the AOFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
31
Appendix I. Symantec Backup Exec - Agent for Microsoft SQL Server . . . . . . . . . . . 1013 Requirements for Using the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014 Installing the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015 Using Backup Exec Logon Accounts for SQL Resources . . . . . . . . . . . . . . . . . . . . . . 1015 Backup Strategies for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017 Consistency Checks for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021 Using Snapshot Technology With the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022 Using AOFO With the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023 Using the ADBO With the SQL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024 Setting Backup Options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024 Automatic Exclusion of Files During Volume Level Backups . . . . . . . . . . . . . . . 1028 Backing Up SQL Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029 Backing Up SQL Filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031 Backing Up SQL Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033 Restore Options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035 About Restoring SQL Databases and Filegroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040 Restoring from SQL Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041 Restoring from SQL Transaction Logs Up to a Point in Time . . . . . . . . . . . . . . . 1042 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction . . . . 1043 Restoring from SQL Filegroup Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044 Restoring the SQL Master Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047 Redirecting Restores for SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049 Setting Default Backup and Restore Options for SQL . . . . . . . . . . . . . . . . . . . . . . . . . 1052 Preparing for Disaster Recovery of SQL 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057 Disaster Recovery of SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059 Manual Recovery of SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060 Appendix J. Symantec Backup Exec - Agent for Microsoft Exchange Server . . . . . . 1065 Requirements for Using the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066 Installing the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
32
Using Backup Exec Logon Accounts with Exchange Resources . . . . . . . . . . . . . . . . 1068 Backup Strategies for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068 Recommended Configurations for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072 Using Snapshot Technology With the Exchange Agent . . . . . . . . . . . . . . . . . . . . . . . 1074 Backup Options for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075 Backing Up Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079 Automatic Exclusion of Files During Volume Level Backups . . . . . . . . . . . . . . . 1080 Reviewing Circular Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081 Backing Up Exchange Mailboxes and Public Folders . . . . . . . . . . . . . . . . . . . . . . . . . . 1082 Restore Options for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086 Restoring Exchange Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089 Restoring Exchange 2003 Data Using the Recovery Storage Group . . . . . . . . . 1092 Restoring Exchange Mailboxes and Public Folders . . . . . . . . . . . . . . . . . . . . . . . . 1094 Redirecting Exchange Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096 Redirecting Exchange 2000 and 2003 Storage Group and Database Restores . 1098 Redirecting Exchange 5.5 Database Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098 Redirecting Exchange 2003 Restores Using the Recovery Storage Group . . . . 1099 Redirecting Mailbox Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100 Setting Default Backup and Restore Options for Exchange . . . . . . . . . . . . . . . . . . . . 1102 Preparing for Disaster Recovery of Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . 1108 Disaster Recovery for Exchange 2000 and 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108 Disaster Recovery for Exchange Server 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1111 Appendix K. Symantec Backup Exec - Library Expansion Option . . . . . . . . . . . . . . . . . 1115 Setting Up Robotic Library Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115 Configuring Multi-drive Robotic Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116 Installing the Library Expansion Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117 Starting Backup Exec After Installing the Library Expansion Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117 Viewing Robotic Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
33
Appendix L. Backup Exec Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . . 1121 How the Desktop and Laptop Option Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121 System Requirements for the Administration Console . . . . . . . . . . . . . . . . . . . . . . . 1124 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125 Media Server Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125 Server Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125 Authentication Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126 Using DLO with Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126 Configuring DLO to Use a Specific Port for Database Access . . . . . . . . . . . . . . . 1126 Excluding Files that are Always Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127 Using DLO with other Symantec Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128 Using Hidden Shares as Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128 Installing the Backup Exec Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . 1130 Updating DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131 Deploying the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133 Using the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134 Setting a Recovery Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135 Data Integrity Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135 Creating Administrator Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137 Connecting to DLO on a Backup Exec Media Server . . . . . . . . . . . . . . . . . . . . . . . 1141 The DLO Overview View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142 Setting Up DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145 Setting up a DLO Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146 Managing Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155 Creating DLO Storage Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 Setting up Automated User Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168 Configuring the Global Exclude List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174 Managing Desktop Agent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177 Managing Desktop Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184 Restoring Files and Folders from the DLO Administration Console . . . . . . . . . . . . 1186
Searching for Desktop Files to Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189 Deleting a Desktop Computer from DLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1191 Monitoring DLO Job Histories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192 Viewing the DLO Job History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192 Setting Job History View Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194 Monitoring Alerts on the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . 1200 Configuring Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204 Managing Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1205 DLO Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206 Viewing Report Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208 Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1209 Maintaining the DLO Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1210 Clustering the Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1210 DLO Command Line Interface Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213 DLO Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213 Commands in Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214 Using the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229 Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229 System Requirements for the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230 Using the Desktop Agent Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1230 Installing the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1233 Connecting to the media server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235 Using the Desktop Agent to Back Up Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238 Modifying Desktop Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1249 Synchronizing Desktop User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254 Viewing the Desktop Agent Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1259 Restoring Files Using the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264 Monitoring Job History in the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1269 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274 Troubleshooting the DLO Administration Console . . . . . . . . . . . . . . . . . . . . . . . . 1274
Troubleshooting the Desktop Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1278 DLO Administration Console Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281 Desktop Agent Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284 DLO History Log Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1290 Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293 Appendix M. Symantec Backup Exec - Agent for Oracle Server . . . . . . . . . . . . . . . . . 1297 Requirements for Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298 Backup Strategies for An Oracle Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298 Types of Oracle Database Data You Can Protect . . . . . . . . . . . . . . . . . . . . . . . . . . 1299 Requirements for Configuring the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300 Creating a New Oracle User Account for the Oracle Agent . . . . . . . . . . . . . . . . . 1301 Verifying ARCHIVELOG Mode and Automatic Archival Settings . . . . . . . . . . . 1302 Running Multiple Database Instances on a Single Server . . . . . . . . . . . . . . . . . . 1304 Using Fully Specified Paths for Oracle Data Files . . . . . . . . . . . . . . . . . . . . . . . . . 1305 Understanding the Oracle Agent Configuration Utility . . . . . . . . . . . . . . . . . . . . 1306 Installing the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307 Configuring the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308 Adding Media Servers to Use with the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . 1311 Backing Up Data Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312 Backing Up an Entire Online Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312 Backing Up Individual Online Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314 Backing Up a Closed Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315 Restoring the Oracle Database Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . 1316 Restoring an Online Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317 Restoring a Closed Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1318 Restoring Individual Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1319 Restoring the Database Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1320 Disaster Recovery Using the Oracle Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1321 Disaster Recovery Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1321
36
Recovering a Remote Oracle Database Server from a Disaster . . . . . . . . . . . . . . 1322 Recovering a Combination Oracle Database Server/Media Server . . . . . . . . . . . 1323 Oracle Agent Error Message Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324 Appendix N. Symantec Backup Exec - Agent for Lotus Domino . . . . . . . . . . . . . . . . 1327 Lotus Domino Agent Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328 Installing the Lotus Domino Agent on the Media Server . . . . . . . . . . . . . . . . . . . . . . 1329 Viewing and Selecting Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1330 Configuring Default Lotus Domino Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1332 Backing Up Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1332 Supported Lotus Domino Database Configurations . . . . . . . . . . . . . . . . . . . . . . . . 1333 Lotus Domino Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1333 Backup Options for Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335 Restoring Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337 Selecting Lotus Domino Databases for Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . 1338 Restore Options for Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1340 Redirecting Restore Jobs for Lotus Domino Databases . . . . . . . . . . . . . . . . . . . . . 1341 Preparing for Disaster Recovery on a Lotus Domino Server . . . . . . . . . . . . . . . . . . . 1343 Disaster Recovery of a Lotus Domino Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1343 Disaster Recovery of a Lotus Domino Server Using Archive Logging . . . . . . . . 1344 Disaster Recovery of a Lotus Domino Server Using Circular Logging . . . . . . . . 1345 Appendix O. Symantec Backup Exec - Agent for R/3 for Oracle Server . . . . . . . . . . . 1347 Backup Exec R/3 Agent Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1348 Backup Exec Alerts and the BACKINT Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349 Requirements for Backup Exec R/3 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1349 Installing the Backup Exec R/3 Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1350 Using the R/3 Agent to Back Up the R/3 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 1350 Specifying Backup Exec Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351 Backing Up the R/3 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1353 Restoring the R/3 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354
Disaster Recovery Using the Backup Exec R/3 Agent . . . . . . . . . . . . . . . . . . . . . . . . . 1354 Disaster Recovery Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355 Recovering a Remote R/3 Database Server from a Disaster . . . . . . . . . . . . . . . . 1355 Recovering a Combination R/3 Database Server/Media Server . . . . . . . . . . . . . 1356 Appendix P. Symantec Backup Exec - Agent for Microsoft SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359 Requirements for the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1359 Installing the SharePoint Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360 Using the SharePoint Agent with SharePoint Portal Server 2001 . . . . . . . . . . . . . . 1360 Backing Up SharePoint Portal Server 2001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1362 Backing Up the SharePoint Portal Server Database . . . . . . . . . . . . . . . . . . . . . . . 1362 Backing Up Folders and Documents from a SharePoint Portal Workspace . . . 1362 About Restoring SharePoint Portal Servers and SharePoint Portal Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364 Restoring a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364 Restoring a SharePoint Portal Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365 Restoring Previous Versions of Documents from Workspace Backups . . . . . . 1365 Redirecting SharePoint Portal Server Restore Jobs . . . . . . . . . . . . . . . . . . . . . . . 1366 Redirecting Restored Workspace Data to Another Workspace . . . . . . . . . . . . . 1368 Redirecting Restored Workspace Data to a File Path . . . . . . . . . . . . . . . . . . . . . . 1369 Disaster Recovery of a SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1370 Uninstalling and Reinstalling the SharePoint Portal Server Software . . . . . . . 1371 Best Practices for SharePoint Portal Server 2001 . . . . . . . . . . . . . . . . . . . . . . . . . 1371 Using the SharePoint Agent with SharePoint Portal Server 2003 . . . . . . . . . . . . . . 1372 Selecting SharePoint Portal Server 2003 Resources for Backup . . . . . . . . . . . . 1372 Adding a Server Farm to the Backup Selections List . . . . . . . . . . . . . . . . . . . . . . 1373 Disabling or Enabling Communication Between a Web Server and Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374 Changing the Name of a Farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375 Deleting a SharePoint Portal Farm from the Microsoft SharePoint Server Farms Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376
Backing Up SharePoint Portal Server 2003 Resources . . . . . . . . . . . . . . . . . . . . . 1376 Selecting SharePoint Portal Server 2003 Resources for Restore . . . . . . . . . . . . 1377 Restoring SharePoint Portal Sites, Services Sites, Document Library Stores, Configuration Databases, and Single Sign-on Databases . . . . . . . . . . . . . . . . . . . 1378 Restoring SharePoint Document Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1379 Restoring Previous Versions of Documents from Document Library Backups 1379 Redirecting a Restore Job for SharePoint Portal Server 2003 . . . . . . . . . . . . . . . 1381 Redirecting Restored Document Library Data to Another Document Library 1382 Redirecting Restored Document Library Data to a File Path . . . . . . . . . . . . . . . . 1383 Setting Default Options for SharePoint Portal Server 2003 . . . . . . . . . . . . . . . . 1384 Appendix Q. Symantec Backup Exec - Agent for Microsoft Data Protection Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1385 Requirements for the Agent for Microsoft Data Protection Manager . . . . . . . . . . . 1386 Backup Job with DPM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1386 Restore Job with DPM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1389 Appendix R. Symantec Backup Exec - Remote Agent for NetWare Servers . . . . . . . 1391 Requirements for Installing the Remote Agent on a NetWare Server . . . . . . . . . . . 1392 Installing the Remote Agent on a NetWare Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392 Adding NetWare Servers to the NetWare Agents List . . . . . . . . . . . . . . . . . . . . . . 1393 Adding BESTART to the AUTOEXEC.NCF File on the NetWare Server . . . . . . . 1393 Unloading the Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394 About Backing Up NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394 Backing up the NetWare Directory Services (NDS) . . . . . . . . . . . . . . . . . . . . . . . . 1396 Backing Up NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398 About Restoring NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1400 Restoring NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1400 Default Settings for the Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1402 Saving Configuration Information for the NetWare Server . . . . . . . . . . . . . . . . . . . 1404 Disaster Recovery of NetWare Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
39
Appendix S. Accessibility and Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407 Keyboard Navigation and Shortcuts in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . 1408 General Keyboard Navigation Within the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1408 Keyboard Navigation Within Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1409 Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1410 Support for Accessibility Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
40
Using Backup Exec Documentation

This comprehensive manual provides detailed information and procedures for using Symantec 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 capital letters. For example: ENTER, ESC, DELETE, etc. When two or more keys need to be pressed simultaneously to perform a function, they appear with a plus sign. For example: SHIFT + F1
41
Conventions
42
Chapter
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:
Symantec Backup ExecTM for Windows Servers
Installs on and protects any supported version of Microsoft Windows Server 2003, Windows 2000, and Windows XP Professional. Also includes Backup Exec agent software to protect unlimited remote workstations running on Windows XP Professional, Windows 2000 Professional, 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 Windows Server 2003, Windows 2000, NetWare servers, databases, open files, and more can be purchased separately.
43
Small Business Server
Installs on and protects Microsoft Small Business Server for Windows Server 2003 or Windows 2000, and Standard Edition operating systems. It includes the Backup Exec for Windows Servers Agent for Microsoft Exchange Server, Agent for Microsoft SQL Server, and Intelligent Disaster Recovery Option. You can purchase Small Business Server versions of the following options: Library Expansion Option, Advanced Open File Option, Desktop and Laptop Option, and the Remote Agent for Windows and NetWare Servers. With Small Business Server, the Remote Agent for Windows and NetWare Servers will only protect Windows servers; to protect NetWare servers or databases, you must upgrade to the Backup Exec for Windows Servers Edition. The Small Business Server Edition supports client workstations running Windows XP Professional, Windows 2000 Professional, Windows Me, and Windows 98. 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.
QuickStart Edition (OEM release only)
Installs on and protects any supported version of Microsoft Windows Server 2003 or Windows 2000. Also includes Backup Exec agent software for workstations running on Windows XP Professional, Windows 2000 Professional, Windows Me, 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.
Related Topics: Backup Exec Options on page 51
44
Whats New in Backup Exec
Whats New in Backup Exec

This release of Backup Exec includes the following new features and capabilities. For information about new features in the Backup Exec agents and options, see Whats New in Backup Exec Agents and Options on page 47.
Whats new in Backup Exec New Feature Policies Description Policies provide a method for managing backup jobs and strategies. Policies contain job templates, which are job attributes that define how and when Backup Exec processes a job. Templates specify the devices, settings, and schedule for a job, but do not include the selections to be backed up. To create jobs, combine a policy with a selection list. Backup Exec offers four types of templates: backup, duplicate backup data, export media, and synthetic backup (the Advanced Disk-based Backup Option is required to create synthetic backup templates). The Extensible Firmware Interface (EFI) is required to boot Windows on all Intel Itanium 64-bit computers. You can back up and restore EFI system partition data on remote Intel Itanium 64-bit computers. You can now set a time range for when resources in a selection list will be available for backup. You can set a default availability window for all selection lists, or set the availability window for each individual selection list you create. Create and edit custom filters for the current jobs view and the job history view to display only the information that you specify. These are filters that you name and save for later use so that you can sort large lists of objects depending on your specific criteria. If the Backup Exec services become unresponsive, you can set the threshold at which Backup Exec changes the status of active jobs to stalled and at which Backup Exec fails the jobs that were stalled and recovers them. Enables you to specify dates for media sets to send media to vaults. This feature enables you to update the vault with the media location, and generates a report so that you can physically collect the media and take it to or from a vault.
EFI system partition backup and restore
Availability windows for selection lists
Custom filters
Set thresholds for recovering stalled jobs
Vault rules
Chapter 1, Introducing Backup Exec
45
Whats New in Backup Exec Whats new in Backup Exec New Feature Backup Exec for Windows Server Environment Check Description This new utility runs before Backup Exec is installed and checks if the media server has the proper system environment (operating system version, service packs, etc.) and checks 3rd party application versions (Internet Explorer, ODBC, MDAC,etc.). Use audit logs to examine and review information about operations that have been performed in Backup Exec. The audit log displays the date and time of the activity, who performed it, the activity type, and a description of the activity. You can save audit logs as files, and groom audit logs as part of the Backup Exec database maintenance. In addition to applying a default error-handling rule to a group of similar errors, or an error category, you can now create a custom error-handling rule for one or more specific error codes in an error category. Errors that are reported in the job log each have a unique code, called a Unique Message Identifier (UMI). These codes contain hyperlinks that you can click to go to the Symantec Software Support Services web site and access technical notes and trouble-shooting steps that are related to a specific error. Unique Message Identifier (UMI) error code establishes unique error and message codes across all Symantec products.
Audit logs
Custom error-handling rules
Unique Message Identifier error codes
46
Whats New in Backup Exec Agents and Options
Whats New in Backup Exec Agents and Options

This release of Backup Exec includes the following new features and capabilities in the agents and options:
Whats new in Backup Exec agents and options Agent or Option New Feature
Backup Exec Continuous The new Symantec Backup ExecTM Continuous Protection Server (CPS) Protection Server software uses disk-based data protection to ensure that business-critical data is always protected and available. CPS integrates with Backup Exec for traditional tape-based data protection, and delivers integrated management via Backup Exec SmartLink technology. CPS reduces administration costs by allowing end-users to restore their own files through an intuitive web-based interface. Agent for Microsoft Data The new Symantec Backup Exec - Agent for Microsoft Data Protection Protection Manager Manager (DPM Agent) enables network administrators to perform backup and restore operations between Microsoft Data Protection Manager (DPM) and Backup Exec. Centralized Admin Server Option The new Backup Exec for Windows Servers Central Admin Server Option (CASO) enables you to maximize your Backup Exec for Windows Servers investment by providing centralized administration and job processing and load balancing functionality for Backup Exec for Windows Servers media servers in your storage environment. The Central Admin Server Option transforms your stand-alone Backup Exec media server-based environment into a centrally managed data protection enterprise, built on the following concepts:
Use of a Backup Exec for Windows Servers media server as a centralized administration server. Use of the central administration server to store catalogs, device and media information, policies, jobs, and selection lists. Job log information generated by the various Backup Exec media servers can also be stored on this central server. Use of existing storage hardware using job delegation concepts, which enable you to distribute the processing of backup and restore jobs to various Backup Exec media servers on your network. Use of a scalable architecture to handle the future growth of data on your network.
47
Whats New in Backup Exec Agents and Options Whats new in Backup Exec agents and options Agent or Option Remote Agent for Linux/Unix Servers New Feature The new Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers (RALUS) is installed as a separate, add-on component that enables Windows Server network administrators to perform backup and restore operations on major Linux and Unix hosts that are connected to the network. The following new features are available for IDR:
Intelligent Disaster Recovery
64-bit IDR. IDR is now available for remote, LAN-based computers that use Intel 64-bit Itanium processors. Alternate operating system media path. When you create bootable tape or CDs, you must provide the Windows operating system files. In previous releases of Backup Exec, IDR only accepted the Windows operating system installation CD. In this release, you can enter a path to the Windows operating system files on the network or to existing .iso image files. In addition, you can use MSDN-style CDs. Offline protection. If a computer crashes before you create disaster recovery media, IDR can still recover the computer if a full backup that includes information needed to restore the system was made prior to the crash. Support for VERITAS Storage Foundation for Windows. If you use VERITAS Storage Foundation for Windows on Windows 2003, IDR can restore the dynamic volumes. During backup, IDR gathers the components necessary to restore the dynamic volumes and adds them to the recovery media. Alternate location for storage of tape-based IDR image. You can now select the location where IDR stores the tape-based IDR image. Text file with partition information on IDR media. The bootable media now contains a text filed called <computer name>-diskconf.txt, which contains information about the computers hard disk layout.
SAN SSO SharePoint Agent
Plug-and-play tape driver support is now available. The SharePoint Agent now enables you to back up and restore SharePoint Portal Server 2003 resources. The SharePoint Agent version supports SharePoint server farms.
48
Whats New in Backup Exec Agents and Options Whats new in Backup Exec agents and options Agent or Option Advanced Disk-based Backup Option New Feature The Advanced Disk-based Backup Option (ADBO) provides the following features: Synthetic backup - Uses a policy to enable a full backup to be assembled, or synthesized, from a baseline and subsequent incremental backups that are also contained in a policy. Offhost backup - Enables the backup operation to be processed on a Backup Exec media server instead of on the remote computer, or host computer. Moving the processing associated with backups from the remote computer to a media server enables better backup performance and frees up bandwidth on the remote computer as well. Advanced Open File Option The Advanced Open File Option (AOFO) now enables the backup of multiple volumes in one job, while creating a snapshot of only one logical volume at a time. (A logical volume can comprise multiple physical volumes. A single logical volume can encompass all of the volumes on which databases reside.) After the logical volume is snapped and backed up, the snapshot is deleted before the next logical volume is snapped. This option increases the ability to meet the minimum quiet time needed to complete a snapshot. The Remote Agent for Windows Servers and the Remote Agent for NetWare Servers are now available as one add-on option instead of two separate options.
Remote Agent for Windows and NetWare Servers
Remote Agent for Use the Remote Agent for Windows Servers Monitor to check if a Windows Server Monitor backup or restore job is running on the computer. The Remote Agent Monitor is installed when the Remote Agent is installed on a remote Windows computer. You can set options for how often the Remote Agent Monitor checks for activity on the remote computer, to start the Remote Agent Monitor whenever you log on, to enable advertising from the Remote Agent to media servers, and to activate debug logging. SQL Agent The SQL Agent now supports the Microsoft Volume Shadow Copy Service (VSS) snapshot technology to create point-in-time, recovery consistent snapshots of SQL Server 2000 on Windows Server 2003. SQL Server 2000 snapshots can be created using the SQL Agent and the Advanced Open File Option (AOFO) for On-host local snapshots or the Advanced Disk-based Backup Option (ADBO) for Off-host transported snapshots. Using VSS snapshots in SQL reduces restore time.
49
Whats New in Backup Exec Agents and Options Whats new in Backup Exec agents and options Agent or Option Exchange Agent New Feature The Exchange Agent now supports the Microsoft Volume Shadow Copy Service (VSS) and the ExchangeVSS Writer snapshot technology to create point-in-time, recovery consistent snapshots of Exchange Server 2003 on Windows Server 2003. Exchange Server 2003 snapshots can be created using the Exchange Agent and the Advanced Open File Option (AOFO) for On-host local snapshots or the Advanced Disk-based Backup Option (ADBO) for Off-host transported snapshots. The Oracle Agent now supports some capabilities of Oracle Database Server version 10g. Users of Microsoft Operations Manager can proactively monitor and manage Backup Exec servers through the Microsoft Operations Manager Management Pack.
Oracle Agent
Microsoft Operations Manager Support
50
Backup Exec Options
Backup Exec Options

You can purchase the following options for your Backup Exec configuration:
Symantec 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 Symantec Backup Exec Library Expansion Option on page 1115. Symantec Backup Exec Advanced Open File Option ensures that all files on your network are protected even if they are being used. Whether used alone or in combination with specific database agents, this option handles open files at the volume level and is seamlessly integrated with Backup Exec. You do not need to know which files are open ahead of time; just set a scheduled backup to use this option. For more information, see on page 991. Symantec 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 by allowing you to restore from your last complete backup set - including full, incremental, differential and working set backups. For more information, see Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901. Symantec Backup Exec Agent for Microsoft Exchange Server provides a fast and flexible way of protecting your online Exchange 5.5 and Exchange 2000 and 2003 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 Symantec Backup Exec - Agent for Microsoft Exchange Server on page 1065. Symantec 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 with truncation. Redirected restores allow you to easily restore SQL data to other SQL servers on the network. For more information, see Symantec Backup Exec - Agent for Microsoft SQL Server on page 1013.
51
Backup Exec Options
Symantec Backup Exec Remote Agent for Windows or NetWare Servers
On Windows servers, the Remote Agent 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 Symantec Backup Exec - Remote Agent for Windows Servers on page 789. On NetWare servers, the Remote Agent 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. Data and special files on resources for a remote NetWare server can only be selected for backup with the Remote Agent is installed. In addition to backing up NetWare servers from your Windows media server, you get 100 percent SMS compatibility supporting the current versions of NetWare. You can set network defaults for all backup and restore operations performed on the NetWare servers by Backup Exec, including specifying a dynamic port range to be used by the Remote Agent. You can override these defaults each time you create a backup or restore job. For more information, see Symantec Backup Exec - Remote Agent for NetWare Servers on page 1391.
Symantec Backup Exec Agent for Oracle provides seamless online backup protection for Oracle Database Server versions 8.0.5, 8i-8.1.6, 9i, 10g, 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 Symantec Backup Exec Agent for Oracle Server on page 1297. Symantec 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 Symantec Backup Exec Agent for R/3 for Oracle Server on page 1347. Symantec 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 Symantec Backup Exec - Agent for Lotus Domino on page 1327. Symantec 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
52
Backup Exec Options
performance and backup speeds in the SAN environment, the Shared Storage Option load balances backup activity across multiple Backup Exec media servers and centralizes management tasks while lowering the total cost of hardware ownership. For more information, see Symantec Backup Exec - SAN Shared Storage Option on page 957.
Symantec Backup Exec - Agent for Microsoft SharePoint Portal Server protects all of the files and attributes associated with an installation of SharePoint Portal Server 2001 or 2003. Backup Exec, which offered the first complete backup and recovery solution for SharePoint Portal Server, 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 Symantec Backup Exec - Agent for Microsoft SharePoint Portal Server on page 1359. Symantec Backup Exec - ServerFree Option enables you to increase backup performance by making media server processor resources available and moving the backup processing operations to hardware solutions that may be installed in your storage area network. Use of this option requires Symantec Backup Exec Advanced Open File Option and Symantec Backup Exec SAN Shared Storage Option. For more information, see Symantec Backup Exec - ServerFree Option on page 981. Symantec Backup Exec - Desktop and Laptop Option enables you to protect all business data. It provides continuous backup protection whether users are in the office or on the road. Users can synchronize files between their desktop and laptop. For more information, see Backup Exec Desktop and Laptop Option on page 1121. Symantec Backup Exec - Central Admin Server Option enables you to maximize your Backup Exec for Windows Servers investment by providing centralized administration and load balanced job processing functionality for existing or newly configured Backup Exec for Windows Servers media servers. For more information, see Symantec Backup Exec - Central Admin Server Option on page 819. Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) enables the following types of backup:
Synthetic backup - This feature enables a backup to be assembled, or synthesized, from one previous full or incremental backup and subsequent incremental backups. This feature eliminates the need to run full backups, and because the synthesis is performed on the Backup Exec media server without accessing the remote computer, the overall backup window and the network bandwidth requirements are reduced. Offhost backup - This feature allows the backup operation to be moved away from the remote computer to a Backup Exec media server in a fiber connected SAN environment. Moving the backup from the remote computer to a media server enables better backup performance and frees the remote computer as well.
53
Backup Exec Options
For more information, see Symantec Backup Exec - Advanced Disk-based Backup Option on page 875.
Symantec Backup Exec for Windows Servers Remote Agent for Linux/Unix Servers (RALUS) enables Windows Server network administrators to perform backup and restore operations on Linux, Unix and Solaris workstations and servers that are connected to the network. This agent must be running on these computers before backup or restore operations can be performed. For more information, see Symantec Backup Exec - Remote Agent for Linux or Unix Servers on page 803. Symantec Backup Exec - Agent for Microsoft Data Protection Manager - enables network administrators to perform backup and restore operations between Microsoft Data Protection Manager (DPM) and Backup Exec. For more information, see Symantec Backup Exec - Agent for Microsoft Data Protection Manager on page 1385.
54
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 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.
55
Wizards guide you through most Backup Exec operations, including the creation of a backup or restore job, setting up media rotation jobs, and setting media overwrite protection. You can monitor a jobs progress through the Job Monitor, or use Backup Execs Calendar to quickly view all jobs scheduled to run for the day, week, or month. The media server contains media and device databases designed to simplify the process of organizing and allocating storage devices attached to your media server and to aid in preventing media from being accidentally overwritten. Through Backup Execs device management functions, you can logically group storage devices together in device pools. Through the media management function, you can organize, track, and troubleshoot all of the media in your library. You can define:

Overwrite protection periods to ensure that media is not accidentally overwritten. Set up automatic media labeling. View media statistics such as the medias age, hours of use, number of mounts, bytes written and read, and errors encountered, which are automatically tracked by Backup Exec.
After a job has been processed, the jobs results are stored in a job history database. A record of the data that was backed up is kept in Backup Execs catalog. The job history is a report of what happened during the processing of the job (statistics, errors, and so on), and the catalog file is the record from which restore selections are made.
56
Chapter
Installing Backup Exec
Backup Exec installation on the media server includes:
Running the Backup Exec Environment Check on the computer on which you are installing Backup Exec. The Environment Check analyzes the computer to make sure that the installation process can complete. If configuration issues are found that can be fixed by Backup Exec during the installation, or that may prevent the installation, warnings are displayed. 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. 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).
Microsoft SQL Server 2000 Desktop Engine (MSDE) Components Installed with Backup Exec
The Backup Exec installation program installs Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 3a components required to run Backup Exec. These include SQL Server 2000 core components, Microsoft Data Access Components (MDAC) 2.8, and Open Database Connectivity (ODBC) 3.0. With ODBC, the installation program installs and configures the base 32-bit ODBC administrator 3.0, including runtime dynamic link libraries (DLLs), and the ODBC driver for the Backup Exec catalogs.
57
Microsoft SQL Server 2000 Desktop Engine (MSDE) Components Installed with Backup Exec
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. Caution The MDAC version that Backup Exec installs as part of the MSDE 2000 installation is incompatible with a clustered version of Microsoft SQL Server 7.0. Do not install Backup Exec on a clustered version of SQL 7.0 server. If an existing SQL instance is detected, you will be prompted to do one of the following:

Install the required MSDE 2000 components with Backup Exec and create a default Backup Exec instance. Select a Microsoft SQL Server 2000 (with service pack 3a) instance that already exists on the network on which you want to run Backup Exec.
If you choose to install Backup Exec into an existing SQL 2000 instance, make sure that SQL 2000 Service Pack 3a or later is installed before you continue with the installation. When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. When Backup Exec is installed into an existing instance, the Cluster Configuration Wizard is not available. Note If you are installing a managed media server, it is recommended that you select a local Microsoft SQL Server 2000 (SP3a) instance on which to install the Backup Exec database for this managed media server. Do not select the same SQL Server instance that is used by the central administration server.
58
System Requirements
System Requirements
The following are the minimum system requirements for running this version of Backup Exec:
Minimum System Requirements Operating System Microsoft Windows 2000 Server family. Microsoft Windows Server 2003 family. Microsoft Windows XP Service Pack 1 or later. Microsoft Windows Storage Server 2003 Microsoft Small Business Server 2003 Standard and Premium Microsoft Small Business Server 2000 Internet Browser Processor Memory Internet Explorer 6.0 or later. Intel Pentium, Xeon, or compatible Required: 256 MB RAM Recommended: 512 MB RAM (or more for better performance). Note RAM requirements may vary depending on operations performed, the options installed, and the specific machine configuration. 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 2000, click Start, point to Settings, and then click Control Panel. Double-click System, click the Advanced tab, and then click Performance Options. Click Change to reset the paging file size for all drives. On Windows Server 2003 and Windows XP, go to Control Panel, double-click System, click the Advanced tab, and then in Performance, click Settings. Click the Advanced tab, and then in Virtual memory, click Change to reset the paging file size for all drives.
Disk Space
350 MB (Typical installation) 550 MB (Includes all options)
Note Disk space requirements may vary depending on operations performed, the options installed, and the specific system configuration. Backup Exec database and catalogs will require additional space.
Chapter 2, Installing Backup Exec
59
System Requirements Minimum System Requirements (continued) Other Hardware
(Recommended if remote activity is to be performed) Network interface card or a virtual network adapter card. CD-ROM drive. (Recommended) A mouse. (Optional for pager notification) Modem supported by Microsoft Windows. (Optional for printer notification) Printer supported by Microsoft Windows.
Storage Hardware
Backup Exec requires at least one storage media drive and/or single-drive 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 (http://support.veritas.com/rd/bews-compatibility.htm) for a complete list of devices that are supported. Support for a single robotic library drive is available when you purchase Backup Exec. To enable support for additional robotic library drives, you must purchase the Backup Exec Library Expansion Option.
60
Changing Windows Security

You can set up Windows security with the Backup Exec service account to protect your data. Depending on how the Windows network is configured, change security properties for the following scenarios:

Servers in one domain. Servers and selected workstations in one domain. Servers in more than one domain. Servers and workstations in more than one domain.
The following procedures give the Backup Exec service account administrative rights in the appropriate domains and workstations. You must grant the Backup Exec service account administrative rights to give Backup Exec access to the administrative shares (for example, C$) and the ability to protect the Windows registry.
For Windows 2000, use the Active Directory Users and Computers tool and Domain and Trusts tool in the Active Directory administrative tools group.
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. 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.
61
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. 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 (for example, Administrator) in the Local Administrators group.
62
The Backup Exec Environment Check

The Symantec Backup Exec for Windows Server Environment Check is a utility that you run on a computer and that reports the following:

If the computer meets the minimum requirements for installation, such as the operating system, disk and memory space, sufficient logon account privileges, etc. If third-party software that uses Backup Exec ports is configured correctly. If required components are installed, and if they are versions that are compatible with Backup Exec. If previous versions of Backup Exec and Backup Exec options are installed. If storage device hardware and associated drivers are properly installed and recognized by the Windows operating system.
For each item, the Environment Check reports if it passed the check, if additional configuration during the Backup Exec installation will be necessary, or if changes will be required before the Backup Exec installation can be successful. It is recommended that you run the Backup Exec Environment Check on a computer before you install Backup Exec. You can also run it at any time after installation to check the computers configuration. To run the Backup Exec Environment Check: 1. Insert the Backup Exec installation CD into a drive on the computer that you want to review. 2. From the installation CD browser, under Installation, click Backup Exec Environment Check. The Welcome screen for the Backup Exec Environment Check appears. 3. Click Next to start the check. The results that are reported for each item are:
Passed. There are no incompatibilities that will prevent the Backup Exec installation. For hardware, this result indicates that the hardware configuration is recognized by Backup Exec. Warning. An incompatibility with Backup Exec exists, but can be resolved during the Backup Exec installation. Failed. An incompatibility with Backup Exec exists, and it will cause the installation to fail. Some action is required before you can successfully install Backup Exec.
63
A final summary in the results window on the Backup Exec Environment Check lists recommended and required actions. You can print the results by clicking Print on the Environment Checks screen. The results are also saved to: C:\temp\VERITAS\EnvironmentChecks.html. 4. Click Finish to exit the wizard.
64

Note To make sure that the computer meets the minimum system requirements before installing Backup Exec, run the Backup Exec Environment Check. See The Backup Exec Environment Check on page 63. 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 Server 2003 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.
System Rights
65
Installing Backup Exec Minimum system requirements (continued) The Backup Exec Service Account All Backup Exec services on the media server run in the context of a user account configured for the Backup Exec system services. This account can be created during the Backup Exec installation, or an existing user account can be used. To create a service account for Backup Exec during installation, enter the name and password of an Administrator account for the Backup Exec services to use. If this computer is in a domain, enter a Domain Administrators account, or an equivalent account that is part of the Domain Admins group. In the Domain list, select or enter the Domain name. If this computer is in a workgroup, enter an Administrators account, or an equivalent account that is part of the Administrators group on the computer. In the Domain list, select or enter the computer name. The account designated for Backup Exec 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." On a computer running Windows Server 2003 or Windows XP, you cannot install Backup Exec using a service account that has a blank password. If you attempt to do so, the following error message displays when Backup Exec services are created: "The given password is not correct for account [server]\[username]." You can configure Windows to allow for blank passwords. For more information, see your Windows documentation.
Related Topics: Installing Backup Exec Using the Installation Program on page 67 Installing Backup Exec Using the Command Line (Silent Mode) on page 81
66
Installing Backup Exec Using the Installation Program

The Backup Exec CD includes an installation program that guides you through the installation process. Note 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 it using a UNC path. Installation via mapped drives is not supported in this situation. To install Backup Exec using the installation program: 1. From the installation CD browser, select the option to install Symantec Backup Exec. The Welcome window appears. 2. Click Next to continue 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, and then continue with step 5. To install the Administration Console as a Remote Administrator, select Install Remote Administration Console only, and then go to step 4 in Installing the Backup Exec Remote Administrator on page 95 for further instructions. To install Backup Exec, Backup Exec options, and Backup Exec remote agents to remote computers, select Remote Install. If you are not also performing a local install, clear the check box for Local Install.
To install Backup Exec media servers and options to remote computers, go to Installing Backup Exec to Remote Computers on page 73 for further instructions. To install the Backup Exec Remote Agent for Windows Servers, the Advanced Open File Option, or the Desktop and Laptop Agent to remote computers, or to install the Backup Exec NetWare Agent to remote NetWare servers, go to Installing Backup Exec Agents to Remote Computers on page 77 for further instructions.
5. Click Next. The Symantec Backup Exec Serial Numbers dialog box appears.
67
If you are upgrading from a previous version of Backup Exec, see Upgrading from Previous Versions of Backup Exec on page 104. 6. You can type 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 a previous installation of Backup Exec 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 an Evaluation version, click Next without entering serial number information. Installing an Evaluation version 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 Microsoft Cluster Server on page 660. 7. Review the local features to be installed. You can also select additional features that are available for install when you enter a Backup Exec for Windows Servers serial number. These additional features are:
Copy Server Configurations - Enables you to copy server configurations, logon account information, jobs, policies, and selection lists to remote media servers. You cannot select this feature if you entered a CASO serial number. Tivoli Storage Manager Option - This 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. For more information, see Symantec Backup Exec - Tivoli Storage Manager on page 771.
68
Create Clone CD - A clone CD image captures the Backup Exec installation program and your installation settings, such as account information, additional options, and destination directory. After the CD image has been created, it can be copied to a CD. You can then use that CD to install Backup Exec on additional servers using the same settings. For more information, see Installing Locally Using a Clone CD Image on page 99. Managed Media Server - Makes a standalone media server into a managed media server that is controlled by the central administration server. You cannot select this feature if you entered a CASO serial number.
These features are not selected for install by default, so if you want to use them, you must select them. All features that are not to be installed have a red "X" displayed in the feature icon. To enable any of these options, click the 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. Note Selecting a mount point as the destination directory is not recommended because the mount point is deleted if Backup Exec is uninstalled. 9. Provide a user name and password that the Backup Exec system services can use (see The Backup Exec Service Account on page 66), and then click Next. The Symantec Backup Exec Database dialog box appears, and you are prompted to select a location on which to store the Backup Exec database. 10. Do one of the following:
Choose to create a local Backup Exec MSDE instance on which to store the Backup Exec database, and then click Next. For more information about creating a local Backup Exec MSDE instance, see Microsoft SQL Server 2000 Desktop Engine (MSDE) Components Installed with Backup Exec on page 57. Choose to use an existing SQL Server 2000 instance (with service pack 3a installed) that is on the network. You are prompted to select an instance from a list, or to type the instance name, and then click Next. Backup Exec will attempt to connect to the instance.
69
Note When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. When Backup Exec is installed into an existing instance, the Cluster Configuration Wizard is not available. 11. If prompted, select how the VERITAS Device Driver Installer should install device drivers for the tape storage devices that are connected to the server, and then click Next. It is recommended that you select Use VERITAS device drivers for all tape devices. 12. If you are prompted, enter information or choose settings for additional options being installed. Click Next after each selection. 13. Read the Backup Exec installation review, and then click Install. The MSDE 2000 (if selected), VERITAS Update, and Backup Exec program files are installed. 14. When the installation is complete, you can 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. 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. The last line of the log indicates if the installation was successful and if restarting the computer is required. After installing Backup Exec on the media server, Backup Exec Workstation Agent software can be installed and configured on remote workstations on the network. Related Topics: Getting Started on page 107
70
Installing Backup Exec Options to the Local Computer

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 on page 65. 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) edition, you can install evaluation versions of the additional options. Note 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. The Backup Exec services are stopped while the additional options are installed. If any active jobs are running, you are prompted to stop them, or to wait for the jobs to finish. Note If the Central Admin Server Option is installed, and you want to install additional options on a managed media server, you can pause the managed media server to disable the central administration server from delegating jobs to it. When the installation is complete, un-pause, or resume, the managed media server. For more information see Pausing and Resuming a Managed Media Server on page 848. To install Backup Exec options 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. 3. Review the Welcome window, and then click Next . 4. Type the serial number for the option you want to install, and then click Add. To import the serial number from an existing besernum.xml file, click Import. If a previous installation of a Backup Exec for Windows Servers option 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 a fully functional Evaluation version. 5. Click Next, and review the local features to be installed.
71
6. To accept the local features for installation, and to accept the default Destination Folder for the option, click Next. To select another destination folder for the Backup Exec options, click Change, and follow the prompts. All options that are not to be installed have a red "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. The Backup Exec services are stopped while the additional options are installed. If any active jobs are running, you are prompted to stop them, or to wait for the jobs to finish. When the installation is complete, the services are restarted. 9. Click Finish. Related Topics: Installing Backup Exec to Remote Computers on page 73 Installing Backup Exec Agents to Remote Computers on page 77
72
Installing Backup Exec to Remote Computers

To install Backup Exec to a remote computer, you must have one of the following installed on the local media server:

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. 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. 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 Symantec 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 on the local computer, on the Tools menu, click Serial Numbers and Installation. Click Next when the Welcome window appears.
2. To install Backup Exec media servers and options to remote computers, select Remote Install, and then click Next. 3. Right-click Backup Exec Servers and then do one of the following:

Click Add Remote Computer, and then browse the list to select all of the remote computers that you want to install an option to, and then click Next. Click Add Remote Computer Manually, and then type the Domain and Computer Name, and then click OK. Add as many remote computers as you want to install Backup Exec to.
4. Type the user name, password, and domain credentials of an account that has administrative rights on the remote computers, and then click OK. Note To avoid entering credentials separately for each remote computer that you have selected, click Use this user name and password when attempting to connect to additional computers during the installation.
Chapter 2, Installing Backup Exec 73
5. Select one of the following options, and then click Next:
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 Backup Exec for Windows Servers to a remote computer, then you are prompted to select a destination folder. You can accept the default destination folder on the remote computer, or make changes. After selecting this option, continue with step 6 on page 74.
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 14 on page 76.
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 89). When this option is selected, you can browse to a parameter file. After selecting this option, continue with step 14 on page 76.
6. On the Destination Folder dialog box, enter the folder to which the Backup Exec media server files on the remote computer will be installed, and then click OK. The default location is C:\Program Files\VERITAS\Backup Exec\NT. 7. Type the serial numbers for Backup Exec and any options that you want to install. Click Add after entering each serial number. When finished, click Next. To import the serial numbers from an existing besernum.xml file, click Import, and then browse for and select an existing besernum.xml file. When finished, click Next. The serial numbers you entered are saved to the file besernum.xml, located in the Windows directory. Note A unique serial number must be entered for each option for each remote computer that you are installing to.
74
If a previous installation of a Backup Exec 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 a fully functional Evaluation version. 8. Provide a user name and password that the Backup Exec system services can use (see The Backup Exec Service Account on page 66), and then click Next. 9. You are prompted to select a location on which to store the Backup Exec database. Do one of the following:
Choose to create a local Backup Exec MSDE instance on which to store the Backup Exec database, and then click OK. For more information, see Microsoft SQL Server 2000 Desktop Engine (MSDE) Components Installed with Backup Exec on page 57. Choose to use an existing Microsoft SQL Server 2000 instance (with service pack 3a installed) that is on the network. You are prompted to select an instance from a list, or to type the instance name, and then click OK. Backup Exec will attempt to connect to the instance.
Note When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. When Backup Exec is installed into an existing instance, the Cluster Configuration Wizard is not available. 10. You are prompted to install device drivers for tape storage devices that are connected to the server. You can only click OK, and continue with the installation. After Backup Exec is installed, you can install device drivers for the tape storage devices. See step 20. The Remote Installation Status dialog box appears, and selected options are installed on the remote computer. If the remote computer needs to be restarted, the installation status column displays the message that a reboot is required. 11. If you are prompted, enter information or choose settings for additional options being installed. Click Next or OK after each selection. 12. Review the features to be installed, and then click Next.
All options that are not to be installed have an "X" displayed in the feature icon. To enable any of these options, click the icon to clear the X, and then follow the prompts to install it. If the feature icon is gray, the option is not available for change. 13. Read the Backup Exec installation review, and then click Install. When Backup Exec is being installed to a remote computer, if the Microsoft Data Access Components (MDAC) version on the remote computer needs to be updated to the version that ships with Backup Exec (MDAC v2.8), you are prompted to restart the remote computer. Go to step 14. If the MDAC version does not need to be updated, continue with step 9. For more information on the MDAC version that is installed with Backup Exec, see Microsoft SQL Server 2000 Desktop Engine (MSDE) Components Installed with Backup Exec on page 57. 14. If the MDAC version on the remote computer must be updated, restart the remote computer. Right-click the computer name, and then click Reboot Computer. 15. After the computer has restarted, right-click the computer name and select the Retry Install option. Verify the credentials when prompted. 16. To restart the remote computer now, on the Remote Installation Status dialog box, right-click the server name, and then click Reboot Computer. You can also wait, and restart the remote computer after you exit the installation wizard. The installation status column displays the message that the computer is rebooting. 17. When the installation status indicates that the reboot is 100% complete, right-click the server name again, and click View Install Log or View Push Log. An installation job log named bkupinst.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. The last line of the log indicates if the installation was successful and if restarting the computer is required. 18. Exit the log, and then on the installation wizard, click Next, and then click Finish to exit the wizard. 19. If you did not restart the remote computer, you may need to do it now in order for the configuration to take effect. 20. (Optional) To install device drivers for the tape storage devices that are connected to the server, do the following:
76
a.
Using either the First Time Wizard, or the Device Configuration Wizard, on the Detected Hardware page, click Configure Devices.
b. On the Device and Resource Management for Windows 2000 screen, click the button to install VERITAS device drivers. c. On the VERITAS Device Driver Installation Welcome page, click Next.
d. Choose an option to install tape drivers. It is recommended that you select Use VERITAS device drivers for all tape devices. For more information, see Configuring Devices on page 128.
Installing Backup Exec Agents to Remote Computers

You can install the following to remote computers:

Backup Exec for Windows Servers (see Installing Backup Exec to Remote Computers on page 73) Remote Agent for Windows or NetWare Servers Advanced Open File Option (AOFO) Desktop and Laptop Option (DLO) Desktop Agent Backup Exec DPM Agent
These features are push-installed to remote computers from a media server. Push installations save time by eliminating the need for local access at the target computer for the installation to be successful. You can also push-install the Remote Agent for Windows Servers and the AOFO using the command line. See Push-Installing the Remote Agent for Windows Servers and the Advanced Open File Option Using the Command Line on page 87. Note Before installing the Advanced Open File Option to a remote computer, enable the remote registry. Make sure that the logon account that is used has permissions to modify remote servers registries. You cannot push-install the Backup Exec Remote Agent for Windows Servers to a remote Windows XP Professional computer when the operating system on the remote computer is in the ForceGuest configuration and the remote computer is not in a domain. ForceGuest is a configuration that limits incoming users to Guest-level access. Instead,
77
you must locally install the Remote Agent on the Windows XP computer by using the installation CD, or over the network by following the procedure in Installing Backup Exec Using the Command Line (Silent Mode) on page 81. You cannot push install the 64-bit version of the Remote Agent for Windows Servers. Note If you are installing Backup Exec agents and options through Terminal Services and the installation media is on a shared drive (CD-ROM or network share) you must install using a UNC path. Installation via mapped drives is not supported. To install a Backup Exec agent or option to a remote computer: 1. Do one of the following:
If Backup Exec is already installed on the local computer, on the Tools menu, click Install Remote Agents. Click Next when the Welcome window appears. Then proceed to step 2. If you are installing Backup Exec for the first time from the installation CD browser: Select the option to install Symantec Backup Exec, and then when prompted, click Next to proceed with the installation.
a.
b. Select I accept the terms of the license agreement, and then click Next. c. To install Backup Exec remote agents and options to remote computers, select Remote Install, and then click Next. If you do not need to install any Backup Exec options to the local computer, clear the Local Install selection.
2. Right-click Windows Remote Agents or NetWare Remote Agent to display a menu for selecting the remote computer or computers that you want to install to:
Windows Remote Agents. Enables you to install the Backup Exec Remote Agent for Windows Servers, the Advanced Open File Option, and the Desktop and Laptop Options Desktop Agent to a remote computer. NetWare Remote Agents. Enables you to install the Backup Exec Remote Agent for NetWare Servers to a remote NetWare server.
3.
On the right-click menu, do one of the following:

Click Add Remote Computer, and then browse the list to select all of the remote computers that you want to install an option to, and then click Next. Click Add Remote Computer Manually, and then type the Domain and Computer Name, and then click OK.
78
Add as many remote computers as you want to install the option to. 4. Type the user name, password, and domain credentials of an account that has administrative rights on the remote computers, and then click OK. Note To avoid entering credentials separately for each remote computer that you have selected, click Use this user name and password when attempting to connect to additional computers during the installation. 5. In the Features pane, click the selection box next to the option that you want to install, and then select This feature will be installed on <server names> hard drive. All features that are not to be installed have an "X" displayed in the feature icon. To enable any of these options, click the icon to clear the X, and then follow the prompts to install it. If the feature icon is gray, the option is not available for change. If you are installing the Remote Agent for Windows or NetWare Servers, continue with step 6; otherwise, go to step 8. 6. When the Enable Network Backups (Optional) dialog box appears, select the appropriate options as follows:
Enable Network Backups (Optional) dialog box Item Enhance backups run over the network for <server name> Description Click this check box to direct primary backup traffic generated by Backup Exec to a specific local network. Then specify the media server that will use an alternate network in the Media server name or IP address field. For each media server that you enter, you can specify a local network for traffic generated by backup and restore jobs when operations are performed between the media server and the remote computer on which the Remote Agent is installed. For more information, see Specifying Default Backup Network and Firewall Options on page 336. Media server name or IP address Type the name or IP address of a media server that will use an alternate network to back up the computer on which the Remote Agent is installed. After entering a media server name or IP address, click Add to enter the media server on the displayed list. To change a media server name or IP address, select the media server in the displayed list, and then click Edit.
Add
Edit
79
Installing Backup Exec to Remote Computers Enable Network Backups (Optional) dialog box (continued) Item Remove Description To delete a media server name or IP address from the list of media servers to advertise to, select the media server in the displayed list, and then click Remove.
To bypass this dialog box and continue with the installation, click OK. If you skip this dialog box, you can add media server names or IP addresses later by using the Remote Agent Monitor on the remote computer. For more information, see Enable Advertising for the Remote Agent for Windows Servers on page 800. 7. Click Next. 8. Read the installation review, and then click Install. The Remote Installation Status dialog box appears, and selected options are installed on the remote computer. 9. When the installation status indicates that the reboot is complete, right-click the server name again, and click View Install Log or View Push Log. 10. 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. 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. The last line of the log indicates if the installation was successful and if restarting the computer is required. Note If there are problems installing the Backup Exec Remote Agent using this method, you can try to manually install the Remote Agent (see Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line on page 794.) 11. Exit the log, and then on the installation wizard, click Next, and then click Finish to exit the wizard. 12. If you did not restart the remote computer, you may need to do it now in order for the configuration to take effect.
80
Installing Backup Exec Using the Command Line (Silent Mode)

Installing Backup Exec using the command line is referred to as Silent Mode Installation. This method of installation uses the setup.exe program on the Backup Exec CD, a series of command switches, and the -S switch. 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 using the command line: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL\BE. 4. 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 82. 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. The last line of the log indicates if the installation was successful and if restarting the computer is required.
81
Command Line Switches for Backup Exec Silent Mode Installation

The command line switches used for silent mode installation of Backup Exec are described in the following table. Note the following general rules for using these switches:

Substitute values appropriate for your environment for values shown in italics; for example substitute your password for password. Enclose the value in quotation marks if it contains spaces, such as Operations Weekly Backup.
Note Additional switches appearing in BOLD are required.

Command Line Switches for Silent Mode Installation of Backup Exec Switch /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" Required. Specifies an existing user, domain, and password for the Backup Exec system service account. Silent mode installation will not create a user. Note When using /PASS:, if a quote is needed as part of the password, specify it as \". For example, if the password is pass"word, type it as /PASS:pass\"word. If the characters \" are used as part of the password, you must precede each character with a \. For example, if the password is pass\"word, type it as /PASS:pass\\\"word. /DEST:"path" Specifies the path where Backup Exec will be installed. Otherwise, the default path Program Files\VERITAS\Backup Exec\NT is used. Installs online documentation.
/DOCS:
82
Installing Backup Exec to Remote Computers Command Line Switches for Silent Mode Installation of Backup Exec (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 in conjunction with the /CPF: or /XML: switches. 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. /DBSERVER:<server\instance> Installs the Backup Exec database to the specified SQL server. /NOVUPDATE: Skips the installation of VERITAS Update.
/SNO:serial number
/XML:"file name"
83
Installing Backup Exec to Remote Computers Command Line Switches for Silent Mode Installation of Backup Exec (continued) Switch Additional Switches Description
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. 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 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 Remote Agent for NetWare Servers. Installs the ServerFree Option.
/R3:
/OFO: /TSM:IP address:port /SSO:
/SSO:server name
/SHAREPT:
/EXCH:
/LOTUS: /ORACLE: /SQL:
/NTA:
/NWA:
/SVRFREE:
84
Installing Backup Exec to Remote Computers Command Line Switches for Silent Mode Installation of Backup Exec (continued) Switch Additional Switches /BEWSA: Description Installs the Backup Exec Web Administration Console. Installs the Backup Exec Desktop and Laptop Option. Installs the Advanced Disk-based Backup Option. Installs the Central Admin Server Option Creates a managed media server for use with the Central Admin Server Option.
/DLO:
/ADBO:
/CASO: /MMS:<CAS server name>
Related Topics: Push-Installing the Remote Agent for Windows Servers and the Advanced Open File Option Using the Command Line on page 87
Installing the Remote Administrator Using the Command Line

You can also use Silent Mode Installation to install the Remote Administrator. Options for the Remote Administrator are specified with the use of additional command switches. To install the Remote Administrator using the command line: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL\BE 4. Type setup /RA: and the appropriate switches. For example: setup /RA: -s The command line switches used for silent mode installation of the Remote Administrator are described in the following table. Remember the following general rules for using these switches:
Substitute values appropriate for your environment for values in italics; for example, substitute your password for password.
85
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. 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.
/DOCS: /NOINSTALL:
/CPF:"file name"
/XML:"file name"
86
Push-Installing the Remote Agent for Windows Servers and the Advanced Open File Option Using the Command Line
You can use silent mode installation, also known as command line installation, to push-install the Backup Exec Remote Agent for Windows Servers and the Advanced Open File Option (AOFO) to one or more remote computers. You can also push-install the Remote Agent and the AOFO to more than one remote computer at a time by creating a command file that reads the remote computer names from a .txt file. To push-install the Remote Agent or AOFO using the command line: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL\BE. 4. To use a command file to read a list of remote computers to install to, go to step 6; otherwise, continue with step 5. 5. Type one of the following:
To install the Remote Agent, type: SETUP /PUSHRAWS: /USER:<user> /DOM:domain /PASS:password /SVR:<server name> -S
To install the Advanced Open File Option, type: SETUP /PUSHRAWS: /USER:<user> /DOM:domain /PASS:password /SVR:<server name> /AOFO: -boot -S
For the switch /SVR:, type the name of the remote computer that you want to install to. For descriptions of the other switches, see Command Line Switches for Backup Exec Silent Mode Installation on page 82. 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. 6. (Optional) To install the Remote Agent or the AOFO using a command file that reads server names from a .txt file, use the following sample script, substituting the correct values for the variables:
87
for /f %%I in <ServerList.txt> do call :sub1 %%I goto :eof :sub1 Echo Pushing to %1 call ..\BE\setup.exe /PUSHRAWS: /DOM:DOMAIN /USER:administrator /PASS:password /SVR:%1 -S if "%errorlevel%" == "0" goto :good echo %1 failed with error %errorlevel% goto :eof :good echo %1 completed successful goto :eof 7. Press ENTER. 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. The last line of the log indicates if the installation was successful and if restarting the computer is required.
Uninstalling Backup Exec Using the Command Line

If Backup Exec is already installed, you can use the setup.exe program to uninstall Backup Exec program files and Backup Exec data. To uninstall Backup Exec using the command line: 1. Open a Windows command prompt. 2. Change to the drive containing the Backup Exec CD. 3. Change directories to \WINNT\INSTALL\BE. 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
88
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\BE. 4. Type setup /TS: and the appropriate switches, including /CPF: and the full path name of the parameter file. For example, type: setup /TS: /USER:user /DOM:domain /PASS:password /SNO: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\BE. 4. Type: SETUP /PARAMS:"A:\file name" -S
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 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. Related Topics: Installing Backup Exec Using the Command Line (Silent Mode) on page 81 Command Line Switches for Backup Exec Silent Mode Installation on page 82
Registering Backup Exec Online

Start the Symantec 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 Symantec Backup Exec. 2. Follow the wizard prompts. The Online Registration Wizard guides you through submitting a registration form to Symantec Corporation and provides a survey designed to aid Symantec in understanding how you use the product and in better understanding your needs. Note If your LAN uses a proxy server to connect to the Internet, the online registration may fail with the error "Logon request was denied". To correct this error, change the LAN settings to automatically detect the proxy settings. Refer to your web browser documentation for details on how to change the LAN settings.
90
Repairing Backup Exec
Repairing Backup Exec

If you have missing or corrupted Backup Exec files or registry keys on the local media server, run the Repair option. The program stops all Backup Exec services, reinstalls corrupted files and registry keys, reinstalls tape devices (stand-alone drives and libraries), and restarts the services. The database is not reinstalled. Any changes made to Backup Exec program files and registry keys will be reset to the original settings. To run the Repair option: 1. Close the Backup Exec application. 2. Click Start, point to Settings, click Control Panel, and then double-click Add or Remove Programs. 3. At the Add or Remove Programs dialog box, select Symantec Backup Exec for Windows Servers, and then click Change. 4. On the Welcome screen, 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.
91
Starting and Stopping Backup Exec Services
Starting and Stopping Backup Exec Services

To stop or start Backup Exec services: 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 stop all Backup Exec services and then restart the services for the selected server. Click this to change service account information or to change startup options. Click this to refresh this dialog box. Click this to remove a selected server or servers from the server list.
Start all services Stop all services Restart all services
Services credentials
Refresh Remove Servers
92
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. At the Add/Remove Programs dialog box, select Symantec Backup Exec for Windows Servers, and then click Remove. 4. When prompted to confirm the deletion of Backup Exec from your computer, click Yes. 5. When prompted to remove 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 Symantec tape class drivers. If you reinstall Backup Exec and want to use Symantec tape class drivers, you must reinstall them. Related Topics: Push-Installing the Remote Agent for Windows Servers and the Advanced Open File Option Using the Command Line on page 87
93
Uninstalling Backup Exec Options from the Local Media Server

The install wizard is used to uninstall Backup Exec options from the local media server. To uninstall Backup Exec options: 1. From the Tools menu, click Serial Numbers and Installation. 2. At the Welcome screen, click Next. 3. On the Backup Exec Serial Numbers dialog box, select the serial number of the option that you want to uninstall, and then click Remove. 4. On the Backup Exec Local Features dialog box, click the icon next to the option, and select This feature will not be available, and then click Next. An "X" will be displayed in the feature icon. 5. On the Installation Review dialog box, click Next, and then click Install to start the process. 6. When the install wizard has completed, click Finish. Corresponding files, registry keys, and configuration will be uninstalled.
94
Installing the Backup Exec Remote Administrator

The Backup Exec Remote Administrator allows you to administer the media server from a remote Windows server or workstation. To remotely administer both Backup Exec 9.1 and 10.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 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, select the option to install Symantec Backup Exec. The Welcome window appears. 2. Click Next to continue with the installation. The License Agreement appears. 3. Select I accept the terms of the license agreement, and then click Next. 4. To install the Administration Console as a Remote Administrator, select Install Remote Administration Console only, and then click Next. The Destination Folder dialog box appears. 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 107. To run the Remote Administrator: 1. Click Start. 2. Point to Programs, and then click Symantec 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 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. Logon Information User name Type an administrator user name for the server to which you are connecting. Note On Windows Server 2003 and Windows XP, you cannot log on to the remote administration console with a user name that has a blank password, unless you set Windows to allow blank passwords. The error message "Logon failure: user account restriction" displays. For more information, see your Windows documentation. Password Domain Type the password. From the drop-down list, select the domain to which the user belongs, or type the appropriate domain name if it does not appear in the list.
96
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.
The status of the local services appear at the bottom of this dialog box. If you try to connect to a server and the connection fails, this dialog box displays the services status for the server you attempted to connect to. 4. Click OK. The Administration Console connects to the services running on the media server. You should now be able to operate the media server as though you were running the Administration Console from there. You may be prompted for a user name and password to browse some network shares even if you are logged into the Remote Administrator computer under an account that is valid for those shares. Provide a domain-qualified user name and password when prompted (for example, domain1\howard). For workgroup accounts, when logging in between different workgroups, you can provide only a user ID when prompted, and leave the workgroup line blank.
97
Using a Clone CD Image

A clone CD image captures the Backup Exec installation program and your installation settings, such as account information, additional options, and destination directory. After the CD image has been created, it can be copied to a CD. You can then use that CD to install Backup Exec on additional servers using the same settings. The clone CD image is not removed from your system when Backup Exec is uninstalled.
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 65. You must use the Backup Exec installation CD or a copy of the CD when creating the clone CD image for the first time. A downloaded version of Backup Exec does not have the same directory layout as the installation CD, and, therefore, cannot be used to create a clone CD image. 2. When the list of features being installed appears, select Create Clone CD. 3. Click Next and continue with the installation procedures. 4. When the Create Clone CD Image dialog box appears, ensure the directory listed is the directory where you want the clone CD image file copied. If the location is not correct, click Change and browse to select the correct location. The directory to which the clone CD image file will be copied should be an empty directory. 5. Click Next and continue with the installation procedures. 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.
98
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. Because the installation parameters, or options, have already been captured in the clone CD image, you will not be prompted for these options.
Installing to a Remote System Using a Clone CD Image

To install remotely using a clone CD image: 1. Begin the Backup Exec installation procedures as described in Installing Backup Exec on page 65. 2. Add the remote systems to which you are installing.
Remote install options
99
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 89). 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.
100
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 Symantec web server for any available updates. VERITAS Update can be polled on a daily, weekly, or monthly interval, and you can configure when the polling will start. If updates are available, VERITAS Update alerts you so you can download and install any selected updates. Note To quickly view any hot fixes or service packs that are installed on the media server, see Viewing Installed Updates on page 102. VERITAS Update cannot be used if the security setting for Internet Explorer is set to high. To set Internet Explorer security: 1. On the Internet Explorer Tools menu, click Internet Options, and then click the Security tab. 2. Click the Internet icon, and then click Custom Level. 3. Set the security to medium or lower. 4. Verify that the following settings are set to Enable or Prompt

Download signed ActiveX Controls Run ActiveX Controls and plug-ins Script ActiveX Controls marked safe for scripting Active scripting
To configure VERITAS Update: 1. On the Tools menu, click VERITAS Update. 2. On the VERITAS Update Welcome screen, click Configure. 3. Click Notify 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:
101
Viewing Installed Updates

Daily. Backup Exec polls every day at the time you selected. Weekly. Backup Exec polls every week on the same day of the week and at the same time you selected. Monthly. Backup Exec polls every month on the same date and at the same time you selected.
6. Enter Local Task Credentials. 7. Click Apply.
Viewing Installed Updates

You can view hot fixes and service packs that are installed on a media server without using VERITAS Update. You must be logged on with administrator privileges. To review installed updates: 1. After installing Backup Exec and completing the First Time Startup Wizard, on the menu bar, click Help. 2. Click About Symantec Backup Exec for Windows Servers, and then click the button Installed Updates. The Installed Updates window appears. If a hot fix is installed prior to a service pack, that hot fix is no longer displayed as installed since the service pack contains the hot fix. A hot fix offered after the service pack is released is displayed with the prior service pack. Service packs and hot fixes cannot be uninstalled. 3. To install hot fixes and service packs, Click Click here for VERITAS Update. 4. Click Next. The update should complete successfully. You will be advised if a reboot is necessary.
102
Viewing License Information
Viewing License Information

To review license information:
On the Help menu, click About Symantec Backup Exec for Windows Servers, and then click the button License Information. The License Information dialog box provides the following information:
License Information dialog box options Item Option Licensed Description Name of the available Backup Exec options. Displays Yes if the option is licensed on the media server, and No if the option is not licensed. Displays Yes if the option is installed on the media server, and No if the option is not installed. If the option is installed, it may still require some additional configuration.
Installed
103
Upgrading from Previous Versions of Backup Exec
Upgrading from Previous Versions of Backup Exec

This version of Backup Exec for Windows Servers replaces any previous versions; no separate migration or upgrade utility is necessary. Most settings and all catalogs and data directories from previous versions of Backup Exec are kept (for example, when the TSM option adds registry settings). At the end of the installation, the upgrade process is summarized. Only Backup Exec version 8.0 and later can be migrated to this release. The new version of Backup Exec for Windows Servers (including the Evaluation version) will replace any current installation. Separate installations of different versions cannot exist on the same computer. For information on migrating templates from Backup Exec version 9.0 and 9.1, see Migrating Templates from Previous Versions of Backup Exec on page 367. For information on upgrading from Symantec Network Storage Executive (NSE), see Migrating from Network Storage Executive v8.6 (NSE) on page 838. Before upgrading Backup Exec, do the following:

Delete job histories and catalogs that you no longer need in order to shorten the upgrade window. Run a database maintenance job
To upgrade from Backup Exec version 8.0 or later: 1. Perform steps 1 through 5 in the topic Installing Backup Exec Using the Installation Program on page 67. 2. Enter serial numbers for Backup Exec, and for each Backup Exec option that you want to install, and then click Next. Read the Installation Review. To add additional serial numbers, click Back until the Symantec Backup Exec Serial Numbers page is displayed. Enter the serial numbers, and then click Next to continue. The default location is C:\Program Files\VERITAS\Backup Exec\NT. 3. On the Back Up Existing Catalog and Data page, enter or browse to a directory to which all existing catalogs and data will be backed up. The default location is C:\Program Files\VERITAS\Backup Exec\NT\DataBackup. If you do not want to keep previous catalogs and data, click Do not back up previous data and catalogs. 4. Click Next to continue. An upgrade summary is displayed.
104
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 Computers on page 793. Backup Exec NetWare Agent. For more information, see Installing the Remote Agent on a NetWare Server on page 1392 and Installing Backup Exec Agents to Remote Computers on page 77. Backup Exec Advanced Open File Option. For more information, see Installing the Advanced Open File Option on page 996.
To reinstall these options, repeat the installation steps for each option.
105
106
Chapter
Getting Started
In Getting Started, youll find:

A checklist to help you prepare for the First Time Startup Wizard. Details on the Backup Exec Assistant, Information Desk, System Summary, and other parts of the Backup Exec Administration Console. Details of default options set when Backup Exec is installed. Descriptions of Backup Exec menus.
Before Starting Backup Exec

For best results before starting Backup Exec, do the following: Make sure your storage devices are connected and configured properly. Decide if your backup will be to a tape device or a disk device. You can configure both devices 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 176.
Understand how Backup Exec provides overwrite protection for your media. For more information, see Media Overwrite Protection on page 213.
107
Starting Backup Exec
Understand the default media set and its infinite overwrite protection period. For more information, see Media Overwrite Protection Levels on page 226. Learn about creating new media sets with weekly, monthly, or quarterly retention periods. For more information, see Default Media Set on page 217. 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 386.
Starting Backup Exec
To start the Backup Exec Administration Console, click Start, point to Programs, and then click Symantec Backup Exec for Windows Servers. If you selected the option to add an icon to your desktop when you installed Backup Exec, you can also double-click the icon to start Backup Exec.
Related Topics: Using the Administration Console on page 110 Using Backup Exec Dialog Boxes on page 113
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 features of Backup Exec, including media sets, overwrite protection settings, devices, and logon accounts. You must complete the applicable sections of this wizard to prepare 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 213. Preferred Overwrite Media Type. Review the circumstances and order in which Backup Exec searches for overwritable media in Media Overwrite Options on page 228. 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 226.
108
First Time Startup Wizard
Detected Hardware. The Device Configuration wizard enables you to verify that all of the storage devices attached to your system appear, and that robotic libraries and storage devices are configured properly. If you do not see one or more of your attached storage devices in the Backup Devices window when using the Device Configuration Wizard, 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 176. 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.
Configure IDR Options. If you installed the Intelligent Disaster Recovery Option, youll be prompted to configure IDR. For more information, see Getting Started with IDR on page 906. Logon Accounts. Use the Logon Account Wizard to set up Backup Exec logon accounts, which enable users to access resources such as servers, shares, and databases. For more information, see Configuring Logon Accounts on page 386.
After you use the First Time Startup Wizard, you can access some of the wizards included in 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
109
Using the Administration Console

After you install Backup Exec, the Administration Console displays. From the Administration Console, you can access all Backup Exec features. 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 712.
Administration Console Menu bar Navigation bar
Columns
Task pane
Status bar Selection pane Preview pane Results pane
The main Administration Console screen includes the following components:
Menu bar. Backup Execs menu bar appears across the top of your screen. To display a menu, click the menu name or use the keyboard shortcut. You can launch Backup Exec operations by clicking options from a menu. Some options may be unavailable until you select an item from the console screen. For example, you cannot select Rename cannot from the Edit menu unless you have first selected an item to rename from either the Devices view or the Media view.
110
Navigation bar. The navigation bar appears under the menu bar and enables you to create a backup or restore job or to navigate to Backup Execs eight views. The 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 the Desktop and Laptop Option (DLO) if it has been installed. Media Server. This view displays only if you have installed the Central Admin Server Option (CASO). Use this view to monitor and manage media servers in a CASO-enabled Backup Exec environment. Job Setup. Use this view to perform tasks for new backup, restore, and media rotation jobs, as well as to launch some utility jobs. Job Monitor. Use this view to monitor jobs and job history. Through this view, you can also access the Outlook-like job calendar.
Note If you are using BEWAC, the Outlook-like job 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. 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, such as files to back up or restore.
111
Results pane. The Results pane is the large pane on the right side of the screen that usually contains a list or tree view of items that correspond to items that are selected in the Selection pane. For example, if you select a Backup-to-Disk folder in the Selection pane, the Backup-to-Disk files that are contained in the folder display in the Results pane. This pane can be divided to display a preview pane. Preview pane. The preview pane displays on the bottom right of the Administration Console. It displays information about the item selected in the list or tree view. This pane can be hidden by selecting View, and then selecting Preview Pane.
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.
112
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
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. 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 Symantec company web site.
113
To view the Information Desk: 1. On the navigation bar, click Overview. 2. Click the Information Desk tab.
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. To view the System Summary: 1. On the navigation bar, click Overview. 2. Click the System Summary tab.
System Summary
115
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. The Backup Exec Assistant is not available in BEWAC.
Backup Exec Assistant
To display the Backup Exec Assistant in a resizable window: 1. On the navigation bar, click Overview. 2. Click the Backup Exec Assistant tab. 3. In the task pane, click Open Assistant in new window.
116
Frequently Asked Questions

How do I run a backup job? There are several ways to run a backup, depending on your backup needs and level of experience with Backup Exec.
If you are new to Backup Exec, you can use the Backup Wizard, which guides you through the setup of a backup job. If you are an experienced Backup Exec user, do one of the following:

On the navigation bar, click Backup to configure the options for a backup job. On the navigation bar, click Job Setup to create a policy to use for multiple backup jobs.
To quickly create a backup job to back up the media server, click Back up this media server now with One-button Backup on the Information desk. Use Windows Explorer to create a backup job.
For more information about the various ways to create a backup job, see Creating a Backup Job on page 261. Where can I find the wizards? You can find wizards in the following locations:
On the Information Desk. a. On the navigation bar, click Overview.
b. Click the Information Desk tab.
On the Tools menu.
From the Tools menu, click Backup Exec Assistant or click Wizards.
Where can I find the Readme file? The Readme file is available in the following locations:
b. Click the Information Desk tab. c.
Under Documentation, click View ReadMe file.
In the directory where Backup Exec was installed.

117
On the Help menu.
Where can I find the online documentation for Backup Exec?
b. Click the Information Desk tab. c.
Under Documentation, click View Symantec Backup Exec Administrators Guide. From the Help menu, click Topics to see the online help or click View Symantec Backup Exec Administrators Guide to view an online version of the System Administration Guide in the Adobe Portable Document Format (PDF).
On the Help menu.
How do I get in touch with Technical Support?
From the Information Desk. a. On the navigation bar, click Overview.
b. Click the Information Desk tab. c. Under Technical Support, click Symantec Backup Exec support.
118
Backup Exec Defaults

When you start Backup Exec for the first time, defaults are already configured. You can adjust the defaults to meet the needs of your environment. Default settings are available for various types of jobs, such as backup, restore, and test run. You also can set defaults for catalogs, media management, bar code rules, and database maintenance. The defaults that will probably affect you the most are the backup job defaults. You can change many of these defaults after devising a media rotation strategy and creating additional media sets and drive pools. In the short term though, you can run Backup Exec and backup and restore jobs safely by using only the defaults set during installation. Related Topics: Setting Default Backup Options on page 324 Setting Restore Defaults on page 490 Setting Test Run Default Options on page 323 Setting Default Pre/Post Commands on page 331 Configuring Default Job Log Options on page 435 Specifying Default Backup Network and Firewall Options on page 336 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Setting Default Backup and Restore Options for SQL on page 1052 Setting Default Backup and Restore Options for Exchange on page 1102 Configuring Default Lotus Domino Options on page 1332 Default Settings for the Remote Agent on page 1402 Configuring Default Schedule Options on page 403 Changing Default Preferences on page 120 Setting Catalog Defaults on page 454 Setting Default Media Options on page 239 Bar Code Rules in Mixed Media Libraries on page 236 Configuring Database Maintenance on page 447 Setting Offhost Backup Options for Backup Jobs on page 892 Setting Default Options for SharePoint Portal Server 2003 on page 1384 Using Checkpoint Restart on Microsoft Cluster Server Failover on page 665 Creating Multiple Selection Lists from a Single Selection List on page 303 Setting Priority and Availability Windows for Selection Lists on page 301 Setting Thresholds to Recover Jobs on page 445
119
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. 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 305. If this option is cleared, you will not be able to submit backups using the Backup Exec Windows Explorer interface.
Inventory all drives on Backup Exec services startup
Enable backup from Windows Explorer
Display the job summary Select this option to have Backup Exec display a summary of before creating a job the job options you selected before submitting the job to the job queue. Create jobs after a new policy is created Select this option to have Backup Exec automatically display the Create or Delete Policy Jobs dialog box after you create a policy. You can use the Create or Delete Policy Jobs dialog box to create jobs by associating selection lists with policies.
120
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 percentage complete number while a backup job is processing. These indicators appear in the Job Activity tab, and they allow you to monitor the progress of the job. Backups might take a little longer to complete when this option is selected because the target resources must be scanned to determine the amount of data to be backed up. Note Due to the time required to scan the target resources, selecting this option when backing up remote resources is not recommended. Enable percentage bars when available Select this option to display a shaded percentage complete bar in the Percent Complete column for active jobs. The percentage complete bar displays in addition to the percentage complete number.
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
ScreenTips Enable ScreenTips Select this option to enable or disable ScreenTips, which provide brief explanations of selected items on the Administration Console. When ScreenTips are enabled, you can view them by holding the mouse pointer on an item. Only selected items have ScreenTips.
Seconds to delay display If you selected the Enable ScreenTips option, type the of ScreenTips number of seconds you want Backup Exec to wait before displaying ScreenTips. For example, if you type 10, the mouse must be held over the item for 10 seconds before Backup Exec displays the ScreenTip for the item.
121
Backup Exec Defaults Options - Set Application Defaults - Preferences (continued) Item Row highlights Enable highlighting of every other row in Backup Exec views Select this option to enable or disable highlighting on every other row in various lists, such as the current jobs and job history lists on the Job Monitor. Highlighting facilitates viewing of long lists. This option is selected by default. If you selected the Enable highlighting of every other row in Backup Exec views option, use the slide bar to set the darkness of the highlighting in the rows. Description
Set contrast of highlighting
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 Device Description Select the device that you want to use as the default device for jobs. You can change this default for each job individually. Select the media set that you want to be used as the default media set for jobs. You can change this default for each job individually.
Media set
122
Chapter
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. http://support.veritas.com/rd/bews-compatibility.htm.
For a list of supported devices, see: With Backup Exec, you can maximize your hardware investment by organizing your devices in one or both of the following methods:
Device pools. Devices are grouped so that jobs assigned to the device pool are run on the first available device. Setting up device pools offers the following benefits:
Automatic job rescheduling. If a device fails while a job is running on it, that job is rescheduled and placed on hold. Other scheduled jobs are rerouted to working devices in the device pool. Concurrent processing. Devices in the device pool run different jobs at the same time, allowing maximum hardware efficiency. Dynamic load balancing. Jobs are more evenly distributed between all of the devices included in the device pool when running simultaneous jobs.
123
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 device pool, All Devices (Computer Name) is the default destination device when you create a backup job. By default, the All Devices device pool contains all locally attached devices, or if you are using the SAN Shared Storage Option, both locally attached and shared storage devices appear in All Devices (Computer Name). In addition to device pools and cascaded drive pools, Backup Exec provides other device management capabilities. You can:

Identify and monitor the current status of all storage devices. Change physical tape devices without rebooting the Backup Exec server. Monitor device usage statistics and track hardware errors. Backup Exec keeps track of the devices age, hours of use, mounts, number of bytes processed (written and read), errors, when the device was last cleaned, and so on. Manage the physical devices attached to the media server and perform operations on these devices and the media contained in them.
Note Most of the benefits derived from Backup Execs device management functionality are realized when using more than one storage device. However, users with only one device can still take full advantage of Backup Execs device monitoring to help make sure their devices are working properly. Related Topics: Symantec Backup Exec - SAN Shared Storage Option on page 957
124
Viewing Devices
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. A stand-alone drive is a single, locally attached tape drive. Note Support for a single robotic library device is included with Backup Exec for Windows Servers. Licenses for additional robotic library devices are available for purchase. If you group one or more robotic library slots into partitions, the partition drive pools appear in the Devices view under the Device Pools icon. For information about partitioning robotic library slots, see Creating Robotic Library Partitions on page 172. Click Devices on the navigation bar to see how devices are organized logically in device pools, and how devices are arranged physically on servers. All devices that are displayed under Storage Devices are available, including device pools, stand-alone drives, robotic libraries, backup-to-disk folders, and cascaded drive pools. If the Shared Storage Option is installed, you can also view available secondary storage devices on the storage area network. All logical groupings of the physical devices are displayed under Device Pools and Cascaded Drive Pools. Cascaded drive pools are displayed under servers because they only consist of drives from that server; they effectively act as a single device under that server. The default device pool All Devices (Computer Name) contains the media servers locally attached devices as well as any Backup-to-Disk Folders created. Backup-to-Disk Folders are destination devices for backups that are directed to your hard disk. The data from these backups is saved on disk as backup files. If you are using the SAN Shared Storage Option, each server on the SAN will have an All Devices (Computer Name) node that contains both local and shared devices available to the server. At installation, all storage devices are automatically assigned to All Devices (Computer Name). Related Topics: Viewing Media Information on page 126 Viewing Device Pool Properties on page 138 Viewing Properties of a Cascaded Drive Pool on page 143 Viewing and Using Device Properties and Statistics on page 151 About Devices in the Shared Storage Environment on page 961
Chapter 4, Managing Devices
125
Viewing Devices
Viewing Media Information

If you select a device or select Slots from the Devices view, information for the media contained in the device or slot appears in the right pane. This information is also displayed when you click Media on the navigation bar, and then click All Media.
Media information in the Devices view Item Slot number Bar Code Description Number of the slot. This field only appears if Slots has been selected. Label obtained from a bar code reader. This field only appears if Slots has been selected. Bar code information only appears if the robotic library has a bar code reader and a bar code label is on the media. Check the box to define this slot as a cleaning slot. 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. Media label that was assigned automatically by Backup Exec, or that was assigned or changed by the administrator, or that was a pre-assigned bar code label. You can edit the media label, which is limited to 32 characters. Editing the label changes the name of the media in the display, but does not write the new label to the media until an overwrite operation occurs. When you edit a media label, try to make it a concise identifier that will remain constant even when the media is reused. You should write this media label on a label fixed to the outside of the physical media. Duplicate labels can be automatically generated. For example, reinstalling Backup Exec or bringing media from another Backup Exec installation could cause duplication in labels. Duplicate labels are allowed, but not recommended. Note If a bar code is available, and a bar code-equipped device is used, then the media label automatically defaults to that bar code. Description By default, displays the original media label if the media is imported media. If the media description has been edited, the new description appears. Otherwise, this field is blank.
Cleaning slot
Media label
126
Viewing Devices Media information in the Devices view 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. To change the media type, click the browse button to the right of the field, and select another media type. Export pending When a template runs that has an associated export template to export this media, Yes is displayed; otherwise, No is displayed. For more information, see Adding an Export Media Template to a Policy on page 370. Name of the media set this media belongs to. Name of the device or vault where this media is located. Date and time when the media was first entered into Backup Exec. Date and time when the media was added to a media set as a result of an overwrite operation. Date and time when data was last written to the media. Date and time after which the media can be overwritten.
Media set Media location Creation date Allocated date
Modified date Overwrite protection until Appendable until Number of cleanings
Date and time after which the media can no longer be appended to. 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
Related Topics: Symantec Backup Exec - Library Expansion Option on page 1115 About Devices in the Shared Storage Environment on page 961
127
Configuring Devices
Configuring Devices
Backup Exec provides two wizards for configuring and adding storage devices to your media server:
The Device Configuration Wizard. This wizard, which also 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. The VERITAS device driver Installation Wizard. This wizard guides you through the installation of VERITAS device drivers.
If you are using a robotic library, make sure the robotic library hardware is configured properly. Related Topics: First Time Startup Wizard on page 108 Hot Swap for Storage Devices on page 128 VERITAS device driver Installation Wizard on page 129 Setting Up Robotic Library Hardware on page 1115
Hot Swap for Storage Devices

You can replace or add a hot-swappable tape device on a Backup Exec media server without having to reboot the 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 media server and stops the Backup Exec services. You can then add or replace any storage devices. The wizard detects the new or replaced device, and adds information about the device to the Backup Exec database. The wizard is then completed, and you can reopen the Backup Exec Administration Console. The new storage device is displayed in the Devices view, and usage statistics for the devices begin accumulating. You can add the new device to a device pool or cascaded drive pool.
128
Configuring Devices
The replaced storage device is displayed in the Devices view with a status of Offline. To remove the storage device from Backup Exec, disable it and then delete it from the Devices view. Note Only tape devices that have hot-swap capability are supported for hot swapping and adding. Refer to the documentation for the tape device 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.
VERITAS device driver Installation Wizard

This wizard guides you through the installation of the VERITAS device drivers. You can use this wizard to view available tape devices and the associated drivers. To run the VERITAS device driver Installation Wizard 1. From the Backup Exec for Windows Servers installation directory, double-click tapeinst.exe. The default location is C:\Program Files\VERITAS\Backup Exec\NT. 2. After reading the Welcome screen, click Next to continue. 3. On the Choosing tape drivers screen, click More Information to read current details about each choice. 4. Click Next to continue. 5. On the Scanning hardware screen, click Details to view changes that will be made based your selections on the Choosing tape drivers screen. Note If you want to view information only, click the X box at the top right corner of the dialog, and exit the tapeinst.exe application instead of clicking Next. 6. Click Next to allow the changes that were displayed in Details to be made. Tapeinst.exe is updated by the Device Driver Installer package that is available as a download from the Symantec support site
129
Configuring Devices
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. You can pause a media server to prevent scheduled and new jobs from running on that server while maintenance activities, such as replacing a tape device, are being performed. Active jobs will not be affected if they started before the server was paused. To pause or resume the media server: 1. On the navigation bar, click Devices. 2. Click the server icon. 3. Under Device Tasks in the task pane, select Paused. A check mark appears next to the Paused option if the media server is currently paused. If the media server was not already paused, it is now paused. If the media server was already paused, it is now resumed. To pause or resume a robotic library or device: 1. On the navigation bar, click Devices. 2. Click the robotic library device or stand-alone drive. 3. Under Device Tasks in the task pane, select Paused. A check mark appears next to the Paused option if the device is currently paused. If the device was not already paused, it is now paused. If the device was already paused, it is now resumed. To rename a robotic library or device: 1. On the navigation bar, click Devices. 2. Click the robotic library or device that you want to rename. 3. Under General Tasks in the task pane, click Rename. 4. On the Rename dialog box, type the new name, and then click OK.
130
Configuring Devices
Related Topics: Renaming a Backup Folder on page 180 Pausing and Resuming a Backup Folder on page 182 Renaming a Device Pool on page 137 Renaming a Cascaded Drive Pool on page 143
131
Using Device Pools
Using Device Pools

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

Device pools can consist of stand-alone drives, drives in single or multiple drive robotic libraries, fixed backup-to-disk folders, and removable backup-to-disk devices. Tape drives that are in a cascaded drive pool are not available to be placed in another device pool unless they are deleted from the cascaded drive pool first. To create a device pool: 1. On the navigation bar, click Devices. 2. Click Device Pools. 3. Under Device Pool Tasks in the task pane, select New device pool. 4. Select the appropriate options as follows, and then click OK:
New Device Pool fields Item Device pool name Description Device List Filter Device type Select a device type from the drop-down list to filter the list of devices available for the new device pool. Only devices of this type are displayed for selection. If device sub-types are available, you can select a subtype to increase the filter on the list of devices available for the new device pool. Only devices of this type and sub-type are displayed for selection. Description Type the name of the new device pool that you want to create. Type a description of the new device pool.
Device sub-type:
Select the devices to be Select the devices that you want to include in the new device pool. included in this device pool
Related Topics: Using Cascaded Drive Pools on page 139 Creating a Cascaded Drive Pool on page 139
133
Using Device Pools
Adding Devices to a Device Pool

You can add a device to an existing device pool, unless it is a tape drive in a cascaded drive pool. Tape drives that are in a cascaded drive pool will be automatically deleted from the cascaded drive pool if they are placed in another device pool. To add a device to a device pool: 1. On the navigation bar, click Devices. 2. Select the device pool. 3. Under Device Pool Tasks in the task pane, select Add device. 4. Select the appropriate options as follows, and then click OK:
Add Device to Device Pool options Item Device pool name Description Device List Filter Device type Select a device type from the drop-down list to filter the list of devices available for the device pool. Only devices of this type are displayed for selection. If device sub-types are available, you can select a subtype to increase the filter on the list of devices available for the device pool. Only devices of this type and sub-type are displayed for selection. Description Name of the device pool to which you want to add devices. Description of the device pool.
Device sub-type:
Select the devices to be Select the devices you want to include in the device pool. included in this device pool
134
Using Device Pools
Setting Priorities for Devices in a Device Pool

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

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

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

If a device pool or media set is deleted, and scheduled jobs are assigned to that device pool or media set, you are prompted to redirect the jobs to another device pool or stand-alone drive, or to another media set. To redirect a scheduled job: 1. When prompted to redirect the jobs, click Yes. The job to be redirected is displayed in the Retarget Job dialog box. If there are scheduled jobs assigned to the deleted device pool or media set, you are prompted to redirect the jobs to another device or device pool, or media set. 2. In the Destination field, click the <Down arrow> to see available choices, and then select the new device pool, stand-alone 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 destination. Note If you choose not to retarget a job, the job will fail. To target the job to another destination later, you must manually edit the job.
Renaming a Device Pool

The default All Devices device pool cannot be renamed, but you can rename any user-created device pool using either the Rename option or the device pools Properties dialog box. To rename a device pool: 1. On the navigation bar, click Devices. 2. Under Device Pools, select the device pool you want to rename.
Chapter 4, Managing Devices 137
Using Device Pools
3. Under General Tasks, select Rename. 4. On the Rename dialog box, type the new name of this device pool, and then click OK. The device pool is listed with the new name. Related Topics: Viewing Device Pool Properties on page 138
Viewing Device Pool Properties

Use Properties to view properties for a device pool, or to rename the device pool. To view properties for a device pool: 1. On the navigation bar, click Devices. 2. Under Device Pools in the tree view, select the device pool. 3. Under General Tasks in the task pane, select Properties. The Device Pool Properties dialog box provides the following information:
Device Pool properties Item Name Description Name of the device pool. Rename the device pool by typing a new name in this field. Description of the device pool. You can enter a description or modify the description. Date and time that this device pool was created.
Description
Creation date
138
Using Cascaded Drive Pools

You can cascade (link) multiple stand-alone tape drives together to create one logical drive. By cascading the tape drives, backup jobs can automatically roll to the media in the next tape drive when the media is filled. Although multiple tape drives are linked to form the cascaded drive pool, only the name of the cascaded drive pool is listed as the destination device when a backup job is created. Tape drives in a cascaded drive pool are not available for concurrent operations. Only one tape drive is used at a time. The next tape drive in the cascaded drive pool is used only when a backup job fills the current media, or when the next job requires a different media (such as an overwrite job). Use cascaded drive pools to run unattended backup jobs, or to make sure a large backup job will complete without operator intervention. You may also want to use cascaded drive pools if you want data from a job or group of jobs to reside on the same tape family. Related Topics: Using Device Pools on page 132
Requirements for Using Cascaded Drive Pools

In order to cascade tape drives, the tape drives must be the same drive type, such as DLT 32K. To determine the drive type, look in the tape drives property page. For more information, see Viewing and Using Device Properties and Statistics on page 151. Caution If a tape drive that does not support hardware compression is added to a cascaded drive pool, the hardware compression option on all other tape drives in that pool is automatically disabled. You can enable the hardware compression option on the other tape drives again, but the pool will then have mixed compression, which could make restore operations difficult. Backup-to-Disk- folders cannot be placed in cascaded drive pools.
Creating a Cascaded Drive Pool

When you select drives for a cascaded drive pool, only drives of the same drive type are displayed for selection. Any drives that you move to a cascaded drive pool are removed from device pools that they are currently in. Note Overwrite and append periods for media take precedence over tape drive priority.
139
To create a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Select Cascaded Drive Pools. 3. Under Device Pool Tasks in the task pane, select New device pool. 4. Select the appropriate options as follows, and then click OK:
New Cascaded Drive Pool options Item Drive pool name Description Type the name of the new cascaded drive pool that you want to create. Description of the cascaded drive pool.
Description Device List Filter Device type
Select a device type from the drop-down list to filter the list of drives available for the cascaded drive pool. Only drives of this type are displayed for selection. If device sub-types are available, you can select a subtype to increase the filter on the list of drives available for the cascaded drive pool. Only drives of this type and sub-type are displayed for selection. Select the drives that you want to include in the new cascaded drive pool. Any drives moved to a cascaded drive pool will be removed from any device pools they are currently in.
Device sub-type:
Select the drives to be included in this device pool.
Related Topics: Deleting Drives from a Cascaded Drive Pool on page 142 Deleting a Cascaded Drive Pool on page 142
140
Adding Drives to a Cascaded Drive Pool

You can add a drive to an existing cascaded drive pool provided the drive is of the same type as the drives already in the pool and provided that the drive is not in another cascaded drive pool. Drives that are part of a non-cascaded drive pool will be removed from the other pool when added to a cascaded drive pool. To add a drive to a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Select the cascaded drive pool to which you want to add a drive. 3. Under Device Pool Tasks in the task pane, select Add device. 4. Select the appropriate options as follows, and then click OK:
Add Drive to Cascaded Drive Pool fields Item Device pool name Description Device List Filter Device type Only stand-alone drives are displayed for selection for a cascaded drive pool. Select a sub-type, or media type, to increase the filter on the list of drives available for the cascaded drive pool. Only drives that use this media type are displayed for selection. Description Name of the cascaded drive pool to which you want to add drives. Description of the cascaded drive pool.
Device sub-type:
Select the devices to be Select the drives you want to include in the drive pool. included in this device pool
141
Deleting Drives from a Cascaded Drive Pool

Use Delete to remove a drive from a cascaded drive pool, or drag the drive you want to delete from the cascaded drive pool to the Stand-alone Drives icon. If the move is allowed, the mouse arrow icon displays a plus sign (+) in a box. The drive will still be in the Backup Exec device database and will still be available for use in other device pools. It is not necessary to delete drives from a cascaded drive pool before you delete that pool; the drives are automatically removed when the cascaded drive pool is deleted. The following instructions describe the menu-driven method. 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. 4. Under Device Pool Tasks in the task pane, select Remove device. 5. When prompted, click Yes to delete the drive that is displayed. Related Topics: Deleting a Cascaded Drive Pool on page 142 Erasing Media on page 195
Deleting a Cascaded Drive Pool

It is not necessary to delete drives from a cascaded drive pool before you delete that pool; the drives are automatically removed from the pool when the pool is deleted. If scheduled jobs are assigned to the deleted cascaded drive pool, you are prompted to redirect them to another device or drive pool. To delete a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Under Cascaded Drive Pools, select the drive pool or pools that you want to delete. 3. Under General Tasks, click Delete.
142
4. When prompted, click Yes or Yes to All to delete the cascaded drive pool or pools that are displayed. 5. If scheduled jobs are assigned to the deleted cascaded drive pool, you are prompted to redirect the jobs to another device pool or stand-alone drive. 6. If scheduled jobs are assigned to the deleted cascaded drive pool, you are prompted to redirect the jobs to another destination. Related Topics: Retargeting Jobs from a Deleted Device Pool or Media Set on page 137
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 then click OK.
Viewing Properties of a Cascaded Drive Pool

Use Properties to view properties for a cascaded drive pool, or to rename the cascaded drive pool. To view properties of a cascaded drive pool: 1. On the navigation bar, click Devices. 2. Under Cascaded Drive Pools, select the cascaded drive pool for which you want to view properties. 3. Under General Tasks in the task pane, select Properties.
143
Viewing Media Server Properties and Running Server Diagnostics
The Cascaded Drive Pool Properties dialog box provides the following information:
Cascaded Drive Pool properties Item Name Description Name of the cascaded drive pool. Rename the drive pool by typing a new name in this field. Description of the cascaded drive pool. You can enter a description or modify the current description. Date and time that this cascaded drive pool was created.
Description
Creation date

Use Properties to view information about your media server, including the version of Backup Exec that is installed, and system information. Most of the details presented in the properties tabbed pages are for information only. However, from the General tab, you can run Diagnostics, a Backup Exec diagnostic utility. To view media server properties: 1. On the navigation bar, click Devices. 2. Select the media server from the tree view. 3. Under General Tasks in the task pane, select Properties, and then click one of the tabs. Related Topics: Viewing Media Server General Properties on page 145 Viewing Media Server System Properties on page 147 Viewing Media Server License Information Properties on page 150
144
Viewing Media Server General Properties

From the General tab, you can run 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, see Running BEDIAG.EXE to Generate a Diagnostic File for Troubleshooting on page 629. Technical services can use the results of BE Diagnostics to troubleshoot problems. Note You can also run Diagnostics for a remote server (see Running BEDiag on a Remote Computer on page 631). To view media server general properties: 1. On the navigation bar, click Devices. 2. Select the media server from the tree view. 3. Under General Tasks in the task pane, select Properties, and then click the General tab. The Media Server Properties General tab provides the following information:
Media Server Properties General Tab properties Item Name Media server status Description The name of the media server. The status of the media server:

Online - All services are running. Pause - The server has been paused. You can pause a media server to prevent scheduled and new jobs from running on that server while maintenance activities, such as replacing a tape device, are being performed. Active jobs will not be affected if they started before the server was paused. Unavailable - The Backup Exec services are not responding. Depending on the thresholds that were set, active jobs will become stalled, then failed, and then will be recovered. For more information, see Setting Thresholds to Recover Jobs on page 445. Offline - The media server is not online. Services have been stopped.
Note If the Central Admin Server Option is installed, additional statuses are displayed. For more information, see Columns in the Media Servers View on page 853 Chapter 4, Managing Devices 145
Viewing Media Server Properties and Running Server Diagnostics Media Server Properties General Tab properties (continued) Item Media server type Description If this is a single installation of Backup Exec, the media server type displayed is a stand-alone media server. If the Central Admin Server Option is installed, the media server type displayed is either a managed media server or a central administration server. For more information, see Columns in the Media Servers View on page 853. Description Version Serial number Enter a description of the server. Backup Exec version and revision information. The serial number under which Backup Exec is installed. Evaluation Edition is displayed if a serial number was not provided during Backup Execs installation. Number of storage devices connected to this media server. In systems with multi-drive robotic libraries attached, each drive in the robotic library represents a separate device. Number of jobs currently in progress on this media server. Total number of alerts generated on this media server since the Backup Exec services were last started. Displays the time zone set for this media server. Date and time Backup Exec was initially installed and launched on this media server. Current date and time.
Number of devices
Number of active jobs Alerts since startup
Time zone Start date and time
Current date and time
146
Viewing Media Server Properties and Running Server Diagnostics Media Server Properties General Tab properties (continued) Item Run Diagnostics Description Note If you call Technical Support, 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 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.
Refresh
Click to update the displayed fields.
Viewing Media Server System Properties

To view media server system properties: 1. On the navigation bar, click Devices. 2. Select the media server from the tree view. 3. Under General Tasks in the task pane, select Properties, and then click the System tab. The Media Server Properties System tab provides the following information:
Media Server Properties System tab properties Item Operating system Type Version Operating system currently running on this media server. Version of the operating system. Description
147
Viewing Media Server Properties and Running Server Diagnostics Media Server Properties System tab properties (continued) Item Build Processor Type Total processors Memory Physical Virtual remaining Page size Page file Amount of hardware RAM installed in the media server. Amount of virtual memory remaining on the media server. Size of a single virtual memory page. Size of the virtual memory paging file. Processor installed in this media server. Number of processors on this media server. Description Build number of the operating system.
Viewing Media Server Advanced Properties

From the Advanced tab, you can view information about the location of the databases for Backup Exec, which include the Backup Exec database, the device and media database (ADAMM), and the catalog database. During Backup Exec installation, if you chose the default option to create a local Backup Exec MSDE instance on which to store the Backup Exec database, the databases are all located on the local media server. If you chose another instance on the network on which to store the Backup Exec database, then the databases are all located on the Microsoft SQL Server that contains that instance. In a SAN SSO configuration, on the secondary servers, the database locations are the same as the database locations displayed on the primary server. In a Central Admin Server Option configuration, on the managed media servers, the device and media database location is the same as the device and media database location displayed on the central administration server. The Backup Exec database and the catalog database on the managed media servers are on the local media server if the default option to create a local instance on which to store the Backup Exec database is chosen during installation. After installation, the location of the catalog database can be changed to the central administration server (see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840).
148
Note Advanced properties are displayed only for the media server that the Backup Exec Administration Console is connected to. To view media server advanced properties: 1. On the navigation bar, click Devices. 2. Select the media server from the tree view. 3. Under General Tasks in the task pane, select Properties, and then click the Advanced tab. The Media Server Properties Advanced tab provides the following information:
Media Server Properties Advanced tab properties Item Backup Exec Database Server Name of the Microsoft SQL Server that contains the Backup Exec database. Name of the instance that the Backup Exec database is installed on. SQL database name of the Backup Exec database. The path of the Backup Exec database. Description
Instance Name Path
Device and Media Database Server Name of the Microsoft SQL Server that contains the Advanced Device and Media Management (ADAMM) database. Name of the instance that the Advanced Device and Media Management (ADAMM) database is installed on. SQL database name for the Advanced Device and Media Management (ADAMM) database. The path of the Advanced Device and Media Management (ADAMM) database.
Instance
Name
Path
149
Viewing Media Server Properties and Running Server Diagnostics Media Server Properties Advanced tab properties (continued) Item Catalog Database Server Name of the Microsoft SQL Server that contains the Backup Exec catalog database. Database instance that contains the catalog database. SQL database name for the Backup Exec catalog database. The path of the Backup Exec catalog database. Description
Instance Name Path
Viewing Media Server License Information Properties

1. On the navigation bar, click Devices. 2. Select the media server from the tree view. 3. Under General Tasks in the task pane, select Properties, and then click the License Information tab to view additional options licensed and installed on the media server. The Media Server Properties License Information tab provides the following information:
Media Server Properties License Information tab properties Item Option Licensed Description Name of the Backup Exec options. Displays Yes if the option is licensed on the media server, and No if the option is not licensed. Displays Yes if the option is installed on the media server, and No if the option is not installed. If the option is installed, it may still require some additional configuration. Refer to the Symantec Backup Exec for Windows Servers System Administrators Guide, or click Help.
Installed
150
Viewing and Using Device Properties and Statistics

Backup Exec provides details on each device connected to a media server and the first robotic library drive. Note Support for a single robotic library drive for use with Backup Exec is provided when you purchase Backup Exec. To enable support for additional robotic library drives, you must purchase the Library Expansion Option. Most of the details presented in the device properties tabbed pages are for information only. To view a devices properties: 1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. 3. Select the device for which you want to view properties.
4. Under General Tasks in the task pane, select Properties. Related Topics: Viewing General Device Properties on page 152 Viewing Drive Configuration Properties on page 154 Viewing Drive SCSI Information Properties on page 158 Viewing Drive Statistics Properties on page 159 Viewing Drive Cleaning Properties on page 161 Viewing and Specifying a Devices Media Types on page 163
151
Viewing General Device Properties

The Device Properties General tab provides information about the device. Most of this information is for viewing only; however, you can rename your device from this tabbed page by typing the new name in the Name field. To view a devices general properties: 1. On the navigation bar, click Devices.
4. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click General. The General tab for device properties provides the following information:
General Device Properties Item Name Description Name of the device. You can also rename the device by typing a new name in this field.
152
Viewing and Using Device Properties and Statistics General Device Properties (continued) Item Status Description
Pause: Select this check box to pause the device, and then click OK. Enable: Select this check box in order for Backup Exec to use this device. Clear this check box to disable the device, and allow it to be available for other applications. If the box is clear, the device is disabled, and cannot be used by Backup Exec. After changing the option, click OK. Online: If the device is online, the check box appears dimmed, with a check mark. If the device is offline, the check box is available, with no check mark. To bring the device online, check Online. No operations are allowed on the device until it is online again. The device was turned off after Backup Exec was started. The device was being used by another application (such as a Windows backup utility) when Backup Exec was started. The device is removed from the computer. A tape drive failure occurred. A tape is stuck in the drive. The firmware of the device was updated; Backup Exec will behave as if the device with its old name or identity no longer exists.
The device is displayed as offline if:

To bring the device online, try the following:
Check to make sure the device has power and that cables are properly attached. Turn the device on and reboot the server, or stop and restart the Backup Exec services. Stop the utility that is using the device, and then reboot the server, or stop and restart the Backup Exec services. To restart the Backup Exec services: For Windows 2000, Windows XP, and Windows Server 2003, go to Computer Management, select System Tools, select Services, and then select Applications. If the device firmware has changed, delete the device and restart Backup Exec services. After the device appears with its new firmware identity, retarget all jobs that were using the old device name to the new device name.
Vendor Product ID Chapter 4, Managing Devices
Name of the vendor of the drive. Product ID from the SCSI Inquiry string. 153
Viewing and Using Device Properties and Statistics General Device Properties (continued) Item Firmware Drive type Media type Description Version of the firmware used in the device. Media and memory specifications of the device. If the device is a stand-alone drive, the media type used in this drive type is displayed. Date this device was first detected by this installation of Backup Exec. Serial number of the drive.
Date in service
Serial number
Related Topics: Viewing and Using Device Properties and Statistics on page 151 Viewing Backup Folder Properties on page 183
Viewing Drive Configuration Properties

The Drive Properties Configuration tab allows you to:

Enable or disable hardware compression (if compression is supported by the drive). Change the preferred block size, buffer size, buffer count, and high water count.
Caution Preferred Configuration settings are used to tune the performance of backup and restore operations. Changing Preferred Configuration settings is not generally recommended and may have a negative effect on your backup and system performance. Any changes should be thoroughly tested to make sure system performance does not deteriorate before being put into general use. To view a drives configuration properties: 1. On the navigation bar, click Devices.
2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. 3.
154
Select the device for which you want to view properties.

4. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click Configuration. The Configuration tab for drive properties provides the following information:
Drive Configuration Properties 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 device on which hardware compression is disabled (even though it is supported), hardware compression is considered unavailable and is not used. If a device that does not support hardware compression is added to a cascaded drive pool, the hardware compression option on all other drives in that pool is automatically disabled. You can enable the hardware compression option on the other drives again, but the pool will then have mixed compression, and could make restore operations difficult.
155
Viewing and Using Device 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 devices) provide better performance when larger block sizes are used. The preferred block size can range from 512 bytes to 64 kilobytes. Backup Exec does not ensure that the requested block size is in fact supported by that device. You should check the device specifications to make sure that the block size is supported. If the device does not support a block size, it will default to its standard block size. If the device does not support block size configuration, this option is unavailable. Buffer size (per device) The default is the preferred amount of data sent to the device on each read or write request. The buffer size must be an even multiple of the block size. You can change the buffer size by selecting another size from the scroll list, and then clicking OK. Depending on the amount of memory in your system, increasing this value may improve device performance. Each type of device requires a different buffer size to achieve maximum throughput. Description
156
Viewing and Using Device Properties and Statistics Drive Configuration Properties (continued) Item Buffer count Description The default is the preferred number of buffers allocated for this device. You can change the buffer count by selecting another count from the scroll list, and then clicking OK. Depending on the amount of memory in your system, increasing this value may improve device performance. Each type of device requires a different number of buffers to achieve maximum throughput. If you change the buffer count, you may need to adjust the high water count accordingly. High water count The default is the preferred number of buffers to be filled before data is first sent to the device, and any time after that if the device underruns. You can change the high water count by selecting another count from the scroll list, and then clicking OK. The high water count cannot exceed the buffer count. A value of 0 disables the use of high water logic; that is, each buffer is sent to the device as it is filled. The default setting provides satisfactory performance in most instances; in some configurations, throughput performance may be increased when other values are specified in this field. If you increase or decrease the buffer count, the high water count should be adjusted accordingly. If a device has a high water count default of 0, it should be left at 0. Default Settings Click this button to return all the Preferred Configuration settings to their defaults, and then click OK. Select this check box to have this device read only one block of data at a time. If this check box is selected, the device will read a single block of data at a time, regardless of the size of the buffer block. Symantec recommends selecting this option if the device is a shared storage device. Write single block mode Select this check box to have this device write only one block of data at a time. Selecting this check box provides greater control over the handling of data write errors. Symantec recommends selecting this option if the device is a shared storage device.
Read single block mode
157
Viewing and Using Device Properties and Statistics Drive Configuration Properties (continued) Item Read SCSI pass-through mode Description Select this check box to have this device read data without going through a Microsoft tape device API. Selecting this check box allows the data to pass directly through the device and allows more detailed information if device errors occur. Symantec recommends selecting this option if the device is a shared storage device. Write SCSI pass-through mode Select this check box to have this device write data without going through the Microsoft tape device API. Selecting this check box allows data to pass directly through the device driver and allows more detailed information if device errors occur. Symantec recommends selecting this option if the device is a shared storage device.
Related Topics: Viewing and Using Device Properties and Statistics on page 151
Viewing Drive SCSI Information Properties

To view a drives SCSI information properties: 1. On the navigation bar, click Devices.
4. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click SCSI Information. The Drive Properties SCSI Information tab provides the following information about the Small Computer System Interface (SCSI):
Drive Properties SCSI Information Tab Item Inquiry Description Device information read from the device firmware.
158
Viewing and Using Device Properties and Statistics Drive Properties SCSI Information Tab (continued) (continued) Item Port Description Identifying number of the port on the server to which the device is attached. Identifying number of the bus to which the device is attached. Unique SCSI ID number (physical unit number). Logical Unit Number of the device.
Bus Target ID LUN
Viewing Drive Statistics Properties

The Drive Properties Statistics tab provides the date the device was last mounted, device totals such as the total number of bytes written and read, and device errors. Error rates are affected by media, head cleaning, and head wear. The documentation included with your device should list the acceptable limits for hard and soft errors; if not, check with the hardware manufacturer. To view a drives statistics properties: 1. On the navigation bar, click Devices.
4. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click Statistics. The Statistics tab provides the following information:
Device Properties Statistics Tab Item Last mount date Chapter 4, Managing Devices Description Last date that media was mounted by this device. 159
Viewing and Using Device Properties and Statistics Device Properties Statistics Tab (continued) Item Drive totals Total bytes written Total bytes read Total mounts Total seeks Number of bytes that have been written by this device. Number of bytes that have been read by this device. Number of times media has been mounted by this device. Total number of seek operations (performed when a specific piece of information is being located) that have been performed by this device. Total number of hours that this device has been in use (performing read, write, mount, and seek operations). Description
Total hours in use
Drive errors Seek errors Soft read errors Number of errors encountered while trying to locate data. Number of recoverable read errors encountered. If you receive soft errors, it may indicate the beginning of a problem. If you receive excessive errors for your environment, check the device and perform maintenance on it, and check the media for damage. Number of unrecoverable read errors encountered. If you receive hard errors, check the device and perform maintenance on it, and check the media for damage. Number of recoverable write errors encountered. If you receive soft errors, it may indicate the beginning of a problem. If you receive excessive errors for your environment, check the device and perform maintenance on it, and check the media for damage. Number of unrecoverable write errors encountered. If you receive hard errors, check the device and perform maintenance on it, and check the media for damage.
Hard read errors
Soft write errors
Hard write errors
160
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. To view a drives cleaning properties: 1. On the navigation bar, click Devices.
4. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click Cleaning. The Cleaning tab provides the following information:
Drive cleaning properties Item Last cleaning date Hours since last cleaning Description Last date a cleaning operation was performed on the device. Number of hours that the device has been in use since the last cleaning. Click this to reset all cleaning statistics to zero (stand-alone drives only).
Reset Cleaning Statistics
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.
Bytes read
161
Viewing and Using Device Properties and Statistics Drive cleaning properties (continued) Item Total mounts Description Number of times media has been mounted by this device since the last cleaning. Total number of seek operations (performed when a specific piece of information is being located) that have been performed by this device since the last cleaning. Total number of hours that this device has been in use (performing read, write, mount, and seek operations) since the last cleaning.
Total seeks
Hours in use
Errors since last cleaning Seek errors Number of errors encountered since the last cleaning while trying to locate data. Number of recoverable read errors encountered since the last cleaning. Soft errors may indicate the beginning of a problem. If excessive errors are reported for your environment, check the device and perform maintenance on it, and check the media for damage. Number of unrecoverable read errors encountered since the last cleaning. If you receive hard errors, check the device and perform maintenance on it, and check the media for damage. Number of recoverable write errors encountered since the last cleaning. Soft errors may indicate the beginning of a problem. If excessive errors are reported for your environment, check the device and perform maintenance on it, and check the media for damage. Number of unrecoverable write errors encountered since the last cleaning. If you receive hard errors, check the device and perform maintenance on it, and check the media for damage.
Soft read errors
Hard read errors
Soft write errors
Hard write errors
162
Viewing and Specifying a Devices Media Types

Use the Media Types tab of a devices Properties dialog box to view media types that can be placed in the device and to specify whether these media types can be used for read or write operations. 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 device 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 beside the media type, that media entry is available for use when creating a bar code rule. You can specify that the device be limited to performing read and write operations on specific media types. For example, if your devices documentation states that the device 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. To view a devices media type properties: 1. On the navigation bar, click Devices.
4. Under General Tasks in the task pane, select Properties, and then on the Drive Properties dialog box, click Media Type. The Media Types tab provides the following information:
Media type options for a device 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.
163
Using Robotic Libraries with Backup Exec Media type options for a device (continued) Item Read Description Displays Yes if this media type can be read by the device; otherwise, displays No. Displays Yes if this media type can be written to by the device; otherwise, displays No.
Write
Related Topics: Viewing and Using Device Properties and Statistics on page 151 Bar Code Rules in Mixed Media Libraries on page 236
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 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. The operator inserts six blank tapes and targets backup jobs to various media sets within the robotic library. Depending on whether the backups are overwrite or append jobs, Backup Exec automatically allocates available tapes in the robotic library. If a job exceeds the capacity of one
164
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; for example, media in slot 2 would be selected before equivalent media in slot 4. If a job requiring overwritable media is targeted to a robotic library and no overwritable media is available, the job is skipped and the next job targeted to the robotic library is queued. When overwritable media becomes available either by the addition of media to the robotic library or by the overwrite protection period expiring for a media currently in the robotic library, the skipped job will run. Related Topics: Symantec Backup Exec - Library Expansion Option on page 1115
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, then on the Tools menu, click Serial Numbers and Installation, 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 the 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 from the Tools menu, click Wizards, and then click Device Configuration Wizard. Make sure that each device in the robotic library is properly associated with the robotic library. If a robotic library appears in the backup devices list as a stand-alone drive, 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.
165
During startup, if there is media in the storage devices in the robotic library, Backup Exec attempts to return the media to its original magazine slot. If the media cannot be returned to the slot, an error message appears requesting that the media be ejected from the storage device. Related Topics: Setting Up Robotic Library Hardware on page 1115 Installing Backup Exec on page 65 First Time Startup Wizard on page 108 Setting Up Cleaning Jobs on page 204
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. Related Topics: Viewing General Robotic Library Properties on page 166 Viewing Robotic Library Configuration Properties on page 169 Viewing SCSI Information for a Robotic Library on page 170 Viewing Statistics for a Robotic Library on page 171
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, and to change its status.
166
To view general properties of a robotic library: 1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries. 3. Select the robotic library. 4. Under General Tasks in the task pane, select Properties, and then on the Library Properties dialog box, click General. The General tab provides the following information:
General properties options for robotic library Item Name Description Name of the robotic library. You can rename the device by typing a new name in this field.
167
Using Robotic Libraries with Backup Exec General properties options for robotic library (continued) Item Status Description
Pause: Select this check box to pause the device, and then click OK. Enable: Select this check box in order for Backup Exec to use this device. Clear this check box to disable the device, and allow it to be available for other applications. If the box is clear, the device is disabled, and cannot be used by Backup Exec. After changing the option, click OK. Online: If the device is online, the check box appears dimmed, with a check mark. If the device is offline, the check box is available, with no check mark. To bring the device online, check Online. No operations are allowed on the device until it is online again. The device was turned off after Backup Exec was started. The device was being used by another application (such as a Windows backup utility) when Backup Exec was started. The device is removed from the computer. A tape drive failure occurred. A tape is stuck in the drive. The firmware of the device was updated; Backup Exec will behave as if the device with its old name or identity no longer exists.
The device is displayed as offline if:

To put the device online, try the following:
Check to make sure the device has power and that cables are properly attached. Turn the device on and reboot the server, or stop and restart the Backup Exec services. Stop the utility that is using the device, and then reboot the server, or stop and restart the Backup Exec services. To restart the Backup Exec services: For Windows 2000, Windows XP, and Windows Server 2003, go to Computer Management, select System Tools, select Services, and then select Applications. If the device firmware has changed, delete the device and restart Backup Exec services. After the device appears with its new firmware identity, retarget all jobs that were using the old device name to the new device name.
Vendor Product ID 168
Name of the vendor of the robotic library. Product ID from the SCSI Inquiry string. Administrators Guide
Using Robotic Libraries with Backup Exec General properties options for robotic library (continued) Item Firmware Library type Date in service Serial number Description Version of the firmware used in the device. Manufacturer and model number of the robotic library. Date this device was first detected by Backup Exec. Serial number of the robotic library.
Related Topics: Viewing Properties of a Robotic Library on page 166
Viewing Robotic Library Configuration Properties

Through the Configuration tab of a robotic librarys properties dialog box, you can enable startup initialization for the robotic library, enable bar code rules, enable Removable Storage, and specify slot base numbering. To view configuration properties of a robotic library: 1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries. 3. Select the robotic library. 4. Under General Tasks in the task pane, select Properties, and then on the Library Properties dialog box, click Configuration. The Configuration tab provides the following information:
Configuration properties options for robotic library Item Enable startup initialization Description Select this option to have Backup Exec initialize the robotic library when Backup Exec is started. Depending upon the robotic library, initialization can include reading all bar code labels on media. Select this check box to enable bar code rules (see Bar Code Rules in Mixed Media Libraries on page 236).
Enable bar code rules
169
Using Robotic Libraries with Backup Exec Configuration properties options for robotic library (continued) Item Enable Removable Storage (RSM) Description 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 189. 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.
Viewing SCSI Information for a Robotic Library

To view SCSI information properties of a robotic library: 1. On the navigation bar, click Devices.
2. Expand the server icon in the tree view, and then click Robotic Libraries. 3. Select the robotic library. 4. Under General Tasks in the task pane, select Properties, and then on the Library Properties dialog box, click 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 Description Device information that is read from the device firmware.
170
Using Robotic Libraries with Backup Exec SCSI Information for a robotic library (continued) Item Port Description Identifying number of the port on the server to which the device is attached. Identifying number of the bus to which the device is attached. Unique SCSI ID number (physical unit number). Logical Unit Number of the device.
Bus Target ID LUN
Viewing Statistics for a Robotic Library

To view statistics properties of a robotic library: 1. On the navigation bar, click Devices. 2. Expand the server icon in the tree view, and then click Robotic Libraries. 3. Select the robotic library. 4. Under General Tasks in the task pane, select Properties, and then on the Library Properties dialog box, click Statistics. The Statistics tab of a robotic librarys properties dialog box provides the following information:
Statistics 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.

Creating Robotic Library Partitions

You can group one or more robotic library slots into partitions. Partitioning robotic library slots provides more control over which media is used for backup jobs. When you set up robotic library partitions, Backup Exec creates a device pool for each partition. Jobs targeted to a partition device pool run on the media located in the partitions slots. For example, if you set up a partition that contains slots 1 and 2 and you want to run a weekly backup only on the media in these slots, you would submit the job to the partition device pool containing slots 1 and 2. The partition device pools appear in the Devices view under the Device Pools icon. If the robotic library is partitioned, Backup Exec searches for the oldest recyclable media in the targeted partition only. If more than one media meeting the requirements is found, Backup Exec then selects the media in the lowest-numbered slot; for example, media in slot 2 would be selected before equivalent media in slot 4. In order to fully benefit from Backup Execs partition management feature, Symantec recommends that you create a partitioning scheme that best matches the manner in which you want to control your backups. For example, some administrators may feel that network backups are best managed by allowing access to partitions based on users and groups, while others may want to base their partitions on operation types (Backup, Tape Rotation, Archive, etc.). To create partitions: 1. On the navigation bar, click Devices. 2. Expand the server icon, and then click Robotic Libraries. 3. Select the robotic library containing the slots that you want to partition. 4. Under Robotic Library Tasks in the task pane, select Configure partitions. 5. Select the robotic library slots to include in each partition by clicking the slots on which each new partition should begin. A partition divider that lists the range of slots included in the partition is inserted wherever you click. For example, if you want to create two, 5-slot partitions on a robotic library with 10 slots, click Slot 1 and Slot 6. In this example, Slots 1-5 will be included in the first partition and Slots 6-10 will be included in the second. Partitions can include any number of robotic library slots; however, the first partition cannot be moved or deleted when other partitions exist.
172
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
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 the selected partition divider down to decrease the number of slots in the partition. (The number of slots in the preceding partition is increased.) Remove all partition settings.
Move Up
Move Down
Remove All
7. Click OK after completing the configuration of your partitions.
173
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. For example, if a robotic library that had been partitioned with:
Partition 1 Partition 2 Partition 3
Slots 1 - 2 Slots 3 - 4 Slots 5 - 10
is repartitioned so that:
Partition 1 Partition 2 Partition 3
Slots 1 - 4 Slots 5 - 6 Slots 7 - 10
174
Then any jobs targeted to the old partition 2 (slots 3-4) must be retargeted. Note If a job is targeted to a particular robotic library drive (or a device pool that is not a partition drive pool), the job defaults to the first partition in the robotic library. Related Topics: Creating Robotic Library Partitions on page 172 Retargeting Jobs from a Deleted Device Pool or Media Set on page 137
175
Using Backup-to-Disk Folders and Files

The Backup-to-Disk feature enables you to back up data to a folder on a hard disk, and 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 backup process where you back up data to disk first and then transfer the data to a tape when more time is available. Before using Backup-to-Disk, create a backup folder, which is a virtual device that Backup Exec treats as any real device. Backup folders can be part of device 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 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. Disaster recovery from virtual devices, such as Backup-to-Disk devices, must be done via Remote IDR using a media server with access to the virtual device. Related Topics: Viewing Devices on page 125
176
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) Symantec 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-RW DVD-RW ZIP JAZZ Removable hard disk
For CDR-RW 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.
The New Backup-to-Disk Folder dialog box appears. 4. Select the appropriate options as follows, and then click OK:
New Backup-to-Disk Folder options Item Name Description Type a name for this folder. Note Backup folder names must not exceed 243 characters. Path or Drive 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 browse to 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) Symantec 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, Symantec recommends that you do not select this option if you want to use removable media, such as a zip drive.
178
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-RW DVD-RW ZIP JAZZ Removable hard disk
For CDR-RW 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 to set a default path for all future backup folders. Then, type or select the default path.
The folder appears on the Devices tab below the Backup-to-Disk Folders or Removable Backup-to-Disk Devices icon, depending on which type you created, and the All Devices icon. It also appears in Windows Explorer as a folder. You can back up data to this folder now. Related Topics: Viewing Devices on page 125
179
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 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

To change the path of a backup folder, you must first create a new backup folder, and then 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 Scan on the shortcut menu, or select the new backup folder and press <F5>. 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. Related Topics: Adding a Backup Folder on page 177 Renaming a Backup Folder on page 180 Deleting a Backup File on page 187
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. To delete a backup folder: 1. On the navigation bar, click Devices. 2. Under the server icon, click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices. 3. Select the backup folder that 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. 7. Right-click the folder that you want to delete, and then on the shortcut menu, click Delete.
181
8. When prompted to delete the folder, click Yes. The folder is removed from the disk. You cannot recreate the folder or the files.
Recreating a Backup 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 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. Related Topics: Adding a Backup Folder on page 177 Inventorying Media in Devices on page 193
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, after you correct the problem, you can select the folder and then under Devices task in the task pane, select Online.
182
To pause or resume a backup folder: 1. On the navigation bar, click Devices. 2. Expand the icon for the computer where the backup folder is located. 3. Click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices. 4. Select the backup folder you want to pause or resume. If the backup folder is currently paused, this status is displayed next to the backup folder name in the Devices tree view. 5. Under Device Tasks in the task pane, select Pause. If the folder was not already paused, it is now paused. If the folder was already paused, it is now resumed.
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 folder 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 computer where the backup folder is located. 3. Click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices. 4. Select the folder you want to view. 5. Under General Tasks in the task pane, select Properties.
183
Viewing Backup Folder General Properties

To view general properties of a backup folder: 1. On the navigation bar, click Devices. 2. Expand the icon for the computer where the backup folder is located. 3. Click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices. 4. Select the folder you want to view. 5. Under General Tasks in the task pane, click Properties, and then click the General tab. General properties of the backup folder include:
General Backup Folder Properties dialog box Item Name Status Description Name of the backup folder. You can type a new folder name here.
Pause: Select this check box to pause the device, and then click OK. Enable: Select this check box in order for Backup Exec to use this device. Clear this check box to disable the device, and allow it to be available for other applications. If the box is clear, the device is disabled, and cannot be used by Backup Exec. After changing the option, click OK. Online: If the device is online, the check box appears dimmed, with a check mark. If the device is offline, the check box is available, with no check mark. To bring the device online, check Online. No operations are allowed on the device until it is online again.
Path
The path to the folder.
184
Using Backup-to-Disk Folders and Files General Backup Folder Properties dialog box Item Priority Description The Priority field is only available when the backup folder belongs to a device pool and is selected for viewing under the device 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 Devices in a Device Pool on page 135. Set a priority for a backup folder that determines the order in which the devices in a device pool are used. In the Priority box, type a number from 1 to 99, with 1 designating this device as the first device to be used in the device pool, or click the arrows to select a value. The default priority is 10 so all devices have the same priority initially. The device to which you assign the lowest number is the first device to be used in the device pool; for example, a device with a priority of 1 is used before a device with a priority of 5. Note Overwrite and append periods for media take precedence over device priority.
Viewing Backup Folder Configuration Properties

To view general properties of a backup folder: 1. On the navigation bar, click Devices. 2. Expand the icon for the computer where the backup folder is located. 3. Click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices. 4. Select the folder you want to view. 5. Under General Tasks in the task pane, click Properties, and then click the Configuration tab.
185
6. Enter or change information as appropriate, and then click OK:

Configuration properties for Backup-to-Disk folder 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 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.
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
Buffered writes
Concurrent Operations Allow x concurrent operations for this Backup-to-Disk Folder 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.
186
Renaming a Backup File

When you rename a backup file, the name changes in Backup Exec, on the disk, and on the media label. To rename a backup file: 1. On the navigation bar, click Devices. 2. Double-click the icon for the computer where the backup folder is located. 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. When prompted to delete the backup file, 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.
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. Click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices. 4. Select the folder where the backup file was located before you deleted it. 5. Under Media 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. Related Topics: Inventorying Media in Devices on page 193
188
Using Microsofts Removable Storage Feature with Backup Exec

Removable Storage is a feature of Windows 2000, Windows XP, and Windows Server 2003 computers that allows applications to share removable storage devices. Removable Storage performs requests for device access from different applications on a first in, first out basis. It also tracks media usage for online media (media currently mounted in a robotic library) and for offline media that has been installed previously in a robotic library. Removable Storage does not manage single-slot tape drives. On the media server, you can allow Removable Storage to share the devices in robotic libraries between two or more applications, or you can allow some or all devices in robotic libraries to be controlled and used exclusively by Backup 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 169), Backup Exec uses Removable Storage for device and media operations; if the Enable Removable Storage option 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 (Microsoft Management Console) to disable all of the drives in the robotic library. This allows Backup Exec to control the robotic library and all of the drives. If you do not need to share the devices, exclusive use by Backup Exec will allow faster tape backups and restores. If you allow exclusive use by Backup Exec, you can still enable or disable devices in Removable Storage while Backup Exec is running; Backup Exec will respond by switching to other devices in the robotic libraries as appropriate. 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 464. 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."
189
Only Microsoft tape class drivers can be used if you plan to use Backup Exec and the Removable Storage feature. If you want to use a third party tape class driver or a Symantec tape class driver, you must disable the device through Removable Storage before installing the driver.
Using Media in Drives Managed by Removable Storage

Use the Removable Storage snap-in to manually control the movement of media into and out of the robotic libraries managed by Removable Storage, to allocate media to one application process or another, and to prepare new, imported, or unrecognized media for use within the Removable Storage domain. You must use appropriate processes to move media between applications. Media that is assigned by Removable Storage to an application other than Backup Exec cannot be accessed by ADAMM. Media in the Removable Storage Import and Free media pools are available for use in Backup Exec, and can be assigned to Backup Exec using one of the following methods:
In Computer Management on the local computer, under the Storage node, open Removable Storage, and then open Media Pools. Move media from the Import or Free media pools into a Backup Exec media pool (see your Microsoft Windows 2000 documentation or online help for details). The next time that Removable Storage is scanned, any media that is in the Backup Exec pool is allocated to Backup Exec and marked as "in use" by Backup Exec. Acquire available media through normal Backup Exec operations. This media is then placed in the Removable Storage Import pool and can be accessed by Backup Exec using the policies you established for Imported media.
Media that is in the Removable Storage Free media pool or that is unrecognizable by Removable Storage is marked as unknown media within Backup Exec. You must run an Inventory job to mount and read the media header. The media is imported into Backup Exec and marked as "in use" by Backup Exec. If you do not want that media used by Backup Exec, delete it from the ADAMM database. For more information, see Deleting Media on page 252. 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.
190
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 169). Symantec recommends enabling or disabling devices using Removable Storage only when the device is not in use and the internal drives are empty.
Monitoring Backup Exec and Removable Storage

To view the Removable Storage Work Queue: 1. Click Start, and then point to Programs. 2. Point to Administrative Tools, and then click Computer Management. 3. Expand the tree view of Storage. 4. Expand Removable Storage, and then click Work Queue. You can also track the location and status of media by viewing the media and drive objects associated with the loader being shared with Backup Exec. The status of the media is updated as the media is moved.
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.
191
Creating Utility Jobs

Backup Exec includes utility jobs that aid in managing devices and media. You can specify a job priority and a recipient for notification when these jobs run. Utility jobs, 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 device Erase media in a robotic library or device Import media Export media Export expired media (robotic libraries only) Lock robotic library Unlock robotic library Clean drive
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.
192
Inventorying Media in Devices

Run Inventory to mount the media in the device and read the media label, which is then displayed in the Devices view. If this is the first time that Backup Exec has encountered this media, the media label is also added to the Media view. If you change the media in the robotic library or device, run Inventory so that the current media in the device is displayed in the views; otherwise, the previous media is still displayed as being in the device. You should run an inventory operation when Backup Exec is started for the first time following a new installation or a product upgrade. When Backup Exec is exited and restarted, it saves information pertaining to the location and contents of all of the media from the last Backup Exec session (provided the media in the devices hasnt changed). With this information, Backup Exec can immediately begin processing operations when it is restarted. When media is changed in a robotic library, you can inventory all of the slots in the robotic library or select the slots to be inventoried. You are not required to re-inventory slots when adding media requested by Backup Exec. For example: 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.
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 Settings, click Preferences. 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 computer where the backup folder is located.
b. Double-click Backup-to-Disk Folders. c. Double-click either Backup-to-Disk Folders or Removable Backup-to-Disk Devices.
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.
5. Under Media Tasks in the task pane, select Inventory. 6. Select the appropriate options as follows:
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 Administrators Guide
194
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 Notification on page 534). 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 398). There may be a delay (up to several minutes for some drives) as the media is mounted and inventoried. The inventory operation can be monitored or canceled through the Job Monitor. Related Topics: Media Labeling on page 234 Inventory all drives on Backup Exec services startup on page 120
Erasing Media
You can erase media using either Quick erase or Long erase. Not all devices support a long erase; those that do not can only perform a quick erase. Quick erase writes an indicator at the beginning of the media that makes the data contained on the media inaccessible. For most uses, a Quick erase is sufficient. Long erase instructs the drive to physically erase the entire media. If you have sensitive information on the media and you want to dispose of it, use Long erase. Running Long erase on media can take several minutes to several hours to complete (depending on the drive and the media capacity). Quick and Long erase do not change the media label. To change a media label, use Label Media or Rename prior to the Erase operation. To erase media: 1. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, or if the device resides in a robotic library, click Robotic Libraries. 3. Select the drive or slot containing the media you want to erase. 4. Under Media Tasks in the task pane, select either Erase media, quick or Erase media, long.
195
Note If the drive does not support a long erase, Erase media, long will not be available. The following warning is displayed: "This operation will be performed on the current media in the drive or slot. If the media has been changed since the last inventory operation was performed, the media label in the next dialog may not match the media in the drive or slot selected." 5. Click OK to continue. The media displayed was read during the last inventory operation; the display does not change until another inventory operation occurs. Therefore, if you change media in the slot or drive but did not run Inventory, the media label displayed may not match the actual media in the slot or drive. 6. When prompted, click Yes to erase the media. 7. Select the appropriate options as follows:
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
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 Notification on page 534). 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 398). 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.
196
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 187.) 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 computer 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. 8. Select the appropriate options as follows:
Erase media options Item Job name Description Type a name for the job or accept the default name.
197
Creating Utility Jobs Erase media options (continued) Item Job priority Description Select the priority for the job. Available options are:

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 Notification on page 534). 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 398).
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. 4. Under Media Tasks in the task pane, select Retension media.
198
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:

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 Notification on page 534). 7. Click Run now. The job will be submitted as a Run now job, unless you submitted the job on hold. You can monitor the Retension operation from the Job Monitor. You cannot cancel a Retension operation after it has started; however, you can use Cancel to stop a queued retension operation.
Formatting Media in a Drive

Use Format media to format the media currently in the drive. Most devices do not support formatting. If formatting is not supported, the option is not available. If you use Format on a DC2000 tape, the formatting may take two or more hours to complete. Caution Formatting erases the media. All data on the media is lost. 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.
199
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:

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 Notification on page 534). 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.
200
Labeling Media
Use Label media to immediately write a new media label on the media in the selected drive. This operation destroys any data on the media. To change the media label without destroying the data on the media (until an overwrite operation occurs), use Rename. To label media: 1. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, or if the drive is attached to a robotic library, click Robotic Libraries. 3. Select the drive or slot containing the media you want to label. 4. Under Media Tasks on the task pane, select Label media. The following warning is displayed: "This operation will be performed on the current media in the drive or slot. If the media has been changed since the last inventory operation was performed, the media label in the next dialog may not match the media in the drive or slot selected." 5. Click OK. 6. Type the name you want to use as the recorded media label for this media. Note This media will be overwritten. 7. Click OK to erase all data on the media and re-label the media. 8. Select the appropriate options as follows:
Label media options Item Job name Description Type a name for the job or accept the default name.
201
Creating Utility Jobs Label media options (continued) Item Job priority Description Select the priority for the job. Available options are:

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 Notification on page 534). 10. Click Run now. The job will be submitted as a Run now job, unless you submitted the job on hold. You can monitor the Label media operation from the Job Monitor. You cannot cancel a Label media operation after it has started; however, you can use Cancel to stop a queued Label media operation. 11. Write this same media label on an external label fixed to the outside of the physical media. Related Topics: Renaming Media on page 238
202
Ejecting Media from a Drive

Use Eject media to eject the media currently in the drive. If the media is a tape, Eject rewinds the tape before ejecting it. Some drives do not support a software-driven media eject. If the media is a tape, the tape is rewound and you may be instructed to manually remove it. To eject media from a drive: 1. On the navigation bar, click Devices. 2. Expand the server icon, click Stand-alone Drives, and then select the drive. 3. Under Media Tasks in the task pane, select Eject media. 4. Select the appropriate options as follows:
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:

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 Notification on page 534). 6. Click Run Now. The job will be submitted as a Run now job, unless you submitted the job on hold.
203
Setting Up Cleaning Jobs

You can submit once-only cleaning jobs, or set up scheduled cleaning jobs. Before submitting a cleaning job, you must define a cleaning slot that contains the cleaning tape. To define a cleaning slot: 1. On the navigation bar, click Devices. 2. Click Robotic Libraries, and then click the drive or robotic library for which you are setting up the cleaning. 3. Click Slots to display the librarys slots in the right pane. 4. Select the slot that contains the cleaning tape. 5. Under Device Tasks in the task bar, select Clean. 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 drive or robotic library containing the drive, and then select the drive. 3. Under Device Tasks in the task pane, select Clean. 4. Select the appropriate options as follows:
Clean Robotic Library Drive options Item Job name Description Type a name for the job or accept the default name.
204
Creating Utility Jobs Clean Robotic Library Drive options Item Job priority Description Select the priority for the job. Available options are:

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 Notification on page 534). 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 398). 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 Device Properties and Statistics on page 151.
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.
205
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:

7. If you want Backup Exec to automatically create an inventory job to run after the import job completes, double-click Settings, click Options and select Auto-inventory after import is completed. 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 Notification on page 534). 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 398). You can monitor the import job through the Job Monitor.
206
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. 6. Select the appropriate options as follows:
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:

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 Notification on page 534). 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 398). 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. 4. Select the appropriate options as follows:
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:

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 Notification on page 534). 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 398). 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. 4. Select the appropriate options as follows:
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:

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 Notification on page 534). 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 398). You can monitor the unlock job through the Job Monitor.
Exporting Expired Media

The export expired media job allows you to automate media handling in robotic libraries by removing media that cannot be written to so that scratch media can easily be added to the library in preparation for the next backup window. Expired media is any media that cannot be written to. When you export expired media from the robotic library, the media status is displayed as offline. If the media is in a media set that has a vault media rule, then the media is moved to the vault location. Cleaning media can be exported with the export expired media job. You can include all cleaning media, or all cleaning media that has been used more than a specified number of times. You can choose to be prompted as a reminder to import new media after an export expired media job completes successfully.
209
To export expired media from a robotic library: 1. On the navigation bar, click Devices. 2. Select the robotic library. 3. Under Robotic Library Tasks in the task pane, select Export expired media. 4. On the Export Job Properties pane, under Settings, click General, and enter information as necessary:
Export expired 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:

5. To set options for the export expired media job, on the Properties pane, under Settings, click Options, and select the following as appropriate:
Export expired media Job options Item Include cleaning media in export Description Select this check box to include cleaning media in the export of expired media.
Export cleaning media Select the number of times that the cleaning media can be used used more than x times before it is exported by this job. After export, automatically prompt for new media to be imported Select this check box to be prompted to import new media to the slot after the export expired media operation has completed.
210
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 Notification on page 534). 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 398). You can monitor the export expired media job through the Job Monitor.
211
212
Chapter
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 can locate 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
213
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). These two restrictions, the append period and the overwrite protection period, are applied to groups of media, called media sets. Media sets are media that have the same append period and the same overwrite protection period.
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 and 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 and is measured from the time of the last write to the media, that is, at the end of the last append or overwrite job. It can be specified in hours, days, weeks, or years. When the overwrite protection period is over, the media becomes recyclable and can be overwritten.
214
Media Overwrite Protection Append Periods and Overwrite Protection Periods

The Append Period begins when the media is allocated to a Media Set.
APPENDPERIOD
The Overwrite Protection Period is measured from the time of the last write to the media. During the Append Period, data can be added to the media. Any data already on the media is protected against loss. The Append Period ends. After the Append Period expires, and while the Overwrite Protection Period is still active, data cannot be added to the media. Any data already on the media is protected against loss. The Protection Period expires. 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
OVERWRITE PROTECTION PERIOD
TIME
New data
TIME
After the Overwrite Protection Period expires, the media becomes Recyclable. This means that new data can be written to the beginning of the media by a new backup job (causing loss of the original data).
Old data
The append and overwrite protection periods that you specify apply to all the data on the media. Therefore, each time data is written to a media, the time remaining in the overwrite protection period is reset and the countdown restarted.
Chapter 5, Managing Media
215
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
Protection Period 14 Days
The media can be overwritten at this time
First Day
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Normal Bkup Normal Bkup
Second Day
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Normal Bkup Normal Bkup Normal Bkup Normal Bkup Normal Bkup
1 1 2 1 23 1 234
Fifth Day
Because the overwrite protection period does not begin until the job completes, the amount of time that the job takes to complete affects the amount of time until the media can be overwritten. For example, suppose that you create a media set named Weekly with an overwrite protection period of seven days, and an append period of 0 days, and you schedule a full backup job to run each Friday at 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 account for 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.
216
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 risk 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. Related Topics: Creating Media Sets on page 218 Deleting a Media Set on page 221 Renaming a Media Set on page 222 General Media Set Properties on page 223
217
Creating 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. When you create a media set, you can also specify vault rules, which allow you to set dates for when media should be moved to or returned from a media vault. You must physically move the media to and from the vault, but by enabling vault rules, you can use a wizard to print or view reports that contain details on which media are ready to be moved, and to update the media location (see Update Media Vaults by Using a Wizard on page 245). If your environment includes remote sites, you should create separate media sets for each remote site, so that if vault rules are enabled, the reports contain details on which media are ready to be moved for just that site. To create a media set: 1. On the navigation bar, click Media. 2. Under Media Set Tasks in the task pane, click New Media Set. 3. On the General tab, select the appropriate options as follows, and then click OK:
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.
218
Media Overwrite Protection 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. To specify vault rules to set dates for when media should be moved to or returned from a media vault, click the Vault Rules tab.
219
5. Select the appropriate options as follows, and then click OK.

New Media Set, Vault Rules tab Item Select the media vault to use with this media set: Description Click the drop-down arrow to select a media vault. This media vault will be used to store the media in this media set that meet the move and return time periods. Before the media location can be updated, even if the move and return dates are overdue, you must run the task Update vault using wizard (see Update Media Vaults by Using a Wizard on page 245). This wizard can print reports that detail which media are ready to move to and return from the vault, and can update the location of the media if you choose to move them. However, you must physically collect the media, and move the media to and from the vault. Move media to this vault x after it Specify a time period after which this media will be can no longer be written to reported as ready to be moved to this vault. Return media from this vault x after it was sent to the vault Specify a time period after which this media will be reported as ready to be returned from this vault.
Related Topics: Media Overwrite Protection on page 213 Deleting a Media Set on page 221 Renaming a Media Set on page 222 General Media Set Properties on page 223 Vault Rule Properties for Media Sets on page 225 Update Media Vaults by Using a Wizard on page 245
220
Running the Media Set Wizard

The Media Set Wizard guides you through the process of creating a new media set, and may be helpful if you are new to Backup Exec or are unfamiliar with the concepts and terminology of media sets. Before you run this wizard, you should understand media overwrite protection and append periods. For an overview of these terms, see Media Overwrite Protection on page 213. If you do not need a wizard to set up a new media set, see Creating Media Sets on page 218. To run the Media Set Wizard: 1. On the Tools menu, point to Wizards. 2. Click Media Set Wizard, and then follow the instructions. If you set the media overwrite protection level to Full, you must have blank media ready and online before the first backup job runs. If you plan to use imported media, you must inventory it first.
Deleting a Media Set

Use Delete to remove a media set from the Media Sets category. If you delete a media set to which scheduled jobs are targeted, you are prompted to retarget the jobs to another media set. You cannot delete a media set that 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.
221
5. If there are scheduled jobs allocated to the deleted media set, you are prompted to redirect the jobs to another media set. 6. In the Media Set selection box, click the Down arrow to see more options, and then select the new media set to which you want to redirect the scheduled jobs. 7. Click Yes to redirect the displayed job to the selected media set, or if there are multiple scheduled jobs, click Yes to All to redirect all scheduled jobs to this media set without further prompting. The scheduled jobs are redirected.
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, and then click OK.
222
General Media Set Properties

On general media set properties, you can change the:

Name of a media set Overwrite protection and append periods for a media set Media vault and the vaulting periods associated with a media set.
To change or view general media set properties: 1. On the navigation bar, click Media. 2. In the Media selection pane, under Media Sets, select a media set. 3. Under General Tasks on the task pane, click Properties. 4. To change the media set name or overwrite or append periods, click the General tab. The Media Set Properties General tab appears. 5. Select the appropriate options as follows, and then click OK:
Media Set properties, General tab Item Name Description View or change the media set name. 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. See Renaming a Media Set on page 222. Creation date Date when the media set was created.
223
Media Overwrite Protection Media Set properties, 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 is measured from the time of the last write to the media, that is, at the end of the last append or overwrite job. For example, setting the overwrite protection period for seven days and the append period for four days ensures that data will not be overwritten for at least seven days, and that data can be appended to the media for the next four days. The last data appended to this media is retained for seven days. Because of the method Backup Exec uses to compute time, the unit of time that you enter may be converted. For example, if you enter 14 days, the next time you view this property, it may be displayed as two weeks. The default is Infinite - Dont Allow Overwrite, which protects the media from being overwritten for 1,000 years, unless the media is erased, formatted, labeled, 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 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. Description
224
Vault Rule Properties for Media Sets

On the vault rule properties for media sets, you can add or change:
The media vault that you want the media in this media set sent to after a period of time. The amount of time to wait after the media cannot be written to before sending it to the vault. The amount of time to return the media from the vault after it was first sent.
The media are not automatically moved to or from the vault. Use the task Update vault using wizard to print or view reports that contain details on which media are ready to be moved to and from the vault, and to update the media location. For more information, see Update Media Vaults by Using a Wizard on page 245. To change or view vault rule properties for media sets: 1. On the navigation bar, click Media. 2. In the Media selection pane, under Media Sets, select a media set. 3. Under General Tasks on the task pane, click Properties. 4. Click the Vault Rules tab. The Media Set Properties, Vault Rules tab appears. 5. Select the appropriate options as follows, and then click OK:.:
Media Set Properties, Vault Rules tab Item Select the media vault to use with this media set: Description Click the drop-down arrow to select a media vault. This media vault will be used to store the media in this media set that meet the move and return time periods. Before the media location can be updated, even if the move and return dates are overdue, you must run the task Update vault using wizard (see Update Media Vaults by Using a Wizard on page 245). This wizard can print reports that detail which media are ready to move to and return from the vault, and can update the location of the media if you choose to move them. However, you must physically collect the media, and move the media to and from the vault.
225
Media Overwrite Protection Media Set Properties, Vault Rules tab (continued) Item Description
Move media to this vault x after it Specify a time period after which this media will be can no longer be written to reported as ready to be moved to this vault. Return media from this vault x after it was sent to the vault Specify a time period after which this media will be reported as ready to be returned from this vault.
Related Topics: Update Media Vaults by Using a Wizard on page 245 Creating Media Sets on page 218
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, and overwrite scratch media. 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 231 illustrates the media overwrite protection level. Related Topics: Setting Default Media Options on page 239
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 126. 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.
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.
Scratch Media. Media that do not belong to a media set and can be overwritten, including:

New or blank media. Media that you have moved from another group, such as a media set or Imported Media. Erased media.
Cleaning Media. All cleaning media. Imported Media. Media created by a product other than this installation of Backup Exec. By default, Imported media have an overwrite protection period of Infinite, but can still be overwritten if the media overwrite protection level is set to Partial or None. You can overwrite imported media using several methods. Data can be restored from imported media until that media is overwritten. Other media pools that are contained in Imported Media are:
Backup Exec and Windows NT Backup Media. Media from another installation of Backup Exec. Backup Exec Archive Media. Media that was used for archive jobs. Foreign Media. Media from a product other than Backup Exec.
227
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 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.
228
Note In a device pool, Backup Exec selects the oldest recyclable media in all of the devices in the device pool to use first. In a robotic library, Backup Exec selects the oldest recyclable media in the library to use first. If the robotic library is partitioned, Backup Exec searches for the oldest recyclable media in the targeted partition only. Caution It is recommended that you physically write-protect media containing critical data by using the write-protect tab on the media cartridge to protect against unintentional move or erase operations, or expired overwrite protection periods. Related Topics: Setting Default Media Options on page 239
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
229
Media Overwrite Protection How Backup Exec searches for overwritable media (continued) Overwrite protection level and overwrite option: Partial + Overwrite recyclable media first Media is overwritten in this order:
1. Recyclable media in the targeted media set 2. Scratch media 3. Recyclable media in any media set 4. Imported media
None - No overwrite protection + overwrite scratch media first Caution This option is not recommended because it does not protect data from being overwritten.
1. Scratch media 2. Recyclable media in the targeted media set 3. Recyclable media in any media set 4. Imported media 5. Allocated media in any media set 1. Recyclable media in the targeted media set 2. Scratch media 3. Recyclable media in any media set 4. Imported media 5. Allocated media in any media set
None - No overwrite protection + overwrite recyclable media first Caution This option is not recommended because it does not protect data from being overwritten.
230
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) Media Overwrite Option can reverse these, causing the Scratch media set to be examined second rather than first.
Scratch Media
Scratch Media
Recyclable Media (current user media
Recyclable Media (other media sets)
Recyclable Media (other media sets)) Imported Media
Imported Media
Allocated Media
Allocated Media
With the Media Overwrite Options, you can make Backup Exec favor scratch media over the expired (recyclable) media in the Media Set of the current job (on the right side of this page), or favor the latter over the former (on the left of this page).
When Backup Exec is unable to locate usable media, it prompts you to provide one.
The most obvious candidates for backup jobs requiring overwritable media are scratch media and recyclable media (media with expired overwrite protection periods). These are the first types of media for which Backup Exec searches when a backup requires media to overwrite. The search pattern is different according to whether you have chosen Full, Partial, or None. The media indicate that a type of media set is examined for availability. In addition to setting overwrite protection levels, you must set overwrite options, which set the order in which Backup Exec searches for overwritable media. Related Topics: Media Overwrite Options on page 228
Chapter 5, Managing Media 231
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 229.
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 device 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.
Related Topics: Creating a Backup Job on page 261
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.
232
Label the media. The Label Media operation immediately writes a new media label on the media, which destroys any data contained on the media. Format the media. Formatting destroys any data contained on the media. Change the overwrite protection period for the media set so that it is expired. Select the media set, and then under General Tasks, click Properties.
Related Topics: Deleting Media on page 252 General Media Set Properties on page 223 Media Overwrite Options on page 228
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. Related Topics: Deleting Media on page 252 Viewing Statistics for Media Properties on page 255 Failed Backup Jobs Report on page 576
233
Media Labeling
Media Labeling
Media used in Backup Exec is identified by its media label. When new, blank, or unlabeled media is used during a backup operation, Backup Exec automatically labels the media. This label consists of a prefix that identifies the cartridge type, and an incrementing number. For example, if the media is a 4mm tape, then the prefix would be 4M, followed by 000001. The next media label generated for an unlabeled 4mm tape would be 4M000002, and so on. You can allow the media label to be assigned automatically by Backup Exec, or you can specify a label prefix and number to be assigned for a type of media. For example, you can specify that all 4mm media that are entered for the first time into this installation of Backup Exec are labeled with a prefix of ACCT, and with numbering starting from 1000. You can specify another media type to be labeled with a prefix of FIN, and with numbering starting at 10,000. Customizing labels in this manner can help you recognize and organize media. Another type of media label used by Backup Exec is the media ID, which is a unique label assigned by Backup Exec to individual media used in Backup Exec. The media ID is used internally by Backup Exec in order to keep statistics on each media. Because the media label or bar code label for media can be changed, Backup Exec must use the media ID, which cannot be changed or erased, to preserve continuity in record keeping for each individual media. The media ID has no effect on the media label, or on your ability to rename, label, or erase media. At times, you may need to use the media ID to distinguish media that have duplicate media labels. Duplicate labels can be automatically generated in instances when Backup Exec is reinstalled or media from another Backup Exec installation is used. Use the media ID to distinguish between duplicate labels. You can view the media ID in a medias property page. Write the media label on an external label fixed to the outside of the physical media. Whenever you change the media label, you should also change the external label to match. 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.
234
Media Labeling
Related Topics: Setting Default Media Options on page 239 Labeling Media on page 201 Bar Code Labeling on page 235 Renaming Media on page 238 Viewing General Media Properties on page 253
Imported Media Labeling

Backup Exec does not automatically relabel imported media. The imported medias existing label is read and displayed in the Media view, in one of the Imported Media sets. Additionally, the imported medias original media label is displayed under the heading Media Description in the Results pane of the Media view. You can edit the media description in the medias property page to make it a more descriptive label. If the media overwrite protection level is set to Partial or None, the imported media may be selected for a job and be overwritten. The imported media is automatically labeled when it is overwritten during a job. If you want to label a specific imported media while maintaining full media overwrite protection for other imported media, erase the specific media and then label it. Related Topics: Viewing General Media Properties on page 253
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
235
Media Labeling
scans the bar code ID on the media label. Backup Exec selects this media for the operation and detects that a bar code label has been assigned to the media. Backup Exec automatically uses the bar code label and continues the operation. When you change magazines or insert new media in a magazine, bar code readers allow you to quickly update slot information by right-clicking the slot (or slots) and selecting Scan. Related Topics: Media Labeling on page 234
Bar Code Rules in Mixed Media Libraries

If you have bar code support for a robotic library that uses different types of drives, you can create a bar code rule so that Backup Exec can identify which media type to use in a drive. When Backup Exec reads the bar code rule, it locates the type of media that corresponds to the prefix or suffix and then mounts the media into a drive that accepts that type of media. After setting up bar code rules, you must set up two more items in order for the bar code rules to work:
Enable the bar code rules for the robotic library by selecting the bar code rules option on the Configuration tab in the robotic librarys properties. For each drive in the mixed media library, indicate what type of media can be used and whether that media can be used for read or write operations. To set this up, see Viewing and Specifying a Devices Media Types on page 163.
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. 3. Click New. 4. Select the appropriate options as follows:
Add Bar Code Rule dialog box Item Select a media type Description Select the media for which you want to add a bar code rule.
236
Media Labeling Add Bar Code Rule dialog box (continued) Item Vendor Description (Optional) Type the name of this librarys manufacturer. You can find the name of the library manufacturer on the librarys property page. This field is not case-sensitive. By typing a vendor name here, you restrict the bar code rule to that vendors libraries. If you are creating a general bar code rule that applies to libraries from different vendors, leave this field blank. Barcode prefix Type a code to be placed before the bar code that represents a media type. The code can be up to 16 characters, and any combination of letters and numbers. This field is not case-sensitive. Type a code to be placed after the bar code that represents a media type. The code can be up to 16 characters, and any combination of letters and numbers. This field is not case-sensitive.
Barcode suffix
5. Click OK to save the bar code 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 169. To change a bar code rule: 1. On the Tools menu, click Options. 2. In the Properties pane, under Settings, click Bar Code Rules. 3. Click Edit, and then change the options as needed. 4. Click OK to save the changes, and then click OK to exit. To delete a bar code rule: 1. On the Tools menu, click Options. 2. In the Properties Pane, under Settings, click Bar Code Rules. 3. Select a bar code rule to delete, and then click Delete. 4. Click Yes to verify that you want to delete the rule, and then click OK.
237
Media Labeling
Renaming Media
Use Rename to assign a new label to media. The new label is not actually written to the media until an overwrite operation occurs. All data on the media is preserved until the next overwrite job. However, the new media label is stored in the database and is displayed for that media. To write a new media label to the media immediately, use Label Media on the devices property page. The medias contents will be erased. If you rename a media, and then use it in another installation of Backup Exec, that media is treated as imported media, and the medias original media label is displayed; the renamed label is not transferred to other installations of Backup Exec. To rename a media label: 1. Do one of the following:
If the media is in a device, then from the navigation bar, click Devices, and then click that device to display the media. If you dont know where the media is, from the navigation bar, click Media, and then click All Media to display all media.
2. Select the media you want to rename. 3. Under General Tasks in the task pane, click Rename. 4. In Name, type a new media label, and then click OK. 5. Write this media label on an external label fixed to the outside of the physical media. Related Topics: Viewing General Media Properties on page 253
238
Setting Default Media Options
Setting Default Media Options

Use this procedure 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. 3. Select the appropriate options as follows, and then click OK:
Media Options - Set Application Defaults dialog box 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.
Partial - protect only allocated media
Select this option to allow imported and scratch media to be overwritten. Media in a media set that has an overwrite protection period that has not expired (allocated media), cannot be overwritten. This option is recommended if you have media from an earlier version of Backup Exec or another product (imported media) that you want to reuse.
Prompt before overwriting imported media
Select this option to be prompted before Backup Exec overwrites imported media when Partial has been selected. Note The job will not run until you respond to this prompt.
239
Setting Default Media Options Media Options - Set Application Defaults dialog box (continued) Item None Caution This option is not recommended because it does not protect data from being overwritten. Description Select this option to disable the media overwrite protection feature. With this option, you are responsible for making sure that the media in your storage devices are not accidentally overwritten. For example, when an overwrite job is submitted to a device, and the media overwrite protection level is set to None, the media in that device is overwritten. If you selected None (no overwrite protection), it is highly recommended that you select this option to be prompted before overwriting allocated or imported media. Note The job will not run until you respond to this prompt. 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 229. 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.
Prompt before overwriting allocated or imported media
240
Setting Default Media Options Media Options - Set Application Defaults dialog box (continued) Item Overwrite recyclable media contained in the targeted media set before overwriting scratch media Description 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 229. 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. Displays the current default prefix for the selected cartridge type. To specify a new prefix on the label, type from one to eight alphanumeric characters. 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.
Prefix
Next value
241
Setting Default Media Options Media Options - Set Application Defaults dialog box (continued) Item Digits Description 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. Backup-to-Disk default folder location 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 176. When making selections for backups that 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.
Related Topics: Media Overwrite Options on page 228 Media Append Options on page 232 Media Labeling on page 234
242
Media Location
Media Location
Backup Exec helps you track the location of your media. There are three categories available for tracking media:
Online media. The online media 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 media. The offline media location displays all media that are onsite but are not in devices or slots, or media vaults. Media are automatically moved to this location if you use Backup Exec to remove media from a device or slot. You can add media to the offline location from another media location. To move offline media back to online, run an inventory of the devices or slot, or catalog the media. You cannot delete or rename the offline location. User-defined media vault. A media vault is a logical representation of the actual physical location of media. You can create media vaults to keep track of where media is physically stored, such as a special media room, a scratch bin, or an offsite location. For example, you could create a media vault where media to be sent offsite are moved. Then, print the Media Vault Contents report, which lists the media contained in that vault, to accompany the physical media to their offsite storage. You can also create vault rules to help you track when media should be moved to or returned from a vault.
Related Topics: Finding Media in a Location or Vault on page 244 Vault Rule Properties for Media Sets on page 225 Update Media Vaults by Using a Wizard on page 245 Renaming a Media Vault on page 244 Adding Media to the Offline Location or a Media Vault on page 245 Moving Media by Dragging and Dropping on page 247 Deleting a Media Vault on page 248 Media Vault Contents Report on page 583
243
Media Location
Creating Media Vaults

Create media vaults so that you can 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., and then click OK.
Finding Media in a Location or Vault

You can find where media is located by searching for the name on the media label. To find media: 1. On the navigation bar, click Media. 2. On the Media selections pane, click Media Location. 3. Under Media Location Tasks on the task pane, click Find media. 4. Type the name from the media label of the media you want to find, and then click OK. The location of the media is highlighted and its properties are displayed in the preview pane. Note If you are using BEWAC, the preview pane is not available.
Renaming a Media Vault

You can rename a media vault. You cannot rename the system-defined online and offline media locations. 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.
244
Media Location
3. Under General Tasks in the task pane, click Rename. 4. Type the new name, and then click OK.
Adding Media to the Offline Location or a Media Vault

You can add media to the Offline Media Location or to a media vault. You cannot add media to the Online Media Location. When you place media in a different location or vault, Backup Exec updates the media location. To add media to the Offline Media Location or to a 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. You can also drag media from the Media view to the vault. 5. Click Add. 6. Repeat steps 4 and 5 for all the media you want to add. 7. Click OK.
Update Media Vaults by Using a Wizard

When you create a media set, you can also specify vault rules, which allow you to set dates for when media should be moved to or returned from a media vault. You must physically move the media to and from the vault, but by enabling vault rules, you can use the task Update vault using wizard to print or view reports that contain details on which media are ready to be moved to and from the vault, and to update the media location in Backup Exec. Note If your environment includes remote sites, you should create separate media sets for each remote site, so that if vault rules are enabled, the reports contain details on which media are ready to be moved for just that site.
245
Media Location
To specify vault media rules when creating a new media set, see Creating Media Sets on page 218. To change vault media rules for an existing media set, see Vault Rule Properties for Media Sets on page 225. To update media vaults: 1. On the navigation bar, click Media. 2. Select the vault that you want to update. 3. Under Media Location Tasks on the task pane, click Update vault using wizard. The Vault Wizard appears. 4. Follow the instructions on the wizard. Related Topics: Creating Media Sets on page 218 Vault Rule Properties for Media Sets on page 225
246
Media Location
Moving Media by Dragging and Dropping

When you are working with media in a location, you cannot move it using the move media operation that you use when you are working with media in media sets, imported media, or other media areas. To move media between locations, drag and drop it from one location to another location. The following table lists the drag-and-drop rules for media: Note If you move media from an online location, its overwrite protection period and append
period remain in effect. Media Drag-and-Drop Rules From/To Online Location No Offline Location Yes, with a warning that the media is not physically moved from the online location. No Media Vaults Media Pools/Sets Yes, with a No warning that the media is not physically moved from the online location. Yes No All Media
Online location
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
247
Media Rotation Strategies
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 Media Vault

You can delete an empty media vault. If there is any media in the vault, you must move it before you can delete the vault. You cannot delete the online or offline locations. To delete a 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.

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 249. 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 249. 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 250.
For information on how to create these strategies, see Creating a New Policy on page 362.
248
Son Media Rotation Strategy

Number of media required: 1 (minimum) Overwrite protection period: last backup The Son strategy involves performing a full backup every day. Although the Son strategy is simple to administer, backing up with a single media is not an effective method of backup. This is because magnetic media eventually wears out after many uses and the data you can restore only spans back to your last backup.
Son Backup Strategy Mon Media 1 Week 1 Tue Media 1 Wed Media 1 Thu Media 1 Fri Media 1
Full Backup
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.
249
Media Rotation Strategies Father/Son Backup Strategy Mon Media 1 Week 1 Media 1 Week 2 Media 2 Media 3 Media 4 Media 6 Tue Media 2 Wed Media 3 Thu Media 4 Fri Media 5
Full Backup
Incremental or Differential Backup
Note When this backup strategy is first implemented, you must start with a full backup. The Father/Son strategy is easy to administer and allows you to keep data longer than the Son strategy, but it is not suitable for the stringent data protection needs of most network environments.
Grandfather Media Rotation Strategy

Number of media required: 19 (minimum) Overwrite protection period: One year The Grandfather method is one of the most common media rotation strategies. It is simple to administer and comprehensive enough to allow easy location of files when they need to be restored. In the Grandfather scenario, four media are used Monday through Thursday for incremental or differential backups; another three media are used every Friday for full backups. The remaining 12 media are used for monthly full backups and are kept offsite.
250
Media Operations 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.
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 media. In addition, you can view properties for the media, including the general, management, statistical, and cleaning properties. Related Topics: Deleting Media on page 252 Moving Media to a Media Set or Media Vault on page 252 Cataloging Media in a Drive on page 452 Viewing General Media Properties on page 253 Viewing Statistics for Media Properties on page 255
251
Media Operations
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, 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. 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. Related Topics: Removing Damaged Media on page 233
Moving Media to a Media Set or Media Vault

You can move media to a media set or to a media vault. 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.
252
Media Operations
To move media: 1. On the navigation bar, click Media. 2. Expand All Media to display a list of media, and then select the media you want to move. 3. You can drag the media to a media set, or under Media Tasks on the task pane, click Move to media set or Move to vault. 4. Click the Down arrow next to the Move to field to display the media set to which you want to move this media, and then click Yes or Yes to All.
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.
253
Media Operations
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. 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. When a template runs that has an associated export template to export this media, Yes is displayed; otherwise, No is displayed. For more information, see Adding an Export Media Template to a Policy on page 370. Name of the media set this media belongs to. Name of the device or vault where this media is located. Date and time when the media was first entered into Backup Exec.
Export pending
Media set Media location Creation date
254
Media Operations General Media Properties tab (continued) Item Allocated date Description 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. Date and time after which the media can be overwritten.
Modified date Overwrite protection until Appendable until
Date and time after which the media can no longer be appended to.
Note In BEWAC, the servers date and time format are used instead of the clients date and time format. Related Topics: Media Labeling on page 234 Creating a Test Run Job on page 320 Viewing Media Information on page 126 Viewing Statistics for Media Properties on page 255
Viewing Statistics for Media Properties

To view statistics for 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 in the task pane, click Properties. 4. Select the Statistics tab.
255
Media Operations
The Media Properties Statistics tab provides the following information:

Media Properties, Statistics tab Item Hours in use Used capacity Description The total number of hours that this media has been in use. The amount of raw capacity on the media that has been used. Used Capacity is calculated by subtracting Available Capacity from Total Capacity. Used Capacity may or may not equal Bytes Written. Available capacity The amount of expected raw capacity on the media that remains unused. Some tape devices support the ability to read the amount of remaining capacity of the media that is currently loaded in the device. If a tape device supports reading of the remaining capacity amount, then Available Capacity is derived from the remaining capacity amount. Otherwise, Available Capacity is calculated by subtracting Bytes Written from Total Capacity. Because Free Space is reported in terms of unused raw capacity, review Bytes Written and Compression Ratio to better estimate if there is enough free space to accommodate a specific job. Total capacity The amount of expected total raw capacity of the media. Some tape devices support the ability to read the amount of total capacity of the media that is currently loaded in the device. If a tape device supports reading of the total capacity amount, then Total Capacity is derived from the total capacity amount. Otherwise, Total Capacity is estimated based on past usage of the media. The ratio of Bytes Written to Used Capacity. Compression ratio will show the overall effect that data compression and media flaws are having on the amount of data that is being stored on the media. The amount of data that has been written into blocks on the media. Bytes Written may differ from Used Capacity due to the effects of data compression and media flaws. Data compression will tend to increase Bytes Written when compared to Used Capacity. Media flaws will decrease Bytes Written when compared to Used Capacity. Number of bytes that have been read from this media. Number of times this media has been mounted.
Compression ratio
Bytes written
Bytes read Mounts
256
Media Operations Media Properties, Statistics tab (continued) Item Seeks Description The total number of seek operations (performed when a specific piece of information is being located) that have been performed on this media. The number of errors encountered while trying to locate data. The number of recoverable write errors encountered. If you receive soft errors, it may indicate the beginning of a problem. If you receive excessive errors for your environment, check the media for damage. The number of unrecoverable write errors encountered. If you receive hard errors, check the media for damage. The number of recoverable read errors encountered. If you receive soft errors, it may indicate the beginning of a problem. If you receive excessive errors for your environment, check the media for damage. The number of unrecoverable read errors encountered. If you receive hard errors, check the media for damage.
Seek errors Soft write errors
Hard write errors
Soft read errors
Hard read errors
Related Topics: General Media Set Properties on page 223 Creating Media Sets on page 218
257
Media Operations
258
Chapter
Backing Up Data
Backups are crucial for data protection, and Backup Exec offers you many choices for creating backup jobs to protect your data, including:
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 selection list. Select the data you want to back up and save the selections as a selection list. You can then choose the selection list when creating a backup job. You can use selection lists for multiple jobs. You can also choose a selection list and combine it with a policy to create a job. You can also choose 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.
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.
259
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 Device Pools on page 133. Create media sets. For more information, see Creating Media Sets on page 218.
Caution To protect remote resources, you must install the Backup Exec Remote Agent for Windows Servers on the remote computer. The Remote Agent is a system service that runs on Windows servers and workstations and provides efficient backup processing by locally performing tasks that, in typical backup technologies, require extensive network interaction. Related Topics: Creating a Backup Job on page 261 Setting Default Backup Options on page 324 About Backup Strategies on page 351 Symantec Backup Exec - Remote Agent for Windows Servers on page 789
260
Creating a Backup Job

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. Related Topics: Using the Backup Wizard on page 262 Creating a Manual Backup Job by Configuring Job Properties on page 262 Setting Default Backup Options on page 324 Specifying Backup Networks on page 334
Chapter 6, Backing Up Data
261
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. Related Topics: Creating a Manual Backup Job by Configuring Job Properties on page 262 Setting Default Backup Options on page 324 Monitoring Jobs on page 405
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 284) or choose an existing selection list from the Selection list name field (see Using Selection Lists on page 293). For more information about the Selections options, see Selections Options for Backup Jobs on page 264. 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 266. 4. On the Properties pane, under Settings, click General and complete the options as described in General Options for Backup Jobs and Templates on page 270.
262
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 276. 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 280. If you are using the Advanced Open File Option, on the Properties pane, under Settings, select Advanced Open File and complete the options as described in Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999. 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 Firewall, and then set up the backup network for this job (see Changing the Backup Network for a Job on page 339). 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 Notification on page 534). If you want Backup Exec to notify someone when a backup job containing a specific selection list completes, on the Properties pane, under Source, click Selection List Notification (see Selecting Recipients for Notification on page 534).
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 398), and then click Submit. Note If you are using Backup Exec Web Administration Console (BEWAC), under Frequency, click Schedule to set the scheduling options or click OK to run the job. 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 119).
263
Note If a drive loses power during a backup operation, you should restart the backup job using a different tape. You can restore the data written to the tape up to the point of the power loss, but you should not reuse the tape for subsequent backup operations. Related Topics: Using the Backup Wizard on page 262 Selecting Data to Back Up on page 284 Setting Default Backup Options on page 324
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
264
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 293). Otherwise, use the default Selection list name, which creates a new selection list using this name.
Selection list description Enter a description for the selection list. 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 293).
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 288). Select this option if you want to select the contents of all the subfolders when a directory is selected.
Text Advanced
Include subdirectories
Related Topics: Selecting Data to Back Up on page 284 Changing the Order for Processing Backup Selections on page 291 Changing and Testing Logon Accounts for Resources on page 292 Including or Excluding Files for Backup Using Advanced File Selection on page 288 Creating Selection Lists on page 293 Setting Up User-defined Selections on page 304
265
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
266

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 176). 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.
267
Creating a Backup Job Device and Media options for backup job (continued) Item Media set Description Select the media set for the backup (see General Media Set Properties on page 223). 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 239. 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
268
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 239. Depending on your configuration, overwritable media is selected from scratch media or recyclable media. For more information, see Media Overwrite Options on page 228. If the media in the drive is not overwritable, an alert appears requesting that you insert overwritable media. Append to media, overwrite Select this option to append this backup to the media set listed in if no appendable media is the Media Set field in this dialog box. The backup set is appended if available an appendable media is available in the selected media set; if not, an overwritable media is used and added to the media set. Note If an append job fills a media, the job continues on another piece of overwritable media. If the media in the drive is not overwritable, an alert appears requesting that you insert overwritable media. Append to media, terminate Select this option to append this backup to the media set listed in job if no appendable media the Media Set field in this dialog box. The backup set is appended if is available an appendable media is available in the selected media set; if not, the job is terminated. Eject media after job completes Retension media before backup Select this option to have Backup Exec automatically eject the media in the drive when the operation completes. Select this option to have Backup Exec run the tape in the drive from beginning to end at a fast speed, which helps the tape wind evenly and run more smoothly past the tape drive heads. Retensioning is primarily for Mini Cartridge and quarter-inch cartridges and is not supported on most other types of tape drives. Description
269
Creating a Backup Job Device and Media options for backup job (continued) Item 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. Description
General Options for Backup Jobs and Templates

General options for backup jobs, including the name of the job and the backup method to be used, can be set through the Backup Job Properties dialog box. To set these options, on the Properties pane, under Settings, click General.
General settings options for backup job
270

General settings options Item Job name/Template name Description Enter the name for this backup job or template, or accept the default name that appears. The name must be unique Type a description of the information you are backing up.
Backup set description
271
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 - Using archive bit (reset archive bit). Includes all of the files selected for backup and resets the archive bit to indicate that the files have been backed up. - Using modified time. Includes all of the files selected for backup and allows the use of incrementals and differentials using the modified date and time stamp. - Copy the files. Includes all selected data, and does not affect any media rotation scheme because the archive bit is not reset. - Archive the files (delete files after successful copy). Backs up the selected data, verifies the media, and then deletes the data from the volume. For data to be deleted, rights to delete a file must be granted; otherwise data will be backed up, but not deleted.
Note Backup Exec does not delete data from Backup Exec Agent workstations when using the archive feature.
Differential - Back up changed files since last full - Using archive bit (does not reset archive bit). Includes all files that have changed (based on the archive bit) since the last full backup, and does not affect any media rotation scheme because the archive bit is not reset. - Using modified time. Includes all files changed since the last full backup, using the files last modified date and time stamp. Make sure that the same script or selection list is used for the differential backup that was used for the full backup.
Incremental - Back up changed files since last full or incremental - Using archive bit (reset archive bit). Includes only the files that have changed (based on the archive bit) since the last full or incremental backup and resets the archive bit to indicate that the files have been backed up. - Using modified time. Includes all files that have changed since the last full or incremental backup, using the files last modified date and time stamp. Make sure that the same script or selection list is used for the incremental backup that was used for the full backup.
Working Set - Back up files - Changed today. Backs up all files that were created or modified today.
272
Creating a Backup Job General settings options (continued) Item Backup method for files (continued) Description - 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. For more information, see Understanding Backup Methods and Their Advantages on page 354. Files accessed in x days 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 Symantec recommends that you specify at least 30 days in order to include the data needed to make your system operational if you have to restore a working set backup. Use the Windows Change Journal if available Select this option if you want to use Windows NTFS Change Journal to determine which files have been modified since the last full backup. This option can only be used with NTFS volumes and only when the backup method selected is FULL - Back Up Files Using modified time, DIFFERENTIAL - Back up changed files since last full - Using modified time or INCREMENTAL - Back up changed files since last full or incremental - Using modified time. 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.
Preserve tree on archive
273
Creating a Backup Job General settings options (continued) Item Collect additional information for synthetic backup Description This option displays only for templates. It is used with synthetic backups. It specifies that Backup Exec collects the information required to detect files and directories that have been moved, renamed, or newly installed since the last backup, and then includes those files and directories in the backup jobs. If this option is not selected, Backup Exec skips these files and directories if their archive bits are unchanged. With this option selected, Backup Exec compares path names, file names, modified times, and other attributes with those from the previous full and incremental backups. If any of these attributes are new or changed, then the file or directory is backed up. Backups that have this option selected require more disk space, and take more time to run, than backups that do not. You must select this option for the baseline and incremental backup template in a synthetic backup policy. For more information about synthetic backups, see Symantec Backup Exec Advanced Disk-based Backup Option on page 875. Verify after backup completes Select this option to have Backup Exec automatically perform a verify operation to make sure the media can be read once the backup has been completed. Verifying all backups is recommended.
274
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.
Related Topics: Creating a Manual Backup Job by Configuring Job Properties on page 262
275
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
276
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.
277
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.
278
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. 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.
If closed within x seconds
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. Related Topics: Creating a Manual Backup Job by Configuring Job Properties on page 262 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999
Chapter 6, Backing Up Data 279
Pre/Post Commands for Backup or Restore Jobs

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

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

Pre- and post-command options Item Pre-command Description Specify a command to be run on the specified server before the backup or restore job is run. Use local paths, and make sure the paths exist on each server and are correct. Note Commands that require user interaction, such as prompts, are not supported. Post-command Specify a command to be run on the specified server after the backup or restore job has run. Use local paths, and make sure the paths exist on each server and are correct. Note Commands that require user interaction, such as prompts, are not supported.
281
Creating a Backup Job Pre- and post-command options (continued) Item Allow pre- and post-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-commands to determine if they completed successfully. An exit code of zero returned to the operating system by the pre- or post-command is interpreted by Backup Exec to mean that the command completed successfully. A non-zero exit code is interpreted by Backup Exec to mean the command ended with an error. After checking the return codes, Backup Exec continues processing according to selections you made for running the pre- and post-commands. If this option is not selected, the success of the pre- and post-commands is not determined based on the return code. Run job only if Select this option to run the backup or restore job only if the pre-command is successful pre-command is successful. If the pre-command fails, the job does not run, and is marked as failed. If it is critical that the job does not run if the pre-command fails, then select Allow pre- and post-commands to be successful only if completed with a return code of zero. If a non-zero code is returned, it is interpreted by Backup Exec to mean that the pre-command did not run successfully. The job is not run and the job status is marked as Failed. Run post-command only if Select this option to run the post-command only if the pre-command is successful pre-command is successful. If it is critical that the post-command does not run if the pre-command fails, then select Allow pre- and post-commands to be successful only if completed with a return code of zero. If a non-zero code is returned for the pre-command, it is interpreted by Backup Exec to mean that the pre-command did not run successfully. The post-command does not run. If you also select Run job only if pre-command is successful, and both the pre-command and the job are successful, but the post-command returns a non-zero code, the job log reports both the job and the post-command as failed.
282
Creating a Backup Job Pre- and post-command options (continued) Item Run post-command even if job fails Description Select this option if it is critical to run the post-command regardless of whether the job is successful or not. If you also select Allow pre- and post-commands to be successful only if completed with a return code of zero and the post-command returns a non-zero code, the job log reports the post-command as failed. Run post-command after job verification completes If you selected the Verify after backup completes option on the General backup properties dialog box, select this option to run the post-command after the verification completes.
Cancel command if not Select the number of minutes Backup Exec should wait before completed within x minutes canceling a pre- or post-command that did not complete. The default time-out is 30 minutes. Run these commands On this media server Select this option to run the pre- and post-commands on this media server only. Select this option to run the pre- and post-commands one time on each server backed up. The pre- and post-command selections apply to each server independently. If you select this option, the pre- and post-commands are run and completed for each server before processing begins on the next selected server.
On each server backed up
Related Topics: Creating a Manual Backup Job by Configuring Job Properties on page 262 Setting Default Backup Options on page 324 Setting Default Pre/Post Commands on page 331
283
Selecting Data to Back Up

When you are setting up a backup job, the first thing you do is select the data you want to back up. You make your selections from the backup selections pane on the Backup Job Properties dialog box.
Backup Data Selection
Server name Local drives System State Backup Exec databases User-defined selections Network shares
There are several ways you can select data to back up. You can select an entire drive, a folder, files, System State, network share, Backup Exec Agent volume, or user-defined selection. You also can use the Advanced File Selection feature to include or exclude specific files or specific types of files. Or you can set up a selection list that you can reuse for several backups. Note If the account to which you are logged on does not have sufficient rights, you are required to supply another logon account that can be used to view files for backup. To expand the view for an item, click the plus sign (+) next to it or double-click the item name. To collapse the view, click the minus sign (-) next to an item or double-click the item name. To view the contents of an item, double-click the items icon. The items contents appear in the right frame of the backup selections view. For all items (except System State), you can traverse file levels from either side of the window by clicking folders and subfolders as they appear. 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.
284
Selecting Data to Back Up 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.
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. Shadow Copy Components (Windows Server 2003 only). The Backup Exec Shadow Copy Components file system uses Microsofts Volume Shadow Copy Service to protect critical operating system and application service data, and third party application and user data on Windows Server 2003 resources. A Writer is specific code within an application that participates in the Volume Shadow Copy Service framework to provide point-in-time, recovery-consistent operating system and application data. Writers appear as Shadow Copy Components, which are listed as resources in backup and restore selections. When expanded, the Backup Exec Shadow Copy Components file system includes the following types of Writers:
Service State. Critical operating system and application service data, such as Event Logs, Windows Management Instrumentation (WMI), Removable Storage Manager (RSM), etc. System State. Critical operating system data, such as Windows System File Protection (System Files), COM+ Class Registration Database, Registry, Active Directory, etc. User Data. Third party application and user data, etc.
285
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 Windows Server 2003 documentation.
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 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 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. The Remote Selections include:
Network Shares. Includes Microsoft Windows systems protected by the Remote Agent for Windows Servers. On 64-bit Intel Itanium computers, EFI system partitions can be displayed here. Workstation Agents. The Backup Exec Workstation Agents protect workstations running Windows 98/Me, Macintosh, and UNIX. 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.
286
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. Related Topics: Protecting Windows Server 2003 Systems on page 344
About Selecting Distributed File System (Dfs) Links for Backup

Only the Dfs links themselves are backed up; the data that the links lead to is not included. To back up the data in the Dfs links, back up the data on the server where the data resides. If you are backing up any volumes along with the Dfs root, it is recommended that you exclude any Dfs links that reside on those volumes from the backup. To back up Microsofts Distributed File System (Dfs): 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, select Network and Firewall. 3. Select the Enable selection of user shares check box, and then click OK. 4. On the navigation bar, click Backup. 5. Create a user-defined selection for the computer that hosts the Dfs root (even if the computer that hosts the Dfs root is the local selection). Note Backup Exec does not support the use of Dfs domain root paths (\\domain\dfsroot). Add only the computer that hosts the Dfs root to protect the Dfs links. 6. In the backup selection tree, expand User-defined Selections, and then expand the node for the computer you added. 7. Select the Dfs root. 8. Run the backup job. Related Topics: Setting Up User-defined Selections on page 304 Restoring Distributed File System (Dfs) Links on page 476
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. 5. Select the appropriate options as follows:
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.
288
Selecting Data to Back Up Advanced File Selection options (continued) Field 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:

Description
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.
289
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
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.
290
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 262.
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.
To specify the order in which selections are backed up: 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 262).
291
Changing and Testing Logon Accounts for Resources

A logon account enables Backup Exec to access resources for backup. You can verify that the logon accounts you select can access the resources you want to back up. To change and test a logon account for a resource: Note For remote selections, do not change the logon account information. They rely on the logon account used to connect to the server they reside on, and will ignore the additional logon account you can specify. This applies to drives, Lotus, System State, and Exchange selections (except mailboxes, which can and do use logon accounts). 1. On the navigation bar, click 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 388). 7. To verify that the logon account you are using can access the resources selected for backup, click Test All. While Backup Exec attempts to connect to the resources, "Testing" displays in the Test Results column. After a test has completed, the Test Results column will display one of the following results: Successful, Not tested, or an error message. The Not Tested result indicates that either the logon accounts have not been tested or that the tests have been performed but the server that contains the selection could not be accessed. Some tests may take a long time to complete. To cancel a logon account test, click Cancel Test. 8. Click OK.
292
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 policy and quickly create a backup job. Backup Exec detects and notifies you about items in a selection list that are no longer on the resource. Notification occurs as a selection list is loaded for local selections, and as any remote server is expanded in the tree. You can also choose to notifiy recipients when a job completes that contains a particular selection list. This feature allows you to notify users who may be interested that a particular set of selections was backed up. The completion status of the job is included in the notification. To view the job history of the jobs that are associated with a selection list, from Job Setup, right-click the selection list, and then from the shortcut menu, click View History. Related Topics: Creating Selection Lists on page 293 Using Selection Lists to Create a Backup Job on page 296 Selecting Recipients for Notification on page 534 Deleting Selection Lists on page 298 Editing Selection Lists on page 298 About the Excludes Selection List on page 299
Creating Selection Lists

A backup selection list is a list of the resources you want to back up. After you create a selection list you can use it with any backup job or policy. Depending on how you set the Backup Exec default options for selection lists, Backup Exec will do one of the following when you create a new selection list:

Create a separate selection list for each computer you choose. Create a separate selection list for each resource you choose. Create one selection list, regardless of the number of computers or resources you choose.
293
To create a backup selection list: 1. On the navigation bar, click Job Setup. 2. Under Selection Lists Tasks in the task pane, select New backup 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 284. 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 297).
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 288). Select this option if you want to select the contents of all the subfolders when a directory is selected.
Text Advanced
5. (Optional) To notify users that a job containing this selection list was completed, on the Properties pane, under Source, click Selection List Notification. For details on adding notification recipients, see Selecting Recipients for Notification on page 534. 6. Click OK.
Related Topics: Using Selection Lists on page 293 Using Selection Lists to Create a Backup Job on page 296 Deleting Selection Lists on page 298 Editing Selection Lists on page 298 About the Excludes Selection List on page 299 Creating Multiple Selection Lists from a Single Selection List on page 303
295
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. 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. To see the resources that are included in a selection list, select it from the list and then click Properties. 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 262). Related Topics: Using Selection Lists on page 293 Creating Selection Lists on page 293 Deleting Selection Lists on page 298 Editing Selection Lists on page 298 About the Excludes Selection List on page 299
Holding Jobs That Back Up a Selection List

You can place all jobs that back up a selection list on hold to prevent the jobs from running. The jobs will not run until you change the jobs hold status. To place jobs on hold: 1. On the navigation bar, click Job Setup. 2. On the Backup Selection Lists pane, right-click the selection list whose jobs you want to place on hold, and then click Hold Jobs. The jobs that back up this selection list are placed on hold. To remove the hold and run the jobs according to the schedule, click Remove Hold. You can select multiple selection lists by selecting a selection list, and then pressing the <Ctrl> or <Shift> keys while you click other selection lists.
Merging and Replacing Selection Lists

You can create a new selection list by merging two or more existing lists with new selections. Merging of selection lists can be done when creating a job (see Using Selection Lists to Create a Backup Job on page 296) or by selecting the New backup 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 Selection Lists Tasks in the task pane, select New backup 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. 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 294. 7. Click OK.
297
Deleting Selection Lists

You can delete a selection list. However, if a selection list is associated with a policy, you must dissociate the selection list from the policy before you can delete the selection list. To delete a selection list you are no longer using: 1. On the navigation bar, click Job Setup. 2. On the Backup Selection Lists pane, select the selection list you want to delete. 3. On the Edit menu, click Delete Selection List. The Delete Selection List dialog box appears. The available selection lists are listed in this window. 4. Click the selection list you want to delete, and then click Delete. 5. 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. Related Topics: Using Selection Lists on page 293 Creating Selection Lists on page 293 Using Selection Lists to Create a Backup Job on page 296 Editing Selection Lists on page 298 About the Excludes Selection List on page 299 Deleting a Job Created from a Policy on page 380
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, any change you make to this selection list will affect all jobs associated with it. Click Yes to continue. 5. Make the changes you want to Selections, Resource Order, Resource Credentials, Priority and Availability, and Selection List Notification. 6. Click OK. Related Topics: Using Selection Lists on page 293 Creating Selection Lists on page 293 Selecting Recipients for Notification on page 534 Using Selection Lists to Create a Backup Job on page 296 Deleting Selection Lists on page 298 About the Excludes Selection List on page 299
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. To edit the Excludes 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. On the Edit menu, click Edit Selection List. The Name and Type, such as backup or restore, of each selection list appears. 4. Choose Excludes from the Selection lists. 5. Click Edit.
299
6. 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 288), or select the Selection rule you want to remove and click Delete. 7. 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 288). 8. Click OK to save your changes and exit the Edit Selection List window. Related Topics: Deleting Selection Lists on page 298 Creating Selection Lists on page 293
300
Setting Priority and Availability Windows for Selection Lists

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

Priority and Availability options Item Job priority Description Select the default priority you want to assign to the all jobs associated with this selection list. The choices are Highest, High, Medium, Low, and Lowest.
Availability Window Limit availability of this selection list for backup to the following daily time window: This option displays only when you are setting priority and availability for a specific selection list. It does not display when you are setting default options. Select this check box to enable the availability window, which specifies when the selection list will be available for backup each day. Then specify the window settings or use the default settings. If you do not select this option, the resources in the selection list are always available for backup. First available date Select the first date when the selection list should be available to be backed up. The list will be available every day from this date onward. Select the earliest time when this selection list will be available for backup. Select the latest time when this selection list will be available for backup. Select this option if you want Backup Exec to cancel the job associated with this selection list if the job does not complete within the selected number of hours or minutes. Backup Exec starts timing the length of time the job takes to run when the job is queued, not when the job begins. Type the number of hours or minutes you want to allow jobs to complete before they are automatically canceled. The default amount of time is three hours.
Begin time
End time
Enable automatic cancellation for this selection list
Cancel backup job if not completed within x
302
Creating Multiple Selection Lists from a Single Selection List

Backup Exec includes default settings that enable separate selection lists to be created for each resource or computer you select when you create a new backup selection list outside of a backup job. This feature does not apply when you create a selection list while creating a backup job. If you set up Backup Exec to create a separate selection list for each resource or computer, the selection list name will contain either the default name or a user-defined name followed by an incremented number. For example, if the default selection list name is Backup Selection List 003 and three resources are selected for backup, the resulting three selection lists are named Backup Selection List 003, Backup Selection List 004, and Backup Selection List 005. If you replace the default selection list named Backup Selection List 003 with a user-defined name, such as My Selection List, the resulting three selection lists are named My Selection List 004, My Selection List 005, and My Selection List 006. To set up Backup Exec to create separate selection lists for resources or computers: 1. On the Tools menu, select Options. 2. On the Properties pane, under Settings, select Selection List. 3. Select one of the following options:
Selection List Default Options Item Description
For backup selections that you have chosen, have Backup Exec create a Separate backup selection list for each computer Separate backup selection list for each resource Single backup selection list for all selections Select this option to have Backup Exec create a different backup selection list for each computer that you select when you create a selection list outside of a backup job. Select this option to have Backup Exec create a different backup selection list for each resource that you select when you create a selection list outside of a backup job. Select this option to have Backup Exec create one selection list, regardless of the number of resources or computers selected for backup. This is the default option.
303
Setting Up User-defined Selections
Searching Selection Lists

Backup Exec includes a search feature for selection lists, which enables you to search for selection lists that contain a particular server. This feature is helpful when you have a large number of selection lists. To search for a server in a selection list: 1. On the navigation bar, click Job Setup. 2. On the task pane, under Selection List Tasks, click Search Selection Lists. 3. Type the name of the computer for which you want to locate selection lists. You can type the complete name or part of the name. 4. Click Find Now. The Search Selection Lists dialog box expands to display the results of the search. You can right-click a selection list to create a new job using policies, copy or delete the selection list, or view the selection list properties.
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 path name 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. Right-click User-defined Selections, and then click User-defined Selections. 3. In the UNC Name field, type the server name and volume name, or the computer name. Example: \\Production\graphics
304
Using Backup Execs Windows Explorer Interface
Note TCP/IP addresses can be provided for user-defined selections, but are not recommended. Backup Exec does not support user-defined selections for IP addresses in a Dynamic Host Configuration Protocol (DHCP) environment. 4. Click Add. The share appears in the Selections defined section of the dialog box. Repeat steps 4-5 to add additional user-defined selections. 5. 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. Related Topics: Using Selection Lists on page 293 Creating Selection Lists on page 293 Using Selection Lists to Create a Backup Job on page 296 Deleting Selection Lists on page 298 Editing Selection Lists on page 298 About the Excludes Selection List on page 299

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 95). 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 51. To set up Backup Exec to create backups from Windows Explorer: 1. On the Tools menu, click Options. 2. On the Properties pane, under Settings, click Preferences.
3. Select Enable backup from Windows Explorer. 4. Click OK. The Back up with Backup Exec option will now appear on the Windows Explorer shortcut menu. Related Topics: Backup Exec Defaults on page 119 Submitting a Backup Job from Windows Explorer on page 306 Archiving Data on page 309
Submitting a Backup Job from Windows Explorer

After you have set up Backup Exec to create backups from Windows Explorer, you can submit a backup job. The first time you submit a backup job using the Backup Exec Windows Explorer interface, you can specify logon information for a remote media server and enter a backup device name. The Backup Settings dialog box allows you to save the settings, which are used for subsequent backup jobs submitted from Windows Explorer. If you do not save the settings, you need to enter the logon information and the backup device name each time you submit a backup job from Windows Explorer. Note The first time you run a backup on a resource, you must use the Backup Exec graphical user interface. If the first backup on a resource is from the Windows Explorer interface, the job will fail and will continue to fail until you run a job from Backup Exec. 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. 3. On the Backup Settings dialog box, select the appropriate options as follows:
Backup Settings options Name Server Name Description Type the name of the media server on which Backup Exec is installed.
306
Using Backup Execs Windows Explorer Interface Backup Settings options (continued) Name 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 Backup Options Job Name View or change the job name. Backup Exec 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, Backup Exec could generate the job name Backup ADMN-30P 960576233. If you change the default job name, you must ensure it is a unique job name. Device Name Include subdirectories in backup Save Settings Type the name of the backup device. Select this option to include all subfolders within the selected folders in the backup job. 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. Type the password for the user. Description
Note The backup job defaults to the options set in the Backup tab. For more information, see Setting Default Backup Options on page 324. 4. Click Submit Job.
Running a One-button Backup Job
5. Click Close Dialog after the backup job has been submitted and confirmed. You must close the Backup Settings dialog box to submit another backup job from Windows Explorer. Related Topics: Archiving Data on page 309
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. If you want to perform a one-button backup of a system where Backup-to-Disk folders are located, Symantec recommends that you add the Backup-to-Disk folders to the Excludes Selection List. If you do not exclude Backup-to-Disk folders, data is continuously added to the folders during the one-button backup, which uses all the free drive space. You can back up the following with one-button backup:

Local drives that do not use removable media Lotus Domino resources 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) Microsoft SQL Server filegroup resources Microsoft Sharepoint Portal Server workspaces Microsoft Exchange individual mailboxes and public folders Microsoft Exchange 2000 installable filesystem (IFS) drive (usually M:)
You cannot back up the following types of data with one-button backup:

In addition, you cannot run one-button backup in a cluster environment or in a Central Admin Server Option environment.
308
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 access the Backup Exec Assistant, on the Tools menu, select Backup Exec Assistant. 2. Click the Information desk tab. 3. 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. Note If the checkpoint restart setting is enabled for an archive backup job that is resumed when a cluster failover occurs, the files selected for archive are not automatically deleted from the source volume after the backup completes.
309
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. 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 262. Related Topics: Including or Excluding Files for Backup Using Advanced File Selection on page 288 Archiving Data on page 309
310
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. The Remote Agent is required to discover resources on remote computers. However, installing a MAPI client on the media server enables Exchange resources to be discovered on remote resources on which the Remote Agent is not installed. On Windows Server 2003 resources, Backup Execs Resource Discovery feature will detect the Shadow Copy Components; it will not detect System State. 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. 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. 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 314. 6. On the Properties pane, under Settings, click General and then complete the appropriate options as follows: :
General settings options for resource discovery job Item Job name Description Enter the name for this job.
311
Using Resource Discovery to Search for New Resources General settings options for resource discovery 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
7. On the Properties pane, under Settings, click Resources and then complete the appropriate options as follows:
Resources options for resource discovery job Item Description
Select the types of resources to automatically discover Network administrative Select this option if you want Backup Exec to search for new shares administrative network shares or volumes. Network user shares Select this option if you want Backup Exec to search for new user-defined shares. Select this option if you want Backup Exec to search for new Microsoft SQL databases. 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 or shadow copy components.
Microsoft SQL databases Microsoft Exchange servers
Lotus Domino databases System State and/or Shadow Copy Components
When new resources are discovered:
312
Using Resource Discovery to Search for New Resources Resources options for resource discovery job (continued) Item Send separate notification for each new resource found Send one notification for all new resources found Include previously discovered resources when sending notification Description 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.
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 Notification on page 534). 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 398).
313
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 311), 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. 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.
314
Duplicating Backed Up Data

You can create a job to duplicate backup data, selecting either to duplicate existing backup sets or to duplicate backup sets immediately following a scheduled job. If you select to duplicate existing backup sets, the backup sets you select from catalogs are read from the source media and written to the selected destination, such as a drive, drive pool, or backup folder. You can schedule when this type of job runs. If you 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. 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 the options as described in Device and Media Options for Backup Jobs and Templates on page 266.
315
6. On the Properties pane, under Settings, click General, and complete the appropriate options as follows:
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:

Backup set description Preferred source device
Type a description of the information you are backing up. Select the device used as the destination device for the original backup job.
7. On the Properties pane, under Settings, click Advanced, and complete the appropriate options as follows: :
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.
316
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
Hardware [if available, otherwise none]. Select this option to use hardware data compression (if the storage device supports it). If the drive does not feature data compression the data is backed up uncompressed.
8. 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 Notification on page 534). 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 398).
317
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 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.
318
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:

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 Notification on page 534). 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 398). After verification has completed, you can check the results in the job log. Related Topics: Setting Default Backup Options on page 324 Verify after backup completes on page 316
319
Creating a Test Run Job

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

The logon credentials are incorrect. Insufficient media is available. Media is not in the drive. There is no overwritable media for an overwrite job. There is no appendable media for an append job.
Test run jobs that are targeted to All Drives will fail the test if any of the devices in the All Drives drive pool cannot handle the job. For example, if one of the devices does not have any media. A test run job checks media capacity available for the selected job. However, you can check if there is enough available media for multiple test run jobs in the Test Run Results report. Note Before you create a test run job, Symantec recommends that you run backup jobs to your devices first. Backup Exec does not recognize the capacity of a backup device until an actual backup job is targeted to the device. If you create a test run job before any other jobs, Backup Exec cannot check that the device has sufficient capacity to perform the backup job. After at least one backup job has been targeted to a device, Backup Exec can determine the capacity. To create a test run 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.
320
4. Select the appropriate General options as follows:

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. Select this check box to test if there is enough available capacity on the media to complete the job. Note During the test run job, the number of scheduled jobs in the queue is not checked; therefore, jobs that are scheduled before the test run job may use the media that was available when the test run job was performed. Media check Select this check box to test whether the media is online and overwritable.
Media capacity check to complete individual job
Method for determining job size Use previous job history, Select this option to use past job histories to determine whether if available there is enough media available to run the scheduled backup job. Checking the previous job history is faster than performing a pre-scan. Perform Pre-scan Select this option to enable Backup Exec to scan the scheduled backup job to determine whether there is enough media available to run the job. This is the most accurate method of determining media capacity and should be selected if there is not an existing job history. Select this option to have the scheduled job placed on hold if any failures are detected during the test run.
Upon any failure, place the scheduled job on hold
321
Creating a Test Run Job General settings options for test run job (continued) Item Run at priority Description 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:

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 Notification on page 534). 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 398). Related Topics: Viewing General Media Properties on page 253 Creating a Manual Backup Job by Configuring Job Properties on page 262 Test Run Results Report on page 602
322
Setting Test Run Default Options

To set test run default options: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Test Run. 3. Select the appropriate options as follows:
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 scheduled job Select this option to have the scheduled job placed on hold if any on hold if any failure failures are detected during the test run. occurs during the Test Run job
4. Click OK.
323
Setting Default Backup Options
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. 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 354. When the Working Set backup method is selected, use this field to specify the number of days for which to include accessed files. Select this option if you want to use Windows NTFS Change Journal to determine which files have been modified since the last full backup. This option can only be used with NTFS volumes and only when the backup method selected is FULL -
Files accessed in x days
Use Change Journal if available
Back Up Files - Allow incrementals and differentials using modified time, DIFFERENTIAL - Using modified time or INCREMENTAL - Using modified time.
324
Setting Default Backup Options Backup default options (continued) Item Collect additional information for synthetic backup Definition This option is used with synthetic backups. It specifies that Backup Exec collects the information required to detect files and directories that have been moved, renamed, or newly installed since the last backup, and then includes those files and directories in the backup jobs. If this option is not selected, Backup Exec skips these files and directories if their archive bits are unchanged. With this option selected, Backup Exec compares path names, file names, modified times, and other attributes with those from the previous full and incremental backups. If any of these attributes are new or changed, then the file or directory is backed up Backups that have this option selected require more disk space, and take more time to run, than backups that do not.
325
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 226. 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 120). 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 228. 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 120). The backup set is appended if an appendable media is available in the selected media set; if not, the job is terminated.
326
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.
327
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. If you use junction points created by linkd.exe (or a similar tool) to span volumes, then Advanced Open File Option (AOFO) backups and Change Journal incremental backups will not follow the junction points properly. To perform AOFO and Change Journal incremental backups of volumes with junction points, clear this option. Junction points created by Disk Manager or mountvol.exe are supported. Note Since Mounted Drives that do not have a drive letter assigned to them cannot be selected, the files and directories to which they are linked are backed up regardless of whether this option is selected. If this option is selected and the actual files and directories to which the junction points are linked are also included in the backup selections, then the files and directories are backed up twice; once during the full file and directory backup, and again via the junction point. WARNING: If a junction point is linked to a location that encompasses it, then recursion (a situation where data is backed up repeatedly) will occur, resulting in an error and job failure. For example, if c:\ junctionpoint is linked to c:\, recursion will occur when attempting to back up c:\ junctionpoint, and the backup job will fail.
328
Setting Default Backup Options Backup default options (continued) Item Back up data in Remote Storage Definition 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. Enable single instance backup for NTFS Select this option if you want Backup Exec to protect Single Instance Store (SIS) volumes. SIS, which is used by Remote Installation Services to save disk space, maintains a single physical copy of all identical files on a specified volume. If SIS finds an identical file on the volume, a copy of the original file is placed in the SIS and a link is made to the actual physical location. By selecting this option, Backup Exec will back up the physical file one time, no matter how many links have been created.
Caution If the backup job does not run to completion, the file data may not be included in the backup set. Rerun the backup until it is successfully completed. If the incremental backup method was used, running the job again will not back up the same files. You must run a full or copy backup to ensure that all files are backed up completely. If the incremental - using modified time backup method was used, running the same backup job to completion will back up the files correctly.
329
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.
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 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 on page 991.
Without a lock
330
Setting Default Pre/Post Commands

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

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

Pre-job and Post-job options Item Allow pre- and post-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-commands to determine if they completed successfully. An exit code of zero returned to the operating system by the preor post-command is interpreted by Backup Exec to mean the job completed successfully. A non-zero exit code is interpreted by Backup Exec to mean the job ended with an error. After checking the return codes, Backup Exec continues processing according to selections you made for running the pre- and post-commands. If this option is not selected, the success of the pre- and post-commands is not determined based on the return code. Run job only if pre-command is successful Select this option to run the backup or restore job only if the pre-command is successful. If the pre-command fails, the job does not run, and is marked as failed. If it is critical that the job not run if the pre-command fails, then select Allow pre- and post-commands to be successful only if completed with a return code of zero. If a non-zero code is returned, it is interpreted by Backup Exec to mean that the pre-command did not run successfully. The job is not run and the job status is marked as Failed. Run post-command only if Select this option to run the post-command only if the pre-command is pre-command is successful. successful If it is critical that the post-command fail if the pre-command fails, then select Allow pre- and post job commands to be successful only if completed with a return code of zero. If a non-zero code is returned for the pre-command, it is interpreted by Backup Exec to mean that the pre-command did not run successfully. The post-command is not run. If you also select Run job only if pre-command is successful, and both the pre-command and the job are successful, but the post-command returns a non-zero code, the job log reports both the job and the post-command as failed.
332
Setting Default Pre/Post Commands Pre-job and Post-job options (continued) Item Run post-command even if job fails Description Select this option if it is critical to run the post-command regardless if the job is successful or not. If you also select Allow pre- and post job commands to be successful only if completed with a return code of zero and the post-command returns a non-zero code, the job log reports the post-command as failed. Run post-command after If you selected the Verify after backup completes option on the job verification completes General backup properties dialog box, select this option to run the post-command after the verification completes. Cancel command if not completed within x minutes Run these commands On this media server Select this option to run the pre- and post-commands on this media server only. Select the number of minutes Backup Exec should wait before canceling a pre-job or post-command that did not complete. The default time-out is 30 minutes.
On each server backed up Select this option to run the pre- and post-commands one time on each server backed up. The pre- and post-command selections apply to each server independently. If you select this option, the pre- and post-commands are run and completed for each server before processing begins on the next selected server.
4. Click OK. Related Topics: Pre/Post Commands for Backup or Restore Jobs on page 280
333
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
backup network network ID: 128.10.0.0 subnet mask: 255.255.0.0 IP address: 128.10.0.1 IP address: 128.20.0.1 database server running Remote Agent Backup Exec media server
corporate network network ID: 128.20.0.0 subnet mask: 255.255.0.0
IP address: 128.10.0.2 IP address: 128.20.2
IP address: 128.10.0.3
router A
IP
router B mail server running Remote Agent
database user
mail user
database and mail user
In the example, the database server and mail server are connected to both the backup network and the corporate network.
When backup operations are performed by the Backup Exec media server, the backup data will use either the backup network or the corporate network to back up the database server. If the backup data goes through the corporate network, the amount of time it takes to back up the database server will increase because the network route between the two computers is longer. This may cause users to experience network latencies when accessing the mail server since there is an increase in network traffic. In contrast, if the Specified Backup Network feature is enabled and you back up the database server, the backup data traffic is isolated to the backup network and users accessing the mail server are not affected. The backup network will be used to perform all backup operations, unless the remote computer is not connected to the backup network. If you want to back up remote computers that are not connected to the backup network, such as the database 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. Related Topics: Using Backup Exec with Firewalls on page 341 Browsing Systems Through a Firewall on page 342
335
Specifying Default Backup Network and Firewall Options

You can specify a network to be used as the default for every Backup Exec job. Before configuring the feature, test for network connectivity between the media server and the remote computers. Note The remote computers that you want to back up must have the most current version of Backup Exec Remote Agent installed. To set the default backup network: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Network and Firewall. 3. Select the appropriate options as follows:
Network Options - Set Application Defaults Item Enable selection of default shares Enable selection of user selections Enable agents using TCP/IP protocol Description Select this option to enable selection of Windows default shares.
Select this option to enable selection of Windows user shares.
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.
336
Specifying Backup Networks Network Options - Set Application Defaults (continued) Item Description
Enable agents using Select this option to use the IPX/SPX network protocol to NetWare IPX/SPX protocol 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 dynamic port range Select this option if you want to allow the media server to use a range of ports for communications, and then enter the port range. If you select the Media server to remote agent option, you do not need to enter a port range for the media server. 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. Symantec 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 341).
337
Enable Remote Agent TCP Select this option if you want to allow remote agents 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. Symantec recommends using a range of 25 allocated ports for the remote systems if using Backup Exec with a firewall (see Using Backup Exec with Firewalls on page 341). 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. 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
IP address
Subnet mask
Network ID
Physical address
Use any available network route for remote agents not bound to the above Network ID
338
Default network interface for delegated jobs Use any available network This option displays only if you have the Central Admin Server interface Option (CASO) installed. Select this option to use any network interface card installed on the managed media server. For more information, see Setting the Default Network Interface for Delegated Jobs on page 858 Use the default network This option displays only if you have the Central Admin Server interface for the managed Option (CASO) installed. Select this option if you want CASO media server delegated backup jobs to be processed using the network interface card configured as the default in the managed media server. For more information, see Setting the Default Network Interface for Delegated Jobs on page 858
Related Topics: Changing the Backup Network for a Job on page 339 Specifying the Restore Network on page 493
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 262). 3. On the Properties pane, under Settings, click Network and Firewall. 4. Select the appropriate options as follows:
339
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. If you are using the Central Admin Server Option (CASO), select the Use the default network interface for the managed media server option if you want CASO delegated backup jobs to be processed using the network interface card configured as the default in the managed media server. IP address 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. For Windows 2000 and later operating systems, this field displays the Media Access Control (MAC) address for the network card you selected. 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.
Subnet mask
Network ID
Physical address
Use any available network route for remote agents not bound to the above Network ID
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 Notification on page 534). 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 398).
340
Using Backup Exec with Firewalls
Related Topics: Specifying Backup Networks on page 334 Specifying Default Backup Network and Firewall Options on page 336 Creating a Manual Backup Job by Configuring Job Properties on page 262

In firewall environments, Backup Exec provides the following advantages:

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

Because most firewalls do not allow a remote system to be displayed in the Microsoft Windows Network tree, you may need to take additional steps to select these remote systems in the Backup Exec administration console. To view devices in firewall environments: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Network and Firewall. 3. Verify that a dynamic range of ports has been set for the media server and remote agent and that the firewall is configured to pass these port ranges and the 10,000 port (which is used for the initial connection from the media server to the Remote Agent). 4. Click OK.
342
5. On the navigation bar, click Backup. 6. Right-click User-defined Selection. 7. From the shortcut menu, click User-defined Selections. 8. In UNC Name, after \\, type the name or IP address of the remote system, and then click Add. 9. 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 262.
343
Protecting Windows Server 2003 Systems

The Backup Exec Shadow Copy Components file system uses Microsofts Volume Shadow Copy Service to protect critical operating system and application service data, and third party application and user data on Windows Server 2003 resources. Volume Shadow Copy Service allows a computer to be backed up while applications and services are running by providing a copy of a volume when a backup is initiated. Applications do not need to be shut down to ensure a successful volume backup. Volume Shadow Copy Service enables third party vendors to create snapshot plug-ins, or Writers, for use with this shadow copy technology. Note To fully protect any local or remote servers running production versions of Windows Server 2003, you should upgrade to the latest version of Backup Exec on all media servers and update the Remote Agent for Windows Servers on any remote computers running Windows Server 2003. Remote Agents from Backup Exec 9.0 Revision 4367 are not supported on production versions of Windows Server 2003.
About the Backup Exec Shadow Copy Components File System

A Writer is specific code within an application that participates in the Volume Shadow Copy Service framework to provide point-in-time, recovery-consistent operating system and application data. Writers appear as Shadow Copy Components, which are listed as resources in backup and restore selections. When expanded, the Backup Exec Shadow Copy Components file system includes the following types of Writers:
Service State - Critical operating system and application service data, such as Event Logs, Windows Management Instrumentation (WMI), Removable Storage Manager (RSM), etc. System State - Critical operating system data, such as Windows System File Protection (System Files), COM+ Class Registration Database, Registry, Active Directory, etc. User Data - Active Directory Application Mode, third party application and user data, etc.
Only Writers that have been tested for use with Backup Exec are available for selection in the backup selection list. Other Writers may be displayed in the selection list, but cannot be selected for backup.
344
The following table lists the System State Writers and their equivalents in Windows 2000 System State:
System State Writer Internet Information Services (IIS) Metabase Writer Registry System Files COM+ Class Registration Database SYSVOL Active Directory Cluster Quorum Certificate Services
Windows 2000 System State System State
Registry Boot Files COM+ Class Registration Database SYSVOL Active Directory Cluster Quorum Certificate Server
The following table lists the Service State Writers and their equivalents in Windows 2000
Service State Writer
Selection for backup in Windows 2000
Selection for restore in Window 2000 At the volume level with the Restore Removable Storage data option selected. Volume level
Removable Storage Manager (RSM)
At the volume level, by selecting %SystemRoot%\System32\NTmsdata
Windows Internet Name Service Windows Management Instrumentation
Volume level
At the volume level, by selecting %SystemRoot%\System32\wbem\repo sitory
At the volume level, with the Restore Windows Management Instrumentation repository option selected
345
Service State Writer
Selection for backup in Windows 2000
Selection for restore in Window 2000 At the volume level, with the Restore Terminal Services database option selected. Volume level Volume level Volume level
Terminal Server Licensing
At the volume level, by selecting %SystemRoot%\System32\LServer
Event Logs Remote Storage Dynamic Host Configuration Protocol
Volume level Volume level Volume level
Automatic Exclusion of Files During Volume Level Backups

If you select a volume that contains Shadow Copy data for backup, Backup Exec determines which Shadow Copy files should not be included in a volume level backup. These files will be automatically excluded for backup by a feature called Active File Exclusion. If this exclusion did not happen during a non-snapshot backup, these files would appear as in use - skipped. If this exclusion did not happen during a snapshot backup, the files would be backed up in a possible inconsistent state, which could create restore issues.
Windows SharePoint Services Support

The Windows SharePoint Services feature pack utilizes a SQL (MSDE) instance called SHAREPOINT as a repository for shared information and collaboration data. On Windows Server 2003, in the absence of a Symantec SQL Agent installation, the SQL SHAREPOINT instance can be protected by the Shadow Copy Components file system. If the SQL Agent is installed, then the SQL SHAREPOINT instance can be protected by the SQL Agent. Note If Windows SharePoint Services is installed using an instance name other than the default SHAREPOINT instance name, then it cannot be protected by the Shadow Copy Components file system. In that case, the Symantec SQL Agent must be used to protect the SQL SHAREPOINT instance.
346
Small Business Server 2003 Support

Windows Small Business Server 2003 Standard and Premium contain a SQL (MSDE) instance called SBSMONITORING as a repository for server-related activity data. In the absence of a Symantec SQL Agent installation, the SQL SBSMONITORING instance can be protected by the Shadow Copy Components file system. If the SQL Agent is installed, then the SQL SBSMONITORING instance can be protected by the SQL Agent.
Active Directory Application Mode Writer Support

The Backup Exec Shadow Copy Components file system supports the Microsoft Active Directory Application Mode Writer (AD/AM Writer). AD/AM provides Active Directory service without the need for a domain controller. AD/AM is available in Windows Server 2003 as a non-operating system service. You can run multiple instances of AD/AM concurrently on a single server and configure each instance independently. Related Topics: Restoring Windows Server 2003 Systems on page 473 Using Redirected Restore for Active Directory, Active Directory Application Mode, and Install from Media on page 488
Protecting Upgraded Windows Server 2003 Resources

The information in this topic applies only if you upgraded to Backup Exec 10.0 from version 9.0.4367 or earlier. After upgrading Backup Exec on media servers and remote computers running production versions of Windows Server 2003 or upgrading the operating system from Windows 2000 to Windows 2003, you must edit selection lists and replace the System State selection with the Shadow Copy Components selection. The enhancements made to the Backup Exec Shadow Copy Components file system to support the Volume Shadow Copy Service will cause backup jobs that target Windows Server 2003 resources and include System State to fail. These jobs will also fail if you do not upgrade the media server, but only upgrade Backup Exec on remote computers running production versions of Windows Server 2003. If you upgrade Backup Exec on the media server only, and not on remote Windows resources, then existing remote Windows Server 2003 backup jobs that include System State are not affected and will not fail. Note To fully protect any local or remote computers running production versions of Windows Server 2003, you should upgrade to the latest version of Backup Exec on all media servers and update the Remote Agent for Windows Servers on any
347
remote computers running Windows Server 2003. Remote Agents from Backup Exec 9.0 Revision 4367 are not supported on production versions of Windows Server 2003. To prevent backup jobs that target Windows Server 2003 resources and include System State from failing, you must replace the System State selection with the Shadow Copy Components selection. If both the media server and the remote computers running Windows Server 2003 are upgraded to the latest Backup Exec, then the Backup Exec user interface will detect and notify you when obsolete selections such as System State are found. When you select a server or expand it using the graphical view, selections are checked for items that are no longer on the server, such as System State. If invalid items are found, you are prompted to remove them from the selection list (see To replace the System State selection: on page 348). If only the remote computers running Windows Server 2003 are upgraded to the latest Backup Exec, but the media server is not, you must manually edit the selection lists (see To edit selection lists when only the remote computers are upgraded: on page 349). To replace the System State selection: 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. If System State is in the selection list, the following message is displayed: System State is selected but cannot be found on server LocalTest. If this server has been upgraded to Windows Server 2003 or later, remove this selection, and then select Shadow Copy Components to fully protect your server. Do you want to remove the System State selection? 5. Click Yes to remove the System State selection. After removing invalid items from the selection list, backup jobs for that computer do not fail, but the System State-equivalent resource is not backed up. You must include the Shadow Copy Components resource in the backup selection list in order to back up the equivalent resources.
348
Note To protect Windows Server 2003 resources, you must select all Shadow Copy Components resources, the system drive, and the boot drive for backup. Only full backups can be run on the Shadow Copy Components. 6. Add the Shadow Copy Components resource to the selection list. 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. 7. Make any necessary changes to the job. To edit selection lists when only the remote computers are upgraded: 1. On the Edit menu, click Edit Selection List. 2. On the Edit Selection List dialog box, click the Edit button. 3. Under View Format, click Text. 4. Highlight the System State selection, and then click Delete. 5. Click OK. Related Topics: Editing Selection Lists on page 298
349
Backing Up Utility Partitions
Backing Up Utility Partitions

Backup Exec allows backups and restores 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. You must have Administrator rights to browse and back up 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. Symantec recommends backing up utility partitions when a full system backup is performed, such as during disaster recovery preparation. Related Topics: Restoring Utility Partitions on page 474 Disaster Preparation and Recovery on page 605
Backing Up EFI System Partitions

The Extensible Firmware Interface (EFI) is required to boot Windows on all Intel Itanium 64-bit computers. You can back up and restore EFI system partition data using Backup Exec on Intel Itanium 64-bit computers. EFI system partition data can be backed up only on remote computers using the Backup Exec Remote Agent. If EFI system partitions are on a computer, the EFI System Partition node appears as a resource in backup selections. In most cases, each computer will have only one EFI system partition. However, if more than one exists on a computer, Backup Exec displays only the active partition. The Advanced Open File Option is not available for use with EFI system partition backups. In addition, the Use the Windows Change Journal if available option on the General backup options dialog box is not available for EFI system partition backups. EFI system partitions can be recovered after a disaster using the Backup Exec IDR option. Related Topics: Restoring EFI System Partition Data on page 475
350
About Backup Strategies

A backup strategy is the collection of procedures you implement for backing up your network, including what methods of backups are performed, when backups are performed, and how media is rotated back into use for your regular backups. A good backup strategy allows minimal time to get a system up and running in the event of a disaster. Backup Exec offers flexible solutions for protecting the data on your network. Use the media rotation feature and let Backup Exec do all the administrative work for you, or design and manage your own media rotation strategy, the procedures for reusing media, that meets your exact specifications. You can create backup job templates that define your backup strategy, and then reuse the templates to implement your strategy for all resources being protected by your media server. Related Topics: Media Rotation Strategies on page 248
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.
351
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. 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.
352
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. You have more jobs to keep track of (for example, reviewing job histories, and so forth).
Disadvantages:
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. If any of the devices in the job are not available during the backup, the job results in an abnormal completion status.
Disadvantages:
353
Understanding Backup Methods and Their Advantages

Before you can develop your media rotation strategy, you will need to decide whether you want to perform only full backups or use a strategy that includes Full backups and one of the modified backup methods (differential, incremental or working set backups). The backup methods used by Backup Exec are:
Full. Includes all of the data that was selected for backup and uses the full backup method. Backup Exec detects the device as having been backed up. You can use either archive bit or modified time to determine if a file has been backed up.
Note You will need to perform a full backup of your server to establish a baseline for disaster recovery. Full backups also include Copy backups, which include all selected data and do not affect any media rotation scheme because the archive bit is not reset. Copy backups are useful when you need to:

Back up data for a special purpose (for example, to send to another site). Back up specific data. Perform an additional backup to take off-site. Back up data that belongs to a media rotation job without affecting the rotation cycle.
Another Full backup option is the archive backup option, which automatically deletes files from the volume after they have been successfully backed up. This backup method is designed for migrating data from disk to storage media and should not be incorporated in a regular backup schedule. Using the archive backup method allows you to free valuable disk space and reduce clutter on your server volume by migrating stagnant directories and files from the server to media. An archive backup job backs up the selected data, verifies the media, and then deletes the data from the volume. Note For data to be deleted, rights to delete a file must be granted; otherwise data will be backed up but not deleted. Backup Exec will not delete data from Backup Exec Agent workstations when using the archive feature.
Differential. Includes all files that have changed since the last full 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.
354
Backup Exec provides two differential backup methods, one that uses archive bit and one that uses modified time to determine if the file was backed up. If you select to use the FULL - Back Up Files - Reset Archive Bit and want to run differential backups, you must use the DIFFERENTIAL - Changed Files method. If you select to use the FULL - Back Up Files - Allows incrementals and differentials using modified time, you must use the DIFFERENTIAL - Using modified time method. In most schemes, differential backups are recommended over incremental backups. Differential backups allow much easier restoration of an entire device than incremental backups since only two backups are required. Fewer required media also decreases the risk of not being able to restore important data because of media errors.
Incremental. Incremental backups include only the files that have changed since the last full or incremental backup. Backup Exec provides two incremental backup methods, one that uses archive bit and one that uses modified time to determine if the file was backed up. If you select to use the FULL - 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.
Working set. The working set backup option includes two options; Changed today and Last accessed in x days. The Changed today option was called Daily backup in previous versions of Backup Exec. You can perform backups using the Changed today method in addition to the media rotation scheme selected. The Changed today method backs up all files with todays date (created or changed today). The Changed today method does not affect the files backup status because the archive bit is not reset. The Last accessed in x days method 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 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
355
schemes. However, in environments where active data is migrated frequently between machines, or when restore times are especially critical, working set backups can make up the cost of extra media in time savings for restoring data. There are advantages and disadvantages to each backup method.
Backup Method Advantages and Disadvantages Method Full Advantages
Disadvantages
Files are easy to find - Since full backups include all data contained on a device, you dont have to search through several media to find a file that you need to restore. There is always a current backup of your entire system on one media or media set - If you should need to restore your entire system, all of the most current information is located on the last full backup. 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.
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). Redundant backups - All of the files created or modified since the last incremental backup are included; thus creating redundant backups.
Differential
356
About Backup Strategies Backup Method Advantages and Disadvantages Method Incremental Advantages
Disadvantages
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.
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.
Working Set
Restoring a system backed up with a working set strategy requires only the media containing the latest working set backup media and the media containing the most recent full backup. You can perform a working set backup, restore the data to a new system, and be up and running faster than if you had to restore a full backup followed by all of the incremental or differential backups. Working set backups take less time to run than full backups.
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. 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.
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 293) for his server and submits the job to run at the end of the day on Friday. Since most files on the server, such as operating system files and application files, seldom change, Fred decides that he can save time and media by incorporating incremental or differential backups in his media rotation scheme. Fred opts to use incremental backups, so he schedules the script to run at the end of the day, Monday through Thursday, with the incremental backup method. Heres what happens: Freds Friday tape contains all of the data on the fileserver and Backup Exec changes all of the files statuses to backed up. At the end of the day on Monday, the incremental job runs and only the files that were created or changed (had the archive bit re-set by the operating system) are backed up. When the incremental job completes, Backup Exec will turn the archive bit off, showing that the files have been backed up. On Tuesday through Thursday, the same events happen. If Freds fileserver crashed on Thursday morning, after he got it running, he would restore each backup in the order in which it was created (for example, Friday, Monday, Tuesday, and so forth). If Fred had decided to perform differential backups on Monday through Thursday, he would have only needed Fridays and Wednesdays tapes: Fridays tape because it included all of the data, and Wednesdays tape because it included every file that had been created or changed since Fridays backup.
Understanding Modified Time and Backup Methods

If you select to use FULL - Back Up Files - 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
358
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. Using the modified time allows Backup Exec to run differential backups on file system, such as Unix, which do not have an archive bit. If you want Backup Exec to use modified time to determine if a file has been backed up, the full and incremental (or full and differential) backups must use the same backup selection list. Related Topics: Using Selection Lists on page 293
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.
359
360
Chapter
Policies and Templates
Policies provide a method for managing backup jobs and strategies. Policies contain job templates, which are job attributes that define how and when Backup Exec processes a job. Templates specify the devices, settings, and schedule for a job, but do not include the selections to be backed up. To create jobs, combine a policy with a selection list. Policies are useful in a number of situations. For example, you can set up policies for:
Rotating media. If you use the policy wizard to create a policy, you can use the Monthly full backup with weekly and daily backups option to create a Grandfather, Father, Son media rotation scheme. Setting relationships between jobs. When a policy contains more than one template, you can use template rules to establish relationships between the templates. For example, you can set a template rule so that when one backup job completes, Backup Exec automatically starts another backup job. Creating duplicate copies of backup sets. Set up a policy that contains a backup template and a duplicate backup set template. The duplicate backup set template initiates a job that copies the backup set created by the backup job. Exporting media. Set up a policy that contains an export media template and at least one backup template. Then, set up a template rule that schedules a media export job after the backup completes. Creating a synthetic backup. If you have purchased and installed the Advanced Disk-based Backup Option (ADBO), then you can set up a policy that contains the necessary job templates for creating a synthetic backup.
After you combine a selection list with a policy, Backup Exec automatically creates a job for each template in the policy. For example, if a policy contains three templates, Backup Exec will create one job for each template, for a total of three jobs. Polices are reusable, so you can create a single policy and combine it with several different selection lists.
361
Creating a New Policy
Related Topics: Policy Jobs Summary Report on page 590 Backup Set Details by Resource Report on page 566 Policy Protected Resources on page 592 About the Synthetic Backup Feature on page 876 Resource Backup Policy Performance Report on page 595

Creating a new policy involves choosing a name and description for the policy, adding templates to the policy, and setting up relationships between templates (if necessary). After you set up all of the templates for a policy, you should combine the policy with a selection list to create jobs. You can set up the policy manually or use the policy wizard. The policy wizard guides you through the creation of a policy using one of the following backup strategies:

Daily full backups Weekly full backup with daily backups Monthly full backup with weekly and daily backups (this creates the Grandfather, Father, Son media rotation scheme)
362
To create a new policy manually: 1. On the navigation bar, click Policy. 2. Complete the policy options as follows:
New Policy General options Item Policy name Description Type a unique name for this policy. You might want to use a name that describes the type of backup or the resources that this policy will protect, such as "Monthly full backup policy" or "My documents daily backup". The policy name that you enter here displays in the Policies list on the Job Setup view. Type a description of this policy.
Policy description
3. Click New Template. Then select the type of template you want to add:

Backup template. See Adding a Backup Template to a Policy on page 367. Export media template. See Adding an Export Media Template to a Policy on page 370. Duplicate backup set template. See Adding a Duplicate Backup Template to a Policy on page 382. Synthetic backup template. See Symantec Backup Exec - Advanced Disk-based Backup Option on page 875.
Note If you want to import an existing backup template into this policy, click Import Template. For more information, see Importing a Template into a Policy on page 372. To create a policy using the Policy Wizard: 1. On the navigation bar, click Job Setup. 2. In the task pane, under Policy Tasks, click New policy using wizard. 3. Follow the instructions in the wizard to create a policy.
Chapter 7, Policies and Templates
363
Editing a Policy
To edit a policy: 1. On the navigation bar, click Job Setup to edit a policy that is either associated with a scheduled job or that is not associated with any jobs, or click Job Monitor to edit a policy that is associated with a scheduled job. 2. To edit a policy that is associated with a job, right-click the job, and then select Edit Policy. To edit a policy that is not associated with a job, double-click the policy. Related Topics: Editing a Template in a Policy on page 372
Deleting a Policy
If you no longer need a policy, you can delete it. Before you delete a policy, you should be certain that you no longer need the jobs that are associated with the policy. Before you can delete a policy, you must remove the association between the selection lists and the policy. When you dissociate selection lists and policies, any active jobs that were associated with the policy will complete and then will be deleted. To delete a policy: 1. On the navigation bar, click Job Setup. 2. Select the policy that you want to delete. 3. If selection lists are associated with the policy: a. In the task pane, under Policy Tasks, click Delete jobs created by policy.
b. Clear the check boxes for the selection lists that are associated with this policy. c. Click OK.
4. Select the policy that you want to delete, and then under General Tasks on the task pane, click Delete. 5. Click Yes to confirm that you want to delete this policy.
364
Using an Example Policy

Backup Exec provides example policies that contain standard settings for the following policy types: media rotation, duplicate backup, and synthetic backup. You can copy the example policies and then customize them to meet your needs. To use an example policy: 1. On the navigation bar, click Job Setup. 2. In the Policies pane, right-click the example policy you want to use and then select Copy. The available example policies are Example: Media Rotation, Example: Duplicate Backup Data, and Example: Synthetic Backup Note The Synthetic Backup example policy displays only if you have purchased and installed the Advanced Disk-based Backup Option. For more information about the Synthetic Backup example policy, see Creating a Synthetic Backup By Copying the Example Policy for Synthetic Backup on page 881. 3. Select Copy to this media server or Copy to other media servers, and then click OK. Backup Exec creates a new policy named "Copy of <example policy>" and places it in the list of policies on the Job Setup view. 4. Customize the policy and templates as necessary. For example, you may want to give the policy a new name and description, and change when the templates are scheduled to run. For details on setting options in templates, see Adding a Backup Template to a Policy on page 367. 5. When finished, click OK. 6. Create jobs using this policy and a selection list. For more information, see Creating Jobs Using Policies on page 378.
Re-creating Example Policies

You can re-create example policies. If an example policy with the default example policy name already exists when you select the Re-create example policies option, Backup Exec creates another example policy and adds an incremented number to the example policy name. For example, if the Example: Media Rotation 0002 policy exists, Backup Exec creates another example policy called Example: Media Rotation 0003. To re-create example policies:
On the Tools menu, select Re-create Example Policies.

365
Using Templates in Policies

Templates are the building blocks of policies. They contain all the settings for a job, except the resources to be backed up. Each policy must contain at least one template. Backup Exec includes four types of templates:
Backup. Use this template to create backup jobs, such as full, incremental, and differential. For more information, see Adding a Backup Template to a Policy on page 367. Export media. Use this template to set up an export media utility job that runs automatically after a backup or duplicate backup set job completes. The export media job either moves media from robotic library slots into a portal or displays an alert reminding you to remove the media from a slot. For more information, see Adding an Export Media Template to a Policy on page 370. Duplicate backup set. With this type of template, you can use a staging strategy to create duplicate copies of backup sets. It allows multiple levels of data duplication, either within the backup window or outside of the backup window. For more information, see About Duplicate Backup Set Templates on page 381. Synthetic backup. This template is available only with the Backup Exec Advanced Disk-based Backup Option. For more information, see Symantec Backup Exec Advanced Disk-based Backup Option on page 875.
You can copy backup templates from one policy to another using the Import Template option. You can save time by importing templates that contain all or most of the settings you want to use. After you import templates, you can give the template a unique name and change any of the settings. Related Topics: Exporting Media on page 207 Importing a Template into a Policy on page 372
366
Migrating Templates from Previous Versions of Backup Exec

If you set up templates in Backup Exec version 9.0 or 9.1, you are already familiar with the concept of templates. When you upgrade to Backup Exec 10.0, each template that existed in your previous version of Backup Exec is automatically migrated into a separate policy that contains a single template. For example, if you had 10 templates in Backup Exec 9.1, you will have 10 policies in Backup Exec 10.0. Each policy will have one template. For information about migrating policies from Network Storage Executive (NSE), see Migrating from Network Storage Executive v8.6 (NSE) on page 838.
Adding a Backup Template to a Policy

Each policy you create must include at least one template. The templates include the information that Backup Exec needs to run jobs. Creating a backup template is similar to creating a backup job. You select the device and media you want to use, the settings for the job, and the schedule for the job. However, in templates you do not select resources to back up. After a policy is complete, create a job by combining the policy with the selection list that includes the resources you want to back up. To add a backup template to a policy: 1. Set up a new policy using the steps in Creating a New Policy on page 362. 2. On the New Policy dialog box, click New Template. 3. On the Template Selection dialog box, select Backup Template, and then click OK. 4. Complete the Device and Media options. For more information about completing device and media options, see Device and Media Options for Backup Jobs and Templates on page 266. 5. On the Properties pane, under Settings, click General. Complete the General options for this template. For more information about General options, see General Options for Backup Jobs and Templates on page 270. 6. On the Properties pane, under Settings, click Advanced. Complete the Advanced options for this template. For more information about Advanced options, see Advanced Options for Backup Jobs on page 276.
7. On the Properties pane, under Settings, click Pre/Post Commands. Complete the Pre/Post Command options. For more information about pre/post commands, see Pre/Post Commands for Backup or Restore Jobs on page 280.
Chapter 7, Policies and Templates 367
8. On the Properties pane, under Settings, select additional options for this job as needed:
If you are using the Advanced Open File Option, select Advanced Open File and complete the options as described in Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999. If you want to use Offhost backup, select Advanced Disk-based Backup and complete the options as described in About the Offhost Backup Feature on page 888. If you are backing up other platform types or database agents, such as NetWare, Exchange, SQL, or SharePoint, select the platform type or database agent. Refer to the chapter for that item for instructions on completing the options. If you want to change the backup network for this job, select Network and Firewall. For more information, see Changing the Backup Network for a Job on page 339. If you want Backup Exec to notify someone when the backup job completes, select Notification. For more information, see Selecting Recipients for Notification on page 534. If you want Backup Exec to notify someone when a backup job containing a specific selection list completes, on the Properties pane, under Source, click Selection List Notification (see Selecting Recipients for Notification on page 534). If you want to prevent certain files or file types from being included in the backup, select Exclusions. For more information about file exclusion, see Including or Excluding Files for Backup Using Advanced File Selection on page 288.
9. Set the schedule for the template. See Setting the Schedule for a Template on page 369. 10. Click OK. The template is complete. You can add another template or combine the policy with a selection list. For more information, see Creating Jobs Using Policies on page 378.
368
Setting the Schedule for a Template

There are three types of schedules for a template:
Run now and run according to rules for this template. If you select this option, the job will run as soon as a selection list is combined with the policy in which the template is contained. If the template is also linked to another template via a template rule, the job will also run according to the rule selected for the template. Run according to schedule and run according to rules for this template. If you select this option, you can set a date when the template will go into effect, a time window, and the days on which the job will run. If the template is also linked to another template via a template rule, the job will also run according to the rule selected for the template. This is the default setting for templates. Run only according to rules for this template. If you select this option, the template must be part of a template rule. The job created from the template will run based on the rule set for the template.
You can set an availability window and a priority on selection lists. If you set a schedule for a template that is not within the availability window for the selection list, Backup Exec displays the job status as Invalid Time Window. To set the schedule for a template: 1. On the Properties pane, under Frequency, select Schedule. 2. Select one of the following options:
Template Schedule Options Item Run now and run according to rules for this template Description Select this option to run the job immediately after a selection list is combined with the policy in which this template is contained. If the template is part of a template rule, the job will also run according to the template rule. Select this option to configure a schedule for a recurring job, and then click Edit Schedule Details to set the schedule. For more information, see Editing the Job Schedule on page 401. If the template is part of a template rule, the job will also run according to the template rule.
Run according to schedule and run according to rules for this template
369
Using Templates in Policies Template Schedule Options Item Run only according to rules for this template Description Select this option to set the job to run based on a template rule. For example, with the After <First Template> completes, start <Second Template> template rule, the <Second Template> will run whenever the <First Template> completes. Select this option to submit the jobs that are created using this template with an on-hold status. You should select this option if you want to submit the job, but do not want it to run until you change the jobs hold status.
Submit job on hold
Adding an Export Media Template to a Policy

You can use the export media template to set up an export media utility job that runs automatically after a backup or duplicate backup set job completes. If the targeted device is a library with a portal, the export media job moves the media from its slot in the portal and generates an alert reminding you to remove the media from the portal. If the device is a library that does not have a portal, the export media job will generate an alert reminding you to remove the media from the indicated slot. The export media template must be part of a multi-template policy. There must be a source template that produces media and initiates the export job. For example, if you want to export media after your monthly full backup completes, set up a policy with a backup template for the monthly full backup job and set up an export template to run after the monthly full job completes. If a job requires multiple pieces of media, the export media job starts after the source backup job completes, not after each piece of media is filled. When you create an export media template, Backup Exec automatically adds the After <First Template> completes, start <Second Template> to export media template rule to the policy. Backup Exec replaces the <First Template> with the name of the template that you select as the source for the export media template, such as a backup template. Backup Exec replaces the <Second Template> with the export media template. To add an export media template to a policy: 1. Set up a new policy using the steps in Creating a New Policy on page 362. 2. Set up a backup template, which will be the media-producing template that is the source for the export job. 3. On the New Policy dialog box, click New Template.
4. On the Template Selection dialog box, select Export Media Template, and then click OK. Note The Export Media template displays only if the policy contains a backup template. 5. Select the media-producing template to use as the source for the export job. For example, if you want to export media after the monthly full backup completes, select the template for monthly full backups as the source media set template. 6. On the Properties pane, under Settings, click General. Type a name for this export media template. 7. If you want to set up notification for this job, on the Properties pane, under Settings, click Notification. For more information, see Selecting Recipients for Notification on page 534. Note The export media job must run according to the template rule, so you do not need to set any schedule options for this job. 8. Click OK. Backup Exec adds the template rule called After <First Template> completes, start <Second Template> to export media. The template is complete. You can add another template or combine the policy with a selection list. For more information, see Creating Jobs Using Policies on page 378.
371
Importing a Template into a Policy

Importing templates makes template creation easier. If an existing template contains many of the settings that you want to use again, you can import the existing template into a policy instead of manually creating a new template and duplicating the settings. Backup Exec does not import any template rules that are associated with the imported template. After you import a template into a policy, you can change the template settings as needed. To import a template into a policy: 1. On the navigation bar, click Job Setup. 2. If you want to import a policy into an existing policy, in the Policies section, double-click the policy. If you want to create a new policy and then import an existing template into it, in the task pane, under Policy Tasks, click New policy. Enter a policy name and description. 3. Click Import Template. 4. Select the templates you want to import. 5. Click OK. Backup Exec copies the templates into the policy and provides the default name of "Copy of <template name>". To change the template name or other properties, select it from the list and click Edit Template.
Editing a Template in a Policy

To edit a template in a policy: 1. On the navigation bar, click Job Setup. 2. In the Policies section, double-click the policy that contains the template you want to edit. 3. Select the template from the list that displays in the Policy Templates area. 4. Click Edit Template. 5. Change the template properties as needed.
Setting Template Rules
Deleting a Template from a Policy

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

Template rules enable you to set up relationships between templates in a policy. For example, you can use template rules to determine which job should be processed first if a start time conflict exists, or to determine which job should start when another job starts, ends, or fails. When you set a template rule, you must select the rule you want to use and the templates to which the rule will be applied. Backup Exec displays different rules depending on the types of templates that exist in the policy. For example, if a policy contains a duplicate backup template, Backup Exec displays rules for duplicating backup sets. If Backup Exec automatically adds a template rule to a template, you should not delete that rule.
373
The following template rules are available:

Template Rules Rule Description
Rules to handle conflicting job start times If start times conflict, <First Template> supersedes <Second Template>. If two templates in the same policy have the same start time, the <First Template> will run first. The <Second Template> will run according to the schedule set for it, after the <First Template> job completes. For example, you set a weekly backup to run every Saturday at 5:00 p.m. and a daily backup to run every day at 5:00 p.m. On Saturday, both the weekly backup and the daily backup are scheduled to run at 5:00 p.m. If you set the weekly backup as the <First Template> and the daily backup as the <Second Template>, the weekly backup will run at 5:00 p.m. on Saturday. The daily backup will not run on Saturday, but it will run on Sunday at 5:00 p.m., according to its schedule. If two templates in the same policy have the same start time, the <First Template> will start first. After the <First Template> completes, the <Second Template> will start automatically.
If start times conflict, <First Template> will start and upon completion, starts <Second Template>.
Rules to link jobs together After <First Template> starts, also start <Second Template>. After <First Template> completes, start <Second Template>. With this rule, you can run two jobs simultaneously.
Use this rule if you want Backup Exec to start a job automatically after a selected job completes. The second job will start regardless of whether the first job completes successfully. For example, if the first job fails, the second job will run. Use this rule if you want Backup Exec to automatically start a job after a selected job successfully completes. The second job will not start if the first job fails.
If <First Template> successfully completes, start <Second Template>.
If <First Template> fails, Use this rule if you want Backup Exec to automatically start a new job start <Second if a selected job fails. Template>.
374
Setting Template Rules Template Rules Rule Description
Rules to limit when jobs run <First Template> must complete at least once before any other templates will be allowed to start. This rule is used when baseline backups are needed, such as with synthetic backup templates. If you set up a baseline backup job, it must complete before any other synthetic backups can begin. If you set the baseline backup template as the <First Template> in this rule, you can ensure that no other synthetic backup jobs will run until the baseline backup completes. This rule applies to synthetic backups. If you set up a baseline backup, it needs to run only once.
Run <First Template> only once.
Rules to duplicate backup sets Duplicate all backup sets that were created by <First Template> using <Second Template> as scheduled. This rule applies to a duplicate backup template. It displays only if the policy contains a duplicate backup template and the template has a schedule associated with it. Backup Exec automatically adds this rule to the policy if you set the schedule for the template to Run now and run according to rules for this template or Run according to schedule and run according to rules for this template. With this rule, you can set up the data duplication job to run outside of the backup window. This rule applies to a duplicate backup template and displays only if the policy contains a duplicate backup template. After you create a duplicate backup template, Backup Exec automatically adds this rule to the policy if you set the schedule for the template to Run only according to rules for this template. Backup Exec replaces <First Template> with the template that you selected as the source for the duplicate backup template, and replaces <Second Template> with the duplicate template you created. With this rule, it is likely that the duplication job will run during the backup window. If you do not want to run the duplication during the backup window, use the Duplicate all backup sets that were created by <First Template> using <Second Template> as scheduled rule.
After <First Template> completes, start <Second Template> to duplicate the backup set.
Rules to export media After <First Template> completes, start <Second Template> to export media. This rule applies to export media templates and displays only if the policy contains an export media template. After you create an export media template, Backup Exec automatically adds this rule to the policy. Backup Exec replaces <First Template> with the template that you selected as the source for the export media template, and replaces the <Second Template> with the export media template you created. 375
To set a template rule: 1. On the navigation bar, click Job Setup. 2. If you want to set template rules for existing templates in an existing policy, in the Policies section, double-click the policy. If you want to create a new policy, in the task pane, under Policy Tasks, click New policy. Enter a policy name and description. Then create a new template. 3. On the Policy Properties screen, click New Rule. 4. Complete the fields that display as follows:
Template Rule options Item Template rule First template Description Select the template rule that you want to apply. Select the template that you want to insert into the <First Template> slot in the template rule you selected. The first template is usually the trigger for the second template. For example, in the template rule After <First Template> completes, start <Second Template>, the first template must complete before Backup Exec will start the second template. Select the template that you want to insert into the <Second Template> slot in the template rule you selected. Some rules do not require a second template. If a second template is not required for a template rule, you cannot select a template from this option.
Second template
5. Click OK.
376
Changing Template Rules

To change a template rule: 1. On the navigation bar, click Job Setup. 2. In the Policies section, double-click the policy. 3. On the Policy Properties screen, select the rule you want to change and click Edit Rule. 4. Change the template rule as needed. 5. Click OK.
Deleting Template Rules

You can delete template rules that you added to templates. You should not delete template rules that Backup Exec added to a template automatically. For multi-stage backup templates, at least one template rule must exist. You should not delete template rules for export media templates. To delete a template rule: 1. On the navigation bar, click Job Setup. 2. In the Policies section, double-click the policy. 3. On the Policy Properties screen, select the rule you want to delete and then click Delete Rule. The rule is removed from the policy.
377
Creating Jobs Using Policies

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

You can view a list of the selection lists that are designated for backup by a selected policy, or view a list of policies that are designated to back up a selected selection list. To view a list of selection lists that are designated for backup by a selected policy: 1. On the navigation bar, click Job Setup. 2. Under Policies, right-click the policy for which you want to view selection lists designated for backup. 3. Click View Selection Lists Backed Up By Policy. To view a list of policies that are designated to back up a selected selection list: 1. On the navigation bar, click Job Setup. 2. Under Backup Selection Lists, right-click the selection list for which you want to view policies. 3. Click View Policies That Back Up Selection List.
Editing the Next Occurrence of a Policy-based Job

You can edit the next occurrence of a scheduled policy-based job. Only the next occurrence of a scheduled job can be edited. After the next occurrence of the job completes, the job will resume its original settings as created in the policy. Edits made to the associated policy will overwrite any edits made to the jobs next occurrence. To edit the next occurrence of a scheduled policy-based job: 1. On the navigation bar, click Job Monitor. 2. Click the Job List tab. 3. Right-click the job you want to edit, and then click Edit Next Run.
379
Deleting a Job Created from a Policy

In order to delete a job that was created from a policy, you must dissociate the selection list from the policy. Backup Exec deletes any scheduled jobs that were created from the policy. Any active jobs that were created from the policy will complete and then will be deleted To delete a job created from a policy: 1. On the navigation bar, click Job Setup. 2. Select the policy or the selection list from which the job was created. 3. If you selected the policy, under Policy Tasks, click Delete jobs created by policy. If you selected the selection list, under Selection List Tasks, click Delete jobs created by policy. 4. Clear the check box for the policy or selection list, and then click OK. Backup Exec deletes the jobs that were created from the policy.
Renaming a Job Created from a Policy

When you create a job from a policy, Backup Exec automatically names the job. The job name is a combination of the selection list name, policy name, and template name. For example, a job created from a policy might be named Backup Selection List 0001-Policy 001-Backup Template 0001. You can rename jobs that were created from policies to make them more meaningful to you. Note If you are using BEWAC, you cannot rename jobs created from a policy. To rename a job that was created from a policy: 1. On the navigation bar, click Job Setup. 2. Under Jobs, right-click the policy-created job that you want to rename. 3. Click Rename. 4. Type the new name in the Name field, and then click OK.
380
About Duplicate Backup Set Templates

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

Add a backup template with a recurring schedule. Add a duplicate template and set the Run only according to rules for this template schedule option.
Backup Exec automatically adds the After <First Template> completes, start <Second Template> to duplicate the backup set template rule to the policy.
Chapter 7, Policies and Templates 381
The incremental duplication method. This method requires at least one backup template and at least one duplicate template. If a policy contains several templates, you can use this method to associate one duplicate backup template to several backup and/or duplicate backup templates. With this method, use the Duplicate all backup sets that were created by <First Template> using <Second Template> as scheduled template rule. To set up duplicate backups using this method, you must set up a policy and then:

Add a backup template with a recurring schedule. Add a duplicate backup template with a recurring schedule. Set up a template rule using the Duplicate all backup sets that were created by <First Template> using <Second Template> as scheduled template rule.
Adding a Duplicate Backup Template to a Policy

To add a duplicate backup template: 1. Set up a new policy using the steps in Creating a New Policy on page 362. 2. Set up a backup template. 3. On the New Policy dialog box, click New Template. 4. On the Template Selection dialog box, select Duplicate Backup Sets Template, and then click OK. 5. Select the source template, which is the template that will provide the backup data to be copied. 6. In the Properties pane, under Destination, select Device and Media. For more information about the device and media options, see Device and Media Options for Backup Jobs and Templates on page 266. Note A duplicate backup set template must use a destination device that can be accessed by the same media server as the device specified for the original backup set.
382
7. In the Properties pane, under Settings, select General. Complete the appropriate options as follows:
New duplicate backup Job Template General Options Item Template name Backup set description Preferred source device Description Type the name for this template. Type a description of the information you are backing up. Select the device that was used as the destination device for the original backup job.
8. In the Properties pane, under Settings, select Advanced. Complete the appropriate options as follows:
New duplicate backup Job Template Advanced Options Item Verify after job completes Description This option enables Backup Exec to automatically verify that the media can be read after the backup completes. This option is selected by default. Symantec recommends that you verify all backups.
383
About Duplicate Backup Set Templates New duplicate backup Job Template Advanced Options Item Compression type Description Select one of the following:
None. Select this option to copy the data to the media in its original form. If the data was backed up using software compression, then it is copied in its software compression form. Using some form of data compression can help expedite backups and preserve storage media space. Hardware data compression should not be used in environments where devices that support hardware compression are used interchangeably with devices that do not have that functionality. For example, if a drive that does not support hardware compression is added to a cascaded drive pool that includes drives supporting the feature, hardware compression is automatically disabled. You can manually re-enable hardware compression on the drives that support it, but this results in media inconsistency. If the drive that supports hardware compression fails, the compressed media cannot be restored with the non-compression drive
Hardware [if available, otherwise none]. Select this option to use hardware data compression (if the storage device supports it). If the drive does not feature data compression the data is backed up uncompressed.
9. If you want to set up notification for this job, on the Properties pane, under Settings, click Notification. For more information about notifications, see Selecting Recipients for Notification on page 534. 10. Set the schedule for the backup job. See Setting the Schedule for a Template on page 369. Note You must set a schedule for the template if you want to use the Use scheduled <Second Template> to duplicate all backup sets that were created by <First Template> template rule. 11. Click OK. You can add another template to the policy or combine the policy with a selection list to create jobs.
384
Chapter
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 (Configuring Logon Accounts on page 386) Copy jobs, selection lists, and policies to local or remote servers (Copying Jobs, Selection Lists, and Policies on page 394) Copy media server configuration settings and logon account information to other media servers (Copy Configuration Settings and Logon Information on page 396) Schedule jobs (Scheduling Jobs on page 398) Monitor jobs (Monitoring Jobs on page 405) Link directly from an error code in a job log to the Symantec Technical Support web site to view more information about the error (Unique Message Identifier (UMI) Error Codes In Job Logs on page 432) Configure audit logs (Configuring the Audit Log on page 439) Configure error-handling rules (Error-Handling Rules on page 439) Configure thresholds to recover jobs (Setting Thresholds to Recover Jobs on page 445) Configure database maintenance (Configuring Database Maintenance on page 447)
385
Configuring Logon Accounts

A Backup Exec logon account stores the credentials of a Windows user account. Backup Exec logon accounts enable Backup Exec to manage user names and passwords and can be used to browse resources or process jobs. Using Backup Exec logon accounts enables you to apply Windows credential changes to the jobs that use them. Backup Exec logon accounts are used to browse local and remote resources. Backup Exec logon accounts can also be associated with selection list entries at the device level such as shares, databases, etc. If you need to edit the credentials, you can edit the Backup Exec logon account and the changes will be applied to the selected resources that use the Backup Exec logon account. Backup Exec logon accounts are not Windows user accounts. When you create a Backup Exec logon account, an entry for the account is entered into the Backup Exec database; no operating system accounts are created. If your Windows user account credentials change, you must update the Backup Exec logon account with the new information. Backup Exec does not maintain a connection with the Windows user account. You can view, create, delete, edit, and replace Backup Exec logon accounts using the Logon Account Management dialog box. The dialog box displays property information for each Backup Exec logon account you create. It also displays your default Backup Exec logon account and the Windows user name that is currently logged on to the media server. To view this information, select the Network menu, and then click Logon Accounts. Related Topics: Creating a Backup Exec Logon Account on page 388
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.
386
For example, you are logged on to a media server named MEDIASERVER as the local Windows administrator. When you start Backup Exec, you are prompted to create a default Backup Exec logon account for the local administrator because one does not exist. You can create a Backup Exec logon account for the local administrator that has the credentials for a domain administrator. The Backup Exec logon account will have the following properties: User name: DOMAIN\Administrator Description: MEDIASERVER\Administrator Default Account Owner: MEDIASERVER\Administrator When you change your default Backup Exec logon account, you can use your new default Backup Exec logon account to browse resources immediately; you do not have to restart your system in order for the changes take effect.
Make backup selections. You can select a different Backup Exec logon account when you make selections for backup. If your default does not have rights, the Logon Account Selection dialog box appears and enables you to create or select a different Backup Exec logon account. You can also change the Backup Exec logon account when making backup selections using the Connect As command in the context menu.
Note For more information on using Backup Exec logon accounts with Exchange mailbox and SQL backups, see Using Backup Exec Logon Accounts for SQL Resources on page 1015 and Using Backup Exec Logon Accounts with Exchange Resources on page 1068.
Restore. You can assign Backup Exec logon accounts to resources when you create restore jobs. The default Backup Exec logon account is used unless you choose a different Backup Exec logon account when you create the restore job, in Resource Credentials in the Restore Job Properties.
Related Topics: Changing Your Default Backup Exec Logon Account on page 392
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.
Chapter 8, Administrating Backup Exec
387
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 Command Line Applet Backup Exec R/3 Agent
Related Topics: Creating a New Backup Exec System Logon Account on page 392
Creating a Backup Exec Logon Account

You can create Backup Exec logon accounts using the Logon Account Wizard, which guides you through the creation of a Backup Exec logon account, or by using the Logon Account Management dialog. You can enter Backup Exec logon account property information when you create the Backup Exec logon account; however, Backup Exec assigns the Backup Exec logon account owner to the Windows user name you used to log on to Backup Exec. The owner of the Backup Exec logon account cannot be modified. To create a new Backup Exec logon account using the Logon Account Wizard:
On the Tools menu, point to Wizards, and then click Logon Account Wizard. The wizard will guide you through the process of creating a Backup Exec logon account.
To create a new Backup Exec logon account using the Logon Account Management dialog: 1. On the Network menu, click Logon Accounts. 2. Click New.
388
3. Enter the appropriate options as follows:

Add Logon Credentials dialog box Item User name Description Type the fully qualified user name for the Backup Exec logon account. For example, DOMAIN\Administrator. The user name is provided when you attempt to connect to a resource. The user name you enter is not case-sensitive for the resources that are accessed. Type the password for the account. The password you enter is encrypted for security. You can leave this field blank if this Backup Exec logon account does not need a password. Re-type the password for confirmation. The password must match the password you typed in the Password field. Type the unique name for the Backup Exec logon account. The user name is automatically added if you do not enter information into the field. Type any comments to describe how the Backup Exec logon account will be used. 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.
Password
Confirm password
Account name
Notes
This is a restricted logon account
This is my default logon Select this check box to make this your default Backup Exec logon account account used to browse, make selections, or restore data on your local and remote resources.
4. Click OK to create the Backup Exec logon account. Related Topics: Deleting a Backup Exec Logon Account on page 391 Replacing a Backup Exec Logon Account on page 391
389
Editing a Backup Exec Logon Account

When you edit a Backup Exec logon account, the changes are automatically applied to all the resources that use the Backup Exec logon account. Changes made to a Backup Exec logon account are applied immediately. You do not have to restart your system for the changes to take effect. You can edit the following properties for a Backup Exec logon account:

Type (restricted or common) Account name Password User name Notes
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. If you are using the Backup Exec Web Administration Console, select Check here to change the password for this account.
b. In Password, type a new password. c. In Confirm, re-type the password, and then click OK.
5. On the Edit Logon Credentials dialog box, click OK.
390
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. 3. Select the Backup Exec logon account with which you want to replace the selected Backup Exec logon account. If the Backup Exec logon account is restricted and you are not logged on to Backup Exec with the same user name as the Backup Exec logon account owner, you must provide the password before you can edit the account. 4. Click OK.
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.
391
3. Click Yes to confirm the deletion. The Backup Exec logon account is removed from the Backup Exec logon account list.
Changing Your Default Backup Exec Logon Account

You can change your default Backup Exec logon account that enables you to browse, make selections, or restore data. To change your default Backup Exec logon account: 1. On the Network menu, click Logon Accounts. 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 do one of the following:

Click Set as Default. Click Edit, select the check box This is my default logon account, and then click OK.
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.
392
3. Select the appropriate options as follows, and then click OK to create the system logon account:
Edit Logon Credentials dialog box Item User name Description Type the fully qualified user name for the Backup Exec logon account. For example, DOMAIN\Administrator. The user name is provided when you attempt to connect to a resource. The user name you enter is not case-sensitive for the resources that are accessed. Enables you to type and confirm a new password for the account. The password you enter is encrypted for security. You can leave this field blank if this Backup Exec logon account does not need a password. Type any comments to describe how the Backup Exec logon account will be used. 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.
Change password
Notes
This is a restricted logon account
This is my default logon Select this check box to make this your default account used to account browse, make selections, or restore data on your local and remote resources.
393
Copying Jobs, Selection Lists, and Policies
Copying Jobs, Selection Lists, and Policies

Backup Exec enables you to copy all jobs (including backup, report, utility, and archive jobs), selection lists, and policies that were created on your media server to the same media server, or to another media server. Note To copy jobs, selection lists, or polices to other media servers, the Copy Server Configurations feature must be installed. For more information, see step 7 in Installing Backup Exec Using the Installation Program on page 67. To copy jobs, selection lists, or policies: 1. On the media servers navigation bar, click Job Setup. 2. Select the job, backup selection list, or policy you want to copy. 3. Under General Tasks in the task list, select Copy. 4. On the Copy dialog box, select the appropriate options as follows:
General options for Copy to Media Server job Item Copy to this media server Copy to other media servers Destination media servers Description Select this option if you want to copy to this media server.
Select this option if you want to copy to other media servers.
If you are copying to other servers, select the media server you want to copy to. If the media server doesnt appear on the list, click Add, and then enter the media server name.
Overwrite Select this option if you want to overwrite an existing job, selection jobs/selection lists, or list, or policy having the same name. policies with identical names that already exist on the destination media server Overwrite logon Select this option if you want to overwrite logon accounts for an accounts used by this existing job having the same name. This option only appears if you job already exist on the are copying a job to another media server. destination server
394
Copying Jobs, Selection Lists, and Policies General options for Copy to Media Server job (continued) Item Add Description Click this button if you want to add a media server to the Destination media servers list. Select a media server, and then click this button if you want to edit information stored for a media server, such as logon account information. Select a media server, and then click this button if you want to remove a media server from the Destination media servers list. Click this button if you want to import a list of media servers to be added Destination media servers list. The list should include only the media server name, with one per line.
Edit
Remove
Import List
5. Click OK. The operation is queued. The default time-out is five minutes; if the transfer cannot be completed within five minutes, the transfer is terminated and an alert is issued. The queue checks for copy jobs every 60 seconds, and then sends all the copy jobs that are queued. Backup Exec sends an alert with the job success or failure status along with a log file that allows you to view results. The job log for Copy to Media Server jobs does not display with the other job logs in the Job History. To view the job log for a Copy to Media Server job: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts or Alert History tab. 3. Click the Source column heading. 4. Locate an alert with Job as a Source and Copy to Media Server job as a Job Name. 5. Right-click the alert, and then select View Job Log. 6. If a Copy to Media Server alert does not exist:
395
Copy Configuration Settings and Logon Information
a.
In the task pane, under Alert Tasks, click Configure alert categories and make sure that the alert categories Job Failed and Job Success are enabled.
b. On the Tools menu, click Options, and then click Preferences. Make sure that the option Automatically display new alerts is selected.

You can copy configuration settings and logon information from one media server to another. This copy ability allows you to quickly set up a group of media servers with the same configuration or logon settings. Note To copy configuration settings and logon information to other media servers, the Copy Server Configurations feature must be installed. For more information, see step 7 in Installing Backup Exec Using the Installation Program on page 67. To copy configuration settings: 1. From the Tools menu, click Copy Settings to Media Servers. 2. Select the appropriate options as follows:
Copy options Item Default job options Description Select this option to copy the default job options from this media server to selected servers. For information about default job options, see Backup Exec Defaults on page 119. Select this option to copy the default schedule from this media server to selected servers. For more information about default schedule option, see Configuring Default Schedule Options on page 403. Select this option to copy error-handling rules from this media server to selected servers. For more information about error-handling rules, see Error-Handling Rules on page 439. Select this option to copy alert configurations to selected servers. For more information about alert configuration, see Configuring Alert Category Properties on page 511.
Default schedule
Error-handling rules
Alert configuration
396
3. If the destination media servers appear on the list, select all of the media servers that you want to copy to. 4. If a destination media server name does not appear: a. Click Add.
b. Enter the name of the media server. c. If necessary, click Change Logon Account and select or enter the correct logon account information (see Configuring Logon Accounts on page 386).
5. Repeat step 4, if necessary, to add another media server that you want to copy the configurations to. 6. If you want to import a list of media servers, click Import List, browse to select the list, and then click Open. 7. After all media servers have been selected, click OK. To copy logon account information to another media server: 1. From the Network menu, click Logon Accounts. 2. Select the logon account information you want to copy, and then click Copy to Servers. 3. Enter the name of the media server you want to copy the logon account information to, and then click Add. 4. Repeat step 3 for each media server you want to copy the logon account to. 5. Click OK.
397
Scheduling Jobs
Scheduling Jobs
The schedule option enables you to configure the time and the frequency that you want to run jobs. You can configure a schedule for jobs such as backup, restore, inventory, 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 template in a policy, see Setting the Schedule for a Template on page 369. Note When you create a backup selection list, you can set a time range when the resources in the list will be available for backup. The time range is called the availability window. If you schedule a job to run outside of the availability window, the job does not run and Backup Exec displays an Invalid Schedule status for the job on the Job Monitor. When scheduling a job, be sure that the schedule is within the availability window for the resources. For more information, see Setting Priority and Availability Windows for Selection Lists on page 301. To configure a schedule for a job: 1. Determine the type of job you want to schedule, and then on the navigation bar, click the appropriate button. For example, to schedule a backup job, click Backup. 2. On the Properties pane, under Frequency, click Schedule. 3. Select the appropriate options as described in the following table, and then click Submit:.
Schedule Job Properties dialog box Item Current date and time Schedule Run now Run on Date at Time Select Run now to run the job immediately. Select Run on Date at Time to schedule the job to run one time on the selected date at the selected time, and then type the date and time. Description Displays the current date and time set on this computer.
398
Scheduling Jobs Schedule Job Properties dialog box (continued) Item Run according to schedule Description Select 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 401. 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 four month period with the selected scheduled run dates in bold. Effective date If Run according to schedule is selected, the effective date displays the day that the schedule begins. If Run according to schedule is selected, the time window displays the specified period of time during which a job can begin on any scheduled day. When setting up the time during which a task runs, you can enter a time window that extends past midnight and into the next day. Bear in mind, however, that this may change the days on which the task runs. For example, if you schedule a task to run every Friday between 8:00 PM and 4:00 AM, its possible for the task to run on Saturday morning sometime before or at 4:00 AM. If you dont want the task to run on Saturday, you must alter the time window, for example, by changing the ending value from 04:00:00 AM to 11:59:59 PM. Then, the task is confined to one day. Note When a time window crosses midnight, the start time is later in the day than the end time. Submit job on hold Select Submit job on hold if you want to submit the job with an on-hold status. You should select this option if you want to submit the job, but do not want the job to run until you change the jobs hold status. Enable automatic cancellation Select 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 dispatched to the job engine, not when the job begins. This option is available for restore and utility jobs but not for backup jobs.
Time window
399
Scheduling Jobs Schedule Job Properties dialog box (continued) Item Job deletion Delete the job if the job Select this to delete jobs that complete successfully, have been successfully completes created to run once, either now or at a scheduled time, and have not been created from a template. This option is selected by default. Delete the job after the Select this to delete jobs that complete, but with exceptions, have job completes been created to run once, either now or at a scheduled time, and have not been created from a template. This option is selected by default. Do not delete the job Select this to keep the jobs that were created to run once, and were not created from a template, in the Job Setup view. Description
Note If you are using Backup Exec for Web Administration Console (BEWAC), click OK when you are ready to submit the job to the job queue or run the job after you view the job summary. If you are not satisfied with the settings you selected, click Cancel, and reset all of the settings Related Topics: Backing Up Data on page 259 Monitoring Jobs on page 405 Configuring Default Schedule Options on page 403 Configuring Holiday Scheduling for Jobs on page 404 Setting the Schedule for a Template on page 369
400
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. 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. To edit schedule details for a job: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Frequency, click Schedule. 3. Click Run according to schedule to configure a schedule for a recurring job, and then click Edit Schedule Details to configure the schedule. 4. 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. Description
401
Scheduling Jobs Schedule Options (continued) Item Time Window Description 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. Days of the Month 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. 402 Administrators Guide
Scheduling Jobs Schedule Options (continued) Item Exclude Dates Description 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.
5. Click OK to return to the Schedule dialog box. 6. You can start the job after editing the schedule or select other options from the Properties pane. Related Topics: Configuring Holiday Scheduling for Jobs on page 404
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 401. 4. Click OK to return to the Schedule dialog box.
403
Scheduling Jobs
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. Related Topics: Backup Exec Defaults on page 119
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.
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 with exceptions, failed, and canceled jobs in the Job History pane. The Calendar view displays scheduled, active, and completed jobs in either a day, week, or monthly view. Related Topics: Managing Custom Filters on page 407 Viewing and Changing Active Jobs on page 415 Viewing and Changing Scheduled Jobs on page 420 Viewing and Changing Completed Jobs on page 427
Viewing and Filtering Jobs in the Job List View

The Jobs list view displays active and scheduled jobs, and job histories in the Current Jobs and Job History panes. You can select predefined filters to limit the jobs that appear in each pane, and you can create your own filters, called custom filters, to further refine the list of jobs that appear in each pane. To view jobs in the Jobs list view: 1. On the navigation bar, click Job Monitor 2. Click the Job list tab. To set View Filters for Current Jobs and Job History: 1. On the navigation bar, click Job Monitor. 2. Click the Job list tab.
405
Monitoring Jobs
3. Under Current Job View Filters or Job History View Filters, select or clear the appropriate filters as follows:
Jobs List View Filters Item Current Job View Filters Show active jobs Show scheduled jobs Use custom filter Lists jobs currently processing or in the job queue. Lists the next occurrence for a job. Select a custom filter from the drop down list. Only information that you have specified in a custom filter about current jobs or a type of current job, such as a backup or restore job, is displayed. Note Only custom filters that you have created are displayed. If no custom filters have been created, you are prompted to create one. See Creating Custom Filters for the Current Jobs View on page 408. 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 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. Description
Show canceled jobs Show last 24 hours Show last 7 days Show all
406
Monitoring Jobs Jobs List View Filters (continued) Item Use custom filter Description Select a custom filter from the drop down list. Information that you have specified in a custom filter about job histories is displayed. Note Only custom filters that you have created are displayed. If no custom filters have been created, you are prompted to create one. See Creating Custom Filters for the Job History View on page 410.
Related Topics: Managing Custom Filters on page 407 Viewing and Changing Active Jobs on page 415 Viewing and Changing Scheduled Jobs on page 420 Viewing and Changing Completed Jobs on page 427
Managing Custom Filters

Create and edit custom filters for the current jobs view and the job history view to display only the information that you specify. Custom filters are stored in a file in a folder on the computer on which they were created. The default path for this folder is C:\Program Files\Backup Exec\NT\Data. The logon account name used to log on to the computer is appended to the file name so that a file will exist for each person who creates custom filters. For example, if you log on to the computer using an account named 'Admin' and create custom filters in Backup Exec for the current jobs view, when you close Backup Exec, the custom filters are saved in the following file: C:\Program Files\Backup Exec\NT\Data\CurrentJobsFilters_Admin.xml If you create custom filters in Backup Exec for the job history view, when you close Backup Exec, the custom filters are saved in the following file: C:\Program Files\Backup Exec\NT\Data\JobHistoryFilters_Admin.xml Only the person who created the custom filter is able to view it in the custom filters list.
407
Monitoring Jobs
To create, edit, or delete custom filters: 1. On the navigation bar, click Job Monitor. 2. Click the Job List tab. 3. Under Custom Filter Tasks in the task pane, click Manage custom filters. The Custom Filters Management dialog box appears, and displays the name, description, and type of custom filter that currently exist. 4. Do any of the following:
To create a new custom filter, click New, and then click either Job History Custom Filter, or Current Jobs Custom Filter. To edit a custom filter, select the filter from the list, and then click Edit. To delete a custom filter, select the filter from the list, and then click Delete. When you delete a custom filter, it is also deleted from the files created for each logon account: C:\Program Files\Backup Exec\NT\Data\JobHistoryFilters_<logon account name>.xml C:\Program Files\Backup Exec\NT\Data\CurrentJobsFilters_<logon account name>.xml
Related Topics: Creating Custom Filters for the Current Jobs View on page 408 Creating Custom Filters for the Job History View on page 410 Viewing and Filtering Jobs in the Calendar View on page 413
Creating Custom Filters for the Current Jobs View

Create custom filters to display specific information in the current jobs view. To create a custom filter for the current jobs view: 1. On the navigation bar, click Job Monitor. 2. Click the Job List tab. 3. Do one of the following:
In the Current Jobs Filter box, under Custom Filter, click <new filter>.
408
Monitoring Jobs
Under Custom Filter Tasks in the task pane, click Manage custom filters, click New, and then click Current Jobs Custom Filter.
The New Custom Filter dialog box appears. 4. Select the following options as appropriate, and then click OK.
New Custom Filter options for the Current Jobs View Item General Name
Description
Name - Type a name for the new custom filter for the current job view. Description - Type a description of the new filter.
Criteria State
Enable this filter - Select this check box to use job states as a criteria for refining the current jobs view. If this check box is not selected, State is not used as a criteria for this custom filter. State - Select the check boxes for the job state that you want listed in the current jobs view. For quicker selection, click Check All or Uncheck All. Enable this filter - Select this check box to use job types as a criteria for refining the current jobs view. If this check box is not selected, Job Type is not used as a criteria for this custom filter. Job Type - Select the check boxes of the job types that you want listed in the current jobs view. For quicker selection, click Check All or Uncheck All. Enable this filter - Select this check box to use active job statuses as a criteria for refining the current jobs view. If this check box is not selected, Job Status is not used as a criteria for this custom filter. Job Status (Active Jobs) - Select the check boxes for the active job statuses that you want listed in the current jobs view. For quicker selection, click Check All or Uncheck All.
Job Type
Job Status (Active Jobs)
409
Monitoring Jobs New Custom Filter options for the Current Jobs View (continued) Item Job Status (Scheduled Jobs) Description
Enable this filter - Select this check box to use scheduled job statuses as a criteria for refining the current jobs view. If this check box is not selected, Job Status is not used as a criteria for this custom filter. Job Status (Scheduled Jobs) - Select the check boxes for the scheduled job statuses that you want listed in the current jobs view. For quicker selection, click Check All or Uncheck All.
Media Server
This option is only available if the Central Admin Server Option is installed.
Enable this filter - Select this check box to use media servers as a criteria for refining the current jobs view. Media Server - Select the check boxes of the media servers for which you want current jobs listed in the current jobs view. For quicker selection, click Check All or Uncheck All.
For more information, see Changes to the Job Monitor/Job History View with CASO on page 856. Date Range
Do not use a date range - Select this option to display all of the current jobs that meet the criteria you have specified. Show next <number> <Hours/Days> - Select this option, and then enter a number of hours or days. Only the current jobs that are scheduled or active in the next number of hours or days that you specify and that meet the other criteria for this filter are displayed on the Job Monitor.
Creating Custom Filters for the Job History View

Create custom filters to display specific information in the job history view for successful, completed, failed, and canceled jobs. Creating a custom filter for the job history view: 1. On the navigation bar, click Job Monitor. 2. Click the Job List tab. 3. Do one of the following:
In the Job History Filter box, under Custom Filter, click <new filter>.
410
Monitoring Jobs
Under Custom Filter Tasks in the task pane, click Manage custom filters, click New, and then click Job History Custom Filter.
The New Job History Custom Filter dialog box appears. 4. Select the following options as appropriate, and then click OK
New Custom Filter options for the Job History View Item General Name
Description
Name - Type a name for the new custom filter for the job history view. Description - Type a description of the new filter.
Criteria Job Type
Enable this filter - Select this check box to use job types as a criteria for refining the job history view. Job Type - Select the check boxes of the job types that you want listed in the current jobs view. For quicker selection, click Check All or Uncheck All. Enable this filter - Select this check box to use job status as a criteria for refining the job history view. Job Status - Select the check boxes of the job statuses that you want listed in the job history view. For quicker selection, click Check All or Uncheck All.
Job Status
Media Server
This option is only available if the Central Admin Server Option is installed.
Enable this filter - Select this check box to use media servers as a criteria for refining the job history view. Media Server - Select the check boxes of the media servers for which you want job histories listed in the job history view. For quicker selection, click Check All or Uncheck All.
For more information, see Changes to the Job Monitor/Job History View with CASO on page 856.
411
Monitoring Jobs New Custom Filter options for the Job History View (continued) Item Protected Server Description
Show job histories that backed up or restored data on this server - To show job histories for jobs that have backed up or restored data on a protected server, type all or part of the server name. If you type only part of the server name, all job histories for servers with names that contain that text are displayed. For example, if you type the server name bat, then all protected servers with names that include *bat* are displayed. A protected server is any computer on the network that is being backed up by Backup Exec, including Backup Exec media servers.
Job Name
Show job histories with the following job name - To show job histories for jobs with specific job names, type all or part of the job name. If you type only part of the job name, all job histories for jobs with names that contain that text are displayed. For example, if you type the job name bat, then all job histories for jobs with names that include *bat* are displayed. Do not use a date range - Select this option to display all of the job histories that meet the criteria you have specified. Show last <number> <Hours/Days> - Select this option, and then enter a number of hours or days. Only the job histories created in the last number of hours or days that you specify and that meet the other criteria for this filter are displayed on the Job Monitor. Show using the following range: Select this option, and then enter a range of dates and times. Only the job histories created between the dates and times that you specify and that meet the other criteria for this filter are displayed on the Job Monitor. Enable this filter - Select this check box to use byte count as a criteria for refining the job history view. The byte count is the number of bytes that were processed for the job. Do one of the following: To filter for job histories that have a byte count greater than a given byte count, select Greater than, enter a number for the byte count, and then select the measurement to use in bytes, kilobytes (KB), megabytes (MB), or gigabytes (GB). To filter for job histories that have a byte count less than a given byte count, select Less than, enter a number for the byte count, and then select the measurement to use in bytes, kilobytes (KB), megabytes (MB), or gigabytes (GB).
Date Range
Byte Count
412
Monitoring Jobs New Custom Filter options for the Job History View (continued) Item Elapsed Time Description
Enable this filter - Select this check box to use elapsed time as a criteria for refining the job history view. The elapsed time is the amount of time from when the operation started until it ended. Do one of the following: To filter for job histories that have an elapsed time greater than a given elapsed time, select Greater than, enter a number for the elapsed time, and then select the measurement to use (seconds, minutes, or hours). To filter for job histories that have an elapsed time less than a given elapsed time, select Less than, enter a number for the elapsed time, and then select the measurement to use (seconds, minutes, or hours).
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 2. Click the Calendar tab. Note Icons at the top of the Job Calendar enable you to select calendar views, navigation, and display filters without using the task pane. 3. 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.
413
Monitoring Jobs Calendar Views (continued) Item Week Description 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.
Month
4. 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. Click the Calendar tab. 3. In the Job Calendar Filter box, click 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 Show completed jobs with exceptions Show failed 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. 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. Description
Show canceled jobs
414
Monitoring Jobs Job Calendar View Filters (continued) Item Show media server Description This filter displays only if the Central Admin Server Option is installed. Select the media server for which you want to view jobs. Select All media server to view jobs for all of the managed media servers that this central administration server delegates to. For more information, see Changes to the Job Monitor/Job History View with CASO on page 856. 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.
Related Topics: Viewing and Changing Active Jobs on page 415 Viewing and Changing Scheduled Jobs on page 420 Viewing and Changing Completed Jobs on page 427 Changes to the Job Monitor/Job History View with CASO on page 856.
Viewing and Changing Active Jobs

You can view properties and change the status of active and scheduled jobs that are submitted for processing in the 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. Click the Job list or Calendar tab. 3. Select the active job you want to view from the Current Jobs pane or the Job Calendar, and then under General Tasks in the task pane, click Properties. Note To view the history of an active job from Job Monitor or Job Setup, right-click the active job, and then from the shortcut menu, click View History.
415
Monitoring Jobs
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 and Changing Completed Jobs on page 427. 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. The job log is located in Program Files\VERITAS\Backup Exec\NT\Data. The status of the operation. For details, see Active Job Statuses on page 419. The type of operation currently in progress (Backup, Catalog, Restore, Verify, etc.). The media server processing the job. 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:
Status
Operation
Server name Device name Source
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.
416
Monitoring Jobs Job Activity dialog box (continued) Item Current File Description 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.
Media server
The media server on which this job is running. If the Central Admin Server Option is installed, this is the managed media server that the central administration server has delegated this job to. For more information, see Changes to the Job Monitor/Job History View with CASO on page 856.
Delegation status
If the Central Admin Server Option is installed, indicates the current status of a job that is being delegated from the central administration server to the managed media server. These statuses include the following, where <x> is replaced with the name of the managed media server:

Preparing to delegate job to <x> Delegating job to <x> Job has been delegated to <x> Job has been received by <x> Job is actively running on <x> Job has completed on <x> Error in delegating job ... re-submitting job to <x>
For more information, see Changes to the Job Monitor/Job History View with CASO on page 856. Statistics Directories Files Skipped Files Corrupt Files Files in use Job Rate 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 for the entire job.
417
Monitoring Jobs Job Activity dialog box (continued) Item Bytes Start Time Elapsed Time Percent complete Description Number of bytes processed. Time the operation started. Length of time that has elapsed since the operation started. Select percentage of the job that has completed. To display this option, on the Tools menu, select Options, and then in Preferences, select Display progress indicators for backup jobs. The total number of bytes for the backup job estimated during a prescan. To display this option, on the Tools menu, select Options, and then in Preferences, select Display progress indicators for backup jobs The estimated time it will take for the job to complete. To display this option, on the Tools menu, select Options, and then in Preferences, select Display progress indicators for backup jobs
Estimated total bytes
Estimated time remaining
4. Click Cancel Job to cancel the processing of the job. If the job is scheduled, it will run again at the next scheduled time. Canceling a job may take a considerable amount of time depending on the tape drive selected for the job. 5. Click Print to print the job activity information. You must have a printer attached to the computer and configured in order to print the report. 6. Click Find to search for a word in the Job Activity log. To cancel an active job: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Select the active job from the Current Jobs pane or the Job Calendar, and then under Active Job Tasks in the task pane, click Cancel. Confirm the cancellation of the job. If the job is scheduled, it will run again at the next scheduled time.
418
Monitoring Jobs
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. To place all scheduled occurrences of an active job on hold: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Select the active job from the Current Jobs pane or the Job Calendar, and then under General Tasks in the task pane, click Hold Schedule. The active job continues and all scheduled occurrences of the job are placed on hold. To remove the hold on future jobs, click Hold Schedule again. You can select multiple jobs in the 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 Hold Schedule on more than one job at a time, as long as the state of the jobs are the same. Related Topics: Viewing and Changing Completed Jobs on page 427 Scheduled Job Statuses on page 421
Active Job Statuses

Possible statuses for an active job include:
Active Job Statuses Item Running Queued Description The operation is underway. The job has been initiated, but Backup Exec is actively looking for a suitable drive or media. Backup Exec cannot process the Cancel request immediately. This status is displayed until the job is actually canceled. The job is then displayed in Job History with a status of Canceled. The media is being loaded and positioned on the target device.
Cancel Pending
Loading Media
419
Monitoring Jobs Active Job Statuses Item Pre-processing Description This status can indicate any or all of the following:
Backup Exec is calculating the amount of data that will be backed up, if the Display progress indicators for backup jobs option is enabled. To view this option, from the Tools menu, click Options, and then under Settings in the task pane, click Preferences. Backup Exec is waiting for a pre- or post-command to complete. Backup Exec is retrieving the set maps and is positioning the tape to the append point location for an append job.
Snapshot processing
Backup Exec is processing a snapshot operation for the Advanced Open File Option (AOFO) or the Advanced Disk-based Option (ADBO). The device that the job was sent to is paused. For more information, see Pausing, Resuming, and Renaming Devices on page 130 The media server is paused. For more information, see Pausing, Resuming, and Renaming Devices on page 130 The Backup Exec services have become unresponsive. For more information, see Setting Thresholds to Recover Jobs on page 445. The Backup Exec services continued to be unresponsive past the threshold for being stalled, and the job has been recovered by Backup Exec. Any error-handling rules that are enabled for the error that caused the job to be recovered will apply. For more information, see Custom Error-handling Rule for Recovered Jobs on page 443.
Device Paused
Server Paused
Stalled
Recovered
Related Topics: Scheduled Job Statuses on page 421 Completed Job Statuses on page 433
Viewing and Changing Scheduled Jobs

You can view and 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. To view the history of a scheduled job from Job Monitor or Job Setup, right-click the scheduled job, and then from the shortcut menu, click View History.
420
Monitoring Jobs
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. Related Topics: Running a Scheduled Job Immediately on page 423 Placing a Scheduled Job on Hold on page 424 Changing the Priority for a Scheduled Job on page 425 Running a Test Job for a Scheduled Job on page 426 Deleting Scheduled Jobs on page 426
Scheduled Job Statuses

Possible statuses for scheduled jobs are listed in the following table:
Scheduled Job Statuses Scheduled Job Status Description
Blocked by template rule The scheduled job cannot run because it was created by a policy that contains a job template with the template rule <First Template> must complete at least once before any other templates will be allowed to start. The job designated as <First Template> in the policy must run before this scheduled job can run. For more information, see Setting Template Rules on page 373. Invalid Schedule The scheduled job will not run because:

An associated record in the database is missing, or The availability window and the schedule for the selection list being backed up by this job do not have a time in common. For more information, see Setting Priority and Availability Windows for Selection Lists on page 301.
421
Monitoring Jobs Scheduled Job Statuses (continued) Scheduled Job Status Not in Time Window Description The job was ready to be sent for processing, but the time window for the job closed. This probably occurred because appropriate destination devices were not available during the common time between the jobs time window and the selection lists availability window. For more information, see Setting Priority and Availability Windows for Selection Lists on page 301. On Hold Queued The job has been placed on hold. A temporary state that displays when Backup Exec is applying an error-handling rule that is enabled to retry the job. For more information, see Custom Error-handling Rule for Recovered Jobs on page 443. The job is ready to run, but cannot for the reason displayed:

Ready
Internal error. No devices are available, but the cause is unknown. Invalid job. The job type in unknown; there may be an internal error or the database is corrupted. Invalid target. This is a device type that no longer exists. Media server not available. No devices are available. No license for x. A license must be purchased and installed on the targeted media server. No media servers are available. No media servers available in media server pool. Specified destination cascaded drive pool is empty. Specified destination device pool is empty. Specified destination device is not in media server pool. Specified destination device not on local media server. Specified destination device pool on local media server is empty. The destination device cannot be a cascaded drive pool. The destination device cannot be a device pool. The destination device cannot be a media server. There is another job running in the system that is blocking. execution of this job. This job will run after the other job completes.
422
Monitoring Jobs Scheduled Job Statuses (continued) Scheduled Job Status Recovered Description The Backup Exec services continued to be unresponsive past the threshold for being stalled, and the job has been recovered by Backup Exec. Any error-handling rules that are enabled for the error that caused the job to be recovered will apply. For more information, see Custom Error-handling Rule for Recovered Jobs on page 443. This status may also refer to a media server in a cluster that was shut down while a job was active. If the job did not have the Checkpoint restart option enabled, an error-handling rule was applied, and the job was scheduled to restart immediately. See Cluster Failover Error-Handling Rule on page 444. Scheduled The job is scheduled to run in the future. Scheduled jobs that are linked to another job, such as a job to duplicate backup sets, will not display a scheduled job status. The job is ready, but the Backup Exec media server has been paused. No jobs are dispatched while the media server is paused. See Pausing, Resuming, and Renaming Devices on page 130. The scheduled job cannot run because it was created by a policy that contains a job template with the template rule If start times conflict, <First Template> supersedes <Second Template>. The <Second Template> job will run according to the schedule set for it, after the <First Template> job completes. For more information, see Setting Template Rules on page 373. A state the scheduled job transitions through as it is being sent for processing.
Server Paused
Superseded by job x
To Be Scheduled
Related Topics: Active Job Statuses on page 419 Completed Job Statuses on page 433
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. Click the Job list or Calendar tab.
Chapter 8, Administrating Backup Exec 423
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. Related Topics: Changing the Priority for a Scheduled Job on page 425 Running a Test Job for a Scheduled Job on page 426 Deleting Scheduled Jobs on page 426
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. To place a scheduled job on hold: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then under General 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 Hold Schedule on more than one job at a time, as long as the state of the jobs are the same. Related Topics: Running a Scheduled Job Immediately on page 423 Running a Test Job for a Scheduled Job on page 426 Deleting Scheduled Jobs on page 426
424
Monitoring Jobs
Changing the Priority for a Scheduled Job

The priority determines the order that jobs run. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. The priority is changed for all occurrences of the scheduled job. If there are multiple backup jobs using the same selection list, then updating the priority of one backup job will cause the priority for the other backup jobs to be changed as well. If this occurs, you are prompted before the priority is changed for all backup jobs that use the same selection list. You can select multiple jobs by selecting a job, and then pressing the <Ctrl> or <Shift> keys while you click other jobs that you want to select. This allows you to perform tasks such as setting priorities on more than one job at a time, as long as the jobs are of similar type. To change the priority for a scheduled job from the Job Monitor view: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. The priority of the job is displayed in the Priority column and include the following settings:

3. Select the scheduled job from the Current Jobs pane or the Job Calendar, and then under Scheduled Job Tasks in the task pane, click Increase priority or Decrease priority. The priority is increased or decreased. To change the priority for a scheduled job from the Job Setup view: 1. On the navigation bar, click Job Setup. 2. Select the job from the Jobs pane, and then under General Tasks in the task pane, click Increase Priority or Decrease Priority. The priority is increased or decreased.
425
Monitoring Jobs
Running a Test Job for a Scheduled Job

The test run option determines if a scheduled backup will complete successfully. During the test run, the tape capacity, credentials, and media are checked. If the test job determines there is a problem, the job will continue to run and the problem will appear in the job log. To run a test job for a scheduled job: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Select the active job from the Current Jobs pane or the Job Calendar, and then under Scheduled Job Tasks in the task pane, click Test run. You can select multiple jobs in the 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 321. 5. On the Properties pane, under Settings, click Notification and enter notification information for the items. For more information, see Selecting Recipients for Notification on page 534. 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. If the job was created by a policy, you must first click Delete jobs created by policy in the Job Setup task pane, and dissociate the policy from the selection list. Then, you are prompted to delete the jobs that were created when the policy and selection list were combined.
426
Monitoring Jobs
To delete a scheduled job: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Right-click the scheduled job in the Current Jobs pane or the Job Calendar, and then click Delete. 4. Confirm the deletion of the scheduled job. Deleting this job deletes this occurrence and all other occurrences of this job. To delete only the occurrences for a specific date, click Cancel on the warning message. On the navigation bar, click Job Setup and then right-click the job. Click Properties, and then under Frequency on the Properties pane, click Schedule. Click Run according to schedule, click Edit Schedule Details, and then exclude that date. 5. After clicking Delete, you are prompted to delete backup selection lists that are no longer in use by any other jobs. Click Yes to delete all of the unused backup selection lists, or click No to leave the backup selection lists intact. To delete selection lists later, on the Edit menu, click Delete Selection Lists. Related Topics: Deleting a Job Created from a Policy on page 380
Viewing and Changing Completed Jobs

You can view detailed job-related properties for each job that has been processed. For some jobs, you can right-click the job and choose to retry the job, or choose to configure a custom error-handling rule for the error that the job failed with. Errors that are reported in the job log contain hyperlinks that you can click to go to the Symantec Software Support Services web site and access technical notes and trouble-shooting steps that are related to a specific error. The Job History dialog box contains two tabs: Job History and Job Log. The Job History tab provides summary information for the job. The Job Log tab provides job and file statistics. Most job logs display in XML format. However, some logs may display in text.
427
Monitoring Jobs
To view completed job properties: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Select the completed job you want to view from the Job History pane or the Job Calendar, and then under General Tasks in the task pane, click Properties. The Job History dialog box appears. Click Expand All to view all the information contained in the topics. Click Collapse All to hide the information in the topics. The Job History tab provides the following job summary and set detail information:
Job History Item Previous Description Click this to display the job history of the previous job that was run as part of this recurring job. Click this to display the job history of the next job that was run as part of this recurring job. Job name entered during job configuration. Type of operation that was performed (Archive, Backup, Catalog, Restore, Verify). Status of the operation. File name and location of the job log. Media server that processed the job. Selection list processed in the job. Name of the device that processed the job. Name of the device selected during job configuration. Name of the media set that processed the job.
Next
Job name Job type
Job status Job log Server name Selection list name Device Name Target name Media set name
Job Summary Information Original start time Time the job was submitted for processing.
428
Monitoring Jobs Job History (continued) Item Job started Job ended Elapsed time Files Directories Skipped Files Corrupt files Files in use Byte count Rate Final disposition Set Detail Information Set type Type of operation that was performed on the media set (Archive, Backup, Catalog, Restore, Verify). Status of the operation. Job name entered during job configuration. Name of the resource for the job. Name of the logon account that was used for the job. Description Time the operation started. The time the operation ended. 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. The final status of the job.
Set status Set description Resource name Logon account
429
Monitoring Jobs Job History (continued) Item Error Description If an error occurred, the error code is displayed. Click the Job Log. To locate where the error occurred in the Backup Set Detail Information, click the error text. Then, if additional information on an error is available, click the Unique Message Identifier in the blue hyperlink to go to the Symantec Software Support Services web site. See Unique Message Identifier (UMI) Error Codes In Job Logs on page 432 for more information. After you click OK and exit the log, right-click the job in the Job History pane, and then click Error-Handling. The Error-Handling Rule Settings dialog box is displayed. Using this dialog box, you can enable retry options and final job disposition for jobs when this error occurs. See Error-Handling Rules on page 439 for more information. Agent used Advanced Open File Option used Image used Indicates if the Backup Exec agent was used during the operation. Indicates if the Advanced Open File Option was used during the operation. Indicates if the Backup Exec ServerFree Option was used during the operation. Time the operation started. Length of time the operation took.
Start time End time
4. Click Job Log to view detailed information about the job. The job log is in an HTML format. Click Expand All to view all the information in the topics or Collapse All to hide the information in the topics. The Job Log tab provides the following information, depending on the type of operation:
Job Log Item Job Information Description Displays the job server, job name, the date and time the job started, the type of job, and the job log name. Displays the drive name, media label, the overwrite protection and append periods, and the media set that this job was targeted to. Administrators Guide
Device and Media Information 430
Monitoring Jobs Job Log (continued) Item Utility Job Information Description Displays information about the slot, bar code, media label, status, and device that the utility job was processed on. For more information, see Creating Utility Jobs on page 192. Displays the job end time, completion status, error codes, error description, and error category. The job completion section is green, orange, or red, depending on the job status (for more detail, see Completed Job Statuses on page 433). Displays a detailed description of the errors encountered during job processing. The errors are grouped by set and labeled. The label includes the operation and destination resource name for that set. The error section is red in the job log. To locate where the error occurred in the Backup Set Detail Information, click the error text. Then, if additional information on an error is available, click the underlined error code number to go to the Symantec Software Support Services web site. Exceptions Displays a detailed description of the minor errors encountered during job processing. The exceptions section is orange in the job log.
Job Completion Status
Errors
5. Click Save As to save the job history or job log under a different name or in a different location. 6. Click Print if you want to print the job history or job log; however, you must have a printer attached to your system and configured in order to print the report. 7. Click Find to search for a word in the job history. 8. Click OK to close the log. Related Topics: Completed Job Statuses on page 433 Configuring Default Job Log Options on page 435
431
Monitoring Jobs
Unique Message Identifier (UMI) Error Codes In Job Logs

Errors that are reported in the job log each have a unique code, called a Unique Message Identifier (UMI). These codes contain hyperlinks that you can click to go to the Symantec Software Support Services web site and access technical notes and trouble-shooting steps that are related to a specific error. Unique Message Identifier (UMI) error code establishes unique error and message codes across all Symantec products. To link from an error code in the job log to the Symantec Software Support Services web site: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Select the completed job you want to view from the Job History pane or the Job Calendar, and then under General Tasks in the task pane, click Properties. The Job History dialog box appears. Click Expand All to view all the information contained in the topics. Click Collapse All to hide the information in the topics. 4. Scroll to the Job Completion Status section. 5. Click the Unique Message Identifier, displayed as a blue hyperlink, to launch a new browser window, and go to the Symantec Software Support Services web site. You can create or enable an error-handling rule for this error, which allows you to set retry options and final job disposition for jobs when this error occurs. Related Topics: Error-Handling Rules on page 439
432
Monitoring Jobs
Deleting Completed Jobs

You can delete a job from the Job Monitor, or have Backup Exec automatically delete the job history using database maintenance, or you can set a default when you schedule jobs to automatically delete jobs that are set to run once, and that are not created from templates. If you delete a job, it is removed from the computer and cannot be recovered. To delete a completed job: 1. On the navigation bar, click Job Monitor. 2. Click the Job list or Calendar tab. 3. Select the job you want to delete from the Job History pane or the Job Calendar, and then under General Tasks in the task pane, click Delete. 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. After clicking Delete, you are prompted to make sure that you want to delete the job history and its associated job log. 4. Confirm the deletion of the job history and associated job log. Related Topics: Configuring Database Maintenance on page 447 Scheduling Jobs on page 398
Completed Job Statuses

Possible job completion statuses for jobs that were processed include the following:
Job Completion Status Status Successful Completed with exceptions Description The job completed without errors. The job completed, but a file in use, skipped, or corrupted was encountered during the operation.
433
Monitoring Jobs Job Completion Status Status Failed over Description The job ran in a cluster environment and was active on one computer, and then the cluster performed a failover and the job was restarted on another computer in the cluster. There are two separate sets of job history when a job is failed over. The first job history will have the Failed over status and the second job history will have the status that is appropriate for the completed job. The status is the same as the failed over status, however the Apply CheckPoint Restart option was selected. The administrator terminated the operation as it was running. The Enable automatic cancellation feature in the Frequency Schedule property was enabled and the job was not completed within the specified timeframe. See Scheduling Jobs on page 398. The operation took place, but one or more significant errors occurred. The job log should indicate what caused the errors so that you can decide if you want to run the job again. For example, if a job failure occurred due to a lost connection during job processing, you could choose to resubmit the job when the connection is restored. If a drive loses power during a backup operation, you should restart the backup job using a different tape. You can restore the data written to the tape up to the point of the power loss, but you should not reuse the tape for subsequent backup operations. A failed job will have an error message in the Errors section of the job log with a navigable link to the Symantec Software Support Services web site. See Unique Message Identifier (UMI) Error Codes In Job Logs on page 432. Some reasons a job may fail are:
Resumed
Canceled Canceled, timed out
Failed
Devices specified by the job were not available when the job was run. The logon account information used in the backup job is incorrect. Verify the logon account information is valid for the resource being backed up. There was a problem with the storage device when the job was run. The computer being backed up was shut down before or during the backup job.
434
Monitoring Jobs
Configuring Default Job Log Options

You can configure default options for job logs that specify the amount of detail you want to include in the completed job log. For jobs that produce large job logs, for example, a backup of a considerable number of separate files, you may want to reduce the amount of detail in the job log. The size of the job log increases proportionally to the level of detail configured for the job log. To configure default job log options: 1. On the Tools menu, click Options. 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 Starting date and time Errors encountered Ending date and time Completion statistics
This option also includes the name of files that were skipped, the media set name, the backup type and results of the verify operation if one was performed. Summary information and directories processed Summary information, directories, and files processed Select this option to include summary information and a list of all processed subdirectories.
Select this option to include Summary information, processed subdirectories, and a list of all the filenames that were processed.
435
Monitoring Jobs Job Log default options (continued) Item Summary information, directories, files and file details Prefix for the job log file name Description Select this option to include Summary information, processed subdirectories, a list of all the filenames and their attributes. Selecting this option increases the job log sizes significantly. Enter a prefix to prepend to the job logs that are processed. The default prefix is BEX. The job log file name consists of Prefix_ServerName_Count, where Prefix is the label that you enter in this field, ServerName is the name of the media server that ran the job, and Count is the number of job logs that this job has produced. E-mail job log attachments Attach job logs as html Click this to attach the job logs in an html format when an email notification is sent. Click this to attach the job logs in a text format when an email notification is sent.
Attach job logs as text
Related Topics: Backup Exec Defaults on page 119 Viewing and Changing Completed Jobs on page 427
Using Job Logs with Vertical Applications

The Backup Exec Administration Console provides a view of the job logs in HTML format. If necessary, you can convert the job logs to a text format for use with vertical applications. To convert a job log file to a text format, type the following at a command prompt from the default directory C:\Program Files\VERITAS\Backup Exec\NT, or wherever Backup Exec was installed to: bemcmd -o31 -f"<pathname\job log filename>" For example, to display the job log C:\program files\VERITAS\Backup Exec\NT\Data\bex00001.xml in text format to the command prompt, you would type: bemcmd -o31 -f"C:\program files\VERITAS\Backup Exec\NT\Data\bex00001.xml" To redirect the job log to a file, you would type one of the following:
436
Using Audit Logs to Review Activity Performed in Backup Exec
bemcmd -o31 -f"C:\program files\VERITAS\Backup Exec\NT\Data\bex00001.xml" > bex00001.txt or bemcmd -o31 -l"bex00001.txt" -f"C:\program files\VERITAS\Backup Exec\NT\Data\bex00001.xml"

Use audit logs to examine and review information about operations that have been performed in Backup Exec. The audit log displays the date and time of the activity, who performed it, what the activity was, and a description of the activity. You can view information about activities that occur for all or any of the following:

Audit logs Logon accounts Selection lists Devices and media Error-handling rules Jobs Policies and job templates Alerts Server configuration
You can delete the audit logs as part of the Backup Exec database maintenance, and you can save the audit log to a file. Changes made to the audit log, such as when database maintenance occurs, can also be displayed in the audit log. To view the audit log: 1. On the Tools menu, click Audit Log. The Audit Logs dialog box appears.
437
The Audit Log dialog box provides the following information:

Audit Log Item Description
Select category to view Click the drop-down arrow to view all of the items for which you can view and configure audit logging. Select All to display changes for all Backup Exec items, or select another category for which to display changes. Audit log Date/Time The date and time that this change was made in Backup Exec. Click the column head to sort the information by date. The domain and user name of the user that made the change. Click the column head to sort the information alphabetically. The item or items that you have selected for audit logging. Click the column head to sort the information alphabetically. The action that was recorded by Backup Exec for the operation that was performed. Click the column head to sort the information alphabetically.
User Name
Category
Message
2. Use the scroll bar at the bottom of the Audit log window to view the whole entry, or double-click the entry to display the same information in an easy-to-read Audit Log Record. 3. Do any of the following:

Click Refresh to update the audit log with new entries. Click Clear Log to remove all entries from the audit log. Click Save Log to File to specify a file name and location to save the audit log entries. Click Properties to display information about the entry. Click Configure Logging to select the types of items and the types of changes made to the items that you want to display in the audit log. See Configuring the Audit Log on page 439.
Related Topics: Configuring Database Maintenance on page 447. Configuring the Audit Log on page 439
Error-Handling Rules
Configuring the Audit Log

Configure the audit log to display information about specific operations that are performed on items in Backup Exec. To configure the audit log: 1. On the Tools menu, click Audit Log. The Audit Logs dialog box appears. 2. Click Configure Logging. 3. On the Audit Log Configuration dialog box, select the check box of the category that you want to display in the audit log. Expand the category by clicking the plus sign to the left of the category. Select the operations that you want to display for the category. Clear the check box of any item or operation that you do not want to display. 4. Click OK.
You can enable default rules or create custom rules to set retry options and final job disposition for failed or canceled jobs. Retry options let you specify how often to retry a job if it fails and the time to wait between retry attempts. The final job disposition lets you either place the job on hold until you can fix the error, or cancel the job and reschedule it. To apply an error-handling rule for a group of similar errors, or error categories, you can enable a default error-handling rule. Each default error-handling rule applies to one category of errors, such as Network Errors or Security Errors. Default error-handling rules are disabled by default, so you must edit a rule and enable it before the retry options and job disposition settings will apply to jobs that fail with errors in the selected category. You cannot delete default error-handling rules, or add specific error codes to a category, or add new error categories. Before the error-handling rules will apply, the final error code must be in an error category that is associated with a rule, and the rule must be enabled. To apply an error-handling rule for a specific error code that is in an error category, you can create a custom error-handling rule. You can select up to 28 error codes in an error category that a custom error-handling rule can apply to. You can also add an error code to an existing custom rule.
439
One custom error-handling rule, named Recovered Jobs, is created when Backup Exec is installed and is enabled by default. This rule applies retry options and a final job disposition to jobs that fail and that are not scheduled to run again. See Custom Error-handling Rule for Recovered Jobs on page 443. If both a custom error-handling rule and a default error-handling rule apply to a failed job, the settings in the custom rule are applied to the job. Note If the server on which Backup Exec is installed is in a cluster environment, the Cluster Failover error-handling rule is displayed on the list of error-handling rules. This rule is enabled by default. See Cluster Failover Error-Handling Rule on page 444. To create a custom error-handling rule or to edit error-handling rules: 1. Do one of the following:

On the Tools menu, click Error-Handling Rules. Right-click a failed or canceled job in the Job History pane in the Job Monitor view. Click Properties, and then click Error-Handling. Go to step 4 on page 441.
The Error-Handling Rules dialog box appears. 2. Select the appropriate options as described in the following:
Error Handling Rules dialog box options Item Name Type Description The name of the error-handling rule.
Default: Predefined default error-handling rules for a category of errors. You cannot delete default rules and you cannot modify default rules to include specific error codes in a category. Custom: Error-handling rules that you can create for a specific error code or codes in an error category.
If both a custom error-handling rule and a default error-handling rule apply to a failed job, the settings in the custom rule are applied to the job. Job Status The status of the job that will activate this rule. Statuses are:

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

Final Job Status
Error Canceled Failed
441
Error-Handling Rules Error-Handling Rule Settings (continued) Item Error Category Description The category of error for which the rule will be applied. If you are editing a default or custom error-handling rule, the error category can be viewed, but not modified. If you are creating a custom error-handling rule, you must select an error category that contains the errors to apply this rule to. Available error categories include:

Other Network Server Resource Security Backup Device Backup Media Job System Dispatch
Enabled
Select this check box to enable the error-handling rule, or clear the check box to disable the rule. This check box must be selected before you can set the retry options and the final job disposition options. Error codes that are not associated with a custom error-handling rule. This field will not be displayed if you are editing a default error-handling rule. If you are creating or editing a custom error-handling rule, you must select the check box of the error code that you want this rule to apply to. You can select up to 28 error codes. To change the list of available errors, select a different error category.
Available errors
Retry Options Retry job Maximum retries Select this check box to allow Backup Exec to retry the job. Enter the number of times you want the job retried. The maximum number of times the job can be retried is 99. Enter the number of minutes to wait before the job is retried. The maximum number of minutes is 1440. Administrators Guide
Retry interval
442
Error-Handling Rules Error-Handling Rule Settings (continued) Item Final job disposition Place job on hold until error condition has been manually cleared Cancel job and reschedule for its next scheduled service Notes Select this option to place the job on hold until you can manually clear the error. After you clear the error, you must remove the hold for the job. Select this option to cancel the current job after the selected number of retry options has been met. After the job is canceled, it will run at the next scheduled time. Enter any miscellaneous information for the error-handling rule. Description
Related Topics: Error-Handling Rules on page 439 Custom Error-handling Rule for Recovered Jobs on page 443 Cluster Failover Error-Handling Rule on page 444
Custom Error-handling Rule for Recovered Jobs

Recovered Jobs is a custom error-handling rule that is used by Backup Exec to recover jobs that were failed with specific errors. This rule is created when Backup Exec is installed, and is enabled by default. The retry options for this rule are to retry the job twice, with an interval of five minutes between the retry attempts. The final job disposition is to place the job on hold until you have manually cleared the error condition. The following table describes the error codes that are selected by default for the Recovered Jobs custom error-handling rule.
Error codes for Recovered Jobs custom error-handling rule Error code 0xE00081D9 E_JOB_ENGINE_DEAD Description The displayed error message is: The Backup Exec job engine system service is not responding. See Setting Thresholds to Recover Jobs on page 445.
443
Error-Handling Rules Error codes for Recovered Jobs custom error-handling rule Error code 0xE0008820 E_JOB_LOCAL RECOVERNORMAL 0xE000881F E_JOB_REMOTE RECOVERNORMAL 0xE0008821 E_JOB_STARTUP RECOVERY Description The displayed error message is: The local job has been recovered. is required. The displayed error message is: The remote job has been recovered. is required. The displayed error message is: Job was recovered as a result of Backup Exec RPC service starting. No user action is required. No user action No user action
Note If the Central Admin Server Option is installed, additional error codes are selected. See CASO Error Codes and the Recovered Jobs Custom Error-Handling Rule on page 872. Related Topics: Error-Handling Rules on page 439 Cluster Failover Error-Handling Rule on page 444
Cluster Failover Error-Handling Rule

If the server on which Backup Exec is installed is in a cluster environment, the Cluster Failover error-handling rule is displayed on the list of error-handling rules. This rule is enabled by default. You cannot configure any options for this rule. You can only enable or disable the Cluster Failover error-handling rule. The cluster failover error-handling rule and the Apply CheckPoint Restart option in Cluster Backup Job Properties work together to enable you to resume jobs from the point of failover. The Apply CheckPoint Restart option is dependent on the cluster failover error-handling rule; if you disable the rule, the option will automatically be disabled to match the rules setting. Related Topics: Enabling or Disabling Checkpoint Restart on page 667
444
Setting Thresholds to Recover Jobs
Setting Thresholds to Recover Jobs

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

The Database Maintenance option enables you to manage the Backup Exec database and the Desktop and Laptop Option (DLO) database. Each database maintenance operation is performed independently on each database. The Backup Exec database maintains a record of files and data you have configured such as templates and catalogs. Database maintenance enables you to perform the following:

Optimize database size Delete expired data Save the contents of the database files Perform a database consistency check
You do not have to select all the options; however, each one performs a different process that enables you to protect and maintain your database. Selecting all the options enables you to recover the database quickly and maintain optimal performance. Informational alerts are generated at the beginning and the end of the database maintenance process each time database maintenance is performed. The alerts provide details about the type of maintenance that was performed on each database and the amount of time the maintenance took to complete. If the database maintenance process fails, the alert indicates where the failure occurred and the reason for the failure. To configure database maintenance: 1. On the Tools menu, click Options. 2. On the Properties pane, under Settings, click Database Maintenance. 3. Select the appropriate options as follows, and then click OK:
Database Maintenance options Item Enable Backup Exec database maintenance Last time maintenance was performed Perform database maintenance at Descriptions Select this check box to activate the database maintenance process. The date and time the last database maintenance was performed.
Enter the time you want to perform database maintenance. All the maintenance will occur once a day at the time you specify.
447
Configuring Database Maintenance Database Maintenance options (continued) Item 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. Note For the Desktop and Laptop Option (DLO) database, only the Alert History setting applies. DLO does not have job history, job logs, or reports. 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. Enter the number of days to keep audit log data in the database before it is deleted. Audit logs include information that you have selected about operations that are performed in Backup Exec. See Using Audit Logs to Review Activity Performed in Backup Exec on page 437. 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. Descriptions
Job logs
Alert history
Reports
Audit logs
Perform database consistency check
448
Configuring Database Maintenance 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 Select this check box to dump the data contained in the database database to the Backup into the Backup Exec data directory so that the database backup Exec data directory 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 760.
449
450
Chapter
Restoring Data
The restore operation enables 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 an entire system will need to be restored. Backup Exec offers several 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 enables 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 enables you to see all cataloged, backed up versions of a file, so you can restore earlier versions if needed.
You can select options that you want to use for most restore operations. Backup Exec will use the default options unless you override them when setting up a specific restore job. When creating your restore jobs, you can:
Restore data to the system from which it was originally backed up or redirect the restore to another system.
451
Restore Operations and the Catalog
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.
Related Topics: Using the Resource View on page 479 Using the Media View on page 479 Selecting Data to Restore on page 479 Using Advanced File Selection to Restore on page 482

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. Related Topics: Cataloging Media in a Drive on page 452 Setting Catalog Defaults on page 454 Catalog Levels on page 456
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 193).
452
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 follows:
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
5. On the Properties pane, under Settings, click General. Select the options as follows:
General options for catalog 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:

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 Notification on page 534).
Chapter 9, Restoring Data
453
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 398). The catalog operation can be monitored or canceled through the Job Monitor. Related Topics: Using Backup-to-Disk Folders and Files on page 176 Monitoring Jobs on page 405 Setting Catalog Defaults on page 454 Selecting Data to Restore on page 479 Canceling a Restore Operation on page 495
Setting Catalog Defaults

To configure catalog defaults: 1. On the Tools menu, select Options. 2. On the Properties pane, under Settings, click Catalog. 3. Select the appropriate options as follows:
Default catalog options Item Use storage media-based catalogs Description Select this option to allow Backup Exec to read the catalog information from the media. Media-based catalogs allow quick cataloging of media that are not included in the disk-based catalog (for example, media that was written by another installation of Backup Exec). This feature enables media to be cataloged in minutes, rather than the hours required with traditional file-by-file cataloging methods. If you want to create a new catalog by having Backup Exec read each file block, clear this option. Clearing this option is only recommended if normal catalog methods are unsuccessful.
454
Restore Operations and the Catalog Default catalog options (continued) Item Truncate catalogs after x days Description Select this option to retain only the header information and to 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. 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 after x days This enables Backup Exec to automatically delete disk-stored 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. Truncating and removing the catalogs is performed according to the last accessed date and time, not the created date and time. Check the catalogs last accessed date. Current path The path where the catalog files are located. This path defaults to \Backup Exec\NT\Catalogs. 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. Related Topics: Restore Operations and the Catalog on page 452 Catalog Levels on page 456
455
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 shown 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. Uncataloged Media There is no catalog information for the media. You must catalog the media to view and select files to restore.
Related Topics: Setting Catalog Defaults on page 454 Restore Operations and the Catalog on page 452
456
Restoring Data to a Server or Workstation

Restoring data to a server or workstation involves creating 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 can set your options by configuring restore job properties. Related Topics: Setting Restore Defaults on page 490
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.
457
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 479), and complete other Selections options as described in Selections Options for Restore Jobs on page 460. 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 Source, 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 461. You can select additional configuration options for the restore job before selecting to run or schedule the job. Select additional options on the Restore Job Properties dialog box Properties pane:
If you want to redirect this job to another system other than the one from which the data was backed up, on the Properties pane, under Destination, click one of the following (see Redirecting a Restore Operation on page 487):

File Redirection. Select this option to redirect file sets. Microsoft SQL Redirection. Select this option to redirect SQL Server sets to another SQL server. Microsoft Exchange Redirection. Select this option to redirect Exchange sets to another Exchange server. Microsoft Sharepoint Redirection. Select this option to redirect Sharepoint Portal Server sets to another Sharepoint server.
If you want to set advanced options for the restore job, on the Properties pane, under Settings, click Advanced. Complete the options as described in Advanced Options for Restore Jobs on page 464. 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 467.
458
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 493). 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 514).
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 398). 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 626. Related Topics: Selecting Data to Restore on page 479 Symantec Backup Exec - Remote Agent for Windows Servers on page 789 Redirecting a Restore Operation on page 487 Redirecting Restores for SQL on page 1049 Restoring Exchange Data on page 1089 Restore Options for Exchange on page 1086 Restoring NetWare Servers on page 1400
459
Restore Options for Lotus Domino Databases on page 1340 Viewing and Changing Completed Jobs on page 427 Restoring File Permissions on page 471
Selections Options for Restore Jobs

When the Restore Job Properties dialog box appears, Selections is chosen by default on the Properties pane. Through the Selections options, you choose the data you want to include in the restore job. You can also choose how the data will appear in this dialog box. Options on this dialog box include:
Selections options for restore 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. Click this button to search for files that you want to restore.
Load Selections from Existing List Search Catalogs View by Resources
Select this option to display backed up data by the resource from which it was backed up. This feature is useful for finding files that were located on a certain server or workstation. Select this option to display the data that is contained on a piece of media. This feature is useful for viewing the contents of a tape that was backed up from another media server.
Media
Preview pane
Select this check box to display the preview pane at the bottom of the dialog box, or clear this check box to remove the preview pane.
View Format Graphical Select this option to view selections in a directory tree view.
460
Restoring Data to a Server or Workstation Selections options for restore job (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 restoring (see Using Advanced File Selection to Restore on page 482). Select this option if you want to select the contents of all the subfolders when a directory is selected.
Text Advanced
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
461
Options for this dialog box include:

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

Job priority
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. 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.
Skip if file exists
Skip if existing file is more recent
462
Restoring Data to a Server or Workstation General settings options for restore job (continued) Item Restore corrupt files Description Select this option only if you do not want to have Backup Exec automatically exclude corrupt files from the restore process. This option is only recommended if a job has failed because a catalog query could not determine the corrupt files on the tape. Normally, when a restore job is run, Backup Exec queries the catalog to determine if any corrupt files are on the tape and excludes them from the restore job. If, during the query process, Backup Exec cannot determine if a file is corrupt, the Restore job will not continue and will be marked as Failed. If a corrupt file cannot be excluded automatically, you can manually exclude corrupt files in the Restore selections window and run the job with the Restore Corrupt File option enabled. Restore security Select this check box to restore file-level security information on NTFS partitions, if it exists in the data you selected. Select this check box to restore the data with its original directory structure intact. This option is enabled by default. If you clear this option, all data (including the data in subdirectories) is restored to the path you specify in the Redirection dialog box. Clearing the Preserve Tree option is useful when restoring several subdirectories or individual files from media, but it should not be cleared when restoring an entire drive.
Preserve tree
Related Topics: Creating a Manual Restore Job by Configuring Job Properties on page 458
463
Advanced Options for Restore Jobs

To set Advanced options for restore jobs, on the Properties pane, under Settings, click Advanced. Options for this dialog box include:
Advanced options for restore Item Description
Restore Removable Storage Select this check box to restore the Removable Storage data. The data Removable Storage database is stored in the Systemroot\System32\Ntsmsdata directory and is automatically backed up when the system directory is selected for backup. Removable Storage is a service used to manage removable media and storage devices; it enables applications to access and share the same media resources. Restore disk quota data Select this check box to restore disk quota data. Disk quota data is automatically backed up when the root directory of a volume is selected for backup. Disk quotas track and control disk usage on a per user, per volume basis; the values can be restored to the limits that were set before the backup. Restore Terminal Services database Select this check box to restore the Terminal Services database. The default location for the Terminal Services database, which contains licensing data for client licenses, is the Systemroot\System32\LServer directory and is automatically backed up when the system directory is selected for backup. Terminal Services allow client applications to be run on a server so that client computers can function as terminals rather than independent systems. Restore Windows Select this check box to restore the Windows Management Management Instrumentation (WMI) repository. The WMI repository is stored in Instrumentation repository the Systemroot\System32\wbem\Repository directory and is automatically backed up when the system directory is selected for backup. The Windows Management Instrumentation repository provides support for monitoring and controlling system resources and provides a consistent view of your managed environment. Restore Cluster Quorum Select this check box to restore the cluster configuration. For more information about restoring clusters, see Restoring Data to a Microsoft Cluster on page 684.
464
Restoring Data to a Server or Workstation Advanced options for restore (continued) Item Force the recovery of the cluster quorum even if other nodes are online and/or disk signatures do not match. Description Select this check box to restore the cluster configuration if you are not able to take the other nodes in the cluster offline or if the disk that the cluster quorum previously resided on has been changed. This option is only available if Restore Cluster Quorum is also selected. If this option is selected, the cluster service for any nodes that are online is stopped. This option also enables the drive letter of the disk that the cluster quorum was on to remain the same, even if the configuration has changed and the disk signatures contained in the restore media do not match the disk signatures contained in the cluster quorum. Any changes made to the cluster quorum after the last backup will be lost.
Mark this server as the primary arbitrator for replication when restoring folders managed by the File Replication Service, or when restoring SYSVOL in System State.
Select this check box to designate this server as the primary replicator for all members in the set when restoring FRS-managed folders or SYSVOL as part of System State. If all members of a replication set are to be restored, then stop replication, restore all the member servers, and then when restoring the last member server, select this option to designate the server as the primary replicator. If this option is not selected, replication may not function. Note In this version of Backup Exec, all restores of SYSVOL and FRS-managed folders are non-authoritative. An authoritative restore can only be performed by redirecting the restore and then copying the files to the server. Refer to your Microsoft documentation for details on performing an authoritative restore.
Restore Windows NT 4.0 registry
Select this check box to restore registry information if it exists in the data you selected.
Merge the existing Select this option if you want to merge the existing hardware and hardware configuration and registry services with the data you selected to be restored. This registry services with the option should only be used for restoring System State. data to be restored Overwrite the existing hardware configuration and registry services with the data to be restored Select this option if you want to overwrite hardware configuration and registry services with the data you selected to be restored. This option should only be used for restoring System State and there have been no hardware changes.
465
Restoring Data to a Server or Workstation Advanced options for restore (continued) Item Junction Points Restore junction points, directories, and files from backup media Select this option to restore the information for the junction points and the files and directories to which they are linked. Selecting this option overwrites existing junction points on your system. Note If a junction point was originally backed up without the Back up files and directories by following junction points check box selected (see Back up files and directories by following junction points on page 328), 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. 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 328), 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
466
Pre/Post Commands for Restore Jobs

You can run commands before or after a restore job, and set the following conditions for these commands:

Run the job only if the pre-job command is successful Run the post-job command only if the pre-job command is successful Run the post-job command even if the job fails Allow Backup Exec to check the return codes (or exit codes) of the pre- and post-job commands to determine if the commands completed successfully. An exit code of zero returned to the operating system by the pre- or post-job command is interpreted by Backup Exec to mean the command completed successfully. A non-zero exit code is interpreted by Backup Exec to mean the command ended with an error.
If it is critical that the job not run if the pre-job command fails, then configure Backup Exec to check the return codes of the pre- and post-job commands to determine if the pre-job command failed or completed successfully. For example, if a pre-job command that shuts down a database before a restore is run fails, the database could be corrupted when the restore is run. In this situation, it is critical that the restore job fail if the pre-job command fails. Additionally, if Backup Exec is configured to check the return codes of the pre- and post-job commands, and the post-job command returns a non-zero code, the job log reports that the post-job command failed. If you also selected to run the job only if the pre-job command is successful, and both the pre-job command and the job ran successfully, Backup Exec will mark the job as failed if the post-job command fails. For example, if the pre-job command runs successfully and shuts down the database and the restore job also runs successfully, but the post-job command cannot restart the database, Backup Exec marks the job and the post-job command as failed. If you select the option On each server backed up, the pre- and post-commands are run and completed for each server before processing begins on the next selected server.
467
Restoring Data to a Server or Workstation Pre/post commands options for restore job
To set up commands to run before or after a restore job" 1. On the Properties pane, under Settings, click Pre/Post Commands. 2. Select the following options as needed:
Pre/Post Commands for restore Item Pre-job command Description 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.
468
Restoring Data to a Server or Workstation Pre/Post Commands for restore (continued) Item Post-job command Description Specify a command to be run on the specified server after the restore job has run. Use local paths, and make sure the paths exist on each server and are correct. Note Commands that require user interaction, such as prompts, are not supported. Allow pre- and post-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 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 as the command ended with an error. After checking the return codes, Backup Exec continues processing according to selections you made for running the pre- and post-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. Run job only if pre-job command is successful 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 only Select this option to run the post-job command only if the pre-job 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.
469
Restoring Data to a Server or Workstation Pre/Post Commands for restore (continued) Item Run post-job command even if job fails Description 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. Cancel command if not Select the number of minutes Backup Exec should wait before completed within x minutes canceling a pre-job or post-job command that did not complete. The default time-out is 30 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 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.
On each server restored to
Related Topics: Creating a Manual Restore Job by Configuring Job Properties on page 458 Setting Default Pre/Post Commands on page 331
470
Restoring File Permissions

This section contains details on restoring data using the Restore Security option, which affects file security. This security feature applies only to NTFS partitions. To enable the Restore Security option, on the Properties pane, under Settings, you select General. When restoring data with the Restore Security option, Backup Exec overwrites all directory security information presently on the disk with the security levels associated with the data being restored. This overwrite begins at the root of the restored directory structure and updates each directory in the tree until it reaches the data contained in the last directory. For example: With the following data on the storage media (a backup made prior to making security changes on disk): \(root)Security applied: Users - Full \UsersSecurity applied: Users - Full \User1Security applied: User1 - Full DATA.TXT Security applied: User1 - Full With the following data on the disk (recently changed directory and file security): \(root)Security applied: Users - Read \UsersSecurity applied: Users - Change \User1Security applied: User1 - Full DATA.TXT Security applied: User1 - Full After a restore with the Restore Security option selected, the security level of the data on the disk looks like this: \(root)Security applied: Users - Full \UsersSecurity applied: Users - Full \User1Security applied: User1 - Full DATA.TXT Security applied: User1 - Full If the data is restored without the Restore Security option selected, data.txt would inherit the permissions of the directory in which it was restored. In this case, it would inherit User1 directorys security level of Full. Related Topics: General settings options for restore job on page 462
471
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. 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 My Computer, and then 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.
472
6. After the Backup Exec services have started, run Backup Exec and perform a restore of the System State. Set the following option on the Advanced screen: Mark this server as the primary arbitrator for replication when restoring folders managed by the File Replication Service, or when restoring SYSVOL in System State. For more information, see Advanced Options for Restore Jobs on page 464. Caution When restoring System State, you must reboot your system before performing subsequent restore operations. If you have more than one domain controller in the network and you want Active Directory replicated to the other domain controllers, you must perform an authoritative restore of the Active Directory. To perform an authoritative restore of the Active Directory, you must run Microsofts Ntdsutil utility after the Backup Exec restore job completes and you have restored the System State data, but before you restart the server. An authoritative restore ensures that the restored data is replicated to all of the servers. For more information about authoritative restore and the Ntdsutil utility, see your Microsoft documentation. Related Topics: Creating a Manual Restore Job by Configuring Job Properties on page 458 Advanced options for restore on page 464
Restoring Windows Server 2003 Systems

The Backup Exec Shadow Copy Components file system uses Microsofts Volume Shadow Copy Service to protect critical operating system and application service data, and third party application and user data on Windows Server 2003 resources. A Writer is specific code within an application that participates in the Volume Shadow Copy Service framework to provide point-in-time, recovery-consistent operating system and application data. Writers appear as Shadow Copy Components, which are listed as resources in backup and restore selections. When expanded, the Backup Exec Shadow Copy Components file system includes System State Writers, Service State Writers, and User Data Writers.
System State Writers. To restore System State Writers, see Restoring System State on page 472. Service State Writers. To restore Service State Writers, follow normal restore procedures. See Creating a Manual Restore Job by Configuring Job Properties on page 458.
The User Data Writer in Backup Exec is the Active Directory Application Mode Writer (AD/AM Writer).
473
When restoring data with the AD/AM Writer, Backup Exec stops the service for the AD/AM instance you want to restore before the restore job starts. However, Backup Exec does not restart the AD/AM service when the restore job completes because post-processing operations, such as authoritative restores using Adamutil.exe, may be needed. You must restart the AD/AM service. If Backup Exec cannot stop the AD/AM service or if Backup Exec cannot restore all of the AD/AM files, the AD/AM restore will fail. Related Topics: Protecting Windows Server 2003 Systems on page 344 Using Redirected Restore for Active Directory, Active Directory Application Mode, and Install from Media on page 488
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 475). Utility partitions being restored must belong to the same vendor. For example, Dell utility partitions cannot be restored to a Compaq system. The size of the utility partition on which the data is being restored must be equal or greater in size than the utility partition that was backed up.
Related Topics: Restoring Data to a Server or Workstation on page 457 Selecting Data to Restore on page 479
474
Performing Redirected Restores of Utility Partitions

You may need to perform a redirected restore of a utility partition if, during a disaster recovery, the system being recovered has been renamed. A redirected restore could also be required if a new system is replacing a crashed system. In the latter case, the system being restored must be the same model as the system originally backed up. When doing a redirected restore of utility partitions, the following conditions must be met:
Utility partitions, but not the data belonging to the partitions, must be present on the system. You must have Administrator rights to restore utility partitions. Utility partitions being restored must belong to the same vendor. For example, Dell utility partitions cannot be restored to a Compaq system. The size of the utility partition on which the data is being restored must be equal or greater in size than the utility partition that was backed up. The system on which the redirected restore is targeted must be the same make and model and have the same size utility partitions as the system from which the utility partition was backed up.
Related Topics: Redirecting a Restore Operation on page 487 Manual Disaster Recovery of Windows Computers on page 610
Restoring EFI System Partition Data

The Extensible Firmware Interface (EFI) is required to boot Windows on all Intel Itanium 64-bit computers. You can restore EFI system partition data using Backup Exec on Intel Itanium 64-bit computers. EFI system partition data can be restored only on remote computers using the Backup Exec Remote Agent. You can redirect EFI partition data to any NTFS or FAT drive. However, you cannot redirect a restore job to an EFI partition. If the 64-bit Intel Itanium computer cannot be started because the EFI system partition data is corrupted, you must use the Backup Exec Intelligent Disaster Recovery (IDR) option to restore the EFI data. Related Topics: Backing Up EFI System Partitions on page 350 Redirecting a Restore Operation on page 487 Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901
475
Restoring Distributed File System (Dfs) Links

To restore Distributed file system (Dfs) links: 1. On the navigation bar, click Restore. 2. In the selection list, navigate to the computer that hosts the Dfs root. 3. Expand the Dfs root selection and then select the backup set to restore. If you backed up any Dfs links, de-select them before you restore the volume. The links within the Dfs root are not cataloged, therefore Backup Exec displays "No selections exist". All Dfs link data is associated with the Dfs root name, so the links will be restored with the Dfs root. 4. Run the restore job. Related Topics: About Selecting Distributed File System (Dfs) Links for Backup on page 287
Restoring Media Created With Other Backup Software

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

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

Backup Exec for Windows NT 7.3 and later (MTF) Backup Exec for NetWare Servers 7.x, 8.x, and 9.x (MTF) Software-compressed media created with previous versions of Backup Exec, such as Backup Exec for Windows NT (5.x, 6.x and 7.x)
476

Seagate Backup Director (SIDF) Seagate Storage Exec (SIDF) BrightStor ARCserve for NetWare 4.x, 5.x and 6.x (Native and embedded SMS tape format. Cannot restore System State from tapes created by ARCserve for NetWare 6.x.) BrightStor ARCserve for Windows NT 6.x (cannot restore System State from tapes created from this product) BrightStor ARCserve Backup 9 for Windows BrightStor Enterprise Backup 10 for Windows Novell SBackup (SIDF) Palindrome Backup Director for Windows NT and NetWare (SIDF) Palindrome Storage Manager for Windows NT and NetWare (SIDF)
Note Software-compressed data backed up with products other than Backup Exec for Windows Servers cannot be restored.
Restoring ARCserve Media

Backup Exec enables you to restore data from tapes backed up with ARCserve for Windows NT v6.x, ARCserve 9 and 10, 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:
System State (from tapes created by ARCserve 6.x for NetWare and ARCserve 6.x for Microsoft Windows Databases, such as Microsoft SQL and Exchange Server and NetWare Directory Services Windows registry Interleaved files Compressed files Encrypted files Long filenames and Extended Attributes for OS/2 files
477
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. 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. Media-based catalogs are not supported on tapes created by other vendors backup products. Because of this, cataloging ARCserve tapes takes considerably longer than cataloging a tape made with Backup Exec. 3. Restore selected data to a server or workstation. Due to the naming conventions ARCserve uses for some systems, it may be necessary to select a different location for the data using Backup Execs File Redirection. For more information, see Redirecting a Restore Operation on page 487. Related Topics: Inventorying Media in Devices on page 193 Cataloging Media in a Drive on page 452 Creating a Manual Restore Job by Configuring Job Properties on page 458 Redirecting a Restore Operation on page 487 Restoring Media Created With Other Backup Software on page 476
478
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 enables 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
Chapter 9, Restoring Data 479
Job Properties - Selections dialog box. Remember that only media cataloged or backed up at this server are displayed in the views. If you want to restore data backed up at another installation of Backup Exec, you must catalog the media first. You can traverse file levels from either side of the window by clicking folders and subfolders as they appear. To select data, select the check box next to the drives, directory, or file you want to restore. If the Include Subdirectories option is selected on the Restore Job Properties dialog box, all files and directories at or below the selected directory level are included in the restore operation. 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.
Related Topics: Restore Operations and the Catalog on page 452 Cataloging Media in a Drive on page 452 Creating a Manual Restore Job by Configuring Job Properties on page 458
480
Changing and Testing Resource Credentials for Restore Jobs

If the logon account needed to restore data is different from the default logon account, you can change the account through the Resource Credentials dialog box. You can also use this dialog box to overwrite logon accounts for redirected restores. You can also verify that a logon account can access a resource. To change 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 selection, or click New and create a new logon account (see Creating a Backup Exec Logon Account on page 388). 7. To verify that the logon account you are using can access the resources selected for restore, click Test All. While Backup Exec attempts to connect to the resources, "Testing" displays in the Test Results column. After a test has completed, the Test Results column will display one of the following results: Successful, Not tested, or an error message. The Not Tested result indicates that either the logon accounts have not been tested or that the tests have been performed but the server that contains the selection could not be accessed Some tests may take a long time to complete. To cancel a logon account test, click Cancel Test. 8. Click OK. Related Topics: Creating a Manual Restore Job by Configuring Job Properties on page 458 Redirecting a Restore Operation on page 487
481
Using Advanced File Selection to Restore

Advanced file selection enables 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. For example, you can 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. For example, you can 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. Under View format, click Advanced. 3. Select the appropriate options as follows:
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 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
482
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 cleared.
Type Include Select this option to include the files in the operation. This is the default option. Select this option to exclude files from the operation.
Exclude Selection Criteria Files Dated
Include or exclude the files created or modified during the specified time period.
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. Related Topics: Restoring Data to a Server or Workstation on page 457 Redirecting a Restore Operation on page 487
Searching for Files to Restore

You can search the catalog to easily find files that you want to restore, or to make sure that you have backups of certain files. This feature also enables you to see all cataloged, backed up versions of a file, so you can restore earlier versions if you need to. You can also use this feature to make sure that you have multiple copies of a file before removing it with an archive operation.
483
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 485. 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. Double-click the file to view the files properties. To sort the listings by filename, size, type or date modified, click the appropriate column heading. 4. 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. Related Topics: Restoring Data to a Server or Workstation on page 457
484
Name and Location Options for Catalog Search

To display the Name & Location dialog box, on the Edit menu, click Search Catalogs. Options on this dialog box include:
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
485
Date Modified Options for Catalog Search

To search for files by date modified, on the Search Catalogs dialog box, select the Date Modified tab. Options on this dialog box include:
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) Description This option enables 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, and then specify the number of months.
During the previous x day(s) Click this option if you want to restrict the search to the previous day or days, and then specify the number of days.
Restore 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.
486
Redirecting a Restore 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 479). 3. On the Properties pane, under Destination, click File Redirection. 4. Select the appropriate options as follows:
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. 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 386). 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 drive
Server logon account
Restore to path
Path logon account
487
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 398). Related Topics: Preserve tree on page 463 Using Redirected Restore for Active Directory, Active Directory Application Mode, and Install from Media on page 488 Redirecting Restores for SQL on page 1049 Redirecting SharePoint Portal Server Restore Jobs on page 1366 Scheduling Jobs on page 398
Using Redirected Restore for Active Directory, Active Directory Application Mode, and Install from Media
When you want to install a new Windows Server 2003 Server Domain Controller into an existing domain, the Active Directory and SYSVOL data are replicated from the existing Domain Controller that is in the domain to the new Domain Controller. If there is a large amount of data to be replicated or if the connection between the Domain Controllers is slow or intermittent, the replication time can be lengthy. The Active Directory Application Mode replication time is also affected by the amount of data to be replicated and the connection speed. To decrease the replication time for Active Directory and Active Directory Application Mode, you can use the Install from Media feature. For Active Directory, you can use the Install from Media feature to perform a System State backup of an existing Domain Controller in the domain in which you want to add a new Domain Controller. Then, you can perform a redirected restore of the data from the System State backup to the target Domain Controller. For Active Directory Application Mode, you can back up data using the AD/AM Writer. Then, you can perform a redirected restore of the data from the AD/AM backup to the target system.
488
To install Active Directory using the Install from Media feature: 1. Perform a standard System State backup of an active Windows Server 2003 Server Domain Controller that is in the target domain. 2. Transport the tape to the location of the system that will be installed into the target Domain. Caution The tape is not encrypted or protected. Use caution when transporting it to the location of the target domain. 3. Inventory the drive where the tape is loaded. 4. Catalog the tape. 5. Perform a redirected restore of the System State backup to a temporary location on a volume or directory on the target system. On the Properties pane, under Destination, click File Redirection. And then select redirection options. 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. 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.
489
Setting Restore Defaults
14. Complete the Active Directory Installation Wizard by following the prompts on the screen. 15. Complete the Domain Controller installation. 16. Reboot the system that has the new Domain Controller. 17. Delete any remaining temporary redirected System State files. For more information, refer to your Microsoft documentation. Related Topics: Creating a Manual Backup Job by Configuring Job Properties on page 262 Inventorying Media in Devices on page 193 Cataloging Media in a Drive on page 452 Redirecting a Restore Operation on page 487
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. 3. Select the appropriate options as follows:
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. Description
490
Setting Restore Defaults Restore default options (continued) Item Skip if file exists Description 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 recent 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.
Caution Corrupt files, which appear in the restore selections window with a red X, could be incomplete files. Restoring corrupt files could result in corrupt data. Symantec recommends performing redirected restore of corrupt files rather than restoring to the original location.
Junction Points Restore junction points, files and directories from backup media When this option is selected, the information for the junction points and the files and directories to which they are linked is restored. Selecting this option overwrites existing junction points on your system. If a junction point was originally backed up without the Back up files and directories by following junction points check box selected (see Back up files and directories by following junction points on page 328), 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.
491
Setting Restore Defaults Restore default options (continued) Item Preserve existing junction points and restore files and directories from backup media Description 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 328), 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.
492
Specifying the Restore Network
Specifying the Restore Network

Backup Exec restores data using the default network information (see Specifying Default Backup Network and Firewall Options on page 336). However, you can override the default settings for a restore job. Isolating the restore job to a specific network ensures other connected critical networks are not affected when the restore job is being processed. To specify 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 479). 3. On the Properties pane, under Settings, click Network and Firewall. 4. Select the appropriate options as follows:
Network options for restore job 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 restore network. The list includes all available network interface cards on the media server. If you are using the Central Admin Server Option (CASO), select the Use the default network interface for the managed media server option if you want CASO delegated restore jobs to be processed using the network interface card configured as the default in the managed media server. IP address 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. .Displays the Media Access Control (MAC) address for the network card you selected.
Subnet mask
Network ID
Physical address
493
Specifying the Restore Network Network options for restore job (continued) Item Use any available network route for remote agents not bound to the above Network ID Description 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.
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. Related Topics: Restoring Data to a Server or Workstation on page 457 Specifying Backup Networks on page 334 Scheduling Jobs on page 398
494
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. Click the Job List tab. 3. In the Current Jobs Filter box, click Active jobs. 4. Select the restore job you want to cancel. 5. Under Active Job Tasks in the task pane, select Cancel. 6. Select Yes when prompted to confirm the cancellation of the job. Related Topics: Deleting Scheduled Jobs on page 426
495
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.
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.
496
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.
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.
497
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.
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.
498
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.
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.
The backup set is incomplete because the backup job was terminated. 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.
499
A Shadow Copy backup set that is corrupt on the backup media.
A System State backup set.
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.
500
Chapter
10
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
Note BEWAC does not support the use of color icons for alerts. For information about how alerts appear in BEWAC, see Viewing, Clearing, and Responding to Alerts on page 715. 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
501
Viewing and Filtering Alerts
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. 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.
Related Topics: Responding to Active Alerts on page 507.

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. In addition, the status bar at the bottom of the screen displays an alert icon. The icon that displays in the status bar is for the most severe type of alert in the Active alerts list. Therefore, if the current or most recent alert is not the most severe, the icon in the status bar will not match the icon for the most recent alert in the alert list. To view alerts in the Active alerts or Alert history pane: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts or Alert History tab.
502
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. Note If you are using BEWAC and you want to view values, properties, and alert messages for an alert, select the alert, and then under General Tasks in the task pane, select Properties.
Chapter 10, Alerts and Notifications
503
To set View Filters for Active alerts and Alert history: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts or Alert History tab. 3. In the Active Alerts or Alert History Filter box, click the option for the alerts you want to 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 Show media server 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. This filter displays only if you have the Central Admin Server Option installed. After you select this option, select the media server for which you want to view alerts. Select All media servers to view alerts for all media servers.
Related Topics: Responding to Active Alerts on page 507
504
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. If the alert is in the alert history, you can view response information. To view alert properties: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts or Alert History tab. 3. Select the alert from either the Active Alerts or Alert History pane. 4. Under General Tasks in the task pane, click Properties. The Alert Properties dialog box provides the following items:
Alert Properties Item Alert Properties Category Type The title of the alert. The severity of the alert. The type helps you determine how quickly you want to respond. Following are the alert types:

Descriptions
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.
505
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 SNMP message from Backup Exec regarding status and error conditions. SNMP must be installed to view this message.
The alert is activated or disabled. Notifications are enabled or cleared for the alert. Recipients must be configured in order to use this option. SNMP notifications are enabled or cleared for the alert. SNMP must be installed to use this option. The alert is entered into the Windows Event Viewer. The Windows Event log displays all the property information for the alert. If a link appears in the Windows Event log you can search the Symantec Technical Support web site for information about the Event ID.
Send SNMP notifications Record in event log
Event ID Automatically clear after x days/hours/minutes
The alerts ID in the Windows Event Viewer. The length of time the alert remains active before it is moved to the Alert history. For attention required alerts, you can set a default response. For more information, see Editing Media Server Configurations on page 737. This option is available only for the Media Overwrite, Media Remove, Media Insert, Library Insert alert categories. The response Backup Exec automatically sends. Sends the job log to the recipient configured for notification. This option can only be used for recipients that are configured for e-mail or printer notification.
Respond with
Include job log
506
Responding to Active Alerts Alert Properties (continued) Item Descriptions
Response (Alert History Properties) User who responded Response machine Time user responded User response 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. The response the user entered for the alert.
5. After you view the alert properties, click OK. Related Topics: Configuring Alert Category Properties on page 511 Configuring Recipients on page 518 Configuring SNMP Notification on page 536
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 502), only those alerts that are selected appear. To respond to an active alert: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Select the alert to which you want to respond, and then under Alert Tasks in the task pane, click Respond. Note If you have more than one alert selected, click Respond OK to all to clear the selected alerts to the alert history. The alerts must have an OK response available to be automatically cleared. The alert dialog box appears.
507
Responding to Active Alerts
If you click Close, you will close the dialog box, but the alert remains active. To clear the alert and move it to the alert history, you must select a response such as OK, Yes, No, or Cancel from the alert dialog box. The alert dialog box provides the following information:
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.
Server name Device name Job name Time
Automatically display new Select this check box to have alerts automatically appear in the alerts Backup Exec console when they are sent. If you do not select this option, you must respond to alerts through the Active Alerts pane. For more information, see Changing Default Preferences on page 120. Note The Automatically display new alerts option is not available in Backup Exec Web Administration Console (BEWAC).
4. Click a response for the alert. Note If you are using Backup Exec Web Administration Console (BEWAC), click OK after selecting a response for the alert. After the alert condition is resolved, the alert is moved to the Alert history.
508
Viewing the Job Log for Alerts
Viewing the Job Log for Alerts

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. Click the Active Alerts or Alert History tab. 3. Select the alert for which you want to view the job log from either the Active Alerts or Alert History pane. 4. Perform one of the following:
If the alert is in Active alerts, under Alert Tasks in the task pane, click View job log. If the alert is in the Alert history, under Alert History Tasks, click View job log.
5. To search for a specific word or phrase, click Find. Type the text you want to find, and then click Find Next. Be sure to expand all sections of the job log. The Find feature searches only the expanded sections of the job log. 6. To print the job log, click Print. You must have a printer attached to your system and configured in order to print the log. To save the job log as an .html or .txt file, click Save As and then select the file name, file location, and file type. 7. After you have finished viewing the job log, click OK. Related Topics: Viewing and Changing Completed Jobs on page 427
509
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. Click the Active Alerts tab. 3. Under Alert Tasks in the task pane, click Clear all informational alerts. All the informational alerts in the Active alerts pane are cleared to the Alert history.
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. Click the Active Alerts tab. 3. On the Active Alerts pane, select the alert that you want to enable or disable. 4. Under Alert Tasks in the task pane, click Alert category enabled. The alert will be enabled or disabled, depending on the current setting. The error and attention required alert types cannot be disabled.
510
Configuring Alert Category Properties
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. 2. Click the Active Alerts tab. 3. Under Alert Tasks in the task pane, click Configure alert categories. 4. Under Alert Categories, click the alert for which you want to view or change properties. Tip You can change the options for more than one alert category simultaneously. To select consecutive alert categories, click the first alert, press and hold down <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.
5. Under Category Properties, select the appropriate options as follows:

Alert Category Properties Item Category name 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 510. 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 518.
Enable alerts for this category
511
Configuring Alert Category Properties Alert Category Properties (continued) Item Include job log with a notification to an e-mail or printer recipient Send SNMP Notifications Description 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. 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 536. Select this check box to enter the alert into the Windows Event Viewer. The Windows Event log displays all the property information for the alert. If a link appears in the Windows Event log you can search the Symantec Technical Support web site for information about the Event ID. Automatically clear after x Select this check box to enter the number of minutes, hours, or days/hours/minutes days you want the alert to remain active before it is moved to the Alert history. For attention required alerts, you can set a default response. For more information, see Editing Media Server Configurations on page 737. Respond with This option is available only for the Media Overwrite, Media Remove, Media Insert, Library Insert alert categories. Select the response that you want Backup Exec to send automatically. The choices are Cancel, No, Yes or OK.
Record event in the Windows Event Log
6. Click Apply to apply the properties to the alert and continue configuring additional alerts. 7. Click OK to exit the Alert Configuration dialog box. Related Topics: Assigning Recipients to Alert Categories for Notification on page 533 Using Audit Logs to Review Activity Performed in Backup Exec on page 437
512
Deleting Alerts from the Alert History
Deleting Alerts from the Alert History

Alerts that have been responded to or automatically cleared from the system are kept in the Alert history. All alerts are displayed, except for entries that have been filtered and selected for exclusion. The alerts remain in the Alert history for the length of time you set in the database maintenance option or until you delete the alert. To delete an alert from the Alert history: 1. On the navigation bar, click Alerts. 2. Click the Alert History tab. 3. Select the alert you want to delete, and then under Alert History Tasks in the task pane, click Delete. 4. Click Yes to confirm that you want to delete the alert. The alert is removed from the Backup Exec database. Related Topics: Configuring Database Maintenance on page 447
513
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. Related Topics: Configuring Recipients on page 518 Assigning Recipients to Alert Categories for Notification on page 533
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. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure e-mail and pagers. 4. Click the SMTP Configuration tab and select the appropriate options as follows:
SMTP Configuration dialog box Item Enable Description Select this check box to activate the notification method.
514
Configuring E-mail and Pager Notification Methods SMTP Configuration dialog box (continued) Item SMTP mail server Description 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
5. Click OK. Related Topics: Configuring Recipients on page 518
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. Note If you install Outlook after installing Backup Exec, you must stop and restart the Backup Exec services for MAPI e-mail notification to work and in order to save the MAPI configuration settings. To configure MAPI alert notification: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure e-mail and pagers.
515
4. 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 61. Type the mailbox from whom the notification message will be sent, for example, John Smith. The name appears in the From field in the message and does not require a full address. Note The Backup Exec services must be running under a domain account that has rights to the Exchange mailbox used for MAPI notification in order to save the MAPI configuration settings.
Mailbox name to send e-mail from
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. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure e-mail and pagers.
516
4. Click the VIM Configuration tab and select the appropriate options as follows:
VIM Configuration dialog box Item Enable Notes client directory Description Select this check box to activate the notification method. Type the path of the directory in which the Notes client is located. Type the password that enables you to connect to the Notes client. Re-type the password that enables you to connect to the Notes client.
Mail password
Confirm mail password
Configuring a Pager for Alert Notification

You can configure Backup Exec to page you with alert notification messages. A modem is required for pager notification. Make sure that the modem can communicate properly with your paging service. Before setting up pager notification, contact your paging service for information about modems compatible with the service. 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure e-mail and pagers. The Notification Configuration Properties dialog box appears. 4. Click the Pager Configuration tab and select Enable to activate this alert notification method. 5. Select a modem from the Select a modem for sending pages option. Only modems recognized in Windows appear in the list box. 6. Click OK.
Chapter 10, Alerts and Notifications 517
Configuring Recipients
Recipients are individuals with a predefined notification method, computer consoles, printers, or groups. Recipient configuration consists of selecting a notification method and defining notification limits. After you create entries for the recipients, you can assign them to alerts, jobs, or selection lists. The following types of recipients can be configured for notifications:
Person. 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.
Related Topics: Configuring E-mail and Pager Notification Methods on page 514 Assigning Recipients to Alert Categories for Notification on page 533 Selecting Recipients for Notification on page 534 Using Selection Lists on page 293
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. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4. Click New, click Person in the Recipient Type dialog box, and then click OK. 5. In the Name field, type the name of the recipient that you want to configure.
518
6. 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.
Notify me a maximum of x Type the total number of notifications you want sent to the times within x minutes recipient for all alerts generated within the specified number of minutes. After the specified number of notifications have been sent, additional notifications are not sent until the specified minutes have been reached. The maximum number of minutes that can be set is 1440, which is the number of minutes in a day. Reset the notification limits after x minutes Select this check box to enter the number of minutes that must be reached before the notification limits are reset. When the time limit has been reached, the number of notifications sent is reset to zero.
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 531.
Schedule
7. Click OK. Related Topics: Editing Recipient Notification Methods on page 532 Editing Recipient Notification Properties on page 531
Assigning Recipients to Alert Categories for Notification on page 533
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. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4. Click New, click Person in the Recipient Type dialog box, and then click OK. 5. In the Name field, type the name of the recipient that you want to configure. 6. Click the MAPI Mail tab and select the appropriate options as follows:
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. Note If you are using Backup Exec Web Administration Console (BEWAC), this option is not available. Limit the number of notifications sent Enable Select this check box to activate the option.
Mailbox
Test
520
Configuring Recipients MAPI Mail dialog box (continued) Item Description
Schedule
7. Click OK. Related Topics: Editing Recipient Notification Methods on page 532 Editing Recipient Notification Properties on page 531 Assigning Recipients to Alert Categories for Notification on page 533
521
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. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4. Click New, click Person in the Recipient Type dialog box, and then click OK. 5. In the Name field, type the name of the recipient that you want to configure. 6. Click the VIM Mail tab and select the appropriate options as follows:
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. Note If you are using Backup Exec Web Administration Console (BEWAC), this option is not available. Limit the number of notifications sent Enable Select this check box to activate the option.
Address
Test
522
Configuring Recipients VIM Mail dialog box (continued) Item Description
Schedule
Related Topics: Editing Recipient Notification Methods on page 532 Editing Recipient Notification Properties on page 531 Assigning Recipients to Alert Categories for Notification on page 533
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. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears.
4. Click New, click Person in the Recipient Type dialog box, and then click OK. 5. In the Name field, type the name of the recipient that you want to configure. 6. Click the Pager tab and select the appropriate options as follows:
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. Enter the country or region name and country code in which the pager is located. Type the pager identification number provided by the paging service provider. You will have a pin if you use TAP services and in most cases, the number is the last seven digits of the pagers phone number.
Carrier Phone
Country/region name and code Pager Pin
Advanced Pager setup options Advanced Enables you to configure additional settings for the pager. For more information about the options, see Advanced Pager Information dialog box on page 525. Enables you to test the notification configuration for the recipient. Note If you are using Backup Exec Web Administration Console (BEWAC), this option is not available. Limit the number of notifications sent Enable Select this check box to activate the option.
Test
Notify me a maximum of x Type the total number of notifications you want sent to the times within x minutes recipient for all alerts generated within the specified number of minutes. After the specified number of notifications have been sent, additional notifications are not sent until the specified minutes have been reached. The maximum number of minutes that can be set is 1440, which is the number of minutes in a day.
524
Configuring Recipients Pager dialog box (continued) Item Reset the notification limits after x minutes Description 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
7. 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
525
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
8. Click OK to save the settings in the Advanced Pager Information dialog box, and then click OK to save the pager configuration settings. Related Topics: Editing Recipient Notification Methods on page 532 Editing Recipient Notification Properties on page 531 Assigning Recipients to Alert Categories for Notification on page 533
Configuring a Net Send Recipient

You can configure Net Send to send notification messages to a target computer or user. Note If the target computer has Internet pop-up advertisement blocking software installed, the Net Send notification message will not display. To configure a Net Send recipient: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4. Click New, click Net Send in the Recipient Type dialog box, and then click OK.
526

Net Send Recipient Properties dialog box Item Name Description Type the recipient for whom you are configuring the notification. Type the name of the computer or user to whom you are sending the notification. You should enter a computer rather than a user because the Net Send message will fail if the user is logged off the network. Note If the target computer has Internet pop-up advertisement blocking software installed, the Net Send notification message will not display. All Computers Select the check box to send the notification to all the computers in the network. Enables you to test the notification configuration for the recipient. Note If you are using Backup Exec Web Administration Console (BEWAC), this option is not available. Limit the number of notifications sent Enable Select this check box to activate the option.
Target Computer or User Name
Test
Limit when notifications can be sent Enable Select this check box to activate the option and configure the length of time the recipient is available for notification.
527
Configuring Recipients Net Send Recipient Properties dialog box (continued) Item Schedule Description Enables you to select the days and times when notifications can be sent to the recipient. For more information, see Scheduling Notification for Recipients on page 531.
6. Click OK. Related Topics: Editing Recipient Notification Methods on page 532 Editing Recipient Notification Properties on page 531 Assigning Recipients to Alert Categories for Notification on page 533
Configuring a Printer Recipient

You can select installed printers as a notification method for recipients; however, fax printer devices are not supported by Backup Exec. Only printers that were configured using the same username and password as the Backup Exec service account can be selected. To configure a printer recipient: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4. Click New, click Printer in the Recipient Type dialog box, and then click OK. 5. Click Printer, and then click OK. 6. Select the appropriate options as follows:
528
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. Note If you are using Backup Exec Web Administration Console (BEWAC), this option is not available. Limit the number of notifications sent Enable Select this check box to activate the option.
Target Printer
Test
Schedule
Related Topics: Editing Recipient Notification Methods on page 532 Editing Recipient Notification Properties on page 531 Assigning Recipients to Alert Categories for Notification on page 533
Configuring a Group Recipient

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

During the recipient configuration process, you can enable the Limit when notifications can be sent option to select the times of the day and the days of the week the recipient is available to receive the notification messages. You can modify the schedule after the recipient is configured by editing recipient notification properties. To configure the notification schedule for recipients during recipient configuration: 1. On the Recipient Properties dialog box, under the Limit when notifications can be sent group box, click Enable to activate the option. Note To access the Recipient Properties dialog box, on the navigation bar, click Alerts. On the task pane, under Notification Tasks, click Configure recipients. Click New to create a new recipient or select an existing recipient and then click Properties. 2. Click Schedule. 3. Clear the Include work days check box to exclude Monday through Friday from 8 A.M. to 6 P.M. 4. Clear the Include weeknights check box to exclude Monday through Friday from 6 P.M. to 8 A.M. 5. Clear the Include weekends check box to exclude Saturday and Sunday, 24 hours a day. 6. You can select any combination of Include work days, Include weeknights, or Include weekends, or click any single hour of the chart to select or clear that hour. 7. After selecting the days and times you want, click OK.
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. 2. Click the Active Alerts tab.
531
3. Under Notification Tasks in the task pane, click Configure recipients. The Configure Recipients dialog box appears. 4. Select the recipient you want to edit, and then click Properties. The Recipient Properties dialog box for the type of recipient you selected appears. 5. Edit the properties for the selected recipient. You can edit any of the properties except for the recipient name in the Name field. To modify the recipient name, you must create a new recipient, and then delete the old one. 6. Click OK.
Editing Recipient Notification Methods

You can configure new notification methods or edit existing notification methods after you configure recipients. To edit notification methods: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Assign recipients to alert categories. The Alert Notification Setup dialog box appears. 4. Under Recipients, click Settings. The Notification Configuration Properties dialog box appears. 5. Edit notification properties for the following types of notification methods:

SMTP Configuration. See SMTP Configuration dialog box on page 514. MAPI Configuration. See MAPI Configuration dialog box on page 516. VIM Configuration. See VIM Configuration dialog box on page 517. Pager Configuration. Click Enable to activate or clear the notification method, and then select a modem from the Configured Modems list.
6. Click OK.
Assigning Recipients to Alert Categories for Notification
Removing Recipients
You can delete recipients that do not want to receive notification messages; however, the recipient is permanently removed upon deletion. If you want to keep the recipient, but do not want the recipient to receive notifications, clear the Enable check box in the recipient properties. To remove a recipient: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Configure recipients. 4. Select the recipient you want to delete, and then click Remove.
Assigning Recipients to Alert Categories for Notification

You can assign recipients to alert categories to receive notification messages. When an alert occurs, all the recipients assigned to the alert category receive the notification message. You can also clear a recipient from an alert category and edit properties for the alert categories during the alert notification setup. To assign a recipient to an alert category: 1. On the navigation bar, click Alerts. 2. Click the Active Alerts tab. 3. Under Notification Tasks in the task pane, click Assign recipients to alert categories. 4. Under Alert Categories, select the alert category to which you want to assign recipients. 5. Under Recipients, select the recipients you want to receive notification messages for the alert category, or click Check All to select all the recipients in the list. 6. Click OK.
533
Selecting Recipients for 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. Related Topics: Configuring Alert Category Properties on page 511 Configuring E-mail and Pager Notification Methods on page 514 Configuring Recipients on page 518

You can assign recipients to be notified when a job completes or when a job containing a specific selection list completes. You can configure new recipients or edit existing recipients and add a job log to the notification message; however, the job log can only be added for recipients configured for e-mail or printer notification. To select recipients for notification: 1. Do one of the following:
To select recipients to be notified when a job completes, select the type of job for which you want to configure notifications. When the job properties dialog box appears, on the Properties pane, under Settings, click Notification.
534
To select recipients to be notified when a job containing a specific selection list completes, on the navigation bar, click Job Setup. Then, on the Backup Selection Lists pane, select the selection list that you want to add notification to. Under General Tasks in the task pane, click Properties, and then under Source, click Selection List Notification.
2. Select the recipients you want to assign to the job or selection list. 3. If the recipient is using an e-mail or printer notification method, click Include job log with a notification to an e-mail or printer recipient. 4. You can continue selecting other options from the Properties pane. To configure new recipients or edit recipient properties: 1. Repeat step 1 on page 534. 2. Perform one of the following:
To configure a new recipient, click New, select the recipient type you want to configure, and then click OK. To edit recipient properties, select the recipient for which you want to edit properties, and then click Properties.
3. Enter or edit recipient properties for the following types of recipients:
Person

SMTP Mail. See SMTP Mail dialog box on page 519 MAPI Mail. See MAPI Mail dialog box on page 520 VIM Mail. See VIM Mail dialog box on page 522 Pager. See Pager dialog box on page 524
Net Send. See Net Send Recipient Properties dialog box on page 527 Printer. See Printer Recipient Properties dialog box on page 529 Group. Perform the following: In the Group Name field, type the group for whom you are configuring the notification.
a.
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.
Configuring SNMP Notification
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.
4. Click OK. 5. You can edit recipient properties or select other options from the Properties pane. Related Topics: Backing Up Data on page 259
Configuring SNMP Notification

SNMP (Simple Network Management Protocol) is a method by which a network can be monitored from a central location. SNMP-enabled network applications (like Backup Exec) report to an SNMP Console (a management workstation). The console receives messages (traps) from Backup Exec regarding status and error conditions. A MIB is available in the WINNT\SNMP\language directory on the Backup Exec CD that you can load into your SNMP console. The Object Identifier prefix for Symantec is: 1.3.6.1.4.1.1302 Backup Exec SNMP Traps (messages) have unique object IDs and may include up to four strings. The following SNMP Trap types are supported:
SNMP Traps Trap Type Product Start Object ID 1302.3.1.1.9.1 String 1 Backup Exec: Application initializing Backup Exec: Application terminating Backup Exec: Job canceled by Operator String 2 String 3 String 4
machine name product, version, revision machine name product, version, revision machine name job name local or remote Operator name detail message
Product Stop
1302.3.1.1.9.2
Job Canceled
1302.3.1.2.8.2
Job Failed
1302.3.1.2.8.1
Backup Exec: Job failed
machine name job name
536
Configuring SNMP Notification SNMP Traps Trap Type Object ID String 1 String 2 String 3 String 4 detail message
Storage device 1302.3.2.5.3.3 requires human intervention Robotic library 1302.3.2.4.3.3 requires human intervention
Backup Exec: machine name job name Storage device requires attention Backup Exec: machine name job name robotic library device requires attention
detail message
Intelligent Disaster Recovery Message Intelligent Disaster Recovery Message Backup Exec system error
1302.3.1.4.2.1. Copy to machine name job name 1 alternate path failed
detail message
1302.3.1.4.2.1. Backup 2 complete, update DR disks 1302.3.1.1.9.3 The application has encountered an error Information on normal events The job succeeded
detail message
detail message
Backup Exec general information Job Success
1302.3.1.1.9.4
detail message
1302.3.1.2.8.3
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
537
Configuring SNMP Notification SNMP Traps Trap Type Object ID String 1 String 2 String 3 String 4 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
Job Warning
1302.3.1.2.8.7
detail message
PVL Device Error
1302.3.1.5.1.1. The device has machine name job name 1 encountered an error 1302.3.1.5.1.1. The device has machine name job name 2 encountered a warning 1302.3.1.5.1.1. Normal device machine name job name 3 information 1302.3.1.5.1.1. Device 4 requires attention 1302.3.1.5.2.1. There is an 1 error with the media machine name job name
detail message
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. There may be machine name job name 2 a problem with the media 1302.3.1.5.2.1. Normal media machine name job name 3 information 1302.3.1.5.2.1. Media 4 requires attention 1302.3.1.5.3.1. There is an 1 error with the catalog machine name job name
detail message
PVL Media Information PVL Media Intervention
detail message
detail message
Catalog Error
detail message
538
Configuring SNMP Notification SNMP Traps Trap Type Tape Alert Error Object ID String 1 String 2 String 3 String 4 detail message
1302.3.1.5.4.1. There is a 1 TapeAlert error 1302.3.1.5.4.1. There is a 2 TapeAlert warning 1302.3.1.5.4.1. Normal 3 TapeAlert information 1302.3.2.5.5.1. There is a 1 database maintenance error 1302.3.2.5.5.1. Normal 2 database maintenance information 1302.3.2.5.6.1. There is a 1 software update error 1302.3.2.5.6.1. There is a 2 software update warning 1302.3.2.5.6.1. Normal 3 software update information
Tape Alert Warning
detail message
Tape Alert Information
detail message
Database Maintenance Error
detail message
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. There is an Warning 1 install warning
detail message
Install Update 1302.3.2.5.7.1. Normal Install machine name job name Information 2 information
detail message
539
Adding Windows Management Instrumentation Capability
In order to receive Backup Exec traps at the SNMP console, you must configure the SNMP system service with the SNMP console's IP address. To install the SNMP system service and configure it to send traps to the SNMP console for Windows 2000 and Windows Server 2003: 1. Click Start, point to Settings, point to Control Panel, and then double-click Add/Remove Programs. 2. Click Add/Remove Windows Components. 3. In Add/Remove Windows Components, select Management and Monitoring Tools, and then click Details. When selecting the component, do not select or clear its check box. 4. Select Simple Network Management Protocol, and then click OK. 5. Click Next. SNMP starts automatically after installation. You must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. If your computer is connected to a network, network policy settings might also prevent you from completing this procedure. Related Topics: Configuring Alert Category Properties on page 511

Windows Management Instrumentation (WMI) is an infrastructure through which you can monitor and control system resources. Backup Exec includes performance counter and SNMP providers that can be manually installed and used with WMI. To install the WMI performance counter provider: 1. Insert the Backup Exec Installation CD. 2. At the command prompt, type the following: mofcomp <CD Drive Letter>:\winnt\wmi\backupexecperfmon.mof
540
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.
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
541
542
Chapter
11
Reports
Backup Exec includes 44 reports that show detailed information about your system. When generating most of the reports, you can specify settings that server as filter parameters or a time range for the data that you want to include in the report. You can then run and view the report immediately, or you can create a new job that saves the report data in the Job History. You can also view general properties for each report. Backup Exec also provides:
The ability to schedule a report to run at a specified times or specify a recurring schedule for the report to run. The ability to have Backup Exec distribute reports through notification.
To run reports across multiple media servers, you must install the Backup Exec SAN Shared Storage Option, even if you are not operating in a shared storage environment. Related Topics: Running a Report on page 545 Running and Viewing a New Report Job on page 548 Scheduling Report Jobs and Setting Notification Recipients on page 553 Available Reports on page 555
543
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.
Reports
Related Topics:
Running and Viewing a New Report Job on page 548 Scheduling Report Jobs and Setting Notification Recipients on page 553 Available Reports on page 555
544
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 settings, or parameters, available for you to select depend on the type of data that can be included in the report. After the report is generated, only the items that match the criteria appear in the report. To run a report: 1. On the navigation bar, click Reports. 2. On the Reports pane, select the report you want to run. 3. Under Report Tasks in the task pane, click Run report now. 4. If the Run Report Now Properties box appears, then select the appropriate Settings, or filter parameters, for the data you want to include in the report. Only filter parameters that are available for a report appear. Select the appropriate options as follows:
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 227. Filters the report based on media server names. The media server is the server on which Backup Exec is installed. This setting is only available if the SAN Shared Storage Option is available. Filters the report based on job status. Filters the report based on specific protected server names. The protected server is the server that is being backed up. Filters the report based on specific vault names. A media vault is a virtual representation of the actual physical location of media. For more information on media vaults, see Media Location on page 243.
Media server
Job status Protected server
Vault
Chapter 11, Reports
545
Running a Report Report filters (continued) Item Ranges Description Filters the report based on the time range for the data that you
want to include in the report. If range parameters are not available for a report, you will not be able to select the parameter. Range parameters or options available include:
Days. Select this check box to enable the date filter.
- Number of days before day report runs. Type the number of days prior to the current day to begin the filter process on the data to be included in the report. You can enter a minimum of 0 and a maximum of 32,000 days. - Number of days after day report runs. Type the number of days after the current day to begin the filter process on the data to be included in the report. You can enter a minimum of 0 and a maximum of 32,000 days.
Hours. Select this check box to enable the hours filter. - Number of hours within time report. Type the number of hours either before or after the present hour to filter the data to be included in the report. The time frame depends on the type of report. You can enter a minimum of 0 and a maximum of 32,000 hours.
Event count. Select this check box to enable the event count filter. - Maximum number of events to include. Enter the number of events to include in the report. Events generate alerts and originate from one of the following sources: system, job, media, or device. You can enter a minimum of 0 and a maximum of 32,000 events.
Note Entering a value of zero for the range parameter does not limit the amount of data included in the report; this can result in an extensive report.
5. Click Run report. The report appears and displays data based on the criteria you set when you ran the report. 6. To save the report, click Save As; for a report in PDF, click the Save a Copy icon. When prompted, enter the file name and location where you want to save the report and then click Save.
546
Running a Report
The report is saved in the location you specify. Backup Exec also creates a folder, with the same name as the report, in the same location in which the report is saved. The folder contains images and report pages that enable you to view the saved report. 7. To print the report, click Print; for a report in PDF, click the Print icon. You must have a printer attached to the computer, and configured in order to print the report. 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. 8. After you have finished viewing the report, click OK. The report will automatically be deleted. Related Topics: Scheduling Report Jobs and Setting Notification Recipients on page 553 Available Reports on page 555
Chapter 11, Reports
547
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.
548
If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. 5. On the Properties pane, under Settings, select the appropriate filter parameters for the data you want to include in the report. If filter parameters or settings are not available for a report, you will not be able to view the parameters. Select the appropriate options as follows.
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 227. Filters the report based on media server names. The media server is the server on which Backup Exec is installed. This option is only available if the SAN Shared Storage Option is installed. Filters the report based on job status. Filters the report based on specific protected server names. The protected server is the server that is being backed up. Filters the report based on specific vault names. A media vault is a virtual representation of the actual physical location of media. For more information on media vaults, see Media Location on page 243.
Media server
Job status Protected server
Vault
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 Number of days before day report runs Description Select this check box to enable the date filter. Type the number of days prior to the current day to begin the filter process on the data to be included in the report. You can enter a minimum of 0 and a maximum of 32,000 days.
Chapter 11, Reports
549
Running and Viewing a New Report Job Report ranges (continued) Item Number of days after day report runs Description 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.
Hours
Number of hours within Type the number of hours either before or after the present hour time report to filter the data to be included in the report. The time frame depends on the type of report. You can enter a minimum of 0 and a maximum of 32,000 hours. Event count Maximum number of events to include Select this check box to enable the event count filter. Enter the number of events to include in the report. Events generate alerts and originate from one of the following sources: system, job, media, or device. You can enter a minimum of 0 and a maximum of 32,000 events.
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 Notification on page 534. When the notification is sent to the recipient, the report is not included. 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. To view the report in the Job History: 1. On the navigation bar, click Job Monitor. 2. Click the Job List tab. 3. On the Job History pane, select the report you want to view. 4. Under General Tasks in the task pane, click Properties. The report and job history appear and display data based on the criteria you selected when you set up the job. 5. Click Job History to view detailed information about the job or Report to view the contents of the report. 6. To print the report, click Print; for a report in PDF, click the Print icon. You must have a printer attached to the computer, and configured in order to print the report. For reports in an HTML format, do the following:
To ensure the reports print correctly, in the Layout tab of the Print dialog box, under Orientation, select Landscape. To print all the pages in a multiple page report, in the Options tab of the Print dialog box, select Print all linked documents.
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. 7. After you have finished viewing the report, click OK. The report is saved for the length of time you set in the database maintenance option.
Chapter 11, Reports
551
To save the report to a new location: 1. On the navigation bar, click Job Monitor. 2. Click the Job List tab. 3. On the Job History pane, right-click the report you want to save. 4. Click Properties. 5. Click Save As. The Save As dialog box appears. 6. Enter the file name and location where you want to save the report and then click Save. The report is saved in the location you specify. Backup Exec also creates a folder, with the same name as the report, in the same location in which the report is saved. The folder contains images and report pages that enable you to view the saved report. To delete the report from Job History: 1. On the navigation bar, click Job Monitor. 2. Click the Job List tab. 3. On the Job History pane, select the report you want to delete. 4. Under General Tasks in the task pane, click Delete. 5. Confirm the job deletion. The report and associated job history are deleted. Related Topics: Configuring Database Maintenance on page 447 Viewing and Changing Completed Jobs on page 427 Available Reports on page 555
552
Viewing Report Properties
Scheduling Report Jobs and Setting Notification Recipients

You can create a report job and schedule it to run at a specific time or specify a recurring schedule for a report to run. For information about creating a report job, see Running and Viewing a New Report Job on page 548. For information about scheduling the job, see Scheduling Jobs on page 398. 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 Notification on page 534. 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.

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 Description The name of the report. Describes the type of data that is included in the report.
Chapter 11, Reports
553
Viewing Report Properties Report Properties (continued) Item Category Description 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.
4. Click OK after you have finished viewing the properties. Related Topics: Running a Report on page 545
554
Available Reports
Available Reports
This section provides detailed information about each report available in Backup Exec. The file name of the report, a description, and the information included in the report are listed for each report. The data included in each report will vary depending on the criteria you selected to include in the report. The following reports are included in Backup Exec:
Backup Exec Reports Report Name Active Alerts Description Lists all active alerts chronologically, displaying the most recent alerts first (see Active Alerts Report on page 559). 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 559). Lists all alerts in the alert history chronologically, displaying the most recent alerts first (see Alert History Report on page 561). 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 562). Lists the contents of the audit logs for selected servers for the specified time period (see Audit Log Report on page 563) Lists the success rate for backup jobs run to protect selected servers (see Backup Job Success Rate Report on page 564). Lists the success rate for backup jobs for specified past number of days for resources on selected servers (see Backup Resource Success Rate Report on page 565). 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 566). Lists all backup sets by media set (see Backup Sets by Media Set Report on page 567).
Active Alerts by Media Server
Alert History
Alert History by Media Server
Audit Log
Backup Job Success Rate
Backup Resource Success Rate
Backup Set Details by Resource
Backup Sets by Media Set
Chapter 11, Reports
555
Available Reports Backup Exec Reports (continued) Report Name Backup Size by Resource Description 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 568). Lists the contents of the Backup Exec system configuration parameters table (see Configuration Settings Report on page 569). Details the job queue sorted by status (see Current Job Status Report on page 570). 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 571). Lists device usage and error summary for each selected media server (see Device Summary Report on page 571). Lists all the policies that are targeted to specific drive selections (see Device Usage by Policy on page 573). Lists all the defined error-handling rules (see Error-Handling Rules Report on page 573). Lists all Backup Exec and other system and application event logs (see Event Logs Report on page 575). Lists all events registered by each notification recipient (see Event Recipients Report on page 576). Lists all the failed backup jobs sorted by the resource server and time frame (see Failed Backup Jobs Report on page 576). Lists all the jobs that have been run on each system device during the specified period (see Job Distribution by Device Report on page 577). Lists all the jobs that ran within the last 72 hours in chronological order (see Jobs Summary Report on page 578). Lists all the servers that have been protected by Backup Exec (see Machines Backed Up Report on page 579).
Configuration Settings
Current Job Status
Daily Network Device Utilization
Device Summary
Device Usage by Policy
Event Logs
Event Recipients
Failed Backup Jobs
Job Distribution by Device
Jobs Summary
Machines Backed Up
556
Available Reports Backup Exec Reports (continued) Report Name Managed Media Servers Description Lists the status and configuration for all media servers managed by Backup Exec (see Managed Media Servers Report on page 579). 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 581). 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 582). Lists the media located in each media vault (see Media Vault Contents Report on page 583).
Media Required for Recovery
Media Set
Media Vault Contents
Missed Availability Window Lists all jobs that have missed scheduled availability windows within the specified time range. The jobs are listed in chronological order (see Missed Availability Report on page 584). Move Media to Vault Lists all media that can be moved to a media vault. The media listed are not currently in a media vault and the medias append period has expired (see Move Media to Vault Report on page 585). Lists past and future operations data for user-set period (see Operations Overview Report on page 586). 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 588). Lists all backup sets that were created in the selected period. The sets are grouped by target server and resource (see Policy Jobs by Resource Summary Report on page 589). Lists in chronological order all jobs derived from selected policies that have run within the specified time range (see Policy Jobs Summary Report on page 590). Lists all policies and policy job templates that are defined for the server (see Policy Properties Report on page 591).
Operations Overview
Overnight Summary
Policy Jobs by Resource
Policy Jobs Summary
Policy Properties
Chapter 11, Reports
557
Available Reports Backup Exec Reports (continued) Report Name Description
Policy Protected Resources Lists job information for each job that is derived from a policy and assigned to protect any part of the named resource (see Policy Protected Resources on page 592). Problem Files Lists all the problem files reported for jobs. The files are grouped by day and resource (see Problem Files Report on page 593). Lists all media that have been modified in the last 24 hours (see Recently Written Media Report on page 594). Lists the success rate for policy derived backup jobs (see Resource Backup Policy Performance Report on page 595). 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 596). Lists all restore sets that ran within the last 72 hours. The sets are grouped by the server and resource (see Restore Set Details by Resource Report on page 597). Lists all reusable media currently in the specified vault (see Retrieve Media from Vault Report on page 598). 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 599).
Recently Written Media
Resource Backup Policy Performance Resource Risk Assessment
Restore Set Details by Resource
Retrieve Media from Vault
Robotic Library Inventory
Scheduled Server Workload Lists the estimated scheduled workload for the next 24-hour period by server (see Scheduled Server Workload on page 600). 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 601). Lists the results for the test run jobs set for the selected time period and media servers (see Test Run Results Report on page 602).
Test Run Results
Related Topics: Running a Report on page 545 Running and Viewing a New Report Job on page 548
558
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.
Active Alerts by Media Server Report

The Active Alerts by Media Server report lists all active alerts grouped and filtered by media server, displaying the most recent alerts first. You can limit the amount of data that appears in the report by selecting filter parameters for the Event count or for the Media server option. Information displayed in the Active Alerts by Media Server report is described in the following table.
Active Alerts by Media Server Report Item Time Description Date and time the alert occurred.
Chapter 11, Reports
559
Available Reports Active Alerts by Media Server Report (continued) Item Job Name Device Name Category Message Description 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.
560
Available Reports
Alert History Report

The Alert History report lists all the alerts in the Alert History chronologically, displaying the most recent alerts first. You can limit the number of alerts that appear in the report by entering range parameters for the Days or Event count options Information displayed in the Active History report is described in the following table.
Alert History Report Item Time Received Responded Responding User Job Name Media Server Category Message Date and time the alert occurred. Date and time the user responded to the alert. User that responded to the alert. The name of the job associated with the alert. Name of the media server on which the alert occurred. Title of the alert, such as Service Start or Job Failed. Describes the event that caused the alert. Description
Chapter 11, Reports
561
Available Reports
Alert History by Media Server Report

The Alert History by Media Server report lists all alerts in the alert history grouped and filtered by media server, displaying the most recent alerts first. You can limit the amount of data that appears in the report by selecting filter parameters for the Days, Event Count or Media server options. 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. 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.
562
Available Reports
Audit Log Report

The Audit Log report lists the contents of the audit logs for the selected servers for the selected time period. You can limit the amount of data that appears in the report by entering filter parameters for the Media server or Audit Category options and range parameters for the Days and Event count options. Information displayed in the Audit Log report is described in the following table.
Audit Log Report Item Media Server Category Description Name of the media server on which the audit logs are located. Category in which the change occurred, such as Logon Account, Alerts, or Job. Time and date the change occurred. Description of the change made in Backup Exec. User that made the change.
Date Entered Message User Name
Chapter 11, Reports
563
Available Reports
Backup Job Success Rate Report

The Backup Job Success Rate report lists the success rate for backup jobs run to protect selected servers. You can limit the amount of data that appears in the report by entering filter parameters for the Protected server option and range parameters for the Days option. Information displayed in the Backup Success Rate report is described in the following table.
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.
564
Available Reports
Backup Resource Success Rate Report

The Backup Resource Success Rate report lists the success rate for backup jobs for a specific number of days for resources on selected servers. You can limit the amount of data that appears in the report by entering range parameters for the Days option. Information displayed in the Backup Success Rate by Resource report is described in the following table.
Backup Resource Success Rate Report Item Resource Date Backup Sets Successful Success Rate Description Name of the system being protected. Date the backup job was processed. Total number of backup sets processed by the media server Total number of jobs successfully performed by the media server. Percentage of successful jobs processed by the media server.
Chapter 11, Reports
565
Available Reports
Backup Set Details by Resource Report

The Backup Set Details by Resource report lists all jobs that ran within the specified time range on a selected server. The jobs are grouped by the server and resource. You can limit the amount of data that appears in the report by entering filter parameters for the Protected server option and range parameters for the Hours option. Information displayed in the Daily Jobs by Resource report is described in the following table.
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 Name of the system being protected. Date and time the operation started.
566
Available Reports
Backup Sets by Media Set Report

The Backup Sets by Media Set report lists all the backup sets by media set. You can limit the amount of data that appears in the report by selecting filter parameters for the Media Set option. Information displayed in the Backup Sets by Media Sets report is described in the following table.
Backup Sets by Media Sets Report Item Media Set Media Label Description Name of the media set on which the job ran. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Sequential number for backup sets on the media. Specific type of backup. For more information on backup methods, see Understanding Backup Methods and Their Advantages on page 354. Date and time the data was backed up.
Set Method
Date / Time
Backup Set Description / Describes the data that was backed up and the location of the data. Source Directories Files MB Number of directories backed up. Number of files backed up. Amount of data backed up in megabytes.
Chapter 11, Reports
567
Available Reports
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. This report only shows jobs created by applying a policy to a resource. For information about creating policies, see Creating a New Policy on page 362. For information about creating jobs with policies, see Creating Jobs Using Policies on page 378. You can limit the amount of data that appears in the report by entering filter parameters for the Protected server option. Information displayed in the Backup Size by Resource report is described in the following table.
Backup Size by Resource Job Report Item 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. Date and time the backup job was processed. Amount of data backed up in megabytes. Average amount of data backed up during the seven previous runs. Amount by which the data backed up in the current job differs from the previous backup jobs.
Resource Job Job Date and Time Run Backup Size, MB Trailing Avg, MB Difference %
568
Available Reports
Configuration Settings Report

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

The Current Job Status report provides details about the job queue sorted by status. You can limit the amount of data that appears in the report by selecting filter parameters for the Job status. Information displayed in the Job Queue Status report is described in the following table.
Job Queue Status Report Item Job Status Job Next Due Date Original Due Date Priority Description Displays the job status. Name of the job. Next date and time the job is scheduled to run. Original date and time the job was scheduled to run. Job priority that determines which job runs first. If another job is scheduled to run at the same time as this job, the priority you set determines which job runs first. Available priorities include:

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.
570
Available Reports
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. Number of megabytes processed by the media servers storage device. Percentage of device utilization.
Date Jobs Size (MB) Utilization (%)
Device Summary Report

The Device Summary report lists all the devices for each selected media server. You can limit the amount of data that appears in the report by selecting filter parameters for the Media server option. Information displayed in the Device Summary report is described in the following table.
Device Summary Report Item Server Description Name of the server where the device is located.
Chapter 11, Reports
571
Available Reports Device Summary Report (continued) Item Device Name Description 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 Post Cleaning Totals Hours Errors MB Mounts Totals Hours Errors MB Mounts
Hours the device has been in use since the last cleaning job. Number of errors occurring since the last cleaning job. Megabytes read and written since the last cleaning job. Number of mounts occurring since the last cleaning job.
Total number of hours the device has been in use. Total number of errors occurring on the device. Total number of megabytes read and written to the device. Total number of mounts occurring to the device.
572
Available Reports
Device Usage by Policy

The Device Usage by Policy report lists all the policies that are targeted to specific drive selections. You can limit the amount of data that appears in the report by selecting filter parameters for the Policy Name. Information displayed in the Device Usage by Policy report is described in the following table.
Device Usage by Policy Report Item 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 272. Name of the policy. Name of the job template.
Method
Policy Name Template Name
Error-Handling Rules Report

The Error-Handling Rules report lists all error-handling rules and provides details about each rule. You can limit the amount of data that appears in the report by selecting filter parameters for the Media Server. Information displayed in the Error-Handling Rules report is described in the following table.
Error Handling Rules Report Item Rule Name Notes Description Name of the Error-Handling rule. Information entered in the Notes section when the error-handling rule was created.
Chapter 11, Reports
573
Available Reports Error Handling Rules Report (continued) Item Job Status Description Final job status that activates the rule. Possible statuses are:

Error Canceled
Error Category
Category of error for which the rule will be applied. Available error categories include:

Device Job Media Network Other Resource Security Server System
Enabled Cancel Job
Displays if the rule is enabled or disabled. Displays an X if this option is selected for the error-handling rule. The option cancels all jobs after the maximum number of retries have been attempted. Displays an X if this option is selected for the error-handling rule. The option enables Backup Exec to pause the job until you can manually clear the error. Displays an X if this option is selected for the error-handling rule. The option enables Backup Exec to retry the job. Number of times the job is to be retried. Number of minutes the job is to wait before being retried.
Pause Job
Retry Job
Maximum Retries Retry Interval (minutes)
574
Available Reports
Event Logs Report

The Event Logs report lists all Backup Exec and other system and application event logs. Information displayed in the Event Logs report is described in the following table.
Event Logs Report Item Server Number Event Date Time Source Description Description Name of the server on which the event occurred. Number assigned to the event in the Windows Event log. Type of event that occurred. Date the event occurred. Time the event occurred. Source from which the event originated. Message displayed for the event.
Chapter 11, Reports
575
Available Reports
Event Recipients Report

The Event Recipient report lists events registered by each notification recipient. Information displayed in the Event Recipient report is described in the following table.
Event Recipient Report Item Recipient Type Recipient Name Event Type Event Name Description Type of recipient, such as Person, Net Send, Printer, or Group. Name of the recipient. Alert category or ad hoc job. Detail for the alert category or ad hoc job.
Failed Backup Jobs Report

The Failed Backup Jobs report lists all the failed backup jobs associated with a policy. The jobs are sorted by the server and specified time frame. You can limit the amount of data that appears in the report by entering filter parameters for the Protected server option and range parameters for the Days option. Information displayed in the Failed Backup Jobs report is described in the following table:
Failed Jobs Report Item Resource Start Time Duration Job Name Description Name of the system being protected. Date and time the backup job started. Length of time the operation took to process. Name of job that failed.
576
Available Reports Failed Jobs Report (continued) Item Category Description Category for the failed job that may be generated by a system, job, media, or device error. Displays the error code that corresponds to the failure. Describes the event that caused the error. Status of the operation, such as Completed. Name of the device on which the job ran.
Error Code Description Status Device Name
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 Job Date and Time Run Job Description Name of the device on which the job ran. Date and time the job was processed. Name of the job that ran on the device.
Chapter 11, Reports
577
Available Reports
Jobs Summary Report

The Jobs Summary report lists all jobs that have run within the specified time range. The jobs are listed in chronological order. You can limit the amount of data that appears in the report by selecting range parameters for the Hours option. Information displayed in the Jobs Summary report is described in the following table.
Jobs Summary Report 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 272. 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. Name of the completed job.
578
Available Reports
Machines Backed Up Report

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

The Managed Media Servers report lists status and configuration information for all media servers managed by Backup Exec. You can limit the amount of data that appears in the report by selecting filter parameters for the Media Server option. Information displayed in the Managed Media Servers report is described in the following table.
Managed Media Server Report Item Managed Media Server Status Description Name of the managed media server. Status of the server. Possible status includes:

Online - available for use. Stalled - not responding immediately to messages No Comm - communications to the server have been lost for some period of time.
Chapter 11, Reports
579
Available Reports Managed Media Server Report (continued) Item Communication Threshold Stalled No Comm Catalog Location Time limit used for determining Stalled communications status. Time limit used for determining No Comm communications status. Location where server keeps catalog information. Possible locations are:

Description
Local - the catalog information is kept on the media server itself. CASO - the catalog information is kept on the Central Admin Server.
Upload Job Data Logs When job logs are uploaded from the managed server to the CASO database. Possible upload times are:

timed basis in seconds schedule time completion of job never
History
When job history is uploaded from the managed server to the CASO database. Possible upload times are:

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

Time Difference Display Alert Displays Yes if you have configured an alert to be set if time between server clocks exceed a preset value (maximum time difference tolerance). Administrators Guide
580
Available Reports Managed Media Server Report (continued) Item Sec Description Maximum time difference tolerance in seconds set for server.
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 272. 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
Chapter 11, Reports
581
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.
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.
582
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 Vault Name 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. Date that data on the media may be overwritten.
Overwrite Protection End Date Vault Media Rule Move Date Media Set Vault Media Rule Name
Date media can be moved to vault.
Name of media set to which the media belongs. Name of vault media rule.
Chapter 11, Reports
583
Available Reports
Missed Availability Report

The Missed Availability report lists all jobs that have missed scheduled availability windows within the specified time range. The jobs are listed in chronological order. You can limit the amount of data that appears in the report by selecting range parameters for the Hours option. Information displayed in the Missed Availability report is described in the following table.
Missed Availability Report Item Date Attempted Start Time Job Name Selection List Availability Window Begin Time End Time Date and time for beginning of availability window. Date and time for end of availability window. Description Date and time the job was created. Time Backup Exec attempted to start the job. Name of the job. Name of the selection list for the job.
584
Available Reports
Move Media to Vault Report

Lists all media that you can move to a media vault. The media listed are not currently in a media vault and meets one of the following criteria:
The media has met or exceeded the vault move date specified for the media containing the media. The append period has expired, but the overwrite protection period is still current (allocated).
You can limit the amount of data that appears in the report by entering filter parameters for Media Server and range parameters for the Days option. Information displayed in the Move Media to Vault report is described in the following table.
Move Media to Vault Report Item Media Server Description Name of the media server where the data for the backup job was located. Name of the media set. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Location of the media. Last date that data may be added to the media. Date that data on the media may be overwritten.
Media Set Media Label
Location Append Period End Date Overwrite Protection End Date Vault Media Rule Move Date Vault Name Vault Media Rule Name
Date media can be moved to vault.
Name of vault to which media is to be moved. Name of vault media rule.
Chapter 11, Reports
585
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 or Event Count options. Information displayed in the Operations Overview report is described in the following table.
Operations Overview Item Completed Jobs Summary Job summary for jobs completed in the past x Hours Completed (Canceled) Completed (Failed) Completed (Success) Exceptions Details Backup Exec job activity for the specified time period. Description
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) Active Alerts Summary Errors Warnings Information Attention Required Media Availability Scratch Media
Total number of system, job, media, and device error alerts. Total number of job, media, and device warning alerts. Total number of system, job, media, and device information alerts. Total number of alerts that require a response from the user.
Total number of scratch media available.
586
Available Reports Operations Overview (continued) Item Recyclable Allocated Imported Description Total number of recyclable media available. Number of allocated media (media belonging to a user media set). Number of imported media (media created by a product other than this installation of Backup Exec). Total number of appendable media available. Displays level of overwrite protection (Full, Partial, None) assigned to the media.
Appendable Media Overwrite Protection Level Current Jobs Summary Active Jobs Scheduled Scheduled (On hold) Job Status
Total number of active jobs. Total number of scheduled jobs. Total number of scheduled jobs on hold. Displays the job status.
Chapter 11, Reports
587
Available Reports
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 272. Date and time the operation started. Status of the operation. Category for the job that may be generated by a system, job, media, or device error. Name of the media server on which the job ran. Name of the device on which the job ran. Total number of jobs run within the last 24 hours. Number of jobs that failed and were not run again with successful completion. Percentage of jobs that ran successfully.
Start time Status Error Category
Media Server Device Name Total Tasks Uncorrected Exceptions
Service Level
588
Available Reports
Policy Jobs by Resource Summary Report

The Policy Jobs by Resource Summary report lists all of the backup sets that were created within a selected period. The jobs are grouped by target server and resource. You can limit the amount of data that appears in the report by selecting filter parameters for the Protected Server and range parameters for the Hours option. Information displayed in the Policy Jobs by Resource Summary report is described in the following table.
Policy Jobs by Resource Summary Report Item Policy 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 Name of the policy. Date and time the operation started.
Chapter 11, Reports
589
Available Reports
Policy Jobs Summary Report

The Policy Jobs Summary report lists all jobs created from selected policies that have run within a specified time range. The jobs are listed in chronological order. You can limit the amount of data that appears in the report by selecting filter parameters for the Policy Name and range parameters for the Hours option. Information displayed in the Policy Jobs Summary report is described in the following table.
Policy Jobs Summary Report Item Policy 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 272. 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 Name of the policy. Date and time the operation started. Name of the completed job.
590
Available Reports
Policy Properties Report

The Policy Properties report lists all policies and policy job templates that are defined for the media server. Information displayed in the Policy Definitions report is described in the following table.
Policy Definitions Report Item Template Name Set Description Method Description Name of the job template. Describes the data that was backed up and the location of the data. Specific type of backup. For more information on backup methods, see Backup method for files on page 272. Type of job that will run, such as Backup. Name of the device on which the job will run. Name of the media set on which the job will run. The media overwrite protection option configured for the backup job template properties.
Type Device Media Set Overwrite/Append
Chapter 11, Reports
591
Available Reports
Policy Protected Resources

The Policy Protected Resources report lists job information for each job derived from a policy and assigned to protect any part of a named resource. You can limit the amount of data that appears in the report by selecting filter parameters for the Protected server option. Information displayed in the Policy Protected Resources report is described in the following table.
Policy Protected Resources Report Item Resource Policy Job Name Next Due Date Description System being protected. Name of policy. Name of the job. Next date and time the job is scheduled to run.
592
Available Reports
Problem Files Report

The Problem Files report lists all the problem files reported for jobs. The files are grouped by day and resource. You can limit the amount of data that appears in the report by selecting filter parameters for the Protected server option and range parameters for the Days option. Information displayed in the Problem Files report is described in the following table.
Problem Files Report Item Date Resource Time Reason File Name Type Media Server Description Date the problem file was encountered. System on which the problem file is located. Time the problem file was encountered. Error code listed in the job log summary. Name of the problem file. Specific type of file that caused the problem. Name of the server on which the file is located.
Chapter 11, Reports
593
Available Reports
Recently Written Media Report

The Recently Written Media report lists all the media that has been modified within the specified period. You can limit the amount of data that appears in the report by selecting range parameters for the Hours option. Information displayed in the Recently Written Media report is described in the following table.
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. Date and time media was last modified.
Location Set Date and Time Modified
594
Available Reports
Resource Backup Policy Performance Report

The Resource Backup Policy Performance report lists the success rate for policy backup jobs. You can limit the amount of data that appears in the report by selecting filter parameters for the Protected Server option and range parameters for the Days option. Information displayed in the Resource Backup Policy Performance report is described in the following table.
Resource Backup Policy Performance Item Policy Resource Date Backup Sets Successful Success Rate Description Name of policy. Name of system being protected. Date job completed. 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.
Chapter 11, Reports
595
Available Reports
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 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
596
Available Reports
Restore Set Details by Resource Report

The Restore Set Details by Resource report lists all restore jobs that ran within the specified time range on a selected server. The jobs are grouped by the server and resource. You can limit the amount of data that appears in the report by entering filter parameters for the Protected server option and range parameters for the Hours option. Information displayed in the Daily Jobs by Resource report is described in the following table.
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 Name of the system being protected. Date and time the operation started.
Chapter 11, Reports
597
Available Reports
Retrieve Media from Vault Report

The Retrieve Media from Vault report lists all reusable media currently in a specified media vault. You can limit the amount of data that appears in the report by selecting filter parameters for the Vault option. Information displayed in the Retrieve Media from Vault report is described in the following table.
Retrieve Media from Vault Report Item Vault Name Media Label Description Name of the vault where the media is located. Media label assigned by Backup Exec, assigned by the administrator, or contained on a pre-assigned bar code label. Date that data on the media may be overwritten.
Overwrite Protection End Date Vault Media Rule Move Date Media Set Vault Media Rule Name
Date media can be moved to vault. Name of the media set. Name of vault media rule.
598
Available Reports
Robotic Library Inventory Report

The Robotic Library Inventory report lists the contents of slots in robotic libraries attached to media servers. Usage statistics are provided for each piece of media. You can limit the amount of data that appears in the report by selecting filter parameters for the Media server option. Information displayed in the Robotic Library Inventory report is described in the following table.
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. 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.
State
Modified Write MB Full
Hours Mounts Append
Chapter 11, Reports
599
Available Reports
Scheduled Server Workload

The Scheduled Server Workload report displays the estimated scheduled workload for a server during the next 24-hour period or a user-defined time period. The report only displays recurring jobs that have already run at least one time, not jobs scheduled to run once. You can limit the amount of data that appears in the report by selecting filter parameters for the Media server option and range parameters for the Hours option. Information displayed in the Scheduled Server Workload report is described in the following table.
Scheduled Server Workload Report Item Media Server Job Next Due Date Backup Size, MB Description Name of the media server that will process the scheduled jobs. Name of the job scheduled to run. Time and day the next job is scheduled to run. Estimated amount of data in megabytes to be processed during the next 24 hours. Total amount of data to be processed on the server during the next 24 hours. Total amount of data to be processed on all media servers.
Total Size (MB)
Total Size (MB)
600
Available 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. Capacity of the scratch media available to which data can be written.
Size (GB)
Available to Append (GB) Capacity of scratch media available for append. Group Total Media Total Total number and capacity of scratch media available to the system. Total number of scratch media available.
Chapter 11, Reports
601
Available Reports
Test Run Results Report

The Test Run Results report displays the results for the test run jobs set for the selected period and the selected media servers. You can limit the amount of data that appears in the report by selecting filter parameters for the Media server option and range parameters for the Hours option. Information displayed in the Test Run Results report is described in the following table.
Test Run Results Item Media Server Job Date and Time Run Job Name Media Capacity Summary Media Type Device Name Max Needed 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. Type of media used, such as 4mm. Name of the device, such as the name of the robotic library. Amount of space needed on the media to run the job. Description Name of the media server on which the job ran. Date and time the backup job was processed. Name of the test run job.
Media Total
Available to Overwrite, MB Online Media Total Credential Check Capacity of media available in the device to which data can be written. Total amount of overwritable media available to the system. Indicates if the Backup Exec logon account was verified as correct for the resources being backed up. Size in megabytes of the backup.
Backup Size, MB
602
Available Reports
Chapter 11, Reports
603
Available Reports
604
Chapter
12
Disaster Preparation and Recovery

Disaster preparation planning is the implementation of strategies and procedures that will minimize damage in the event a catastrophe destroys your data. While precautions can be taken to minimize the effects of this type of occurrence (UPS devices, password protection, and so forth), unfortunately there is nothing that can safeguard your data 100 percent. The purpose of a Disaster Preparation Plan (DPP) is to return to an operational status as quickly as possible. Backup Exec is a crucial component of the DPP and this section discusses how to apply this powerful data management tool to your DPP. There are two basic methods available for disaster recovery:
Manual recovery. This section provides procedures for manually recovering both local and remote Windows 2003/XP/2000 computers. Automated recovery. Backup Execs Intelligent Disaster Recovery (IDR) option automates the disaster recovery process for Windows Server 2003/XP/2000 computers. IDR is an option you must purchase separately.
Related Topics: Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901 Disaster Preparation of the Windows Computer on page 607 Manual Disaster Recovery of Windows Computers on page 610
605
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.
Related Topics: Selecting Data to Back Up on page 284
606
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. Related Topics: Creating an Emergency Repair Disk on page 609 Manual Disaster Recovery of Windows Computers on page 610
Returning to the Last Known Good Configuration

Changes to the system configuration may keep the system from booting. If you suspect that boot problems are the result of a configuration change, you may be able to correct the problem by returning to a previous configuration. This method is simple and fast, and in some cases will correct boot problems in a Windows computer. There are slightly different procedures for Windows 2000/XP/Windows Server 2003 computers. This section includes procedures for each type of computers. 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. Press <F8> during startup. A menu appears that allows you to diagnose and fix system startup problems. 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.
Related Topics: Creating a Hardware Profile Copy on page 608 Creating an Emergency Repair Disk on page 609
Chapter 12, Disaster Preparation and Recovery
607
Creating a Hardware Profile Copy

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

When Windows 2000 Server is installed, the installation program prompts you to create an Emergency Repair Disk (ERD). This disk contains system information that can help get the system running in the event of a disaster. It is important to keep the ERD updated whenever system changes are made. The ERD is only useful if it is kept current. For Windows XP or Windows Server 2003, Emergency Repair Disk has been replaced with Automated System Recovery (ASR). Whenever a major change is made to the system, make a fresh copy of the ERD before and after the change is made. Major changes include adding, removing, or otherwise modifying hard drives or partitions, file systems, configurations, and so forth. As a general rule, update the ERD before and after the hard drive configuration is changed. The addition of a new component to the server, such as Microsoft Exchange Server or Microsoft SQL Server, and changes from Control Panel, are also situations in which the ERD should be refreshed both before and after the change. Also remember to make a backup of the ERD; always keep an ERD from at least one generation back. When creating a fresh ERD, use a floppy disk that can be reformatted, because RDISK.EXE, the program that creates the ERD, always formats the floppy disk. Note The Emergency Repair Disk is a useful and necessary tool; it is NOT a bootable disk. There is not enough space on the disk for the boot files and the repair information files. To create the ERD for Windows 2000: 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. 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.
609
Manual Disaster Recovery of Windows Computers
Related Topics: Returning to the Last Known Good Configuration on page 607 Creating a Hardware Profile Copy on page 608 Creating an Emergency Repair Disk on page 609
Using Windows Automated System Recovery and System Restore to Recover a Windows XP or Windows Server 2003 System
The ASR feature, which replaces the Emergency Repair Disk for Windows XP and Windows Server 2003, allows you to restore the operating system to a previous state so that you can start Windows XP Professional or Windows Server 2003 when other recovery methods do not work. Microsoft recommends using System Restore, which saves only incremental changes and lets you start Windows XP Professional in normal or safe mode, before resorting to ASR. For more information about ASR or System Restore, refer to your Microsoft documentation.

Note If your system is protected by Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR), see Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901 for information on automated disaster recovery. The procedures described in the following sections allow you to manually recover a computer not protected by IDR. Different types of computers require different disaster recovery procedures. This section includes separate procedures for recovering the following types of computers:
Local Windows computer (see Manual Disaster Recovery of a Local Windows 2000/XP/Server 2003 Computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) on page 611) Remote Windows computer (see Disaster Recovery of a Remote Windows 2000/XP/Server 2003 Computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) on page 615)
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.
Manual Disaster Recovery of a Local Windows 2000/XP/Server 2003 Computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller)
Note If your system is protected by Backup Exec for Windows Servers Intelligent Disaster Recovery (IDR), see Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901 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 a pre-disaster state and will restore your data files, except those protected by one of the Backup Exec database agents, such as the Exchange Agent or SQL Agent. If any of your data is protected by Backup Exec agents, refer to the section on restoring the data protected by the agent before beginning disaster recovery. A media drive must be attached to the computer that is being recovered. You will also need:
A current full backup of the computer to be recovered and any subsequent incremental/differential backups. The Windows 2000/XP/Server 2003 installation media. The Backup Exec for Windows Servers installation media.
To manually recover a local Windows 2000/XP/Server 2003 computer: 1. Install Windows 2000/XP/Server 2003. This basic Windows installation is necessary to provide Backup Exec with a target to which it can restore the system. The computer name, Windows directory, and the file system (such as NTFS) must be the same as the previous Windows installation. This installation will be overwritten by the backed up version, which will restore your original system configuration, application settings, and security settings.
611
If you are recovering from an entire hard disk failure, use Windows setup to partition and format the new disk during installation. Format the partitions with the same file system as before the failure.
If the system was in a specific domain or workgroup, do not join the domain or workgroup at this time. If you are recovering a domain controller, do not perform the domain controller installation process at this time.
2. Install Backup Exec for Windows Servers to a directory other than where it was originally installed (this is a temporary installation). 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 108. 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 193). 7. Catalog the media containing the latest full backup of the computer to be recovered (see Cataloging Media in a Drive on page 452). If the subsequent differential/incremental backups are on separate media, catalog those also. 8. From the navigation bar, click Restore. 9. Select all sets from the full and incremental backups that contain logical drives on the hard disk. If differential backup sets are to be restored, select only the last differential set. Make sure you include System State or Shadow Copy components as part of the restore selections. 10. On the Properties pane, under Settings, click General, and then select the following options:

Restore over existing files Restore security Preserve tree
612
11. On the Properties pane, under Settings, click Advanced, and then select the appropriate options (see Advanced options for restore on page 464). If you are restoring a computer that is the only domain controller in the domain or the entire domain is being rebuilt and this is the first domain controller, select the option Mark this server as the primary arbitrator for replication when restoring folders managed by the File Replication Service, or when restoring SYSVOL in System State. 12. Click Run Now. 13. If you are restoring a computer that is the only domain controller in the domain or the entire domain is being rebuilt and this is the first domain controller, reboot the computer after the restore job successfully completes. Your computers operating system is now restored to a pre-disaster state. Your data files have been restored, except those protected by Backup Exec database agents. If you are performing an authoritative restore, continue with these steps: 14. Change the Backup Exec services to the local system account. a. Right-click My Computer and then select Manage.
b. From the left pane of the Computer Management utility, double click Services and Applications. c. Click Services.
d. In the right pane, double click each Backup Exec service, and from the Log On tab, change Log on as to use Local System account. e. Close the Computer Management utility.
15. Reboot the computer. 16. Press <F8> during startup. A menu appears that allows you to diagnose and fix system startup problems. 17. Select Directory Services Restore Mode. 18. Launch Backup Exec. 19. From the navigation bar, click Restore.
613
20. Select System State (Windows 2000 or Windows XP) or Shadow Copy (Windows 2003) components as the restore selections. Run the Restore job. 21. At this point, you can either choose to restore the entire Active Directory, or specific objects from the Active Directory: Restore the entire Active Directory by performing the following: a. Open a command prompt.
b. Type NTDSUTIL and press Enter. c. Type Authoritative Restore and press Enter.
d. Type Restore Database, press Enter, click OK and then click Yes. Restore specific objects from the Active Directory by performing the following: a. Open a command prompt.
d. Type Restore Subtree "ou=<OU Name>.dc=<domain name>,dc=<xxx> (without the quotation marks), and then press Enter, where <OU Name> is the name of the organizational unit you want to restore, <domain name> is the domain name the OU resides in, and <xxx> is the top level domain name of the domain controller, such as com, org, or net. You can do this as many times for as many objects you need to restore. 22. Once you have finished restoring Active Directory information, exit NTDSUTIL. 23. Reboot the computer. Related Topics: Creating a Manual Restore Job by Configuring Job Properties on page 458 Disaster Recovery of a Remote Windows 2000/XP/Server 2003 Computer (includes non-authoritative and authoritative restore of Active Directory for a domain controller) on page 615 Manual Disaster Recovery of Windows Computers on page 610
614
Disaster Recovery of a Remote Windows 2000/XP/Server 2003 Computer (includes non-authoritative and 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 Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901 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 51 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/Server 2003 installation media.
Note Always log on to Windows using the Administrator account or its equivalent during this procedure. To manually recover a remote Windows 2000/XP/Server 2003 computer: At the remote computer: 1. Install Windows 2000/XP/Server 2003. This basic Windows installation is necessary to provide Backup Exec with a target to which it can restore the system. The computer name, Windows directory and the file system (such as NTFS) must be the same as the previous Windows installation. This basic installation will later be overwritten by the backed up version, which will restore your system configuration, application settings, and security settings. If you are recovering from an entire hard disk failure, use Windows setup to partition and format the new disk during installation. Format the partitions with the same file system as before the failure.
If the system was in a specific domain or workgroup, do not join the domain or workgroup at this time. If you are recovering a domain controller, do not perform the domain controller installation process at this time.
615
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 Computers on page 793. 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 193). 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 452). 6. From the navigation bar, click Restore, and then select all sets from the full and incremental backups that contain logical drives on the hard disk. If differential backup sets are to be restored, select only the last differential set. Make sure you include System State or Shadow Copy components as part of the restore selections. 7. On the Properties pane, under Settings, click General, and then select the following options:

Restore over existing files Restore security Preserve tree
8. On the Properties pane, under Settings, click Advanced, and then select the appropriate options (see Advanced options for restore on page 464). If you are restoring a computer that is the only domain controller in the domain or the entire domain is being rebuilt and this is the first domain controller, select the option Mark this server as the primary arbitrator for replication when restoring folders managed by the File Replication Service, or when restoring SYSVOL in System State. 9. Click Run Now. 10. After the job completes, 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.
616
If you are performing an authoritative restore, continue with these steps: At the remote server: 11. Press <F8> during startup. A menu appears that allows you to diagnose and fix system startup problems. 12. Select Directory Services Restore Mode. At the media server: 13. Launch Backup Exec. 14. From the navigation bar, click Restore. 15. Select System State (Windows 2000 or Windows XP) or Shadow Copy (Windows 2003) components as the restore selections. 16. From the Properties pane, under Source, select Resource Credentials. 17. Highlight the restore selection for the remote server and click New. 18. Create a new logon account for this restore job. The account should have administrator privileges on the remote server. 19. Select the new logon account and click OK. 20. Run the Restore job. At the remote server: 21. At this point, you can either choose to restore the entire Active Directory, or specific objects from the Active Directory: Restore the entire Active Directory by performing the following: a. Open a command prompt.
d. Type Restore Database, press Enter, click OK and then click Yes. Restore specific objects from the Active Directory by performing the following:
617
a.
Open a command prompt.
d. Type Restore Subtree "ou=<OU Name>.dc=<domain name>,dc=<xxx> (without the quotation marks), and then press Enter, where <OU Name> is the name of the organizational unit you want to restore, <domain name> is the domain name the OU resides in, and <xxx> is the top level domain name of the domain controller, such as com, org, or net. You can do this as many times for as many objects you need to restore. 22. Once you have finished restoring Active Directory information, exit NTDSUTIL. 23. Reboot the computer. Related Topics: Creating a Manual Restore Job by Configuring Job Properties on page 458 Manual Disaster Recovery of Windows Computers on page 610
618
Chapter
13
Troubleshooting
This section provides information on troubleshooting Backup Exec. Note For more information, the Symantec Technical Support web site (support.veritas.com) provides information on error messages, how to/troubleshooting information and software downloads. Problems can be caused by a number of conditions, so when you experience a problem you will need to narrow the possibilities to solve it quickly. Use the following table to help isolate the problem:
For storage hardware problems:
See Hardware-related Questions on page 620.
If you receive an error See Error Messages on page 623 message in Backup Exec: For performance issues: For issues relating to backing up data: For issues relating to restoring data: To contact Technical Support: See Improving Backup Exec Performance on page 626. See Backup Questions on page 624.
See Restore Questions on page 626.
See Contacting Technical Support on page 628.
619
Hardware-related Questions
My drive is not listed in Backup Execs Devices list. The drive is connected, powered on and recognized in the Windows Device Manager. What should I do? First, make sure that your devices are supported by Backup Exec for Windows Servers. Refer to the Hardware Compatibility List available on the Symantec support web site, at http://support.veritas.com/rd/bews-compatibility.htm. If your device is listed on the Hardware Compatibility List, try running Backup Execs Device Configuration wizard and installing VERITAS device drivers (see Configuring Devices on page 128). The VERITAS device driver Installation wizard will find and install the most suitable driver for your storage device. Note The Hardware Compatibility List is frequently updated with newly-supported devices. My drive appears as offline. Why? If the device is offline, this message is displayed. No operations are allowed on the device until it is online again. When the device is online, no message is displayed. Backup-to-Disk folders may go offline if:

The drive containing the Backup-to-disk folder is full. The drive containing the backup-to-disk folder is offline. The remote server containing the Backup-to-disk folder is offline. The device was turned off after Backup Exec was started. The device was being used by another application (such as a Windows 2000/XP/Server 2003 backup utility) when Backup Exec was started. The device is removed from the computer. A tape drive failure occurred (check the Event Log to troubleshoot the problem). A tape is stuck in the drive. The firmware of the drive was updated; Backup Exec will behave as if the drive with its old name or identity no longer exists. 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.
Other storage devices may go offline if:

To place the device online, try the following:
620
Stop the utility that is using the device, and then reboot the server, or stop and restart the Backup Exec services.
To restart the Backup Exec services: From the Tools menu, select Backup Exec Services and then click the Restart all services button. If the drives firmware is updated or changed: If the drives firmware has changed, delete the drive and restart Backup Exec services. After the drive appears with its new firmware identity, retarget all jobs that were using the old drive name to the new drive name. I set up bar code rules through the Tools menu by selecting Options, and then selecting Bar Code Rules. However, my bar code rules dont seem to be working. Why? After setting up bar code rules, you must perform two more steps in order for the bar code rules to work. 1. You must enable the bar code rules for the robotic library by selecting the bar code rules option on the Configuration tab in the robotic librarys properties. 2. In addition to setting the bar code rules for each type of media you use, for each drive in your mixed media library you should indicate what type of media can be used and whether that media can be used for read or write operations. For more information, see Bar Code Rules in Mixed Media Libraries on page 236. How do I get the latest device drivers for my hardware? The latest device drivers for Backup Exec can be found at http://support.veritas.com/rd/bews-drivers.htm. Backup Exec doesnt detect my robotic library. What could be wrong? Be sure that Windows 2000/XP/Server 2003 properly recognizes the device. This can be verified by checking the Windows Device Manager. For configuration and setup instructions, see Symantec Backup Exec - Library Expansion Option on page 1115. You may also want to read Using Microsofts Removable Storage Feature with Backup Exec on page 189. Im getting an error "Storage device [device] reported an error on a request to read/write data to/from media. Error reported: Data error (cyclic redundancy check)." What should I do? The cyclic redundancy check (CRC) error can be caused by many factors. The following list contains the most common reasons for this error and potential ways to resolve the problem:
Chapter 13, Troubleshooting 621
1. Contaminated read/write heads of the tape device. Check with the hardware manufacturer for proper cleaning techniques. 2. Bad media. Replace the media. Try a new tape that is certified by the hardware manufacturer. 3. Tape driver. Load the appropriate Backup Exec tape driver. The latest Backup Exec tape drivers can be downloaded from the Symantec Technical Support web site at http://support.veritas.com/rd/bews-drivers.htm. 4. SCSI controller wide negotiation not configured properly. If the device is a wide (68 pin) SCSI device, then wide negotiation may and should be used. If the device is a narrow (50 pin) SCSI device, disable wide negotiation. Use the manufacturer's SCSI setup program to disable wide negotiation on the SCSI controller card. 5. SCSI controller transfer rate is too fast. Use the manufacturer's SCSI setup program to lower the SCSI transfer rate. Check with the controller and backup device manufacturer for the proper configuration for the SCSI transfer rate. 6. SCSI controller synchronous negotiation enabled. Use the manufacturer's SCSI setup program to disable synchronous negotiation on the SCSI controller card. Check with the controller and backup device manufacturer for the proper configuration for SCSI synchronous negotiation. 7. Incorrect termination or bad cables. Verify that the SCSI cable is good and that it is configured to provide proper SCSI termination. Do not mix passive and active termination. 8. Confirm that the tape drive is functioning properly. Check with the tape drive manufacturer for diagnostic software to test the condition of the tape drive hardware. 9. General SCSI problems. Isolate the tape drive on its own controller card. Why does my DLT tape drive hang when cataloging some tapes? The DLT tape drive maintains internal information about the tape on a tape directory track. The directory track is updated before the tape is ejected from the drive. If the drive is powered off without ejecting the tape first, this information is lost. Re-generating the tape directory information takes several hours to complete, which makes it seem like the drive is hung. Allow sufficient time for the operation to complete and then eject the tape. Normal operation will resume after the directory track has been updated.
622
Error Messages
A backup to my DLT tape drive is stuck at 99% complete. What should I do? The backup most likely fails to complete because the Eject media after job completes option is selected on tape drives that require you to manually remove the tape (such as Digital Linear Tape (DLT), Linear Tape-Open (LTO), Travan, and Onstream drives). To remedy this situation, either deselect the Eject media... option or using BEUTILITY, you can configure Backup Exec to set automatic responses to the media alert (see Editing Media Server Configurations on page 737). Related Topics: Configuring Devices on page 128 Error Messages on page 623 Improving Backup Exec Performance on page 626
Error Messages
Backup Exec generates an error message when a condition occurs that is important enough to warrant your attention, or requires that you submit a response. Most alerts and error messages are self explanatory, but there may be times when you need to get more information to resolve an error condition. There are two ways to get more information on Backup Exec error messages.
Look in the job log and follow the link for the Unique Message Identifier (UMI) error message Unique Message Identifier (UMI) Error Codes In Job Logs on page 432. Search the Symantec technical support knowledge base for the error. From the Help menu, click Symantec on the Web and then select Search Knowledge Base.
Related Topics: Error-Handling Rules on page 439 Hardware-related Questions on page 620.
Chapter 13, Troubleshooting
623
Backup Questions
Backup Questions
I am unable to back up certain files on my system that are being used by other processes. Why is that? When Backup Exec encounters a file that is in use by another process, it either skips the file or waits for the file to become available, depending on the Backup open files setting. When Backup Exec is configured to back up open files, it attempts to open the files in a different mode. It locks these files while they are being backed up to prevent other processes from writing to them. This mode should be a last resort to obtaining a backup of open files; in most circumstances, it is more desirable to close applications that leave files open so their files may be backed up in a consistent state. If you want to back up open files on Windows computers, Backup Execs Advanced Open File Option (sold separately) provides uninterrupted data protection for network environments. Why do Backup Execs consoles continue to own a storage device even when it's not running? Backup Exec is a true client/server application that must always be available to process jobs submitted from both local and remote administrative consoles. Because of the Advanced Device and Media Management functionality, all storage devices attached to the media server are claimed by Backup Exec whenever the server is running. The Advanced Device and Media Management feature in Backup Exec requires constant control of the storage devices in order to perform two important and useful operations: collection of statistics on media and device usage, and media overwrite protection. When performing a local backup, the total number of bytes backed up by Backup Exec does not match the number of bytes displayed by Windows. Why? This problem may be caused by the type of partition for which the system is formatted. If you have a Windows NTFS compressed partition, Backup Exec displays the uncompressed byte count of the files being backed up while Windows Explorer displays the compressed byte count of the files on the hard drive. For example, a NTFS partition that contains 1 GB of data is compressed by Windows to 500 MB. Backup Exec reports that 1 GB of data was backed up, even though Windows Explorer displays that only 500 MB of compressed data exists on the hard drive. If you have a FAT partition, Backup Exec reports the actual number of bytes of the files being backed up while File Manager reports an inflated amount of disk space. For example, a 2 GB FAT partition has a 32 K cluster size and File Manager displays 1.9 GB of used space. Backup Exec reports that 1.4 GB of data was backed up. Assuming that a 50 MB pagefile.sys is excluded from the backup, there is a 450 MB difference in the number of bytes.
Backup Questions
Converting to NTFS will regain disk space since it is more efficient and the default cluster size (automatically set by Windows) in NTFS is less than FAT. Windows allows you to specify a cluster size other than the default; however system performance may decrease. For more information, see the Windows documentation. The following tables display the cluster sizes for NTFS partitions.
NTFS Partition Cluster Sizes Partition Size (MB) <= 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 4 8 16 32
Related Topics: Backing Up Data on page 259 Hardware-related Questions on page 620. Improving Backup Exec Performance on page 626.
625
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 returns a default ACL (access control list) for FAT data; the stream of data is backed up (and the bytes are counted) but is discarded during a restore (and the bytes are not counted). Related Topics: Restoring Data on page 451 Hardware-related Questions on page 620.
Improving Backup Exec Performance

Many variables can affect throughput performance. These include:
Hardware
The speed of the disk controller and hardware errors caused by the disk drive, the tape drive, the disk controller, the SCSI bus, or the improper cabling/termination can slow performance. Confirm that the controller is rated for the tape backup hardware and that the SCSI Bios Settings are set properly. Newer models of SCSI Controllers are set to communicate with SCSI Hard Drives by default. Most tape drives can only handle a maximum sync transfer rate (bus speed) of between 3 to 22 MB/sec when utilizing hardware compression. Speed in excess of this will not only affect the ability for data to write to the tape in a continuous stream, but can also potentially damage the tape hardware. In addition, you should also make sure that:
Enable disconnect and enable Sync Negotiation is set to NO (in most cases). Initiate Wide Negotiation is set to Yes when the tape device is connected to a 68 pin wide SCSI Cable Connector. Tape drives are not connected to a SCSI Raid Controller.
626
Improving Backup Exec Performance
System
The capacity and speed of the media server performing the backup, or the remote system being backed up significantly impacts performance. System activity during backup also impacts performance. Fragmented disks take a longer time to back up. Heavily fragmented hard disks not only affect the rate at which data is written to tape, but also affect the overall system performance. Fragmented files take longer to back up because each segment of data is located at a different location on the disk, which causes the disk to take longer to access the data. Make sure you defragment disks on a regular basis.
Memory
The amount of available memory will impact backup speed. Insufficient memory, improper page file settings, and a lack of available free hard disk space will cause excessive paging and slow performance. The average file can potentially compress at a 2:1 ratio when hardware compression is used. Higher and lower compression occur depending on the type of files being backed up. Average compression can double the backup speed, while no compression runs the tape device at its rated speed. Image and picture files are fully compressed on disks. Therefore, no hardware compression takes place during the backup causing the tape drive to operate at its native (non-compression) rate of speed. Hardware compression is performed by the tape device and not the backup software.
File Types
Compression Successful compression can increase the tape drive's data transfer rate up to twice the native rate. Some tape drives use the Lempel-Ziv (LZ1) compression algorithm for its superior versatility and efficiency. Compression can be highly variable depending on your input data. Compression algorithms look for repeatable data patterns that can be compacted. Image files from a graphical program like Microsoft Paint, may compress at 4.5:1 or more, while binary files may compress at just 1.5:1. Data that has already been compressed or random data (such as encrypted data or MPEG files) may actually expand by about five percent if you attempt to compress it further. This can reduce drive throughput. Files The total number of files on a disk and the relative size of each file impacts backup performance. Fastest backups occur when the disk contains fewer large size files. Slowest backups occur when the disk contains thousands of small files. A large number of files located in the same directory path back up more efficiently than backing them up from multiple directory locations.
627
Contacting Technical Support
Block Size
Larger block sizes improve the compression ratio, which helps the drive to achieve better throughput and more tape capacity. Make sure that the block and buffer size are set properly. The throughput will increase in proportion to the compression achieved, until the drive's maximum throughput is reached. Symantec does not recommend increasing the Block Size above the default settings. The backup speed for a remote disk is limited by the speed of the physical connection. The rate at which a remote server's hard disks are able to be backed up depends on:

Network
The make/model of network cards. The mode/frame type configuration for the adapter. The connectivity equipment (hubs, switches, routers, and so on). Windows Settings.
Local disk drives on the media server can usually be backed up at a higher rate of speed than backing up remote servers across a network.
Related Topics: Backing Up Data on page 259

If you have tried everything you can to solve a problem, but still need a resolution, you can contact Technical Support by phone (see Before Calling Technical Support on page 628) or via the internet with Symantec DirectAssist (see Using Symantec DirectAssist for Troubleshooting on page 633).
Before Calling Technical Support

To expedite the Technical Support process:
Know your Backup Exec version and revision number (see Finding Version and Revision Information for Your Backup Exec Installation on page 629) Use one of the diagnostic utilities (see Locally, the version and build information can be located by selecting the About Backup Exec option from the Help menu. on page 629) included with Backup Exec to collect information that technical support can use to diagnose your issue.
628
Finding Version and Revision Information for Your Backup Exec Installation
Locally, the version and build information can be located by selecting the About Backup Exec option from the Help menu.
Backup Exec Diagnostic Utilities

Backup Exec includes two utilities for compiling and gathering diagnostic information that can help you, and if necessary technical support, troubleshoot issues with your Backup Exec installation.
BEDiag.EXE generates a comprehensive diagnostic file that contains specific environmental information such as service information, registry settings, user privileges, and file versions. This diagnostic file can be used in conjunction with many Symantec Backup Exec knowledgebase articles to resolve your issue more quickly. Running BEDIAG.EXE to Generate a Diagnostic File for Troubleshooting on page 629 BEGather.exe captures the most common diagnostic and historical files necessary for troubleshooting purposes. By default BEGather will find Windows Event Logs, Backup Exec Installation logs, Backup Exec internal application logs, and when present, BEGather also executes BEDIAG. These files can then be used either by you or Symantec Technical support to resolve your issue more quickly. . See Running BEGather to Collect Log File Information for Troubleshooting on page 632.
Running BEDIAG.EXE to Generate a Diagnostic File for Troubleshooting

Backup Exec includes a diagnostic application (BEDIAG.EXE) that gathers information about a Windows XP, Windows 2000, or Windows Server 2003 computer for troubleshooting purposes. You can run it from the media server, or from a remote computer (see Running BEDiag on a Remote Computer on page 631). This application can be run from within Backup Exec, or it can be run from a command line. The BEDIAG command line utility is located in the Backup Exec for Windows Servers directory on your hard drive (by default, \Program Files\VERITAS\Backup Exec\NT). The type of information collected in the bediag.txt file includes:

Account groups, account privileges and environment settings. Backup Exec software version and registry information, Backup Exec Agent listing, Windows version information, SCSI hardware configuration, SQL Server information, Driver services information and Windows Services information. Server information, supported shared directories and Windows sockets information.
629
Note You can also run BE Diagnostics for a remote server (see Running BEDiag on a Remote Computer on page 631) To create a BEDIAG.TXT from within Backup Exec: 1. Start Backup Exec. 2. On the Tools menu, select Backup Exec Diagnostics. Note You can also create a BEDIAG.TXT file from the Device view. On the navigation bar, click Devices. Select the media server. On the Task pane, under General Tasks, click Properties. Then select the System tab. 3. Click Run Diagnostics. The BEDiag text file will appear. From a command line prompt on the media server: 1. Launch the command prompt. 2. From the directory ...\Backup Exec\NT\", type bediag servername (the server can be the local media server or a remote server. If you are running this from a workstation, type bediag workstationname). 3. The file BEDIAG.TXT will be created in the directory containing BEDIAG.EXE (by default ...\Backup Exec\NT\). 4. The following switches can be used with the command line option (bediag [switches] servername):
Switch /a /b:[server] /c /app /sys
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
630
Switch /bex /err /recs:n
Meaning Dump only Backup Exec entries in the Application Event log Dump only error events from any event log Dumps only newest n records from given event logs ***The bex, err and recs switches must be used in conjunction with the app and/or sys switches
/o:[file]
Specifies output job log for append ***Omitting [file] will send output to the screen
/h /l /n /p /q /s /u /v /w /x /?
Dump SCSI hardware subkey from registry Dump Lotus Notes information Dump Windows Socket Network Protocols Dump user privileges Dump Microsoft SQL Server information Dump information on Services Dump Microsoft update information. Dump Server Information Dump Windows version information Dump Microsoft Exchange Server Information Display usage information
Running BEDiag on a Remote Computer You can run diagnostics on a remote media server provided:

Backup Exec is installed on the remote server. Backup Exec services are running.
631
To run BE diagnostics on a remote media server: 1. On the Tools menu, click Backup Exec Diagnostics. 2. Click Select Server and select the remote media server on which you want to run the diagnostic utility. 3. Enter the logon credentials for this remote system. 4. Click Run Diagnostics. Diagnostic information appears in a .TXT file. To print this information, on the File menu select Print.
Running BEGather to Collect Log File Information for Troubleshooting

When troubleshooting an issue with Backup Exec, it may be necessary to review diagnostic logs from the media server. The BEGather utility (BEGather.exe) simplifies this process by creating and compiling a compressed file that includes various system log files that can be sent to technical support. You can run BEGather locally, or you can copy it to another computer. Note To generate specific log file information or to get log file information for remote machines, use BEDiag.exe Running BEDIAG.EXE to Generate a Diagnostic File for Troubleshooting. To use BEGather: 1. From the Backup Exec installation directory double-click BEGather.exe. 2. Select all of the options in the Data to gather field. 3. Enter your case number (if you have one) with the dashes (example 123-346-789). 4. Make sure that Open output directory after gather completes is selected. 5. Click Gather. After BEGather collects all of the log file information, a window containing all of the data collected by the utility opens. The files gathered contain detailed information regarding installation, diagnostics, and error reporting. Reviewing these logs prior to contacting technical support can reveal the source of the issue. If the solution is
632
not evident based on the gathered logs, please have these logs available when contacting support. The support technician may request an e-mail containing the log files.
Using Symantec DirectAssist for Troubleshooting

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

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.
635
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. Related Topics: Requirements for Running the Backup Exec Windows 98/Me Agent on page 636 Installing the Backup Exec Windows 98/Me Agent on the Workstation on page 637 Configuring the Backup Exec Windows 98/Me Agent on page 637 Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent on page 639 Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent on page 641
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.
636
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. 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.
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, click Start and then click Settings. Click Control Panel and then double-click Network. 2. Click the Configuration tab. 3. In the list of installed network components, double-click Backup Exec Agent.
Chapter 14, Symantec Backup Exec - Workstation Agents
637

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 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. For Backup Exec 9.x and later, to access the workstation, you must create a Backup Exec logon account that uses the same password as the one entered here. The logon account user name is ignored. Add this logon account as the resource credential for the workstation. For more information, see Configuring Logon Accounts on page 386 and Changing and Testing Logon Accounts for Resources on page 292. For problems encountered when passwords are changed, see Troubleshooting Workstation Agents on page 656. Action
Computer Name
Password
638
The Backup Exec Windows 98 and Windows Me Agents Backup Exec Agent Publisher Properties (continued) Option Current Status Action 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.
Registry Allow Registry to be restored 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. Enables the workstations Windows 98/Me registry to be restored.
Add
Remove
Details
Related Topics: Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent on page 639 Configuring the Network Protocol for the Backup Exec Windows 98/Me Agent on page 641
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.
639
To publish drives and directories using the Windows 98/Me Agent: 1. For Windows 98 or Windows Me, click Start and then click Settings. Click Control Panel and then double-click Network. 2. Click the Configuration tab. 3. In the list of installed network components, double-click Backup Exec Agent. 4. At the bottom of the General tab, click Details. 5. Select the appropriate options as follows:
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)
6. 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.
640
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, click Start and then click Settings. Click Control Panel and then double-click Network. 2. Click the Configuration tab.
641
The Backup Exec Macintosh Agent
3. In the list of installed network components, double-click Backup Exec Agent. 4. Click the Protocol tab. 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
Configured Media Servers
6. If you select TCP/IP, click Add. 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. Related Topics: Understanding Backup Methods and Their Advantages on page 354
Installing and Configuring the Macintosh Agent on a Mac OS X Computer on page 643 Requirements for Running the Backup Exec Macintosh Agent on page 643
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.
Installing and Configuring the Macintosh Agent on a Mac OS X Computer

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.
643
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 648 and then continue with step 10 in this section.
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>.
644
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. For Backup Exec 9.x and later, to access the workstation you must create a Backup Exec logon account that uses the same password as the one entered here. The logon account user name is ignored. Add this logon account as the resource credential for the workstation. For more information, see Configuring Logon Accounts on page 386 and Changing and Testing Logon Accounts for Resources on page 292. For problems encountered when passwords are changed, see Troubleshooting Workstation Agents on page 656. 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
Chapter 14, Symantec Backup Exec - Workstation Agents 645
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. 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. 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.
646
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.
647
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. Related Topics: Publishing Drives and Directories Using the Backup Exec Windows 98/Me Agent on page 639
648
About the Backup Exec 8.x and 9.x Agent for Unix
The Backup Exec 8.X and 9.x Agent for Unix 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 8.x and 9.x Agent for Unix, Backup Exec allows you to protect data using multiple backup types. These include:

Full - Back up files - Allow incrementals and differentials using modified time Differential - Using modified time Incremental - Using modified time Working set - Back up files - Changed today
Related Topics: Understanding Backup Methods and Their Advantages on page 354 Requirements for Running the Backup Exec 8.x and 9.x Agent for Unix on page 649 Installing the Backup Exec 8.x and 9.x Agent for Unix on the Workstation on page 650 Configuring the Backup Exec 8.x and 9.x Agent for Unix on page 653
Requirements for Running the Backup Exec 8.x and 9.x Agent for Unix

You must have root privileges on the UNIX computer to install the UNIX agent. 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.
649
Installing the Backup Exec 8.x and 9.x Agent for Unix on the Workstation
When you install the Backup Exec 8.x and 9.x Agent for Unix, you are prompted to configure it as well. The agent configuration information is saved to a text file called agent.cfg that you can edit to change any configuration options. Before installing the Backup Exec 8.x and 9.x Agent for Unix on a system using a network name service (for example NIS), you must modify the 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 8.x and 9.x Agent for Unix 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 8.x and 9.x Agent for Unix is then installed by using ftp to push the agent files from the server to the workstation. Installing the Backup Exec 8.x and 9.x Agent for Unix from the Server: 1. Log on as root on the media server, and put the Backup Exec installation CD in the servers CD-ROM drive. 2. Transfer the file be_agent.tar to the Linux or UNIX workstation. Transfer methods include FTP, NFS, SAMBA, and SCP. See your system administrator for transfer details.
650
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 8.x and 9.x Agent for Unix. 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 8.x and 9.x Agent for Unix 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 8.x and 9.x Agents for Unix. 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.
651
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 8.x and 9.x Agent for Unix 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. 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.
652
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 8.x and 9.x Agent for Unix 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 8.x and 9.x Agent for Unix
To configure the Backup Exec 8.x and 9.x Agent for Unix, 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 name <workstation name> Description 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.
653
About the Backup Exec 8.x and 9.x Agent for Unix Agent.cfg Commands (continued) Item password <passwd> Description 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. For Backup Exec 9.x and later, to access the workstation, you must create a Backup Exec logon account that uses the same password as the one entered here. The logon account user name is ignored. Add this logon account as the resource credential for the workstation. For more information, see Configuring Logon Accounts on page 386 and Changing and Testing Logon Accounts for Resources on page 292. For problems encountered when passwords are changed, see Troubleshooting Workstation Agents on page 656. export 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]
654
About the Backup Exec 8.x and 9.x Agent for Unix Agent.cfg Commands (continued) Item tell <machine name> Description 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. 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.
tell_interval <number_of_seconds>
follow_symdirs
exclude_file <filename>
exclude_dir <directory path>
preserve_ctime
655
Loading the Backup Exec 8.x and 9.x Agent for Unix
Loading the Backup Exec 8.x and 9.x Agent for Unix
Load the Backup Exec 8.x and 9.x Agent for Unix using the following command: /etc/bkupexec/./agent.be & Note If the agent.cfg file is not located in the default Backup Exec 8.x And 9.x Agent for Unix installation directory, use the -c parameter in conjunction with a path to the location of the agent.cfg file when loading the agent. For example, /etc/bkupexec/./agent.be -c <path_location_of_agent.cfg> &
Troubleshooting Workstation Agents

If the password for a published directory in a workstation is changed, jobs to back up that published directory cannot access it. Additionally, the Change option on the Resource Credentials dialog box is unavailable. If you encounter this problem, do any of the following:
Modify the job by clearing the selection of the specified published directory, and then reselecting it. You are prompted for new credentials. Update the corresponding logon account credentials stored in Backup Exec with the new password for the published directory. At the workstation, disable access to published directories that use passwords and configure the workstation itself to require password authentication.
656
Chapter
15
Using Symantec Backup Exec with Server Clusters

In a server cluster, Backup Exec can protect data on local disks and shared disks, as well as protect Microsoft SQL and Exchange databases that are configured as virtual server applications; that is, they contain an IP address resource, a Network Name resource, and are displayed on the network with a unique server name (the virtual server name). Clustered servers provide high availability of applications and data to users. In a clustered server, several servers (called nodes) are linked in a network, and run cluster software that allows each node access to the shared disks. If a node becomes unavailable, cluster resources migrate to an available node (called failover). The shared disks and the virtual server are kept available. During failover, users experience only a short interruption in service. Note When performing an offhost backup in a Microsoft Cluster Server (MSCS) or VERITAS Cluster Services environment, the media server and the remote computer must not be in the same cluster group. The cluster applications cannot support devices logical unit numbers (LUNs) that have duplicate signatures and partition layouts, therefore, the snapshots containing the LUNs must be transported to a host, or remote computer, that is outside the cluster. Related Topics: Installing Backup Exec on a Microsoft Cluster Server on page 660 Configurations for Backup Exec and Microsoft Cluster Servers on page 670 Backing Up Microsoft Cluster Servers on page 680 Restoring Data to a Microsoft Cluster on page 684 Requirements for Installing Backup Exec on a Microsoft Cluster Server on page 659 Disaster Recovery of a Cluster on page 697 Installing Backup Exec on a VERITAS Cluster Server on page 691
657
How Backup Exec Works in a Microsoft Cluster Server
Backing Up VERITAS Cluster Servers on page 692 Restoring Data to VERITAS Cluster Servers on page 696
How Backup Exec Works in a Microsoft Cluster Server

When you install Backup Exec into a Microsoft Cluster Server (MSCS) environment, you install it as a virtual server application. You assign an IP address resource, a Network Name resource (the virtual server name), and a disk resource to Backup Exec. When a failover occurs, backup jobs that were running are rescheduled. The Backup Exec services are restarted on a designated failover node, and the backup jobs are restarted by default. Backup Exec provides an additional rule for cluster failover restart called Checkpoint Restart. A checkpoint restart option allows backup jobs to continue from the point at which the jobs were interrupted rather than starting the backup over again, making the backups faster and requiring fewer media. If the rule to retry jobs on a cluster failover is enabled, then an additional option can be specified to do a checkpoint restart when retrying the job. Checkpoint Restart is the only property available for the Cluster Failover Rule. You can change the default so that jobs are not restarted, and you can specify a different failover node if you add a new failover node. When the failed server comes back online, MSCS can automatically rebalance the workload in a cluster, called failback, by moving cluster groups back to the server that has rejoined the cluster. However, by design, Backup Exec does not failback. The backup jobs will continue to run on the designated failover node. By continuing to run backup jobs on the designated failover node, any further risk of having to restart the jobs again when the failed server rejoins the cluster is avoided. Then, when it is convenient, you can move the Backup Exec cluster group back to the controlling node. Specific details of how Backup Exec runs in a cluster vary depending on the configuration you use in the cluster. Related Topics: Configurations for Backup Exec and Microsoft Cluster Servers on page 670 Installing Backup Exec on a Microsoft Cluster Server on page 660
658
Requirements for Installing Backup Exec on a Microsoft Cluster Server
Requirements for Installing Backup Exec on a Microsoft Cluster Server
Two-node clusters are supported with Backup Exec for Windows Servers on Microsoft Windows 2000 Advanced Server, Windows Server 2003 Enterprise, Microsoft Windows 2000 DataCenter, and Windows Server 2003 DataCenter. Four-node clusters are supported with Backup Exec for Windows Servers on Microsoft Windows 2000 DataCenter, Windows Server 2003 Enterprise, and Windows 2003 DataCenter. Up to eight-node clusters are supported with Backup Exec for Windows Servers on Microsoft Windows Server 2003 DataCenter. Backup Exec clusters can be installed on a Windows Server 2003 majority node configuration. However, there must be a shared disk in the configuration in order for Backup Exec to share its database files between nodes. In this type of configuration, if the majority of the cluster nodes fail, then the entire cluster will fail. This configuration normally uses more than two nodes in the cluster configuration. The controlling node and designated failover nodes must be online during installation of Backup Exec into the cluster. A unique IP address and a unique network name for the Backup Exec virtual server is required during installation. During installation of a Backup Exec cluster, the node that runs the installation should own the shared disk. If you use a physical disk resource that belongs to another application, the Backup Exec Cluster Wizard will move all the resources that belong to the other application into the Backup Exec group. It is recommended that Backup Exec not be installed on the cluster quorum. An individually licensed copy of Backup Exec for Windows Servers, as well as any applicable agents and options, is required for each active node in the cluster as defined in the End User License Agreement. When installing an evaluation version of Backup Exec, a cluster environment is automatically detected and serial numbers are not required. When you install Backup Exec clusters in a SAN SSO configuration, all Backup Exec installations must have the same server configuration. Either all nodes should be database servers or all nodes should be secondary member servers connecting to the same primary. All Backup Exec installations into a cluster must either be part of a single cluster group, or be locally installed on each node. If cluster-aware Backup Exec is installed in a cluster as well as a locally installed version of Backup Exec (not cluster-aware), then you cannot log on to the locally installed Backup Exec media server. You can
Chapter 15, Using Symantec Backup Exec with Server Clusters
659
Installing Backup Exec on a Microsoft Cluster Server
only log on using the Backup Exec virtual server name. To be able to log on to the locally installed Backup Exec media server, you must first use the Cluster Configuration Wizard to uninstall cluster-aware Backup Exec from all the nodes in the cluster.
Use the same account for Backup Exec services on all nodes in the cluster. If nodes in a cluster use Backup Exec and have different accounts, change the services to use the same account.
Related Topics: Installing Backup Exec on a Microsoft Cluster Server on page 660 Configurations for Backup Exec and Microsoft Cluster Servers on page 670

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 688. 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 Computers on page 793. 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.
660
Note On the Virtual Server Information screen, Backup Exec automatically displays a default name called BACKUPEXECVRS for the virtual server. Type a new default name if you do not want to use the default. 5. When the Cluster Configuration Wizard completes, create a device pool that contains all the locally attached storage devices on each node to be used when failover occurs. This ensures that jobs can be run on the storage devices that are attached to the failover nodes. For more information, see Creating Device Pools for Microsoft Cluster Servers on page 664. Related Topics: Creating Device Pools for Microsoft Cluster Servers on page 664 Enabling or Disabling Checkpoint Restart on page 667 Configurations for Backup Exec and Microsoft Cluster Servers on page 670 Specifying a Different Failover Node on page 668
Upgrading Backup Exec on a Microsoft Cluster

You can upgrade Backup Exec 9.0.4454 and above on the nodes in a cluster without taking the nodes out of the cluster. Note If you upgrade Backup Exec 8.x you must uninstall the secondary node and then upgrade the primary node before installing Backup Exec on other nodes. You can then run the Backup Exec Cluster Configuration Wizard to cluster all the nodes. To upgrade Backup Exec 8.x and 9.0 on a cluster: 1. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard to uncluster the Backup Exec. 2. Upgrade all the nodes with the options. 3. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard to recluster the Backup Exec nodes. Note Run the option from the same node that was used to uncluster Backup Exec. 4. Repeat step 3 for each node in the cluster.
661
To upgrade Backup Exec 9.0.4454 and above on a cluster: 1. Select a node to upgrade and make that node the active Backup Exec cluster node. 2. Run the Backup Exec installation program on the active node. 3. Move the cluster group to the next node you want to upgrade, and then run the Backup Exec installation program on that node. 4. Repeat step 3 for each node in the cluster. Related Topics: Installing Backup Exec on page 65
Installing Additional Backup Exec Options on a Microsoft Cluster

Install additional Backup Exec options on each node of the cluster. For details on installing each option, see the appropriate section in this guide, or in online Help. Note If you are using the Advanced Open File Option, set those defaults on each physical node the option is installed on, not on the virtual server. Because the default settings for the static volume can be different on each node, Advanced Open File Option defaults do not fail over. To install additional Backup Exec options: 1. On the controlling node, make sure the Backup Exec group is online before you start installing additional options. 2. Follow the instructions in Installing Backup Exec Options to the Local Computer on page 71. 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 1307 and Installing the Backup Exec R/3 Agent on page 1350.
662
Uninstalling Backup Exec From a Microsoft Cluster

To uninstall Backup Exec from a cluster: 1. From the Tools menu, point to Wizards, and then click Cluster Configuration Wizard. 2. Use the wizard to remove cluster-aware Backup Exec from all selected servers. When unclustering the active node, you can either leave the Backup Exec data on the shared drive or delete it. If you delete the data, you can make the data available on the active node. 3. Uninstall Backup Exec from all the nodes. 4. After Backup Exec has been uninstalled, move any resource disks from the Backup Exec cluster group to another group, and then delete the Backup Exec cluster group. 5. On any node, click Start, point to Settings, and then click Control Panel to uninstall Backup Exec. 6. Double-click Add/Remove Programs, and then in the list of currently installed programs, select Symantec Backup Exec for Windows Servers and click Change/Remove. Repeat 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
663
Creating Device Pools for Microsoft Cluster Servers
Creating Device Pools for Microsoft Cluster Servers

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

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

NTFS GRFS Exchange mailboxes and public folders Exchange 2000 and 2003 IS with multiple storage groups SQL database non-snapshot backups System State Lotus Domino Exchange 5.5 IS and DS Exchange 2000 and 2003 IS with one storage group GRFS Oracle NTFS Image sets NTFS Snapped volumes SQL database snapshot backups SQL transaction log backups NetWare SMS (the checkpoint restart option should be disabled for NetWare backups using the Remote Agent) The Advanced Open File Option. The offhost backup feature in the Advanced Disk-based Backup Option. When the option Collect additional information for synthetic backups is selected for the synthetic backup feature in the Advanced Disk-based Backup Option. Incremental backups based on the archive bit.
The following types of files cannot use checkpoint restart:

Checkpoint restart is not supported by the following:

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

To apply checkpoint restart to backup jobs, make sure that the Error-Handling Rule for Cluster Failover is enabled. See Error-Handling Rules on page 439. 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). 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 Error-Handling rdules. 5. Select the Cluster Failover rule, and then click Edit. 6. Verify that the Enabled field is selected.
667
Specifying a Different Failover Node
Specifying a Different Failover Node

You can:

Change the order in which the nodes fail over. Add a failover node to the cluster. Remove a failover node from the cluster.
To change the order in which nodes fail over:
By default, in a 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.
To add or remove a failover node: Before you add a node to the Backup Exec cluster configuration, you must install Backup Exec on it. Cluster services for a node should be online before you add or remove it from the cluster. If you are removing a node, do not run the cluster configuration wizard from the node you want to remove. 1. On the controlling node, on the Tools menu, point to Wizards. 2. Click Cluster Configuration Wizard. 3. Follow the instructions on the screen to add or remove a node. 4. If you have added a failover node, also add any locally attached storage devices that are to be used when failover occurs to the cluster device pool. This ensures that jobs can be run on the storage devices that are attached to the failover nodes. If you remove some, but not all, nodes in a cluster, an uninstall of Backup Exec results in a password being requested for the virtual server and the services continuing to run. You must remove Backup Exec from all nodes on the cluster, following the procedures detailed in Uninstalling Backup Exec From a Microsoft Cluster on page 663. Related Topics: Creating Device Pools for Microsoft Cluster Servers on page 664 Specifying a Different Failover Node on page 668 Configurations for Backup Exec and Microsoft Cluster Servers on page 670
668
Designating a New SAN SSO Primary Server and Central Administration Server in a Microsoft Cluster Server
Designating a New SAN SSO Primary Server and Central Administration Server in a Microsoft Cluster Server
To designate a new primary SAN Shared Storage Option server or central administration server for a cluster environment, use BEUtility.exe. BEUtility enables you to do various types of configuration and maintenance operations on your Backup Exec for Windows Servers media servers. For more information, see Backup Exec Utility on page 717. Note In a cluster environment, do not use Change Service Account in BEUtility.exe. To change a Backup Exec Cluster server from a Database Server to a Member Server: 1. Install the new server as a secondary server with the Library Expansion Option and SAN Shared Storage Option installed. Make sure connections to the Backup Exec cluster and other member servers are working properly. 2. Using the cluster administrator, shut down the Backup Exec cluster services. Be sure to keep the Disk resource online. 3. Move the catalog files from the Backup Exec cluster installation path to the respective installation paths on the new database server. 4. Use BEUtility.exe to connect all Backup Exec servers to the new database server and to start all Backup Exec services. 5. Stop and restart the Backup Exec Services on the new database server. 6. Using the Cluster Administrator, move the Backup Exec resource group to the failover node and make sure services start on that node. 7. Use BEUtility.exe to stop and restart the Backup Exec Services on all the member servers of the SAN in order for them to connect to the new database server. To change a Backup Exec Cluster server from a central administration server to a managed media server: 1. Install the new server as a managed media server. Make sure connections to the Backup Exec cluster and other managed media servers are working properly.
669
Configurations for Backup Exec and Microsoft Cluster Servers
2. Using the cluster administrator, shut down the Backup Exec cluster services. Be sure to keep the Disk resource online. 3. Move the catalog files from the Backup Exec cluster installation path to the respective installation paths on the new central administration server. 4. Use BEUtility.exe to connect all Backup Exec servers to the new central administration server and to start all Backup Exec services. 5. Stop and restart the Backup Exec Services on the central administration server. 6. Using the Cluster Administrator, move the Backup Exec resource group to the failover node and make sure services start on that node. 7. Use BEUtility.exe to stop and restart the Backup Exec Services on all the managed media servers in order for them to connect to the new central administration server. Related Topics: Multi-node Clusters on a Fibre Channel SAN with the SAN SSO on page 675

Backup Exec supports various cluster configurations of between two and eight nodes on a fibre channel SAN, with locally attached storage devices, or with storage devices on a shared SCSI bus. You can use any combination of these configurations. Note If you install the cluster on a private network, use the Cluster Administrator to enable public communication if necessary. If you are using a cluster on a fibre channel SAN or with storage devices on a shared SCSI bus and failover occurs, depending on the capability of your various SAN components, media might be orphaned in the tape drive until the failed node becomes active again. If end-of-job markers were not written to the media before the failover occurred, the media may be marked as unappendable by the Backup Exec engine when the next append backup job is run. The media remains unappendable until it is overwritten (or erased, or the retention period expires, etc.). If the storage device is a robotic library, you can review the Robotic Library Inventory report to discover if the media was marked unappendable by the Backup Exec engine. If the Full column reports a 3, the Backup Exec engine has marked the media as unappendable.
To add or remove hot-swappable devices in a cluster, run the Hot-swap Device Wizard on all Backup Exec Cluster nodes. If a server is not updated to recognize a new device, any job that is targeted to that device may fail. For more information about hot-swapping devices, see Hot Swap for Storage Devices on page 128. See the following for examples of various cluster configurations: Two-node Cluster with Locally Attached Storage Devices on page 671 Two-node Cluster with Tape Devices on a Shared SCSI Bus on page 672 Multi-node Clusters on a Fibre Channel SAN with the SAN SSO on page 675
Two-node Cluster with Locally Attached Storage Devices

In this configuration, cluster-aware Backup Exec is installed on the controlling node, failover occurs to designated nodes in the cluster, and storage devices are locally attached to each node. Each nodes locally attached storage devices are automatically assigned to the All Devices (<Node Name>) device pool, which is also the default destination device on that node when you create backup or restore jobs. You must create a device pool that includes storage devices on the controlling node and on each failover node in order for jobs to run when failover occurs. For more information, see Creating Device Pools for Microsoft Cluster Servers on page 664. To restore data in this configuration, move media to the failover nodes locally attached storage device and reinventory before starting a restore operation.
Two-node Cluster with Locally Attached Storage Devices Backup Exec Virtual Server Controlling node Locally attached storage devices
Failover node Shared SCSI Bus for disks Heartbeat LAN Locally attached storage devices
Related Topics: Multi-node Clusters on a Fibre Channel SAN with the SAN SSO on page 675
671
Two-node Cluster with Tape Devices on a Shared SCSI Bus

In this configuration, cluster-aware Backup Exec is installed on the controlling node, failover occurs to designated nodes in the cluster, and tape devices are attached to a shared SCSI bus that is separate from any shared SCSI bus for disks. Because each node creates a unique tape device name for the same device, if the drive is not serialized, this configuration requires you to create a device pool that includes the tape device name used by each node in order for jobs to run when failover occurs. For more information, see Creating Device Pools for Microsoft Cluster Servers on page 664. 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 673.
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
Related Topics: Multi-node Clusters on a Fibre Channel SAN with the SAN SSO on page 675
672
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 672, 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 673, and the tape device has internal termination, you can use the devices internal termination to terminate the bus.
Example of a shared bus with tape devices at the end of the bus Backup Exec Virtual Server Controlling node Shared SCSI bus for disks Shared SCSI bus for tape devices Heartbeat LAN Failover node
Following are methods you can use to terminate a bus:
SCSI adapters. This method is not recommended because if the server is disconnected from the shared bus, or if there is a power supply failure, the bus may not be properly terminated and may be inoperable.
673
Pass-through (or feed-through) SCSI terminators. These can be used with SCSI adapters and with some tape devices. If the tape device is at the end of the bus, you can attach a pass-through SCSI terminator to terminate the bus. The internal terminators in the tape device must be disabled. This is a recommended method. To ensure termination if a power supply failure occurs, turn off the on-board terminators on the SCSI controller (using the host adapter manufacturers recommended method) and physically terminate the controller with a terminator. Y cables. These can be used with some tape devices. If the tape device is at the end of the bus, you can attach a terminator to one branch of a Y cable to terminate the bus. The internal terminators in the tape device must be disabled. This is a recommended method. Trilink connectors. These can be used with some tape devices. If the tape device is at the end of the bus, you can attach a terminator to one of the trilink connectors to terminate the bus. The internal terminators in the tape device must be disabled. This is a recommended method.
Tip
Besides terminating the bus, Y-cables and trilink connectors also allow you to isolate the devices from the shared bus without affecting the bus termination. You can maintain or remove that device without affecting the other devices on the shared SCSI bus. To configure a shared SCSI bus for tape devices: 1. Install the SCSI controllers for the shared SCSI bus. Make sure that the SCSI controllers for the shared SCSI bus are using different SCSI IDs. For example, on the controlling node, set the SCSI controller ID to 6 and on the failover node, set the SCSI controller ID to 7. 2. Prepare the SCSI controllers for the shared SCSI bus. Refer to your SCSI host adapter manufacturers documentation for details. Note Do not have power on to both nodes while configuring the computers, or if both nodes have power on, do not connect the shared SCSI buses to both nodes. 3. Connect the shared SCSI tape devices to the cable, connect the cable to both nodes, and then terminate the bus segment using one of the methods discussed in the previous section. Related Topics: Two-node Cluster with Tape Devices on a Shared SCSI Bus on page 672
674
Multi-node Clusters on a Fibre Channel SAN with the SAN SSO

In this configuration, one or more clusters are attached to a fibre channel storage area network (SAN), with cluster-aware Backup Exec and the SAN Shared Storage Option (SAN SSO) installed on the controlling node in each cluster. Shared secondary storage devices are attached to the fibre channel, although a single storage device can be shared between one or more clusters. Failover occurs (in alphabetical order of the machine name) to other designated nodes in the cluster. Note When using multiple clusters in a SAN SSO environment, it is strongly recommended that the cluster nodes be connected to the storage devices using a fibre switch. If you use a hub rather than a fibre switch, the hub will receive a reset command during a failover event that causes all other components attached to the hub to be disconnected. You can designate any server on the fibre channel SAN as the Shared Storage Option Database server. You should create a failover device pool for the cluster. For details about creating a failover device pool, see Creating Device Pools for Microsoft Cluster Servers on page 664. This configuration offers increased performance since backups are performed locally instead of over a network. Additionally, centralized media catalogs are available. Because the SAN SSO uses a shared catalog database, a tape that has already been cataloged can be physically moved from one device to another and not have to be recataloged. Tip The SAN SSO option must be installed on each failover node, with the same settings that were used on the primary node. Either all nodes should be database servers or all nodes should be secondary member servers.
Following are examples of multi-node clusters:
675
Configurations for Backup Exec and Microsoft Cluster Servers Two 2-node Clusters on a Fibre Channel SAN with the SAN SSO
Fibre Channel SAN Secondary Storage Devices
Secondary server
Backup Exec Virtual Server A Controlling node Shared SCSI Busfor disks Failover Heartbeat node
Backup Exec Virtual Server B Shared SCSI Bus for disks Controlling node Heartbeat
Failover node
LAN
676
Configurations for Backup Exec and Microsoft Cluster Servers Four-node Cluster on Fibre Channel SAN with the SAN SSO Secondary server Fibre Channel SAN Shared Drives Secondary Storage Devices Backup Exec Virtual Server Controlling node
Failover nodes
Heartbeat
LAN
For details on installing the SAN SSO, see Installing the SAN Shared Storage Option on page 960. Related Topics: Designating a New SAN SSO Primary Server and Central Administration Server in a Microsoft Cluster Server on page 669
677
Using the Central Admin Server Option with Microsoft Clusters and SAN SSO
Managed media servers can be clustered, however, it is not recommended because the central administration server recovers all failed jobs in a distributed job environment. The following configurations can be used when installing Backup Exec clusters with the Central Admin Server Option (CASO) and SAN SSO.

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

To protect all data in the cluster, including file shares, databases, and the cluster quorum, back up the following:
Local disks and System State on each node. The cluster quorum, which contains recovery information for the cluster and information about changes to the cluster configuration, is included in the System State backup. For more information, see Backing Up Local Disks in a Microsoft Cluster on page 682. All shared disks, including the data in the Microsoft Cluster Server folder on the Quorum disk. For more information, see Backing Up Shared Disks in a Microsoft Cluster on page 682. Virtual servers, which may contain data or contain applications such as Microsoft SQL Server or Exchange Server. Use Backup Exec database agents to back up databases. For more information, see Backing Up Database Files in a Microsoft Cluster on page 683.
For details on setting up and running backup operations, see Creating a Backup Job on page 261. Note When performing an offhost backup, the media server and the remote computer must not be in the same cluster group. The cluster applications cannot support devices logical unit numbers (LUNs) that have duplicate signatures and partition layouts, therefore, the snapshots containing the LUNs must be transported to a host, or remote computer, that is outside the cluster. The Command Line Applet can be used with Backup Exec when Backup Exec is installed in a cluster. The only limitation is that you cannot use the Command Line Applet to specify a device for backup. You can use the Command Line Applet to target a device pool, but not a specific device in that pool. Related Topics: Backing Up Local Disks in a Microsoft Cluster on page 682 Backing Up Shared Disks in a Microsoft Cluster on page 682 Backing Up Database Files in a Microsoft Cluster on page 683 Backing Up Windows 2000 and Windows Server 2003 Features in a Microsoft Cluster on page 681
680
Backing Up Windows 2000 and Windows Server 2003 Features in a Microsoft Cluster
You must purchase and install the Backup Exec Remote Agent for Windows Servers on all remote Windows 2000 and Windows Server 2003 computers that you want backed up. Without the Remote Agent, the following Windows 2000 and 2003 features cannot be correctly backed up:

Encrypted files SIS files Disk quota data Removable Storage data Remote Storage data Mount points Sparse files Windows Management Instrumentation Terminal Services System State data, including:

COM+ Class Registration database Boot and system files Registry Certificate Services database (if the server is operating as a certificate server) Active Directory (if the server is a domain controller) SYSVOL (if the server is a domain controller) Cluster quorum (if the server is part of a cluster)
Note You can select System State or Shadow Copy Components for backup on a remote computer only when the Remote Agent is installed on the remote computer. Related Topics: Restoring Windows 2000 and Windows Server 2003 Features to a Microsoft Cluster on page 684
681
Backing Up Local Disks in a Microsoft Cluster

Select local disks for backup from the physical node to which they are attached. To back up local disks in a Microsoft cluster: 1. 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 284. When making backup selections for nodes running Windows Server 2003, select
Shadow Copy Components, which include System State. For more information, see Protecting Windows Server 2003 Systems on page 344.
3. Continue with the full backup procedure as usual. For more information, see Creating a Backup Job on page 261. Tip If you created a device pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs.
Backing Up Shared Disks in a Microsoft Cluster

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

Select database files for back up from a database icon on a virtual server. If a virtual server contains a database application such as Microsoft SQL Server or Exchange Server, use the appropriate Backup Exec database agent to perform the backup operations; otherwise, only the file system is backed up, not the database files. To back up database files in a cluster: 1. On the navigation bar, click 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, and then select the database icon. 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 261. Tip If you created a device pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs.
683
Restoring Data to a Microsoft Cluster

For all file restore operations, including redirecting restores, use the normal procedures as described in Restoring Data to a Server or Workstation on page 457. When restoring files to shared drives, direct those files to the virtual server or the controlling node of the resource. When restoring individual database files, such as Microsoft SQL Server or Exchange Server, direct those files to the virtual server name of a specific installation of the SQL or Exchange database. Related Topics: Restoring the Cluster Quorum for Windows 2000 and Windows Server 2003 Computers to a Microsoft Cluster on page 685 Restoring the Cluster Quorum to a Windows 2000 or Windows Server 2003 Node Running Active Directory to a Microsoft Cluster on page 686 Specifying a New Drive Letter for the Cluster Quorum Disk on page 688
Restoring Windows 2000 and Windows Server 2003 Features to a Microsoft Cluster
To fully restore Windows 2000 features to a remote Windows 2000 system, the restore operation MUST be performed by a Windows 2000 media server, and the Remote Agent must be installed on the remote system. You can restore Windows Server 2003 features from either a Windows 2000 media server or a Windows Server 2003 media server.
684
Restoring the Cluster Quorum for Windows 2000 and Windows Server 2003 Computers to a Microsoft Cluster
The cluster quorum is backed up as part of System State. If Active Directory is running on the target server in the cluster, do not select Restore cluster quorum. For more information, see Restoring the Cluster Quorum to a Windows 2000 or Windows Server 2003 Node Running Active Directory to a Microsoft Cluster on page 686. 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 688. 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 457. 6. When the restore operation is complete, use the cluster administrator software to restart the cluster service on nodes on which it was stopped.
685
Restoring the Cluster Quorum to a Windows 2000 or Windows Server 2003 Node Running Active Directory to a Microsoft Cluster
To restore the quorum to a node that is a domain controller running Active Directory, the node must be in Directory Services Restore Mode. The cluster services cannot run in this mode, so the cluster quorum must be restored separately, after System State is restored and the node has been rebooted. To exclude the cluster quorum from being restored with System State, clear the Restore Cluster Quorum option on the Advanced Restore Job Properties dialog box. When System State is restored, the cluster quorum is copied to a default location. For Windows 2000 the default location is: %SystemRoot%\cluster\BackupExec For Windows Server 2003, the default location is: %SystemRoot%\windows\repair\backup\bootablesystemstate\clusterdatabase Then, use the command-line utility clrest.exe to restore the cluster quorum from the default location to the quorum drive. To restore the cluster quorum to a node running Active Directory without using Backup Exec Cluster: Note If possible, take the other nodes in the cluster offline before restoring the cluster quorum. If the nodes cannot be taken offline, you should use the -f option with the clrest.exe command, explained in step 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 92. 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.
686
6. Start the restore operation. During the restore, the cluster quorum files are copied to the default location. For Windows 2000 the default location is: %SystemRoot%\cluster\BackupExec For Windows Server 2003, the default location is: %SystemRoot%\windows\repair\backup\bootablesystemstate\clusterdatabase 7. When the restore has completed, reboot the target node.
8. After reboot is complete, run clrest.exe from the command line to restore the cluster quorum from the default location to the quorum disk: clrest path where path is the complete path to the cluster quorum; typically, the path is %SystemRoot%\cluster\BackupExec for Windows 2000 and %SystemRoot%\windows\repair\backup\bootablesystemstate\clusterdatabase for Windows Server 2003. A path is required. You can include other options on the command line to force the restore to proceed even if other cluster nodes are online, and/or if the disk signatures do not match, and to specify another disk as the quorum disk: clrest [-f] path [drive letter] where [-f] forces the restore to proceed even if other cluster nodes are online and/or the disk signatures do not match. When this option is selected, the cluster service for any nodes that are online is stopped. This option also allows the drive letter of the disk that the cluster quorum was on to remain the same, even if the configuration has changed and the disk signatures contained in the restore media do not match the disk signatures contained in the cluster quorum. [drive letter] specifies another drive letter for the quorum disk. If you use this option, the drive letter that the cluster quorum resides on will be changed to the drive letter specified. Otherwise, the drive letter that the cluster quorum resides on will stay the same as it was previously. 9. After the cluster quorum is restored, use the cluster administrator to bring the other cluster nodes online.
687
Specifying a New Drive Letter for the Cluster Quorum Disk

To use the clrest.exe command-line utility to specify a new drive letter for the cluster quorum disk, restore System State, but not the cluster quorum. When System State is restored, the cluster quorum is copied to a default location, %SystemRoot%\cluster\BackupExec. Then, use clrest.exe with the [drive letter] option to restore the cluster quorum to the quorum drive, which will be assigned the drive letter you specified. To specify a new drive letter for the cluster quorum disk on Windows 2000: 1. On the 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. 8. After the cluster quorum is restored, use the cluster administrator to bring the other cluster nodes online.
688
Using Backup Exec with a VERITAS Cluster Server
Using Backup Exec with a VERITAS Cluster Server

If you use a VERITAS Cluster Server (VCS), it is recommended that the environment consist of managed media servers installed on each of the VCS nodes and a central administration server. You can install the central administration server on any of the nodes or on a system that is not a VCS node. However, the central administration server must be in the same domain as the VCS nodes. Selections for backup are made on the central administration server, and then based on the backup selections of clustered resources, the central administration server sends the job to the managed media server on which the clustered resource is currently active. The central administration server attempts to balance backup jobs of clustered resources so that the job is run as a local job. If a failover occurs, backup jobs that were running are rescheduled and then the central administration server restarts the job on the new active node for the failed resource. You can also install the Backup Exec Remote Agent on each of the VCS nodes. The standalone media server can then be installed on any of the nodes or outside of the cluster. In this environment, backup jobs for clustered resources are completed remotely. Specific details of how Backup Exec runs in a cluster vary depending on the configuration you use in the cluster. Related Topics: Installing Backup Exec on a VERITAS Cluster Server on page 691 Requirements for Installing Backup Exec on a VERITAS Cluster Server on page 690
689
Requirements for Installing Backup Exec on a VERITAS Cluster Server
Requirements for Installing Backup Exec on a VERITAS Cluster Server
32-node clusters are supported with Backup Exec for Windows 2000, and Windows Server 2003 and Microsoft Windows 2000 Advanced Server and Windows Server 2003 Enterprise and DataCenter and Windows Server 2003 DataCenter. An individually licensed copy of Backup Exec for Windows Servers, as well as any applicable agents and options, is required for each active node in the cluster as defined in the End User License Agreement. You must enter a serial number for each node in the cluster (the cluster must have at least two nodes). Storage Foundation for Windows Servers High Availability server components must be installed on the cluster nodes. Storage Foundation for Windows Servers High Availability Administrative Console components must be installed on the central administration server. VERITAS Cluster Server must be configured to run in Secure mode.
Related Topics: Installing Backup Exec on a Microsoft Cluster Server on page 660
690
Installing Backup Exec on a VERITAS Cluster Server
Installing Backup Exec on a VERITAS Cluster Server

The Remote Agent is automatically installed on all the nodes in the cluster. If this installation of Backup Exec will be used to back up remote servers outside the cluster, install the Remote Agent on those remote servers as well. For more information about the Remote Agent, see Installing the Remote Agent to Remote Windows Computers on page 793. To install Backup Exec on a VERITAS Cluster Server: 1. Install Backup Exec as an managed media server on all the nodes that you want to include in the cluster. All installations must target local drives. 2. Install the Backup Exec Central Admin Server Option (CASO) on a machine that is included in the same domain as the cluster nodes. The Central Admin Server Option can be installed on any of the cluster nodes or outside of the cluster. For more information about the Central Admin Server Option, see Symantec Backup Exec - Central Admin Server Option on page 819. 3. If the managed media server contains locally attached drives, create a drive pool that contains all the locally attached storage devices on each node to use when failover occurs. This ensures that jobs can run on the storage devices attached to the failover nodes. 4. If the Backup Exec Central Admin Server Option is not installed, then install the Backup Exec Remote Agent for Windows Servers on the local drives of all the nodes in the cluster. Related Topics: Symantec Backup Exec - Remote Agent for Windows Servers on page 789
691
Backing Up VERITAS Cluster Servers

To protect all data in the cluster, including file shares and databases, back up the following:

Local disks and System State on each node All shared disks Virtual servers, which may contain data or contain applications such as Microsoft SQL Server or Exchange Server. Use Backup Exec database agents to back up databases.
For details on setting up and running backup operations, see Creating a Backup Job on page 261. Note When performing an offhost backup, the media server and the remote computer must not be in the same cluster group. The cluster applications cannot support devices logical unit numbers (LUNs) that have duplicate signatures and partition layouts, therefore, the snapshots containing the LUNs must be transported to a host, or remote computer, that is outside the cluster. The Command Line Applet can be used with Backup Exec when Backup Exec is installed in a cluster. The only limitation is that you cannot use the Command Line Applet to specify a device for backup. You can use the Command Line Applet to target a device pool, but not a specific device in that pool. Related Topics: Backing Up Local Disks in a VERITAS Cluster on page 694 Backing Up Shared Disks in a VERITAS Cluster on page 694 Backing Up Database Files in a VERITAS Cluster on page 695 Backing Up Windows 2000 and Windows Server 2003 Features in a VERITAS Cluster on page 693
692
Backing Up Windows 2000 and Windows Server 2003 Features in a VERITAS Cluster
You must purchase and install the Backup Exec Remote Agent for Windows Servers on all remote Windows 2000 and Windows Server 2003 computers that you want backed up. Without the Remote Agent, the following Windows 2000 features cannot be correctly backed up:

Encrypted files SIS files Disk quota data Removable Storage data Remote Storage data Mount points Sparse files Windows Management Instrumentation Terminal Services System State data, including:

COM+ Class Registration database Boot and system files Registry Certificate Services database (if the server is operating as a certificate server) Active Directory (if the server is a domain controller) SYSVOL (if the server is a domain controller)
Note You can select System State for backup on a remote computer only when the Remote Agent is installed on the remote computer. Related Topics: Restoring Windows 2000 and Windows Server 2003 Features to a VERITAS Cluster on page 696
693
Backing Up Local Disks in a VERITAS Cluster

Select local disks for backup from the physical node to which they are attached. To back up local disks in a VERITAS cluster: 1. On the navigation bar, click 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 284. When making backup selections for nodes running Windows Server 2003, select
Shadow Copy Components, which include System State. For more information, see Protecting Windows Server 2003 Systems on page 344.
3. Continue with the full backup procedure as usual. For more information, see Creating a Backup Job on page 261. If you created a device pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs. Note If the computer on which you are running a backup using the Advanced Open File Option is in an environment with the Central Admin Server Option and the VERITAS Cluster Server installed, and if failover occurs to a VCS node, you must manually clean up the snapshots before restarting the backup on the failover node. Refer to the VSFW documentation for details.
Backing Up Shared Disks in a VERITAS Cluster

Select shared disks for backup by selecting them from the VERITAS Cluster Server virtual server. To back up shared disks: 1. On the navigation bar, click Backup. 2. On the Backup selection pane, expand Remote Selections, expand the domain that contains the nodes, and then select either the VERITAS Cluster Server virtual server. The virtual servers allow your backup jobs to access shared data via any node that controls the disk.
694
3. Select the drive letters that represent the shared disks. 4. Continue with the full backup procedure as usual. For more information, see Creating a Backup Job on page 261. Tip If you created a device pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs.
Backing Up Database Files in a VERITAS Cluster

Select database files for back up from a database icon on a virtual server. If a virtual server contains a database application such as Microsoft SQL Server or Exchange Server, use the appropriate Backup Exec database agent to perform the backup operations; otherwise, only the file system is backed up, not the database files. To back up database files in a VERITAS cluster: 1. On the navigation bar, click 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, and then select the database icon. 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 261. Tip If you created a device pool for the cluster, select it as the default destination device so that jobs can restart on the failover node if failover occurs.
695
Restoring Data to VERITAS Cluster Servers
Restoring Data to VERITAS Cluster Servers

For all file restore operations, including redirecting restores, use the normal procedures as described in Restoring Data to a Server or Workstation on page 457. 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.
Restoring Windows 2000 and Windows Server 2003 Features to a VERITAS Cluster
To fully restore Windows 2000 features to a remote Windows 2000 system, the restore operation MUST be performed by a Windows 2000 media server, and the Remote Agent must be installed on the remote system. You can restore Windows Server 2003 features from either a Windows 2000 media server or a Windows Server 2003 media server.
Using Backup Job Failover with VERITAS Cluster Servers

A central administration server configuration installed in a VERITAS Cluster Server environment is automatically enabled to failover a job. When you select cluster resources for backup, only a single clustered resource can be included in the backup job. This is necessary to ensure that the central administration server re-delegates the backup job to the designated failover node on the cluster. If a failover of a clustered resource occurs during backup, the job on the managed media server stops and notification is sent to the central administration server. The central administration server then re-delegates the job to the managed media server that has become the new active node of the failed clustered resource.
696
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 606. Prepare to restore SQL, Exchange, Oracle, and Lotus Domino databases in a cluster after a disaster by reading the sections on preparing for disaster recovery in the appropriate chapters. In addition to the initial preparation instructions, further action is required to completely protect the Microsoft cluster servers. If a disaster occurs, the following information is required to successfully recover the cluster:
General Cluster Information

Cluster name Cluster IP address and subnet mask Cluster node names Node IP addresses Local and shared drive letters and partition scheme Disk signatures Group name Preferred nodes Failover/failback policies Resource name Resource type Group membership Possible owners Resource dependencies Restart and Looks Alive/Is Alive properties Resource-related parameters Application-specific configuration (SQL Database Character Set)
Cluster Groups

Cluster Resources

697
If you are recovering a Microsoft Cluster Server, run Dumpcfg.exe from the Microsoft 2000 Resource Kit or and the Clusterrecovery.exe from the Microsoft 2003 Resource Kit to retrieve the disk signatures from the shared disk. The Microsoft 2000 Resource Kit allows you to replace disk signatures. If you are recovering a VERITAS Cluster Server, run Vmgetdrive.exe to retrieve the disk signatures, disk group, and volume information from the shared disk.
Using IDR to Prepare for Disaster Recovery of a Cluster

Backup Exec provides a fully-automated disaster recovery solution that you can purchase called the Intelligent Disaster Recovery (IDR) Option, which allows you to quickly and efficiently recover the nodes that comprise the server cluster after a disaster. Oracle servers and R/3 databases cannot be restored using IDR. For more information about disaster recovery for these options, see the appropriate chapters. For details on using IDR to prepare for disaster recovery, see Symantec Backup Exec Intelligent Disaster Recovery Option on page 901. Note To change the setup, use hardware, or a hardware configuration that is different from the original configuration, you must perform a manual recovery.
Recovering Nodes on the Cluster Using IDR

If you used Backup Execs Intelligent Disaster Recovery to prepare for a disaster, you can use IDR to recover the nodes to their pre-disaster state. Note You 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 and Windows 2003 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 947, 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. 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 Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901. To recover nodes on the cluster using IDR: 1. If you are recovering more than one node, disconnect the shared disks. If you are recovering only one node, the shared disks do not need to be disconnected. If all nodes in the cluster are unavailable and must be recovered, the cluster cannot fail over. Disconnect the shared disks before recovery begins. 2. To restore the nodes, follow the steps in Recovering a Computer Using IDR on page 942. 3. Reconnect the shared drives and bring the nodes online. 4. To restore a database to the shared drives, use the appropriate Backup Exec agent. For procedures, read the following sections:

Disaster Recovery of SQL on page 1059 Disaster Recovery for Exchange Server 5.5 on page 1111 Disaster Recovery of a Lotus Domino Server on page 1343 Recovering a Remote Oracle Database Server from a Disaster on page 1322
699
Recovering Backup Exec on a Microsoft Cluster Using IDR

To fully restore a cluster on which Backup Exec is installed, you can use IDR to restore the cluster node and all shared disks or you can rebuild the cluster. To remotely restore the cluster catalog the media that contains the backup sets of the cluster nodes and the shared disk. 1. Replace all shared disks, if necessary. 2. Run the IDR Recovery Wizard on one of the nodes. During this process, use the disk manager to repartition all shared disks to their original configuration. Restore the local disk, system state, and the data files to the shared disk. 3. Reboot the server. The cluster service and all other cluster applications should come online. 4. Run the IDR Recovery Wizard on all other nodes. Restore only the local disk and system state.
Recovering the Entire Cluster Using a Manual Disaster Recovery Procedure

To recover the entire cluster manually: 1. On the first node you want to recover, reinstall Windows, including the last service pack applied before the failure. For details on how to do this, see Manual Disaster Recovery of Windows Computers on page 610. 2. On the other nodes you want to recover, reinstall Windows, including the last service pack applied before the failure. Refer to the previous Caution as well. 3. Reinstall the cluster services and bring the cluster online.
If you are recovering a VERITAS Cluster Server, install the Storage Foundation for Windows High Availability server components which include Volume Manager and then use Volume Manager to create disk groups and volumes that match the original cluster configuration. If you are recovering a Microsoft Cluster Server, after booting the nodes in a cluster, make sure that the drive letters match the original cluster configuration. If the original configuration does not match, then to a certain extent, you can control the hard drive numbering scheme that Windows devises
700
by using the Disk Administrator. See the table Windows hard drive numbering scheme on page 947 that lists the normal order that Windows uses to assign disk drive numbers. 4. Do one of the following:
If you are recovering a VERITAS Cluster Server, re-install Backup Exec. For more information, seeInstalling Backup Exec on a VERITAS Cluster Server on page 691. If you are recovering a Microsoft Cluster Server, use the Cluster Wizard to reinstall Backup Exec for Windows Servers on the cluster. You must use the same settings used during the initial installation. For more information, see Installing Backup Exec on a Microsoft Cluster Server on page 660.
5. Catalog the media in the cluster. 6. On the Backup Exec navigation bar on the active node, click Restore. 7. In the Restore selections pane, select the last full backup sets made of the active node, and then select System State. 8. Do one of the following:

If you are recovering a VERITAS Cluster Server, proceed to step 9. If you are recovering a Microsoft Cluster Server, on the Properties pane, under Settings, click Advanced and then select the Restore cluster quorum option (this option must be selected).
9. Start the restore operation. 10. When the restore has completed, reboot the active node. 11. For each node that you need to recover, repeat step 6 through step 10. 12. After all nodes are recovered, restore the Backup Exec data files, and all other data files, to the shared disks. 13. To restore a database to the shared disks, use the appropriate Backup Exec agent. For procedures, read the following sections:

Disaster Recovery of SQL on page 1059 Disaster Recovery for Exchange Server 5.5 on page 1111 Disaster Recovery of a Lotus Domino Server on page 1343 Recovering a Remote Oracle Database Server from a Disaster on page 1322
701
Recovering the Microsoft Cluster Data Files

To fully recover the cluster, the cluster files in the MSCS folder may need to be restored. If the Quorum disk is still available and has not changed, then you do not have to restore the data files. If the Quorum disk is new, you need to restore the data files to the new Quorum disk. You should disable the cluster disk driver before 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. 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.
702
Recovering All Shared Disks in a Microsoft Cluster

Recover shared disks using either the Dumpcfg option from the Microsoft 2000 Resource Kit or Clusterrecovery from the Microsoft 2003 Resource Kit, which helps automate the recovery process or by performing a manual recovery. To recover all shared disks using Dumpcfg: 1. Disable the cluster disk driver on all nodes in order to gain access to the new disk. 2. On the Computer Management menu, select System Tools. Then select Device Manager. 3. Right-click the cluster disk driver, and then select Disable. 4. Replace and then repartition the shared disk. Use Disk Manager to verify that all nodes have access to the same shared disk. 5. Run Dumpcfg or Clusterrecovery to replace the disk signature for the Quorum disk. 6. Using a remote Backup Exec server, restore the cluster files to the Quorum disk via the node that has access to the disk. 7. Enable the cluster disk driver on all nodes. 8. On the Computer Management menu, select System Tools. Then select Device Manager. 9. Right-click the cluster disk driver, and then select Enable. 10. Reboot all cluster nodes. To recover all shared disks without using Dumpcfg: 1. Uninstall all cluster applications and the cluster software from both nodes. 2. Replace and then use Disk Manager to repartition the shared disk to the previously saved configuration. 3. Reinstall the cluster software. 4. Reinstall the cluster-aware version of Backup Exec for Windows Servers on the cluster. For more information, see Installing Backup Exec on page 65. 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 452.
703
Recovering All Shared Disks in a VERITAS Cluster

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

If you used the IDR option to prepare disaster recovery media for the shared disks, you must use a manual process to recover Backup Exec on a shared disk. To use a manual process to recover Backup Exec on a shared disk: 1. Replace the shared disk if necessary, and add that disk to the cluster as a disk resource. 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 65. 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 or Clusterrecovery from the Microsoft 2003 Resource Kit to replace the disk. For example, type: dumpcfg.exe /s 12345678 0 Replace 12345678 with the disk signature and replace 0 with the disk number. You can find the disk signature and the disk number in the event log. If you do not have the Microsoft 2000 Resource Kit, you can use -Fixquorum to change the Quorum disk signature. 1. Start the cluster service on one node with the -Fixquorum option in the startup parameters. 2. Open the Cluster Administrator and right-click the cluster, and then select Properties. 3. Select the Quorum tab. 4. In the Quorum resource field, select a different disk. 5. Click OK.
Chapter 15, Using Symantec Backup Exec with Server Clusters 705
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 Microsoft cluster failover occurred. Multiple backup sets were created. When I try to verify or restore using these backup sets, an "Unexpected End of Data" error occurs on the set that contains the data that was backed up prior to the failover. Why does this occur? Is my data safe? You received this error because failover occurred in the middle of backing up the resource, therefore the backup set was not closed on the media. However, the objects that were partially backed up in the first backup set were completely backed up again during restart, ensuring data integrity. Therefore, all of the objects on the media for the given backup set should still be restored and verified. I clustered a primary SAN server with a secondary SAN server. Now the device and media service on the secondary server fails. Why? This occurs when the secondary server becomes the active node and attempts to connect to the Backup Exec database on the primary server, which is no longer available. To correct this, you must use the Backup Exec Utility (BEUTILITY.EXE) or reinstall the secondary server to be a primary server. An Advanced Disk Based backup failed due to the application virtual server failover. How do I clean up VERITAS Storage Foundation for Windows cluster disk groups and their associated volumes? If the application virtual server fails when you use VERITAS Storage Foundation for Windows (SFW) snapshot provider to perform an advanced disk-based backup, the backup job will fail. The original cluster disk group that the snapped volumes belong to has moved from the primary node to a secondary node and the snapped volumes will not be able to resynchronize with the original volumes. The following is a description of the steps that occur for an advanced disk-based backup: 1. The snapped volumes are split from the original volumes. 2. The previously split snapped volumes are placed into a new cluster disk group. 3. The new cluster disk group is removed from the physical node where the production virtual server is currently online and then added to the Symantec Backup Exec media server.
706
4. The new cluster disk group will eventually be removed from the media server and then added back into the physical node where it previously resided, regardless of where the production virtual server is currently located. 5. The new cluster disk group joins the original cluster disk group if it is located in the same node. 6. The snapped volumes resynchronize with the original volumes. During this process if the production virtual fails over from the currently active node to a secondary node, the new cluster disk group cannot rejoin the original cluster disk group. To manually re-join the two cluster disk groups and resynchronize the volumes: 1. Import the cluster disk group into the node, if the original cluster disk group is not already imported into the node where the production virtual server is currently online. 2. Rejoin the new cluster disk group with the original cluster disk group. 3. Snap back the snapped volumes with their original volumes. Ensure that the option to synchronize using the original volume is selected. If you are not able to import the new cluster disk group into the node where the original cluster disk group is currently located, failover the application virtual server back to its original node before rejoining the two cluster disk groups. For detailed instruction on how to perform SFW operations, consult the VERITAS Storage Foundation for Windows user guide. After I performed a manual failover of a VERITAS cluster resource, my backup jobs hang. Why wont the backup jobs terminate? If a manual failover of a VERITAS cluster resource occurs, VERITAS Cluster Server does not dismount MountV resources if there are open handles. It is recommended that all backup jobs complete before performing a manual failover. If a backup job does hang, you must manually cancel the job before you can complete a manual cleanup process.
707
708
Chapter
16
Symantec Backup Exec Web Administration Console

The Symantec Backup Exec Web Administration Console (BEWAC) is an optional user interface for using Symantec Backup Exec on Windows Server Powered appliances and Windows 2000 and Windows Server 2003 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 Windows Server Powered appliance on which Backup Exec is installed or on other servers to which the appliance is attached.
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 are:
Windows 2000 Server

Service Pack 4 or later installed Microsoft Server Appliance Kit 2.0 or later Backup Exec for Windows Servers 10.0
OR
Windows Server 2003

Remote Administration (HTML) components installed Backup Exec for Windows Servers 10.0
Microsoft Server Appliance Kit 2.01 or Windows Storage Server 2003 Backup Exec for Windows Servers 10.0
The client requires Internet Explorer 5.5 or later.

709
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 on page 65. Note This option is only available if the installation requirements for BEWAC are met.
Setting Internet Explorer Properties

When accessing Backup Exec through Internet Explorer, a message may appear stating that a page contains both secure and non-secure items. This message is a result of icons used in Backup Exec and is no threat to system security. By selecting Yes, the contents will display normally and the icon will appear; if No is selected, some screen contents might not display properly. You can avoid this prompt by changing Internet Explorer settings. From the browser tool bar, select Tools, then Internet Options. Click the Security tab, then click Custom Level and scroll to Display Mixed Content. Select Enable to display BEWAC screen content automatically.
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 Most servers require the use of a secure channel to access BEWAC. For these servers, use the format: https://servername:secureportnumber 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.
710
Differences Between BEWAC and Backup Exec for Windows Servers
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:

Alternate server selection for Backup Exec Diagnostics AppleTalk network support Calendar view in the Job Monitor. Only the Jobs list view is available. Connect to another media server Cluster server support 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 714. 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.
Inventorying multiple slots. The ability to perform an inventory on multiple slots of a robotic library is not available. Making multiple selections. Job Summary for restore operations. A Job Summary page for restore jobs does not appear after creating the restore job. Wizards. Some of the wizards that display on the Tools menu or the Information Desk in Backup Exec for Windows Servers, such as the Logon Account Wizard, are not available. However, the First Time Startup Wizard is available in both BEWAC and Backup Exec for Windows Servers. Other wizards available in BEWAC include the Device Configuration Wizard and Policy Wizard. Preview panes. 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.
Chapter 16, Symantec Backup Exec - Web Administration Console
711
Navigating in BEWAC
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 Storage Server 2003 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.
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. 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.
712
Navigating in BEWAC BEWAC screen layout
Status area Primary navigation bar Secondary navigation bar Help button
713
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. The Tools tab includes several Task Categories, such as Main settings. The Task Categories and their available functions include:
Main settings
Configure default options for Backup, Restore, Media, Database Maintenance, Job Logs, Catalogs, and Agents. Copy settings to other Backup Exec servers. Configure alert categories and properties. Configure the recipients available to receive alert notifications. Configure the Audit Log. Modify MAPI, SMTP, VIM, and pager configurations for notifications. Modify the instructions for how to handle job errors. Configure Managed Media Server defaults (only available if the Central Admin Server Option is installed) Add and/or remove edition and option serial numbers. List all installed updates. View available software updates and configure scheduling options. View current installed Backup Exec license options. Stop and start all of the Backup Exec services and change logon credentials. Run Backup Exec diagnostics. Modify the logon account credentials. Re-create the set of example policies that are normally created by the First Time Startup Wizard. Edit the contents of a previously saved selection list. Re-enable all warnings that have been previously disabled.
Configuration

Licenses and updates

Services and diagnostics

Other settings

714
Viewing, Clearing, and Responding to Alerts

In BEWAC, a message that there are Backup Exec alerts appears in the status area above the primary navigation bar. Only one alert indicator appears, even if there are multiple Backup Exec alerts. If you click a backup Exec alert message, and then click View Details and Respond, the BEWAC Alerts tab appears. Through this tab, which is similar to the Alerts tab in Backup Exec, you can view or respond to alerts. For more information about viewing alert details or responding to an alert, see Viewing Alert Properties on page 505 or Responding to Active Alerts on page 507. Both Backup Exec and server appliance alert indicators display in the status area and on the Status tab.
715
716
Chapter
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 installed by default 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.
Caution The Backup Exec Utility should be used only with the guidance of Technical Support. Improper use of this utility can result in configuration changes that may prevent Backup Exec from running. Related Topics: Starting the Backup Exec Utility on page 718 Completing Tasks using the Backup Exec Utility on page 720 Running Backup Exec Utility General Tasks on page 722
717
Starting the Backup Exec Utility
Running Backup Exec Utility CASO Tasks on page 745 Running Backup Exec Utility Services Tasks on page 733 Running Backup Exec Utility SAN SSO Tasks on page 751 Running Database Tasks on page 756 Running Media Server Group Tasks on page 765 Running Cluster Tasks on page 768
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 located in: \Program Files\VERITAS\Backup Exec\NT.
The Backup Exec Utility
results pane
task pane
Media Servers pane
preview pane
Related Topics: Completing Tasks using the Backup Exec Utility on page 720
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. 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 or a CASO 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. Related Topics: Completing Tasks using the Backup Exec Utility on page 720
Chapter 17, Backup Exec Utility
719
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:

See: Running Backup Exec Utility General Tasks on page 722
Add a media server. Add a new media server group. Delete a media server. Delete a media server group. Run Backup Exec diagnostics. Enable debug logs. View media server properties.
Start and stop services on media servers. Change media server service accounts. Edit media server configurations. Copy media server configurations. Apply copied media server configurations. Update media server configuration to reflect a new media server name.
Running Backup Exec Utility Services Tasks on page 733
Set a central administration server. Remove a central administration server. Enable and disable CASO job delegation on a media server. Move the central administration server. Change the storage location for the catalogs.
Running Backup Exec Utility CASO Tasks on page 745
720
Completing Tasks using the Backup Exec Utility Backup Exec Utility tasks (continued) If you want to:

See: Running Backup Exec Utility SAN SSO Tasks on page 751
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.
Check Backup Exec Database consistencies. Age Backup Exec Databases. Compact Backup Exec Databases. Dump Backup Exec Databases. Rebuild, repair and recover Backup Exec Databases. Change the SQL Server sa password. Change the database access. Create a new Backup Exec database location. Copy a database.
Running Database Tasks on page 756
Add a media server to a media server group. Remove a media server from a media server group. Set a central administration server for a media server group.
Running Media Server Group Tasks on page 765
Edit cluster configuration information.
Running Cluster Tasks on page 768
721
Running Backup Exec Utility General Tasks

This section guides you through the following Backup Exec Utility tasks:
Add a New Media Server on page 722 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 723 enables you to create a container where you can logically group together multiple media servers. Delete a Media Server from the All Media Servers Node on page 724 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 725 enables you to remove user-defined media server groups from the Media Server Groups subnode. Run Backup Exec Diagnostics on page 726 enables you to run Backup Exec for Windows Servers Diagnostics application on media servers listed in the Backup Exec Utility. Enable Debug Logs on page 726 enables you to activate logs for a variety of Backup Exec engine-related debugging activities. View Media Server Properties on page 729 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.
722
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. 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. Related Topics: Delete a Media Server from the All Media Servers Node on page 724 Completing Tasks using the Backup Exec Utility on page 720
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.
723
3. Enter the appropriate options as follows.

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. Related Topics: Add Media Server on page 765 Delete a Media Server Group on page 725 Completing Tasks using the Backup Exec Utility on page 720
Delete a Media Server from the All Media Servers Node

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. 3. Select a media server or servers to delete. 4. Click OK.
Related Topics: Remove a Media Server on page 766 Add a New Media Server on page 722 Completing Tasks using the Backup Exec Utility on page 720
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. 3. Select a media server group or groups to delete. 4. Click OK. Related Topics: Create a New Media Server Group on page 723 Add Media Server on page 765 Completing Tasks using the Backup Exec Utility on page 720
725
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 2000, Windows Server 2003, and Windows XP 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. 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). Related Topics: Running BEDIAG.EXE to Generate a Diagnostic File for Troubleshooting on page 629 Completing Tasks using the Backup Exec Utility on page 720
Enable Debug Logs

Enable Debug Logs enables you to activate Backup Exec debug routines for a variety of Backup Exec services. In addition to activating the debug feature, debug log files are created and stored on a media server hard drive. Caution Enable Debug Logs should only be used when Symantec Technical Support personnel need specific information about your Backup Exec installation in order to diagnose issues. Activating debug logging will greatly impact media server performance. In a default installation, Backup Exec log files reside in the Logs directory, in the following path: <drive letter>\Program Files\VERITAS\Backup Exec\NT\Logs If you installed Backup Exec to a different path, use that path instead.
726
To use the Enable Debug Logs task: 1. Select a media server from either a media server group or from the All Media Servers subnode. 2. Under General Tasks, click Enable Debug Logs. 3. Enter the appropriate options as directed by Symantec Technical Support:
Item Media Server
Description Displays the name of the media server.
Debug Log for Backup Exec Server Service Enable Debug Log for Backup Exec Server Service Debug Detail Level Enables you to activate logging and set the log levels for the Backup Exec Server service.
Sets the level of detail desired in the debug log files. Choices include Normal, Medium, High and Max. The level to be selected will be determined by Symantec Technical Support. Activates basic Backup Exec log functions. Sets the level of detail in the SQL logs. Two levels are available, Low and High. The level selected will be determined by Symantec Technical Support. Sets the level of detail in the Job logs. Two levels are available, Low and High. The level selected will be determined by Symantec Technical Support. Activates the logs required to debug the Backup Exec messaging system. Activates the logs required to debug system performance. Activates the log required to debug the Backup Exec message queue service.
Basic Log SQL Log
Job Log
Message Log
Performance Log Enable debug log for message queue
Enable debug log for Activates the log required to debug both the Backup Exec Job Job Engine and Remote Engine and Remote Agent services. Agent service
727
Item
Description
Engine NDMP debug Enables you to set the level of Engine NDMP debug details that are level logged. Choices include: Log NDMP errors only, Log flow messages and Verbose Logging. Selecting Log NDMP errors only gives you general information and errors that are generated. Selecting Log flow messages includes both a higher level overview of the activity occurring, and the NDMP errors that are generated. Verbose Logging offers even more information and should only be used with Symantec Technical Support guidance. Remote Agent NDMP debug level Enables you to set the level of Remote Agent debug details that are logged. Choices include: Log NDMP errors only, Log flow messages and Verbose Logging. Selecting Log NDMP errors only gives you general information and errors that are generated. Selecting Log flow messages includes both a higher level overview of the activity occurring, and the NDMP errors that are generated. Verbose Logging offers even more information and should only be used with Symantec Technical Support guidance. Activates the log required to debug the Backup Exec Notification services. Activates notification logging on a media server running the Backup Exec BESERVER service. Selecting either Media server or Administration console should be done at the direction of Symantec Technical Support. Activates notification logging on a computer running the Backup Exec administration console. Selecting either Media server or Administration console should be done at the direction of Symantec Technical Support.
Enable debug log for Notification services Media server
Administration console
728
View Media Server Properties

Media Server Properties enables you to view server, options and system properties for any Backup Exec media server that appears in Backup Exec Utility. Using Media Server Properties, you can view properties for the following:

Media Server Properties - Server Tab on page 729 Media Server Properties - Options Tab on page 731 Media Server Properties - System Tab on page 732
Media Server Properties - Server Tab To view media server 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 Media Server Properties. 4. Click Server. The Media Server Properties Server tab provides the following information:
Media Server Properties Server Tab properties Item Name Description The name of the media server.
729
Running Backup Exec Utility General Tasks Media Server Properties Server Tab properties (continued) Item Status Description The status of the media server:

Online - All services are running. Pause - The server has been paused. You can pause a media server to prevent scheduled and new jobs from running on that server while maintenance activities, such as replacing a tape device, are being performed. Active jobs will not be affected if they started before the server was paused. Unavailable - The Backup Exec services are not responding. Depending on the thresholds that were set, active jobs will become stalled, then failed, and then will be recovered. For more information, see Setting Thresholds to Recover Jobs on page 445. Offline - The media server is not online. Services have been stopped.
Note If the Central Admin Server Option is installed, additional statuses are displayed. For more information, see Columns in the Media Servers View on page 853 Description Version Serial number A user-defined description of the server. Backup Exec version and revision information. The serial number under which Backup Exec is installed. Evaluation Edition is displayed if a serial number was not provided during Backup Execs installation.
Server Time Start date and time Date and time Backup Exec was initially installed and launched on this media server. Current date and time.
Current date and time Statistics Number of devices
Number of storage devices connected to this media server. In systems with multi-drive robotic libraries attached, each drive in the robotic library represents a separate device. Number of jobs currently in progress on this media server.
Number of active jobs
730
Running Backup Exec Utility General Tasks Media Server Properties Server Tab properties (continued) Item Total number of alerts since startup Description Total number of alerts generated on this media server since the Backup Exec services were last started.
Related Topics: View Media Server Properties on page 729 Completing Tasks using the Backup Exec Utility on page 720
Media Server Properties - Options Tab

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 Media Server Properties. Under General Tasks in the task pane, select Media Server Properties, and then click the Options tab to view additional options licensed and installed on the media server. The Media Server Properties Options tab provides the following information:
Media Server Properties - Options tab Item Option Licensed Description Name of the Backup Exec options. Displays Yes if the option is licensed on the media server, and No if the option is not licensed. Displays Yes if the option is installed on the media server, and No if the option is not installed. If the option is installed, it may still require some additional configuration. Refer to the Symantec Backup Exec for Windows Servers System Administrators Guide, or click Help.
Installed
731
Media Server Properties - System Tab

From the 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. Symantec Technical Support can use the results of Diagnostics to troubleshoot problems. Note You can also run BE Diagnostics for a remote server. To view media server system 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 Media Server Properties. 4. Click System. The Media Server Properties System tab provides the following information:
Media Server Properties System tab properties Item Operating system Type Version Build Processor Type Level Number of processors Memory Physical Virtual remaining 732 Amount of hardware RAM installed in the media server. Amount of virtual memory remaining on the media server. Administrators Guide Processor installed in this media server. The level of the processor installed. For example, Pentium IV. Number of processors on this media server. Operating system currently running on this media server. Version of the operating system. Build number of the operating system. Description
Running Backup Exec Utility Services Tasks Media Server Properties System tab properties (continued) Item Page size Page file BE Diagnostics Description Size of a single virtual memory page. Size of the virtual memory paging file. Note If you call Symantec Technical Support, they may request that you run BE Diagnostics and provide them with the results. Symantec 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 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.
Running Backup Exec Utility Services Tasks

Stop Services on page 734 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 734 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 736 enables you to configure the credentials that comprise the Backup Exec service account. Editing Media Server Configurations on page 737 enables you to configure Backup Exec to set automatic responses to several media alerts. Copy Media Server Configurations on page 742 Apply Copied Media Server Configuration on page 743
733
Update Configuration for New Media Server Name on page 743
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. Related Topics: Start Services on page 734 Running Backup Exec Utility Services Tasks on page 733 Completing Tasks using the Backup Exec Utility on page 720
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.
734
To start 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 Start Services. 3. After the services start, click Close on the Operation Progress screen. Related Topics: Stop Services on page 734 Running Backup Exec Utility Services Tasks on page 733 Completing Tasks using the Backup Exec Utility on page 720
735
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. 2. Enter the appropriate options as follows.
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.
736
Related Topics: Stop Services on page 734 Start Services on page 734 Running Backup Exec Utility Services Tasks on page 733 Completing Tasks using the Backup Exec Utility on page 720
Editing Media 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:
Edit Media Server Configuration dialog box Item Description
Automated Alert Responses Media Overwrite Alert Enables you to set the automated response for the Media Overwrite Alert. Responses include: Yes or OK, No, or Cancel. Enables you to set the automated response for the Media Remove Alert. Responses include: Yes or OK, No, or Cancel. Enables you to set the automated response for the Media Insert Alert. Responses include: Yes or OK, No, or Cancel. Enables you to set the automated response for the Library Insert Alert. Responses include: Yes or OK, No, or Cancel.
Media Remove Alert
Media Insert Alert
Library Insert Alert
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.
737
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. 3. Enter the appropriate options as follows:
Edit Server Configuration 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.
738
Running Backup Exec Utility Services Tasks Edit Server Configuration 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 Enables you to set the automated response for the Media Overwrite Alert. Responses include: Yes or OK, No, or Cancel. Enables you to set the automated response for the Media Remove Alert. Responses include: Yes or OK, No, or Cancel.
Media Remove Alert
739
Running Backup Exec Utility Services Tasks Edit Server Configuration options (continued) Item Media Insert Alert Description Enables you to set the automated response for the Media Insert Alert. Responses include: Yes or OK, No, or Cancel. Enables you to set the automated response for the Library Insert Alert. Your choices are Yes or OK, No, or Cancel.
Library Insert Alert
NTFS File system uses asynchronous I/O Used as a technical support diagnostic option, this option determines whether Backup Exec uses a proprietary method for accessing files (on tape and on hard drive file systems) for both read and write functionality. Selecting this option means Backup Exec will use a proprietary method to accelerate such operations and clearing the option means it will not. This option will negatively affect the performance of Backup Exec tape operations (backup, verify, restore, seeking, and so on) in an attempt to resolve minor hardware-related errors. Enable restrict anonymous support Enables support for Microsofts Restrict Anonymous security feature which prevents anonymous connectivity to a Windows server. Enabling Restrict Anonymous support forces Backup Exec to provide credentials when connecting to a resource.
740
Running Backup Exec Utility Services Tasks Edit Server Configuration options (continued) Item Tape format Use fast file restore When enabled, Backup Exec uses Fast File Access to speed up the process of finding the appropriate spot on the tape that contains the necessary data. In some cases there can be problems accessing the tape using Fast File Access; disabling this feature can work around tape access problems during restores. When enabled, Backup Exec uses Fast File Access which speeds up the process of finding the appropriate spot on the tape that contains the necessary data. In some cases there can be problems accessing the tape using Fast File Access; disabling this feature can work around tape access problems during backups. Description
Use fast append
Related Topics: Running Backup Exec Utility Services Tasks on page 733 Completing Tasks using the Backup Exec Utility on page 720
741
Copy Media Server Configurations

Copy Media Server Configuration enables you to copy the configuration information for a media server to a configuration file that can be stored on hard drive location on your network. Using this configuration file, you can then apply the media servers configuration information to other media servers in your environment. Configuration information that can be copied includes all:

Jobs, including backup, restore, and report jobs. Policies, templates and selection lists Logon information Media sets Other information such as job defaults, error handling rules, alert configuration and default schedule data.
To copy a media server configuration: 1. Start BEUtility. 2. Select a media server from either a media server group or from the All Media Servers subnode. 3. On the task pane, under Services Tasks, click Copy Media Server Configuration. 4. Enter user name and password credentials to the media server listed in the Media server field. 5. Enter the path to a target folder in which to store the configuration file, or click Browse to navigate to a target folder. 6. Enter a name for the configuration file. Include the file name extension, cfg. For example, C:\Datatemp\Eng_1.cfg 7. Click OK. 8. After the copy operation completes, click Close. Note The Copy Media Server Configuration operation may take longer to run on some media servers that on others, as the time required to complete the operation depends on the amount of configuration information contained at a media server. Related Topics: Running Backup Exec Utility Services Tasks on page 733 Completing Tasks using the Backup Exec Utility on page 720
Apply Copied Media Server Configuration

Apply Copied Media Server Configuration enables you to apply the media server configuration information that was copied using the task Copy Media Server Configuration to other media servers in your Backup Exec environment. 1. Start BEUtility. 2. Select a media server from either a media server group or from the All Media Servers subnode. The target media server will be the computer at which you will apply the copied media server configuration information. 3. On the task pane, under Services Tasks, click Apply Copied Media Server Configuration. 4. Enter user name and password credentials to the media server listed in the Media server field. 5. Enter the path to the target folder where a media server configuration file resides, or click Browse to navigate to the target folder. 6. Enter the name of a configuration file you want to use to apply configuration information to the media server. For example, C:\Datatemp\Eng_1.cfg 7. Click OK. 8. After the apply operation completes, click Close. Related Topics: Running Backup Exec Utility Services Tasks on page 733 Completing Tasks using the Backup Exec Utility on page 720
Update Configuration for New Media Server Name

Update Configuration for New Media Server Name enables you to update the server name of a media server that you have changed, without re-installing Backup Exec. You can also update the domain name if you placed the media server in a different domain. Using this task, you can update either the server name or the domain name, or both if you have made changes to both.
743
Caution Using Update Configuration for New Media Server Name does not change the media server name included inside existing backup selection lists. If you use this task to update the media server name, you must recreate all selection lists that back up data from that media server. Otherwise, the backup jobs will fail. In addition, when creating a restore job that targets the original media server, you must redirect all data being restored to the newly named media server. To use the Update Configuration for New Media Server Name task: 1. Start BEUtility. 2. Select a media server from either a media server group or from the All Media Servers subnode that you have renamed. 3. On the task pane, under Services Tasks, click Update Configuration for New Media Server Name. 4. Make the changes, as appropriate:
Update Configuration for New Media Server Name fields Item Current domain name Description The new domain name, of which the media server is now a member. The new computer name of the media server.
Current media server name Previous domain name
The previous domain name, of which the media server was a member. The previous media server name.
Previous media server name
5. Click OK. 6. When the operation completes, click Close. Related Topics: Running Backup Exec Utility Services Tasks on page 733 Completing Tasks using the Backup Exec Utility on page 720
744
Running Backup Exec Utility CASO Tasks

Set Central Administration Server on page 746 enables you to add a stand-alone Backup Exec media server to a Backup Exec central administration server database. Remove Central Administration Server on page 747 enables you to remove a managed media server from the central administration server database. Enable CASO Job Delegation on a Media Server on page 748 enables you to resume communications between the central administration server and a managed media server, bringing the managed media server online. Disable CASO Job Delegation on Media Server on page 748 enables you to stop communications between the central administration server and a managed media server, thus rendering the managed media server unavailable. Move Central Administration Server on page 749 enables you to move the central administration server to a different Backup Exec managed media server. Change Catalog Storage Location on page 750 enables you to change the storage location for the Backup Exec catalogs from the managed media server to the central administration server or from the central administration server to the managed media server.
745
Set Central Administration Server

Set Central Administration Server enables you to add a stand-alone Backup Exec media server to a Backup Exec central administration server database. After using this option the former stand-alone media server becomes a managed media server controlled by the central administration server in a CASO environment. To use the Set Central Administration Server task: 1. Start BEUtility on the central administration server. 2. Select a stand-alone media server from either a media server group or from the All Media Servers subnode. 3. On the task pane, under CASO Tasks, click Set Central Administration Server. 4. Enter the name of the media server to be converted to a central administration server. 5. In the Set Central Administration Server dialog box, enter the name of an existing central administration server. 6. Determine where you want the catalogs produced by this new managed media server and click the appropriate radio button. Storing the catalogs on the central administration server is recommended. 7. Click OK. 8. When the operational status message appears indicating a successful completion, click Close. Related Topics: Running Backup Exec Utility CASO Tasks on page 745 Completing Tasks using the Backup Exec Utility on page 720
746
Remove Central Administration Server

Remove Central Administration Server enables you to remove a managed media server from the central administration server database. Using this option converts the managed media server to a stand-alone Backup Exec media server and permanently removing all communication with central administration server. To re-enable communications with the central administration server, use the Set Central Administration Server option to add the media server back to the central administration server database. To use the Remove Central Administration Server task: 1. Start BEUtility on the central administration server. 2. Select a managed media server from either a media server group or from the All Media Servers subnode. 3. On the task pane, under CASO Tasks, click Remove Central Administration Server. 4. When the operational status message indicates the operation completed, click Close. Related Topics: Running Backup Exec Utility CASO Tasks on page 745 Completing Tasks using the Backup Exec Utility on page 720
747
Enable CASO Job Delegation on a Media Server

Enable CASO Job Delegation on Media Server enables you to enable communications between the central administration server and a managed media server, bringing the managed media server back online, and making it available for job delegation. After using Enable CASO Job Delegation on Media Server, the managed media servers communications status changes from Disabled to Enabled in the Communications Status column in the Communications Status column of the Backup Exec Media Server view. Its status change is also reflected in the Media Server Status column, which changes from Unavailable to Online. Finally, an icon representing a fully functioning managed media server appears. To use the Enable CASO Job Delegation on Media Server task: 1. Start BEUtility on the central administration server. 2. Select a paused managed media server from either a media server group or from the All Media Servers subnode. 3. On the task pane, under CASO Tasks, click Enable CASO Job Delegation. Note Because using this task involves the stopping and starting of Backup Exec services, this operation may take some time to complete. 4. When the operational status message appears indicating a successful completion, click Close. Related Topics: Running Backup Exec Utility CASO Tasks on page 745 Completing Tasks using the Backup Exec Utility on page 720
Disable CASO Job Delegation on Media Server

Disable CASO Job Delegation on Media Server enables you to disable communications between the central administration server and a managed media server, thus making the managed media server unavailable for job delegation. After using Disable CASO Job Delegation on Media Server, the managed media servers communications status changes from Enabled to Disabled in the Communications Status column of the Backup Exec Media Server view. Its status change is also reflected in the Media Server Status column, which changes from Online to Unavailable. Finally, an icon representing a disabled managed media server appears
748
To use the Disable CASO Job Delegation on Media Server task: 1. Start BEUtility on the central administration server. 2. Select a managed media server from either a media server group or from the All Media Servers subnode. 3. On the task pane, under CASO Tasks, click Disable CASO Job Delegation. Note Because using this task involves the stopping and starting of Backup Exec services, this operation may take some time to complete. 4. When the operational status message appears indicating a successful completion, click Close. Related Topics: Running Backup Exec Utility CASO Tasks on page 745 Completing Tasks using the Backup Exec Utility on page 720
Move Central Administration Server

Move Central Administration Server enables you to move the central administration server database to another Backup Exec central administration server. After moving the database, the following occurs:
All managed media servers that previously communicated with the original central administration server now begin communicating with the newly configured central administration server after the move process completes. The original central administration server reverts to a managed media server, which then falls under the management of the new central administration server. All managed media servers that previously communicated with the destination central administration server need to be redirected so that they can communicate with the newly created central administration server. To redirect the managed media servers, see Set Central Administration Server on page 746.
To use the Move Central Server task: 1. Start BEUtility on the central administration server. 2. Select a media server group that contains both central administration servers. If one does not exist, create one.
749
3. On the task pane, under CASO Tasks, click Move Central Administration Server. Note Because this task involves stopping and starting Backup Exec services, this operation may take time to complete. 4. In the Current central administration server list box, select the current central administration server. 5. In the Destination central administration server list box, select the destination central administration server that will become the new central administration server. 6. Click OK. 7. When the operational status message appears indicating a successful completion, click Close. Related Topics: Running Backup Exec Utility CASO Tasks on page 745 Completing Tasks using the Backup Exec Utility on page 720
Change Catalog Storage Location

Change Catalog Storage Location enables you to change the storage location for the Backup Exec catalogs. The catalog storage location determines whether or not the CASO central restore feature can be used. Centralized restore requires catalogs to be stored on the central administration server. Catalogs stored on the central administration server are accessed during the centralized restore feature; catalogs that are stored on a managed media server cannot be accessed, and thus cannot be used for centralized restore. Changing the catalog storage location from a managed media server to a central administration server changes the storage location for future catalog sets, while also physically moving the existing catalogs to the central administration server. Changing the catalog storage location from a central administration server back to a managed media server also changes the future storage location, but it does not physically move existing catalogs back to the managed media server. Therefore, if you configure CASO to use the central administration server as the catalog storage location, and then change the catalog storage location to a managed media server, the centralized restore feature will use the catalogs that remain on the central administration server during central restore operations, but not the catalogs that reside on the managed media server.
Running Backup Exec Utility SAN SSO Tasks
To use the Change Catalog Storage Location task: 1. From a media server group, select a target computer at which you want to store the Backup Exec catalogs. 2. On the task pane, under CASO Tasks, click Change Catalog Storage Location. 3. Click the appropriate radio button to select the new catalog storage location at either a managed media server or a central administration server. 4. Click OK. Related Topics: Running Backup Exec Utility CASO Tasks on page 745 Completing Tasks using the Backup Exec Utility on page 720

Set the Primary SAN SSO Server on page 752 enables you to add a media server to an existing SAN SSO-enabled storage area network. Remove the Primary SAN SSO Server on page 752 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 753 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 754 enables you to reconfigure a media server as the primary SAN SSO Server. Move the Primary SAN SSO Server on page 755 enables you to change the computer that serves as a primary SAN SSO Server.
Note When adding a Backup Exec cluster media server, use the virtual Backup Exec cluster name. Do not use the cluster node name. Related Topics: Completing Tasks using the Backup Exec Utility on page 720
751
Set the Primary SAN SSO Server

Set Primary SAN SSO Server enables you 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 use the Set the Primary SAN SSO Server task: 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. Related Topics: Running Backup Exec Utility SAN SSO Tasks on page 751 Completing Tasks using the Backup Exec Utility on page 720
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.
752
When prompted for confirmation of this operation, click Yes.

4. After the operation finishes, click Close on the Operation Progress screen. Related Topics: Running Backup Exec Utility SAN SSO Tasks on page 751 Completing Tasks using the Backup Exec Utility on page 720
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. Before you modify a SAN SSO configuration, make sure that all servers have a valid SAN SSO license and have SAN SSO installed. You must run the Backup Exec Utility from a licensed server. If you receive the following error when attempting to create a new SAN SSO configuration: Error (1068) - The dependency service or group failed to start Then you must install SAN SSO on that server. See Installing Backup Exec Options to the Local Computer on page 71. 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 the media server that will be the Primary SAN SSO server. 4. Click OK. 5. After the operation finishes, click Close on the Operation Progress screen. Related Topics: Running Backup Exec Utility SAN SSO Tasks on page 751 Completing Tasks using the Backup Exec Utility on page 720
753
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. 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 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. Related Topics: Running Backup Exec Utility SAN SSO Tasks on page 751 Completing Tasks using the Backup Exec Utility on page 720
754
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 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 New primary SAN SSO server
The name of the media server to be converted to the new primary 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. Related Topics: Running Backup Exec Utility SAN SSO Tasks on page 751 Completing Tasks using the Backup Exec Utility on page 720
755
Running Database Tasks

You can perform the following Backup Exec Utility tasks on the Backup Exec database or the Desktop and Laptop Option (DLO) database. The only exception is the Rebuild Indices operation, which you cannot perform on the DLO database. Note The following database tasks can only be run on a stand-alone server or the Primary SAN SSO server. If these functions are run on a secondary SAN SSO server, the functions will fail.
Check the Database Consistency on page 757 enables you to check the consistency or validity of a media servers Backup Exec Database) Age the Database on page 757 enables you to age a media servers Backup Exec Database by deleting information considered old. Compact a Media Server Database on page 758 enables you to shrink the database by removing a databases unused space. Dump a Media Server Database on page 758 enables you to back up the Backup Exec Database to your hard drive. Rebuild Media Server Database Indices on page 759 enables you to rebuild media server database indices in the event the indices become corrupt. Repair a Media Server Database on page 759 enables you to repair a database. Recover a Media Server Database on page 760 enables you to recover a database. Change the SQL Server sa Password on page 761 enables you to change a media servers SQL Server sa password. Change Database Access on page 762 enables you to grant or revoke a users database access. New Backup Exec Database Location on page 763 Copy Database on page 764
756
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. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
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. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
757
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. 3. After the operation finishes, click Close on the Operation Progress screen. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
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. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
758
Rebuild Media Server Database Indices

Rebuild Indices enables you to rebuild media server database indices in the event the indices become corrupt. Note This option does not apply to the Desktop and Laptop Option (DLO) database. The DLO database does not maintain indices on its database. 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. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
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. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
759
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.
Item Server
Description The name of the media server on which the database is being recovered. Select the database you want to recover, either the Backup Exec database or the Desktop and Laptop Option (DLO) database. You can perform this operation on only one database at a time.
Database instance
Recovery method Use best recovery method for current configuration As the Backup Exec Utility default, this option attempts to fix and recover the existing 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 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 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 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 447.
760
Item
Description
Drop existing database Deletes the existing database and creates, in its place, a new and and reload from base empty database. For more information, see Configuring Database Maintenance on page 447.
4. After the operation finishes, click Close on the Operation Progress screen. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
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 Database instance field, select either the Backup Exec database or the Desktop and Laptop Option (DLO) database. You can perform this operation on only one database at a time. 4. In the Old sa Password field, enter the old password. 5. In the New sa Password field, enter the new password. 6. Confirm the password by re-entering it in the Confirm sa Password field. 7. After the operation finishes, click Close on the Operation Progress screen. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
Chapter 17, Backup Exec Utility 761
Change Database Access

Change Database Access enables you to grant or revoke a users database access to the media servers Backup Exec Database and its DLO database, if the DLO option is installed. 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. 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. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
762
New Backup Exec Database Location

New Backup Exec Database Location enables you to change the Microsoft SQL Server instance that the Backup Exec Database is using. The new location can be on another computer running Microsoft SQL Server, or on the same computer running a different instance of SQL Server. To use the New Backup Exec Database Location task: 1. Start BEUtility. 2. On the task pane, under Database Tasks, click New Backup Exec Database Location. 3. Enter a destination SQL Server instance. 4. Click OK. A message appears stating the Backup Exec services will be shut down. 5. Click Yes to continue. 6. After the operation completes successfully, click Close. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
763
Copy Database
Copy Database enables you to copy an existing database that may have been backed up to a hard drive location. 1. Start BEUtility. 2. On the task pane, under Database Tasks, click Copy Database. 3. Enter the name of an existing database file from which to copy, or click Browse to navigate to the location of the existing database. The database file uses the file name extension, .mdf. 4. Enter the name of an existing database log file from which to copy, or click Browse to navigate to the location of the existing database log file. The log file uses the file name extension, .ldf. 5. Click OK. 6. After the operation completes successfully, click Close. Related Topics: Running Database Tasks on page 756 Completing Tasks using the Backup Exec Utility on page 720
764
Running Media Server Group Tasks

Add Media Server on page 765 enables you to add a media server to a media server group. Remove a Media Server on page 766 enables you to remove a media server from a media server group. Set Central Administration Server for the Media Server Group on page 766 enables you set a central administration server for a group of stand-alone media servers that are part of 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. 4. Click OK. Related Topics: Delete a Media Server from the All Media Servers Node on page 724 Remove a Media Server on page 766 Completing Tasks using the Backup Exec Utility on page 720
765
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. 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. 4. Click OK. Related Topics: Delete a Media Server from the All Media Servers Node on page 724 Add Media Server on page 765 Completing Tasks using the Backup Exec Utility on page 720
Set Central Administration Server for the Media Server Group

Set Central Administration Server for Group enables you set a central administration server for a group of stand-alone media servers that are part of a media server group. However, before using this task, you must have the Central Admin Server Option installed on the media server targeted as the central administration server. Note Before using this task, a media server group must be populated with a group of stand-alone Backup Exec 10.0 media servers. To set the central administration server for a media server group: 1. Start BEUtility. 2. On the Media Servers pane, double-click Media Server Groups, and then select a media server group. 3. On the task pane, under Media Server Group Tasks, click Set Central Administration Server for Group.
766
A list of stand-alone media servers that comprise the media server group appears in the Media servers field. 4. In the Central administration server list box, select a stand-alone media server to be the central administration server for the group of media servers listed. 5. Click OK. A message appears stating that the Backup Exec services will be stopped and restarted on both the new central administration server and all other stand-alone media servers in the group. 6. Click Yes to continue. After the operation successfully completes, click Close. Related Topics: Running Media Server Group Tasks on page 765 Completing Tasks using the Backup Exec Utility on page 720
767
Running Cluster Tasks

This section guides you through the following Backup Exec Utility task:
Edit Cluster Configuration on page 768 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.
Related Topics: Completing Tasks using the Backup Exec Utility on page 720 Caution When adding a Backup Exec Cluster Media Server, use the Virtual Backup Exec Cluster name. Do not use the cluster node name.
Edit Cluster Configuration

Edit Cluster Configuration enables you to reset either the entire SCSI bus or a specific SCSI LUN in a clustered environment. 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.
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
768
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.
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. Related Topics: Completing Tasks using the Backup Exec Utility on page 720
769
770
Chapter
18
Symantec Backup Exec Tivoli Storage Manager

The Backup Exec for Windows Servers Tivoli Storage Manager (TSM) enables you to combine the speed and localized control of Backup Exec with the TSM policy-based system of centralized storage management. The TSM feature 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. Related Topics: Requirements for the TSM Feature on page 771 Backup Exec as a TSM Client on page 772 TSM Backup Exec Components on page 773
Requirements for the TSM Feature
Familiarity with TSM terminology and operation, and the operating system on which the server resides. TSM versions 4.2, 4.2.1, 5.1, 5.1.5 and 5.2 Backup Exec for Windows Servers 9.x or later installed on the media server. TCP/IP installed on the media server.
Note The Backup Exec TSM feature does not support the following communication protocols: SPX, NetBEUI, NetBIOS or any mainframe protocols such as SNA The Tivoli Storage Manager Administrators Guide and Administrators Reference Guide may also be helpful.
771
Backup Exec as a TSM Client

Backup Execs TSM feature 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 2000, Windows XP, Windows Server 2003 Exchange Server (optional) SQL Server (optional) Backup Exec for Windows Server v9.x or later Backup Exec for Tivoli Storage Manager option
After establishing communication with the TSM Server, Backup Exec recognizes the TSM server as a virtual single tape drive robotic library and stores the contents of its backup jobs on it. 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.
772
Backup Exec Architecture and the TSM Server Device Driver Backup Exec Scheduler and Job Engine Backup Exec Device Handling Device Driver Device Driver Device Driver Tape Device
Tape Device
Tape Loader
Virtual Tape Loader
TCP/IP Protocol
TSM Server
Related Topics: TSM Backup Exec Components on page 773 Requirements for the TSM Feature on page 771
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. 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
Chapter 18, Symantec Backup Exec - Tivoli Storage Manager
773
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. Symantec includes a TSM server preparation macro named BEX.MAC that automatically performs all steps necessary to prepare the TSM server. Regardless of your experience with TSM, it is extremely important that you use the instructions under Preparing the TSM Server and Running the BEX Macro to properly configure the TSM server. From the Backup Exec interface, you can direct output from Backup Exec jobs to the TSM server by selecting the name of the TSM robotic library as the destination. Related Topics: Preparing the TSM Server on page 775 BEX.MAC Macro Command Details on page 783
774
Preparing the TSM Server

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

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

The high-level macro named BEX.MAC contains commands that automate the process of preparing the TSM server. Note You must install the Backup Exec for Windows Servers TSM feature to obtain a copy of the BEX.MAC macro. During the install, the BEX.MAC macro is placed in the same directory where Backup Exec was installed. However, for the BEX.MAC macro to run correctly, you must first use the TSM DSMFMT utility to allocate space for the storage pool, backupexec_pi, used by the position information (PI) data stream. The TSM DSMFMT utility is delivered as part of the TSM server, and is used to pre-allocate the space needed when disk-based storage pools are created. For information on the DSMFMT utility parameters, see your TSM Administrators Reference Guide. Related Topics: BEX.MAC Macro Command Details on page 783
775
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 2000 or Windows Server 2003 platforms, and you want to format a 30MB file to be located in the root directory, select this location when using the wizard. Other paths can be used, but the other paths must be reflected in the BEX.MAC. 2. After formatting the bexpi.dsm file, edit the BEX.MAC macro to associate the backupexec_pi storage pool with the bexpi.dsm file. The macro also executes commands that complete the preparation of the TSM server. 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
776
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
For example, if you are using TSM on Windows 2000, Windows XP, or Windows Server 2003 platforms and you want to format a 30MB file to be located in the root directory, type: dsmfmt <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. Related Topics: BEX.MAC Macro Command Details on page 783
777
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 feature CD, that automates the association of the new storage pool, and the creation of the necessary policy domain, policy set, management classes, and node registration. With shared nodes, this macro is run once to complete preparation of the TSM server. 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.
Disadvantages of using individual nodes for each Backup Exec server include:
3. After the BEX.MAC macro completes with no errors, enable Backup Exec to run with TSM. Refer to Enabling TSM Support on page 779.
778
Enabling TSM Support
Enabling TSM Support

To install and configure the TSM feature on a Windows computer, see Installing Backup Exec Options to the Local Computer on page 71. Note During the installation, you will need to know both the TSM servers IP and port address settings. Related Topics: Changing the Defaults for Backup Exec for Windows Servers on page 779 Preparing the TSM Server on page 775
Changing the Defaults for Backup Exec for Windows Servers

When the Backup Exec media server sends backup data to the TSM server, the management class names, node names and passwords used on the two servers must match. If the values on the TSM server do not match the values in the Backup Exec registry key, the TSM feature will not work. When the TSM feature is installed, the BEX.MAC macro contains the same default names that are in the Backup Exec server registry key: HKEY_LOCAL_MACHINE/SOFTWARE/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 the values you enter on the TSM server. After you make changes in the registry key, stop and restart the Backup Exec services. The following screen shows the registry key. Key values appear in hexadecimal format.
779
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.
780
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:
NodeName:
781
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.
Related Topics: Changing Passwords on page 783
782
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:

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.
783
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 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 779. Modifies the management class MC_VT to be the default management class.
define mgmtclass VERITAS bex_backup MC_VT SPACEMGTECHnique = NONE
assign defmgmtclass VERITAS bex_backup MC_VT
784
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. Activates all the previously listed additions/modifications.
activate policyset VERITAS 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 779.
785
Troubleshooting
Troubleshooting
If the TSM server and the Backup Exec server cannot communicate after the TSM feature has been installed, check the following:

Are all the necessary API and OPT files copied to the correct locations? Does the DSM.OPT file have the correct TCP/IP address and port number entered? Can you ping the TSM servers TCP/IP address? If you cannot ping the server, the support will not work.
Related Topics: TSM Problem Resolutions for Backup Exec for Windows Servers on page 786
Viewing TSM-related Errors

To view TSM-related errors in Backup Exec for Windows Servers, look in the application log in the Windows event viewer. The DSIERROR.LOG file is located in the directory from which Backup Exec runs. If the IBM client is loaded, you can also view error codes listed in a file named DSMRC.H, located in the TSM API client directory, \ADSM32\API\INCLUDE. The TSM API code also creates an error log file called DSIERROR.LOG. This file can also contain information useful for isolating any TSM-related problems when using Backup Exec. Related Topics: TSM Problem Resolutions for Backup Exec for Windows Servers on page 786
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
786
Viewing TSM-related Errors
Logical Unit Id 1 DeviceName: REG_SZ: Tape41 Identifier: REG_SZ: ADSM Tape Device Type: REG_SZ: TapePeripheral 2. Verify that TSM is enabled in the Registry: HKEY_LOCAL_MACHINE\SOFTWARE\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. 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.
787
Viewing TSM-related Errors TSM Troubleshooting Guide (continued) Error Message An error occurred while processing a TSM command. Session rejected: Unknown or incorrect ID entered. Corrective Action 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.
788
Appendix
Symantec Backup Exec Remote Agent for Windows Servers

The Symantec Backup Exec Remote Agent for Windows and NetWare Servers (Remote Agent) is installed as a separate, add-on component that must be used for the backup and restore of remote Windows or NetWare resources. This section outlines protecting remote Windows resources. For specific information on protecting remote NetWare resources, see Symantec Backup Exec - Remote Agent for NetWare Servers on page 1391. The Remote Agent is a system service that runs on remote Windows servers and workstations, and provides the following:
Enables the remote backup and restore of Windows features. You can use the Remote Agent Monitor, installed with the Remote Agent, to check if a backup or restore job is running on the remote Windows computer, to add or change the media servers that the Remote Agent advertises to, and to enable debug logging. You can also use the Remote Agent Monitor to open the Registry Editor, the Services window, and the Event Viewer on the remote Windows computer.
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 a specified local network.
789
To display the Remote Agent as a selection in a media server's backup selection tree, and to be able to specify a local network for use between the Remote Agent and a media server, you are prompted during installation to enter the names or IP addresses of the media servers that you want the Remote Agent to advertise to. You can add media servers for the Remote Agent to advertise to, and change their names and IP addresses by using the Remote Agent Monitor.
Enables the backup and restore of the Extensible Firmware Interface (EFI) on Intel Itanium 64-bit computers. These computers must have the Remote Agent installed. 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.
Note Network hardware has a major impact on performance. Performance is directly related to the capabilities of the networking hardware in the media server and the remote device. Higher network bandwidth ratings also contribute to faster operation processing. In order to back up and restore the following platforms, the Remote Agent must be purchased and installed. These platforms include:

Windows Server 2003 Product Family (all server versions) Windows 2000 Server Product Family (all server versions)
To protect the Workstation versions of these platforms, you must install the Remote Agent on each platform; however a license is not required for systems running Windows workstation operating systems. Related Topics: Requirements for the Remote Agent on page 791 Installing Backup Exec Agents to Remote Computers on page 77 Specifying Default Backup Network and Firewall Options on page 336 Enable Remote Agent TCP dynamic port range on page 338 Using Backup Exec with Firewalls on page 341 Backing Up EFI System Partitions on page 350 The Remote Agent Monitor for Windows Servers on page 797
790
Requirements for the Remote Agent
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 computer that you want to protect. To back up a remote Windows computer from more than one media server, you must enter the same Remote Agent serial number on each media server. Backup Exec database agents and the Advanced Open File Option (AOFO) also include a Remote Agent that allows you to protect one remote Windows server. The Remote Agent license is enabled when you install the database agent and the AOFO serial numbers on the media server. However, if you are using the database agent or AOFO on the local media server only, you can uninstall the Remote Agent license that was included with one of those options, and install it on one remote Windows computer so that resource can be protected by Backup Exec. You must install the Remote Agent on Windows XP Professional and Windows 2000 Professional computers in order to protect them; however, a Remote Agent serial number is not required for these installations. The Remote Agent is available for both 32-bit and 64-bit computers. Both versions of the Remote Agent provide protection for remote Windows resources, and support the following:

Shadow Copy Components file system. Backup Exec Advanced Open File Option.
The Remote Agent for 64-bit computers also supports the Backup Exec Agent for Microsoft SQL Server on a 64-bit version of SQL Server 2000. The Remote Agent for 64-bit computers has the following limitations:
Can be installed only on 64-bit Intel Itanium and Itanium 2 computers running the Windows Server 2003 family or Windows XP 64-bit Edition. Cannot be push installed. A local installation of the Remote Agent on the 64-bit computer is required. Supports only the Symantec Volume Snapshot Provider (VSP) and Microsoft Volume Shadow Copy Service (VSS) when used with the Advanced Open File Option.
Related Topics: Installing the Remote Agent to Remote Windows Computers on page 793 Enable Remote Agent TCP dynamic port range on page 338
Appendix A, Symantec Backup Exec - Remote Agent for Windows Servers 791
Backing Up Data in a Mixed Environment Using the Remote Agent
Backing Up Data in a Mixed Environment Using the Remote Agent

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

Encrypted files SIS files 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 computer running Windows 2000, Windows XP, or Windows Server 2003 only when the Remote Agent is installed on the remote computer.
792
Installing the Remote Agent to Remote Windows Computers

To install the Remote Agent on a remote 32-bit Windows computer, see Installing Backup Exec Agents to Remote Computers on page 77. To install the Remote Agent on a remote 64-bit Windows computer, see Installing the Remote Agent on a 64-bit Computer Using the Installation Program on page 793. You can also install and uninstall the Remote Agent on remote computers using the Windows command line. See Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line on page 794 Note If you have a previous version of the Remote Agent installed, it will be automatically upgraded when you initiate a new Remote Agent installation. Previous versions of the Remote Agent are automatically detected on the remote computers and replaced with the new version during installation of the new Remote Agent. Note that the name of the system service may have changed when the upgrade is complete.
Installing the Remote Agent on a 64-bit Computer Using the Installation Program
The installation program for the 64-bit Remote Agent is separate from the Backup Exec installation program. In addition, the 64-bit Remote Agent installation process differs from the 32-bit Remote Agent installation process. The 32-bit Remote Agent is installed locally or is push installed to a remote computer. The 64-bit Remote Agent can only be installed locally or via a mapped drive. The 64-bit Remote Agent installation program is available on the Backup Exec media server in the default directory \Program Files\VERITAS\Backup Exec\NT\Agents\RANT64. A Remote Agent serial number is not required during the installation of the 64-bit Remote Agent. However, you must enter a Remote Agent serial number on the media server. After you install the 64-bit Remote Agent, you can use the Windows Add/Remove Programs feature to modify or uninstall the option. To install the 64-bit version of the Remote Agent: 1. On the remote computer, map a drive letter to the Backup Exec for Windows Servers media server using the following path: \Program Files\VERITAS\Backup Exec\NT\Agents\RANT64, or you can type a UNC path. 2. Double-click setup.exe, and then click Next.
Appendix A, Symantec Backup Exec - Remote Agent for Windows Servers
793
3. Select the type of installation you want, either Complete or Custom, and then click Next. The Complete option installs the 64-bit version of the Remote Agent and the Advanced Open File Option. Select the Custom option if you do not want to install the Advanced Open File Option at this time. You can install it later if needed. 4. If you selected the Complete option, go to step 5. If you selected the Custom option, select the option you want to install, and then click Next. You cannot clear the Remote Agent selection because it is a required component and you cannot change the installation destination. 5. Click Install. 6. If you installed the Advanced Open File Option, you must reboot the computer. Backup Exec creates an installation log in \Windows\BKUPINST.log.
Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line
To install the Remote Agent on a remote computer using the Windows command line: 1. At a remote computer, 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 2. Open a command prompt and type the drive letter you mapped in step 1. 3. To install the Remote Agent without advertising enabled, run the following command: setup.exe /RANT32: -s -boot To install the Remote Agent with advertising enabled, run the following command: setup.exe/RANT32: -s /ADVRT: <media server name 1> <media server name 2> The Remote Agent is installed on the remote computer in the following directory: \Program Files\VERITAS\Backup Exec\RANT The Remote Agent installation log file is installed in \WINNT\bkupinst.log or \Windows\bkupinst.log.
794
To uninstall the 32-bit Remote Agent from a remote computer using the Windows command line: 1. At the remote computer, 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 2. Open a command prompt and type the drive letter you mapped in step 1. 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 computer. Related Topics: Enable Advertising for the Remote Agent for Windows Servers on page 800
Installing and Uninstalling the 64-bit Remote Agent and Advanced Open File Option Using a Command Script
You can install and uninstall the 64-bit Remote Agent and the Advanced Open File Option using command script files. The command script files are included in the 64-bit Remote Agent download. The command script file setupaa64 installs the 64-bit Remote Agent. The command script file setupaofo64 installs the Remote Agent and the Advanced Open File Option. One command script file, Uninstallaaofo64, is available to uninstall both the 64-bit Remote Agent and the Advanced Open File Option. The uninstall command script removes both options together. You cannot remove the options separately using the command script. To install the 64-bit Remote Agent and Advanced Open File Option using a command script: 1. Map a drive letter to the Backup Exec for Windows Servers media server using the following path: \Program Files\VERITAS\Backup Exec\NT\Agents\RANT64. Note Scripts do not support UNC paths. 2. Do one of the following:
To install the 64-bit Remote Agent, double-click setupaa64.

795
To install the 64-bit Advanced Open File Option, double-click setupaofo64.
The command script installs the option automatically on the remote server in the following directory: \Program Files\VERITAS\Backup Exec\RANT. 3. If you installed the Advanced Open File Option, you must reboot the remote computer. Backup Exec creates an installation log in \Windows\BKUPINST.log. To uninstall the 64-bit Remote Agent and Advanced Open File Option using a command script: 1. Map a drive letter to the Backup Exec for Windows Servers media server using the following path: \Program Files\VERITAS\Backup Exec\NT\Agents\RANT64. 2. Double-click Uninstallaaofo64. Both the 64-bit Remote Agent and the 64-bit Advanced Open File Option are removed from the computer. 3. Reboot the remote computer.
796
Stopping and Starting the Remote Agent
Stopping and Starting the Remote Agent

The Remote Agent is automatically started as a service when Windows is started on the remote computer. Note You can also use the Remote Agent Monitor to stop and start the Backup Exec Remote Agent for Windows Servers service. To stop or start the Remote Agent on a Windows 2000, Windows XP, or Windows Server 2003 computer: 1. On the Windows computer, 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. Related Topics: The Remote Agent Monitor for Windows Servers on page 797
The Remote Agent Monitor for Windows Servers

Use the Remote Agent Monitor to check if a backup or restore job is running on the remote Windows computer, to add or change the media servers that the Remote Agent advertises to, and to enable debug logging. You can also use the Remote Agent Monitor to open the Registry Editor, the Services window, and the Event Viewer on the remote Windows computer. The Remote Agent Monitor is installed when the Remote Agent is installed on a remote Windows computer. The default path that the vxmon.exe file is installed to is C:\Program Files\VERITAS\Backup Exec\RANT. To start the Remote Agent Monitor: 1. To start the Remote Agent Monitor for the first time, on the computer on which the Remote Agent is installed, go to C:\Program Files\VERITAS\Backup Exec\RANT. 2. Double-click vxmon.
797
The Remote Agent Monitor icon is placed in the system tray. 3. To display the Remote Agent Monitor, double-click the icon in the system tray, or right-click the icon, and then on the shortcut menu click Options. After the Remote Agent Monitor is started for the first time, you can configure it to start whenever you log on. 4. To open the Registry Editor, the Services window, and the Event Viewer on the remote Windows computer, right-click the Remote Agent Monitor icon in the system tray, and then on the shortcut menu click Tools. Related Topics: Setting Defaults for the Remote Agent Monitor on page 799 Viewing Remote Agent Monitor Activity on page 799 Enable Advertising for the Remote Agent for Windows Servers on page 800 Enable Debug Logging for Remote Windows Computers on page 802
798
Setting Defaults for the Remote Agent Monitor

You can set how often the Remote Agent Monitor checks for activity on the remote Windows computer, and you can set an option to start the Remote Agent Monitor whenever you log on. To set general defaults for the Remote Agent Monitor: 1. Double-click the Remote Agent Monitor icon in the system tray to view the monitor, or right-click the icon and then click Options from the shortcut menu. 2. Click the General tab, set the following options as appropriate, and then click Apply.
Backup Exec Remote Agent Monitor Options, General tab Item Refresh interval Description Enter the number of milliseconds for the Remote Agent Monitor to wait before refreshing the status of the computer. The default setting it to check every 5000 milliseconds, or every 5 seconds.
Start the Remote Agent Select this check box to start the Remote Agent Monitor when you Monitor when you log log on. on
Related Topics: Enable Advertising for the Remote Agent for Windows Servers on page 800 Enable Debug Logging for Remote Windows Computers on page 802
Viewing Remote Agent Monitor Activity

To check if a backup or restore job is running on the remote Windows computer, position the cursor over the icon in the system tray to display a status. You can also view specific details on remote agent activity by viewing the Status tab. Possible statuses are:

Idle Backup is running Restore is running Backup and Restore are running The BEREMOTE service or process is not running
799
To view Remote Agent Monitor status: 1. Double-click the Remote Agent Monitor icon in the system tray to view the monitor, or right-click the icon and then click Options from the shortcut menu. 2. Click the Status tab. The options are described in the following table:
Backup Exec Remote Agent Monitor Options, Status tab Item Activity Media server Source Current folder Name of the media server processing the current operation. Media or share that is being processed. Name of the current directory, folder, or database (depending on the specific agent) that is being processed. Name of the current file that is being processed. Description
Current file
Related Topics: Setting Defaults for the Remote Agent Monitor on page 799 Enable Debug Logging for Remote Windows Computers on page 802
Enable Advertising for the Remote Agent for Windows Servers

To enter the name or IP address of a media server or media servers that you want this Remote Agent to communicate with, click the Advertising tab. If you specified media servers to advertise to during the Remote Agent installation, use the Remote Agent monitor to view or change the media server names or IP addresses. For each media servers name or IP address that you enter or that is already displayed, the Remote Agent is displayed under Remote Selections in the media servers backup selection tree. Additionally, for each media server that you enter or that is already displayed, you can specify a local network for traffic generated by backup and restore jobs when operations are performed between the media server and the remote computer on which the Remote Agent is installed.
800
To add or edit names or IP addresses of media servers for Remote Agent advertising: 1. Double-click the Remote Agent Monitor icon in the system tray to view the monitor, or right-click the icon and then click Options from the shortcut menu. 2. Click the Advertising tab, set the following options as appropriate, and then click Apply.
Backup Exec Remote Agent Monitor Options, Advertising tab Item Enable Remote Agent advertising Description Click this to enable the Remote Agent to advertise to media servers.
Media server name or IP address Media server name IP address Add Click this to enter the name of a media server. Click this to enter the IP address of a media server. After entering a media server name or IP address, click Add to enter the media server to the displayed list. To change a media server name or IP address, select the media server in the displayed list, and then click Edit. To delete a media server name or IP address from the list of media servers to advertise to, select the media server in the displayed list, and then click Remove.
Edit
Remove
Related Topics: Specifying Default Backup Network and Firewall Options on page 336 Setting Defaults for the Remote Agent Monitor on page 799
801
Enable Debug Logging for Remote Windows Computers

Caution The debug log should be used only with the guidance of Symantec Technical Support. If you enable debug logging, it may result in poor performance and the use of excessive disk space. To enable debug logging on the Remote Agent Monitor: 1. Double-click the Remote Agent Monitor icon in the system tray to view the monitor, or right-click the icon and then click Options from the shortcut menu. 2. Click the Debug Log tab, and set the following options as appropriate:
Backup Exec Remote Agent Monitor Options, Debug Log tab Item Enable debug log Description Enables you to activate logging for a variety of Backup Exec services. Sets the level of detail included in the debug log files. Choices are Normal, Medium, and High. The level to be selected should be determined by Symantec Technical Support. In a default installation, Backup Exec log files reside in the Logs directory, in the following path: C:\Program Files\VERITAS\Backup Exec\NT\Logs If you installed Backup Exec to a different path, use that path instead.
Debug detail level
Debug log file location
3. If you make changes to the Debug Log tab, you must restart the Backup Exec Remote Agent for Windows Servers service before the changes take effect. 4. To restart the Remote Agent service, right-click the Remote Agent Monitor tray icon, click Tools, and then click Open Services. The local services appear. 5. Right-click the Backup Exec Remote Agent for Windows Servers service, and then click Restart. 6. When prompted to restart this service, click Yes.
802
Appendix
Symantec Backup Exec Remote Agent for Linux or Unix Servers

The Symantec Backup Exec for Windows Servers Remote Agent for Linux or Unix Servers (RALUS) is installed as a separate, add-on component that enables Windows Server network administrators to perform backup and restore operations on Linux, Unix and Solaris hosts that are connected to the network. This agent must be running on these computers before backup or restore operations can be performed. After the agent is configured, the UNIX host computers are ready for backup. When backing up data using the Remote Agent for Linux or Unix Servers, Backup Exec enables you to protect data using multiple backup types. These include:

Full Differential - Using modified time Incremental - Using modified time Working set
Requirements for the Remote Agent for Linux or Unix
Installation on a supported platform and file system. Supported platforms include: Redhat Advanced Server 2.1 and Redhat Enterprise Linux 3.0 (WS, AS or ES) on x86 using ext2, ext3, or VxFS file systems, Solaris 8 and 9 on 32 or 64 bit Sparc systems using Solaris file system or VxFS and Suse Linux Enterprise Server 8 on x86 using ext2, ext3, VxFS, ReiserFS, or JFS.
803
Installing the Remote Agent for Linux or Unix Servers
Caution RALUS has dependencies on other packages and libraries. These must be installed prior to installing RALUS. Installing RALUS on Redhat Enterprise Linux requires libstdc++-libc6.2-2.so.3 or later, which is provided by compat-gcc-c++-7.3-2.96.122.i386.rpm or a newer version. Dependent .rpm files may also have dependencies of their own.
Root, Super User, or Admin privileges are required on Linux and Unix hosts in order to install the Remote Agent for Linux or Unix. Access to a mounted CD-ROM drive. TCP/IP, which is used for communication with the Unix host computers, is required on the media server. RALUS can be installed on the same Unix host where the Backup Exec 8.x and 9.x Agent for Unix is installed. However, only one agent should be running at a time. Running both RALUS and the Backup Exec 8.x and 9.x Agent for Unix simultaneously is not supported. For information on disabling or enabling either of the agents, see RALUS and the Backup Exec 8.x and 9.x Agent for Unix on page 816.

Two methods are available for installing the Remote Agent for Linux or Unix Servers on a Unix host. You can use the RALUS installer provided on the Backup Exec for Windows Servers CD, or you can manually install RALUS from a tar file and then manually start the RALUS daemon.
To install RALUS from the Backup Exec for Windows Servers CD, see Installing RALUS Using the Installer on page 805. To manually install RALUS from a tar file, see Manual Install and Uninstall of RALUS on page 814. To manually start the RALUS daemon, see Manually Starting the RALUS Daemon on page 815.
Creating the BEOPER Group

In order to provide the ability to grant Backup Exec users access to hosts running RALUS during backup or restore operations, a group named beoper must exist on each host, or in the NIS domains group file. The RALUS installer by default will create the beoper group and add root as a member if a NIS server is not detected. The group must be created manually if the host machine is a member of a NIS domain.
Caution If the beoper group is not created by the RALUS installer or is not created manually, connections to the hosts from the Backup Exec media server will fail. When creating the group manually, do the following at each Unix host where RALUS will be installed. For hosts that are members of a NIS domain, refer to the NIS documentation for information on adding groups to a NIS domain.

Create the group beoper. When creating the group, use lowercase letters. After creating the beoper group, add all users to the group that should be granted rights to protect the Unix host with Backup Exec.
For more information on creating groups, see your Unix system documentation.
Installing RALUS Using the Installer

The Remote Agent for Linux and Unix Server installer is capable of installing the agent to both local and remote Linux, Unix and Solaris-based computers (Unix hosts). It is recommended that you install the software from a Unix host using the Backup Exec for Windows Servers CD and the push installation technology built into the installer. Installing the agent in this manner enables you to install it on multiple remote Unix hosts in the least amount of time possible. You can also take the Backup Exec for Windows Servers CD to the target hosts and locally install the software. In either case, you need to know the computer names of the Unix hosts where the software will be installed. Caution If the Backup Exec 8.x and 9.x Agent for Unix is installed on a Unix host, and you are installing RALUS on the same host, you must change the existing agent name in the Backup Exec 8.x and 9.x Agent for Unix configuration file, agent.cfg, before installing RALUS. Otherwise, RALUS will not run properly after it is installed. Modify the agent name in the configuration parameter, Name <hostname> in /etc/bkupexec/agent.cfg to any name besides the name you are using. After modifying the name, save the agent.cfg file and then run the RALUS installer. To install the Remote Agent for Linux or Unix Servers on the Unix host: 1. At a Unix host, place the Backup Exec for Windows Servers CD in a CD-ROM drive. 2. Connect to the target Unix host using a terminal session.
Appendix B, Symantec Backup Exec - Remote Agent for Linux or Unix Servers
805
3. Logon to the target computer with super user, root, or admin privileges. 4. Navigate to Remote Agent for Linux or Unix Servers installer on the Backup Exec CD using the following path: <device_name>/ralus/<platform_name>/installralus 5. At the command prompt, type: installralus and press ENTER. 6. Enter the name of a Unix host or hosts on which to install RALUS and press ENTER. When entering multiple host names, use spaces between each name. 7. After the installer successfully checks for a valid Unix host operating system during the initial system check, press ENTER. 8. After reviewing the package installation summary, press ENTER. 9. Press ENTER to start the RALUS installation requirements precheck. Note If you are running the Backup Exec 8.x and 9.x Agent for Unix, a message appears informing you that the Backup Exec 8.x and 9.x Agent for Unix will be disabled, but not uninstalled. Press ENTER to disable the Backup Exec 8.x and 9.x Agent for Unix and continue with the install process. If you do not want to disable the Backup Exec 8.x and 9.x Agent for Unix, the RALUS installer will terminate and exit and RALUS will not be installed. 10. Press ENTER after the RALUS installer installation requirements precheck completes. 11. Press ENTER when prompted, Are you ready to configure RALUS? [y,n,q] <y>. RALUS configuration consists of answering a set of configuration-related questions designed to guide you through the process of entering the IP address or the DNS name of the Backup Exec media server you want to back up the Unix host. 12. Read the RALUS configuration overview and then press ENTER. 13. Enter the Host Name or IP address of the Backup Exec media server you want to communicate with RALUS, and then press ENTER. When prompted, press either Y then ENTER to repeat the process of adding Backup Exec media servers, or press ENTER to continue. 14. Verify the Backup Exec media server configuration information is correct and then press ENTER.
15. Read the beoper group requirement and then press ENTER to start the NIS server scan. 16. Examine the results of the NIS server scan. If a NIS server is detected the RALUS installer is unable to create the beoper group and it must be done manually. If no NIS server is detected press ENTER to RETURN to have the installer scan for the beoper group and root membership. 17. If no beoper group is found, press ENTER to create the group or press <n> then ENTER if the group will be created manually. 18. Press Y then ENTER to enter a specific Group ID (GID) or press ENTER to have the installer select the next available GID. 19. Press ENTER to have the root user added as a member to the beoper group. Press <n> then ENTER if the account will be added manually. 20. Press ENTER to begin the installation. A message appears stating the installation has completed successfully after the installation finishes. 21. Press ENTER. After RALUS is configured, a message appears stating that the RALUS configuration has completed successfully. 22. Press ENTER. The installation summary, installralus log, and installation response files are saved to the following locations on the Unix host: Installation summary:
/opt/VRTS/install/logs/installralus<summary file number>.summary
Installralus log:
/opt/VRTS/install/logs/installralus<summary file number>.log
Installation response:
/opt/VRTS/install/logs/installralus<summary file number>.response
After the log files are saved, the Remote Agent for Linux or Unix Servers installation is complete.
807
The ralus.cfg File

In order to be backed up by a Backup Exec media server, the Unix hosts must communicate with a Backup Exec media server. To establish communications, the RALUS installer creates a configuration file named ralus.cfg on each Unix host where RALUS is installed. A ralus.cfg configuration file contains a list of Backup Exec media servers that you use to back up that particular Unix host. Since the same Unix host can be backed up by multiple Backup Exec media servers, there is no limit to the number of Backup Exec media servers that can be listed in the ralus.cfg file. Note Backup Exec media server entries in the ralus.cfg file are entered using either the media server name from a naming service provider such as DNS, NIS, or an IP address.
Editing the ralus.cfg File

You can add or delete Backup Exec media servers from the list of media servers found in a Unix host ralus.cfg file. Adding a media server to the list expands the number of media servers that can back up the Unix host, while deleting a media server removes it from the list of media servers to which it advertises itself. You can also modify naming information for a media server such as its DNS name or IP address. A Backup Exec media server entry in a ralus.cfg file conforms to a specific format, which must be followed to ensure communication between the media server and the Unix host.
Ralus.cfg Format Components

The ralus.cfg format contains three components. The first component (A) is a required string that must be entered exactly as pictured: SOFTWARE\VERITAS\Backup Exec\Agents\Agent Directory List The second component is a unique identifier followed by an equal sign (=). A unique identifier can consist of sequential numbers, letters or alpha-numeric characters. For example: 1, 2, 3 or A, B, C. You can also use AA, BB, CC, or A1, A2, B1, B2. Whatever unique identifier you decide to use must be unique if you list multiple Backup Exec media servers in the ralus.cfg file. The third component of the ralus.cfg format is the actual Backup Exec media server IP address or its naming-service accessible name. For example, a DNS name, hosts file name, or NIS name). When entering this information, do not use spaces.
808
Installing the Remote Agent for Linux or Unix Servers Ralus.cfg formatting example A B C
A = Required string B = Required and unique identifier (the order or appearance is irrelevant) C = Required DNS name or IP address
Editing a ralus.cfg file can be done using the Unix text editor, vi. However, any basic text editor can be used for editing purposes. File and Directory Exclusions in ralus.cfg You may have files and directories on the UNIX hosts that you do not want to backed up. Rather than manually deselecting them when making backup selections, you can enter file and directory exclusion information in the ralus.cfg file. After the information is added, the file and directories are ignored and will not be backed up.
File and Directory Exclusions in the ralus.cfg File
A A = Required string B = Required and unique identifier (the order or appearance is irrelevant) C = File or directory to be excluded
809
Using the Remote Agent for Linux or Unix Servers

After installing the Remote Agent for Linux or Unix Servers, you can make backup selections from your Unix hosts and then run backup jobs.
Making Backup Selections with RALUS

RALUS-installed Unix hosts appear in the Selections pane in the Unix Agents node under Remote Selections.
RALUS-installed Unix Agents
On initial access of the Unix host, a Logon Account Selection screen appears stating that the system logon account used by Backup Exec to access to the Unix host has failed, and that access to the Unix host is denied. To proceed, a new logon account must be created for the Unix host using credentials that allow access to the Unix host. Note The logon account credentials you provide during the creation of logon account used during the initial access of the Unix host are stored by Backup Exec. These credentials will be used again when making future backup selections from the
810
Unix host. However, if the access credentials for the Unix host change, a new Backup Exec Unix host logon account will need to be created in order to access the host. Use the following steps to add logon credentials for the Unix host. To add logon credentials: 1. In Backup Job Properties, double-click Remote Selections. 2. Double-click Unix Agents. 3. Double-click the desired Unix host. A Logon Account Selection screen appears stating that the Backup Exec System Logon Account failed to access the Unix host. 4. On the Logon Account Selection screen, click New. 5. Add account credentials for the Unix host and then click OK. Note Credentials supplied for the Unix host must have root or super user privileges that can be authenticated by the Unix host.
Add Logon Credentials dialog box Item User name Description The user name required to access the Unix host. This name must have root, super user, or admin rights, which can be authenticated by the Unix host. The password used to access the Unix host. The same password entered in the Password field, which is used to confirm the password was entered correctly in the Password field. A label you enter to name the logon account. Pertinent notes about the account.
Password Confirm password
Account name Notes
6. After authenticating the credentials entered, access to the Unix host is granted and backup selections can be made.
811
Setting Linux/Unix Properties for RALUS-based Backup Jobs

After making backup selections, job properties for the Unix host backup jobs should be set. Job properties specifically targeted to Unix and Linux backup jobs are found in the Job Properties pane under both Linux/Unix and General. Use the following steps to set the backup job properties. To set backup job properties for RALUS-based backup jobs: 1. After making backup selections from the Unix host, from Properties, under Settings, click Linux/Unix. The following options appear:
Linux/Unix options Item Preserve change time Description Use this option to prevent RALUS from changing an objects (files and directories) attributes when a backup occurs. Normally, during a backup, Backup Exec preserves an objects last access timestamp by resetting the last access timestamp to the value before the backup occurred. When Backup Exec modifies the objects last access timestamp, the Linux/Unix operating system internally updates the objects ctime. An objects ctime is the time when an objects attributes (permissions, timestamps, etc.) have been modified. If the attributes are not changed by RALUS after a backup, the objects ctime will not change. This option does not affect object attributes set during restore operations. Use this option to have Backup Exec follow local mount points when backing up data. For more information on local mount points, see your Unix/Linux documentation. Use this option to have Backup Exec follow remote mount points when backing up data. For more information on remote mount points, see your Unix/Linux documentation.
Follow local mount points
Follow remote mount points
Back up contents of Use this option to back up the contents of directories that are linked soft-linked directories using soft links. For more information on soft linked directories, see your Unix/Linux documentation. Lock remote files Use this option if RALUS requires exclusive access to the files on remote systems connected through Network File System (NFS).
2. Make the appropriate selections or use the default selections provided. 3. Click General in the Properties pane of the Backup Job Properties screen.
Uninstalling the Remote Agent for Linux or Unix Servers
4. In the list box for Backup method for files, select Full - Back up files - Using modified time rather than Full - Back up files - Using archive bit (reset archive bit), as the concept of an archive bit is not valid in Unix environments.
Uninstalling the Remote Agent for Linux or Unix Servers

The Remote Agent for Linux or Unix Servers installer is capable of uninstalling the agent from both local and remote Unix hosts. To uninstall the Remote Agent for Linux or Unix Servers on the Unix host: 1. At a Unix host, place the Backup Exec for Windows Servers CD in a CD-ROM drive. 2. Logon to the target computer with Super User, root, or admin privileges. 3. Navigate to Remote Agent for Linux or Unix Servers uninstaller on the Backup Exec CD using the following path: <device_name>/ralus/<platform_name>/uninstallralus 4. At the command prompt, type: uninstallralus and press ENTER. 5. Enter the name of a Unix host or hosts on which to uninstall RALUS and press ENTER. When entering multiple host names, use spaces between each name. 6. Press ENTER after the RALUS package check completes successfully. 7. Press ENTER when prompted, Are you sure you want to uninstall RALUS packages? [y,n,q] <y>. The removal of the Remote Agent for Linux or Unix Servers begins. A message appears stating the removal process has completed successfully, after the uninstaller finishes. 8. Press ENTER. The uninstallation summary, and uninstallralus log files are saved to the following locations on the Unix host: Uninstallation summary:
/opt/VRTS/install/logs/uninstallralus<summary file number>.summary
Uninstallralus log:
/opt/VRTS/install/logs/uninstallralus<summary file number>.log
After the log files are saved, the Remote Agent for Linux or Unix Servers uninstall is complete.
Appendix B, Symantec Backup Exec - Remote Agent for Linux or Unix Servers 813
Manual Install and Uninstall of RALUS

In some cases, you may want to manually install or uninstall RALUS. Or you may want to manually start and stop the RALUS daemon. This section guides you through the steps required to run these manual processes. Caution If the Backup Exec 8.x and 9.x Agent for Unix is installed on a Unix host, and you are installing RALUS on the same host, you must disable the existing Backup Exec 8.x and 9.x Agent for Unix before installing RALUS. Otherwise, RALUS will not run properly after it is installed. To disable the Backup Exec 8.x and 9.x Agent for Unix, see Disabling the Backup Exec 8.x and 9.x Agent for Unix: on page 816.
Manually Installing RALUS from a TAR File

Use the following steps to manually install RALUS. To manually install RALUS: 1. Connect to the target Unix host as the root user using a terminal session. 2. Create a new directory and change to it. 3. Place the Backup Exec CD in the CD-ROM drive. 4. Navigate to the ralus.tar file on the CD using the following path, and then copy it to the new directory you created in step 2.
<CD_ROM_drive_name>/ralus/<platform_name>/pkgs/<platform_name>/ralus.tar
For example: /ralus/linux/pkgs/linux/ralus.tar 5. Extract the contents of the ralus.tar file using tar -xf ralus.tar (use tar xf ralus.tar on Unix hosts running the Solaris operating system). 6. Change the owner for all RALUS files to root / id 0 (zero) using chown -R 0 etc opt var. 7. Change the group for all RALUS files to id 0 (zero) using chgrp -R 0 etc opt var. 8. Change the permissions for all RALUS binaries using chmod -R 0500 opt.
814
9. Change the permissions for all other RALUS files using chmod -R 0600 etc var 10. Copy the RALUS files to their target destinations using cp -r etc opt var / 11. Change to the /opt/VRTSralus/bin directory. 12. Execute the VRTSralus.service-install script to enable RALUS to start up as a daemon. 13. Reboot the host or start up the RALUS daemon.
Manually Uninstalling RALUS

Manually uninstalling RALUS should only be done if RALUS has been manually installed. To manually uninstall RALUS: 1. Connect to the target Unix host as the root user using a terminal session. 2. Stop the RALUS daemon. 3. Change to the /opt/VRTSralus/bin directory. 4. Execute the VRTSralus.service-uninstall script to remove RALUS daemon initialization files. a. On HP-UX systems, the line containing opt/VRTSralus/bin/VRTSralus.init must be manually removed from the /etc/inittab file.
5. Remove all RALUS files from the Unix host using rm -r /etc/VRTSralus /opt/VRTSralus /var/VRTSralus
Manually Starting the RALUS Daemon

After manually installing RALUS, you must manually start the RALUS daemon. To manually start the RALUS daemon: 1. Connect to the target Unix host as the root user using a terminal session. 2. Issue the following startup command:
Appendix B, Symantec Backup Exec - Remote Agent for Linux or Unix Servers 815
RALUS and the Backup Exec 8.x and 9.x Agent for Unix
/etc/init.d/VRTSralus.init start
Manually Stopping the RALUS Daemon

Use the following steps to manually stop the RALUS daemon. To manually stop the RALUS daemon: 1. Connect to the target Unix host as the root user using a terminal session. 2. Issue the following stop command: /etc/init.d/VRTSralus.init stop
Both the Backup Exec 8.x and 9.x Agent for Unix and RALUS can be installed together on the same host, but only one can be running at one time. If you are manually installing RALUS and the Backup Exec 8.x and 9.x Agent for Unix is already installed, the Backup Exec 8.x and 9.x Agent for Unix must be disabled. After disabling the Backup Exec 8.x and 9.x Agent for Unix, proceed with the manual RALUS installation. Use the following steps to disable/enable the Backup Exec 8.x and 9.x Agent for Unix. Disabling the Backup Exec 8.x and 9.x Agent for Unix: 1. On the Unix host, kill all processes named agent.be. 2. Rename the Backup Exec 8.x and 9.x Agent for Unix binary /etc/bkupexec/agent.be to etc/bkupexec/agent.be.disabled. Enabling the Backup Exec 8.x and 9.x Agent for Unix: 1. On the Unix host where the Backup Exec 8.x and 9.x Agent for Unix was disabled, kill all processes named beremote, which are the processes used by RALUS. 2. Rename the Backup Exec 8.x and 9.x Agent for Unix binary /etc/bkupexec/agent.be.disabled to etc/bkupexec/agent.be 3. Start the Backup Exec 8.x and 9.x Agent for Unix as usual or reboot the host.
816
Disabling RALUS: 1. On the Unix host, kill all processes named beremote. 2. Rename the RALUS binary /opt/VRTSralus/bin/beremote to /opt/VRTSralus/bin/beremote.disabled. Enable RALUS: 1. On the Unix host where RALUS was disabled, kill all processes named agent.be, which are the processes used by the Backup Exec 8.x and 9.x Agent for Unix. 2. Rename the RALUS binary /opt/VRTSralus/bin/beremote.disabled to /opt/VRTSralus/bin/beremote. 3. Start RALUS as usual or reboot the host.
817
818
Appendix
Symantec Backup Exec Central Admin Server Option

The Symantec Backup Exec for Windows Servers - Central Admin Server Option (CASO) is installed as a separate, add-on component of Backup Exec for Windows Servers 10.0. If your organization includes more than one Backup Exec media server, you may benefit from CASO. Related Topics: The Central Admin Server Option Components on page 820 Features of the Central Admin Server Option on page 825 How the Central Admin Server Option Works on page 821 Requirements for Installing the Central Admin Server Option on page 828
About the Central Admin Server Option

CASO enables you to maximize your investment in Backup Exec for Windows Servers by providing centralized administration and delegated job processing and load balancing functionality for Backup Exec for Windows Servers media servers in your storage environment. CASO transforms your stand-alone Backup Exec media server-based environment into a centrally managed data protection enterprise, built on the following concepts:
Use of a Backup Exec for Windows Servers media server as a centralized administration server. Use of the central administration server to store catalogs, device and media information, policies, jobs and selection lists. Job log information generated by the managed Backup Exec media servers can also be stored on this central server.
819
Use of your existing storage hardware through the use of job delegation concepts across media servers. Use of existing storage hardware using job delegation concepts, which enables you to automatically distribute the processing of backup and restore jobs to various Backup Exec media servers on your network. Use of a scalable architecture to handle the future growth of data on your network.
With the Central Admin Server Option installed, you can group your existing Backup Exec media servers into logical media server pools. Using these pools, you can restrict protected server backup jobs to a selected set of Backup Exec managed media servers, while also implementing the CASO job delegation feature. Job delegation automatically load balances jobs to any available Backup Exec managed media server in your environment. As additional managed media servers become available, additional jobs can be delegated for processing. Restore operations are initiated at the managed media servers by default. However, with CASO, you also have the option of centralizing the restore process by running restore jobs from the central administration server. Related Topics: How the Central Admin Server Option Works on page 821 Requirements for Installing the Central Admin Server Option on page 828
The Central Admin Server Option Components

The CASO components include: a. Central administration server (CAS). The central administration server is configured as both a managed media server and as the central administration server. As a central administration server, its tasks include:
creating backup jobs by creating policies and selection lists from a centralized location. centralizing job delegation by targeting a managed media server to run a job and then delegating the job to the selected managed media server for processing. all job policy functionality. the management of notification and alerts. job monitoring. job history and job logs.
The central administration server is also used to centralize:

820
Note The central administration server can also be used to run centralized restore jobs. However, you must centralize the storage of all catalogs produced during backup operations at the individual media servers on the central administration server. For more information, see CASO Restore Operations and Centralized Catalogs on page 861. b. Managed media servers. These Backup Exec media servers, with one or more storage devices attached to them, are managed by the central administration server. They are responsible for the actual processing of backup and restore jobs. By default, the catalogs produced by managed media servers are stored locally at the managed media server where they are produced. However, as an option, you can override the default catalog storage location and select the central administration server as the catalog storage location. Note A central administration server can also be targeted as a managed media server to process jobs. Related Topics: Requirements for Installing the Central Admin Server Option on page 828
How the Central Admin Server Option Works

In a CASO-enabled Backup Exec environment, a group of standard stand-alone Backup Exec media servers are managed and monitored from a Backup Exec media server where CASO has been installed. This media server, known as the central administration server, becomes the focal point of a CASO-based Backup Exec data protection environment, and it is where all Backup Exec-related administration tasks occur. The remaining media servers become managed media servers, which are managed using the central administration server. After configuring a CASO environment, you create policies and selection lists at the central administration server. Jobs created from these policies and selection lists can use the CASO job delegation feature, which automatically delegates Backup Exec jobs among the various storage devices connected to the managed media servers in the CASO environment.
Appendix C, Symantec Backup Exec - Central Admin Server Option
821
CASO Configuration Scenarios

The following diagrams show implementations of CASO in a Backup Exec environment, beginning with a diagram of a typical Backup Exec installation. This diagram shows a typical local area network environment where multiple Backup Exec media servers are configured independently of each other. As such, each media server processes jobs independently. Administration tasks for each media server are handled at the individual media servers.
Stand-alone Backup Exec environment without the CASO option installed
Stand-alone Backup Exec 10.0 media servers
The next diagram shows a local area network environment where one Backup Exec media server is designated as the central administration server, while other media servers become managed media servers, communicating directly with, and being managed and monitored from, the central administration server. Backup Exec jobs can also be delegated by the central administration server to each of the managed media servers for processing.
822
About the Central Admin Server Option CASO-configured Backup Exec Environment - Local Area Network Local Area Network
The next diagram shows a wide area network implementation of Backup Exec with the Central Admin Server Option installed.
823
About the Central Admin Server Option CASO-configured Backup Exec Environment - Wide Area Network
Wide Area Network Windows Data Center Backup Exec 10.0 Central Administration Serve - Device and media - Policies - Job histories - Centralized catalogs Managed Media Servers
Jobs
Protected Servers Remote branch office
Jobs Jobs
Jobs
Remote branch office Managed Media Servers Protected Servers
Managed Media Servers (Backup Exec 10.0)
Remote branch
Jobs
Managed Media Servers (Backup Exec 10.0)
The final diagram shows CASO installed in a Backup Exec SAN Shared Storage Network environment.
CASO-configured Backup Exec Environment - SAN Shared Storage Network
Managed media servers not attached to the SAN
LAN Managed media servers attached
Primary Database Server/Central administration server
Fibre-to-SCSI bridges SCSI tape libraries
824
Features of the Central Admin Server Option

Before implementing the Central Admin Server Option, familiarize yourself with the following CASO features:

Job Processing and Job Delegation with CASO on page 825 Policies with CASO on page 826 Centralized Catalog Storage with CASO on page 826 Centralized Reports on page 826 Centralized Restore on page 827 Centralized Job Logs and History Details on page 827 Centralized Alerts on page 827 Using CASO to Maintain Backup Exec Network Storage Executive 8.6 Functionality on page 827 Using Media Server Pools in CASO on page 866 Using the Central Admin Server Option with Microsoft Clusters and SAN SSO on page 678
Job Processing and Job Delegation with CASO Job delegation is the automatic load balancing of jobs among the various storage devices attached to the Backup Exec managed media servers. These storage devices, when logically grouped in drive pools, process jobs delegated from the central administration server as they become available. For example, if a device pool contains two storage devices and one is busy processing a job, the central administration server automatically delegates another job to the idle storage device. Jobs are automatically created and submitted to the central administration servers job queue after a policy is applied to a selection list. Queued jobs are processed in priority order. Depending on job parameters and system configuration, the central administration server then delegates jobs to available storage devices in a selected device pool. Templates within a policy can be targeted to either a device pool or a specific device. Device pools can consist of devices attached to a single managed media server, or they can consist of devices from different managed media servers. The advantage of job delegation is realized when a template is targeted to a drive pool that spans managed media servers. When multiple managed media servers and their devices are available to the central administration server for job delegation, the efficiency of Backup Exec for Windows Servers is greatly improved because job processing does not have to wait for a specific device or managed media server to become available.
825
For more information on device pools, see Managing Devices on page 123. After the job is processed, the following occurs:
The managed media server retrieves all relevant job completion information and forwards it to the central administration server. If the job ends in an error, the central administration server determines what to do with the job by invoking error-handling rules that specify how the job will be handled if an error condition appears. The managed media server creates a set of catalogs for the processed job, and then moves the catalog set to the central administration server or a designated catalog server for storage.
Policies with CASO Default and user-defined Backup Exec policies are supported using CASO. For more information about policies, see Policies and Templates on page 361. Centralized Catalog Storage with CASO Backup Exec catalogs created on individual stand-alone media servers are stored locally, at the media server where they are created. After CASO is installed and configured, you have the option of either continuing to store catalogs locally at the media server where they are produced, or moving them to the central administration server for centralized storage. Storing catalogs on the central administration server enables you to initiate restore operations from the central administration server, rather than having to run restore operations at each managed media server. For more information on centralizing the catalog storage location, see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840. Centralized Reports Centralized reports are available and can be viewed at the central administration server for all delegated jobs that use the CASO job delegation feature. Reports for jobs that are initiated and run locally at the managed media server, (which are not initiated at the central administration server), cannot be viewed from the central administration server. However, as with stand-alone media servers, the reports can be viewed at the media server where the jobs run. For more information on Backup Exec reports, see Reports on page 543.
826
Centralized Restore Using the Central Admin Server Option, you can run restore operations from a central administration server, or you can run restore operations from each of the managed media servers where the backup jobs occurred. When using the centralized restore feature, restore jobs are created and submitted to the central administration server job queue for job delegation among the managed media servers in the media server pool. For more information, see How Centralized Restore Works on page 862. Centralized Job Logs and History Details Job logs and the job history for each job can be automatically copied from the managed media servers to the central administration server, giving you access to the information from a either the central administration server or the managed media servers. For more information, see Setting Job Log and Job History Options for Managed Media Servers on page 844. Centralized Alerts Using CASO, alerts generated at the managed media server are sent to the central administration server, where they are displayed. For more information, see Configuring CASO Alerts on page 845. Using CASO to Maintain Backup Exec Network Storage Executive 8.6 Functionality Sites running Symantec Network Storage Executive version 8.6 can use the Central Admin Server Option to migrate existing NSE 8.6 installations to Backup Exec for Windows Servers 10.0 and the Central Admin Server Option. By providing a migration path for existing NSE 8.6 installations, you maintain the centralized benefits of your previous NSE installations while incorporating the latest in technology with the Central Admin Server Option. For more information, see Migrating from Network Storage Executive v8.6 (NSE) on page 838. Media Server Pools with CASO CASO enables you to group multiple managed media servers together in media server pools. Media server pools can be used to restrict protected server backup jobs to a specific set of managed media servers and their attached storage devices. And because media server pools are associated with selection lists, the restrictions they encompass are defined by the selection lists being protected.
827
To configure media server pools, see Using Media Server Pools in CASO on page 866. CASO in a Clustered Environment CASO is fully configurable in a Microsoft Cluster Server environment. For more information see Using Symantec Backup Exec with Server Clusters on page 657.
Requirements for Installing the Central Admin Server Option
Administrative rights on both the Windows 2000 or higher computers where you will be installing the Central Admin Server Option. When installing CASO on media servers in multiple domains, the Backup Exec service account should reside in the trusted domain and should have administrative rights on all media servers to be managed by the central administration server. Backup Exec for Windows Servers 10.0 must be installed on the media server you target as the central administration server. 512 MB RAM required, 1 GB recommended.
Note The system requirements (except RAM) for running the Central Admin Server Option follow the minimum requirements for running Backup Exec for Windows Servers 10.0. However, processor speed, memory, and disk space requirements may increase based on the number of managed media servers being managed, the number of protected servers being backed up, and the amount of catalog storage space required. Related Topics: Installing the Central Admin Server Option on page 832
828
Getting Started with the Central Admin Server Option

Installing and configuring CASO is a multi-step process. The steps vary depending on whether you are installing Backup Exec and CASO for the first time or if you are upgrading existing installations of Backup Exec or NSE to CASO. If you are installing Backup Exec and CASO for the first time, follow the steps in To install and configure Backup Exec and CASO for the first time: on page 829. If you are upgrading existing installations of Backup Exec or NSE to CASO, follow the steps in To upgrade existing Backup Exec or NSE installations to CASO: on page 830. To install and configure Backup Exec and CASO for the first time: Symantec recommends that you follow these steps in the order provided to ensure successful installation and configuration of CASO. 1. Determine which media server will be the central administration server, and then install CASO on that media server. You should install CASO only on the media server that you selected to be the central administration server. Be sure to add serial numbers for all options you want to support in your CASO configuration. For instructions on installing Backup Exec options, see Installing Backup Exec Using the Installation Program on page 67. 2. Launch Backup Exec on the central administration server and verify that the Media Servers view displays on the navigation bar. Then from the Media Servers view, verify that Central Administration Server displays in the Media Server Type column for the media server on which you installed CASO. 3. Determine which media servers will be the managed media servers in the CASO environment, and then install Backup Exec with the Managed Media Server feature enabled on each media server. When you install the Managed Media Server feature on a media server, you must enter the name of the central administration server with which the managed media server will communicate. For instructions on installing the Managed Media Server feature, see Installing Managed Media Servers on page 832. 4. Push-install the Backup Exec Remote Agent to all servers you want to back up. For more information, see Installing Backup Exec Agents to Remote Computers on page 77. 5. (Optional) Configure the default options for the managed media servers. You can configure the following:
829
The frequency that Backup Exec sends job logs and job history information from the managed media server to the central administration server. For more information, see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840. The amount of time that Backup Exec waits before changing the media servers status if the media server becomes unresponsive. For more information, see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840. When job log and job history information is sent to the central administration server. For more information, see Setting Job Log and Job History Options for Managed Media Servers on page 844. Centralized catalogs. For more information, see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840.
6. Configure what you want to back up.

Create selection lists for all resources you want to back up. Configure the selection list properties.
For more information about configuring selection lists, see Using Selection Lists on page 293. 7. Configure where you want to back up data. If you want to configure server fault tolerance and load balancing, create one or more device pools that represent the managed media servers on which delegated jobs can run. For more information, see Using Device Pools on page 132. 8. Use policies and templates to configure how and when to back up data. For more information, see Policies and Templates on page 361. 9. Create jobs by associating selection lists with policies. For more information, see Creating Jobs Using Policies on page 378. 10. Use the Job Setup view to review the jobs you created. 11. Use the Job Monitor view to monitor the active and scheduled jobs. The Media Server column indicates which managed media server an active job is running on. For more information, see Monitoring Jobs on page 405. To upgrade existing Backup Exec or NSE installations to CASO: Symantec recommends that you follow these steps in the order provided to ensure successful installation and configuration of CASO.
830
1. Determine which media server will be the central administration server, and then install CASO on that media server. You should install CASO only on the media server that you selected to be the central administration server. For instructions on installing CASO on an existing Backup Exec media server or NSE backup server, see Upgrading a Backup Exec Media Server to a Central Administration Server on page 836. 2. Launch Backup Exec on the central administration server and verify that the Media Servers view displays on the navigation bar. Then from the Media Servers view, verify that Central Administration Server displays in the Media Server Type column for the media server on which you installed CASO. 3. Determine which existing media servers will be the managed media servers in the CASO environment, and then set the central administration server for the media servers. For instructions on setting the central administration server for media servers, see Setting a Central Administration Server for Stand-alone Media Servers on page 837. 4. Push-install the Backup Exec Remote Agent to all servers you want to back up. For more information, see Installing Backup Exec Agents to Remote Computers on page 77. 5. (Optional) Configure the default options for the managed media servers. You can configure the following:
The frequency that Backup Exec sends job logs and job history information from the managed media server to the central administration server. For more information, see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840. The amount of time that Backup Exec waits before changing the media servers status if the media server becomes unresponsive. For more information, see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840. When job log and job history information is sent to the central administration server.Setting Job Log and Job History Options for Managed Media Servers on page 844. Centralized catalogs. For more information, see Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840.
831
Installing the Central Admin Server Option

CASO installation consists of installing software components that convert existing stand-alone Backup Exec media servers to CASO managed media servers or to a central administration server. After installing the central administration server software, you can then convert stand-alone Backup Exec 10.0 media servers to CASO managed media servers. Before beginning the installation, determine which existing Backup Exec media server to designate as the central administration server and which Backup Exec media servers to designate as managed media servers. After making this determination, start by installing the central administration server software first, followed by the managed media server components. If you are installing Symantec Backup Exec for Windows Servers and the Central Admin Server Option for the first time, see Installing Backup Exec on page 57. During the initial installation of Backup Exec, a prompt appears asking for serial numbers for Backup Exec and any additional add-on options to be installed. Enter the Central Admin Server Option serial number and continue with the installation. If you want to upgrade an existing Backup Exec media server to a central administration server, see Upgrading a Backup Exec Media Server to a Central Administration Server on page 836. After you have installed the central administration server, you should install managed media servers.
Installing Managed Media Servers

After installing the central administration server, you can push-install the managed media server feature to any stand-alone server. To push-install managed media servers from the central administration server: 1. On the central administration servers navigation bar, click Media Servers. 2. In the task pane, under Media Server Tasks, click Install additional managed media servers. 3. When the Welcome screen displays, click Next to begin the installation wizard. 4. Right-click Backup Exec Servers, and then do one of the following:
Click Add Remote Computer, and then browse the list to select all of the remote computers that you want to install an option to, and then click Next.
832
Click Add Remote Computer Manually, and then type the Domain and Computer Name, and then click OK. Add as many remote computers as you want to install Backup Exec to.
5. Enter the user name, password, and domain of an account that has administrative rights on the remote computers, and then click OK. Note To avoid entering credentials separately for each remote computer that you have selected, click Use this user name and password when attempting to connect to additional computers during the installation. 6. On the Remote Installation Types dialog box, select Remote install with serialized options, and then click Next. 7. On the Remote Destination Folder dialog box, enter the folder to which the Backup Exec media server files on the remote computer will be installed, and then click OK. The default location is C:\Program Files\VERITAS\Backup Exec\NT. 8. Type the serial numbers for Backup Exec and any options that you want to install. Click Add after entering each serial number. When finished, click Next. To import the serial numbers from an existing besernum.xml file, click Import, and then browse for and select an existing besernum.xml file. When finished, click Next. The serial numbers you entered are saved to the file besernum.xml, located in the Windows directory. Note A unique serial number must be entered for each option for each remote computer that you are installing to. If a previous installation of a Backup Exec 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 a fully functional Evaluation version. 9. Provide a user name and password that the Backup Exec system services can use (see The Backup Exec Service Account on page 66), and then click Next. The Symantec Backup Exec Database dialog box appears, and you are prompted to select a location on which to store the Backup Exec database. 10. Do one of the following:
833
Choose to create a local Backup Exec MSDE instance on which to store the Backup Exec database, and then click OK. For more information about creating a local Backup Exec MSDE instance, see Microsoft SQL Server 2000 Desktop Engine (MSDE) Components Installed with Backup Exec on page 57. Choose to use an existing SQL Server 2000 instance (with service pack 3a installed) that is on the network. You are prompted to select an instance from a list, or to type the instance name, and then click OK. Backup Exec will attempt to connect to the instance.
Note When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, you must replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up. When Backup Exec is installed into an existing instance, the Cluster Configuration Wizard is not available. 11. If prompted, select how the VERITAS device driver Installer should install device drivers for the tape storage devices that are connected to the server, and then click OK. It is recommended that you select Use VERITAS device drivers for all tape devices. 12. Type the name of the central administration server with which this managed media server will communicate, and then click OK. 13. Under Backup Exec for Windows Servers, verify that Managed Media Server is selected, and then click Next. If you are prompted, enter information or choose settings for additional options being installed. Click Next after each selection. 14. Read the Backup Exec installation review, and then click Install. 15. When the installation finishes, restart the computer. After restarting the managed media server, the Backup Exec central administration server and the managed media server begin communicating with one another. Each managed media server name is also added to the Media Server view on the central administration server. Related Topics: Installing Backup Exec to Remote Computers on page 73
Installing Managed Media Servers Behind a Firewall

If you are installing a managed media server across a firewall:
Database connections require an open SQL port in both directions to the central administration servers database. Port 3527 needs to be open in both directions to enable communication for the Backup Exec Server service. An open port range is required for the Remote Agent for Windows Servers, which will allow browsing for remote selections.
In addition, the Alias for the managed media server must be set up correctly. To set up the Alias for managed media servers: 1. On the central administration server, use the svrnetcn.exe utility to determine the port on which the Backup Exec SQL instance is running. The svrnetcn.exe utility is located in \Program Files\Microsoft SQL Server\80\Tools\Binn. a. On the General tab, select the Backup Exec SQL instance. b. Under Enabled Protocols, select TCP/IP, and then click Properties. 2. On the managed media server, use the SQL Server Client Network Utility (cliconfg.exe) to create an alias for the managed media server The cliconfg.exe utility is located in \Windows\System32. a. On the Alias tab, click Add. server name\instance name c. Under Network libraries, select TCP/IP. server name\instance name e. f. Clear the Dynamically determine port check box In the Port number field, type the port number of the remote Backup Exec SQL Server instance. d. In the Server name field, type: b. In the Server alias field, type:
Related Topics: Using Backup Exec with Firewalls on page 341.
835
Upgrading a Backup Exec Media Server to a Central Administration Server

This section guides you through the installation steps required to convert an existing stand-alone Backup Exec media server or a Network Storage Executive 8.6 Master Server to a central administration server. Note If you are upgrading Network Storage Executive 8.6, the terms media server and Backup Server are interchangeable in these steps. For more information on upgrading NSE 8.6, see Migrating from Network Storage Executive v8.6 (NSE) on page 838. To install the central administration server software: 1. Move to the stand-alone Backup Exec for Windows Server 10.0 media server that is designated as the central administration server. 2. Start Backup Exec. 3. From the Tools menu, click Serial Numbers and Installation. 4. From the Welcome screen, click Next to proceed with the installation. 5. Select both Local Install and Add Symantec Backup Exec options on this computer if these options are not selected. 6. Enter the Central Admin Server Option serial number and then click Add. Note Existing Backup Exec serial numbers for the options presently installed on this media server appear in the Existing Serial Numbers field. 7. Click Next. 8. Enter Backup Exec Service Account information. 9. Click Next and follow the directions. 10. Click Finish when the Symantec Install Wizard Completed screen appears. The central administration server installation is finished. Related Topics: Using CASO to Maintain Backup Exec Network Storage Executive 8.6 Functionality on page 827
836
Setting a Central Administration Server for Stand-alone Media Servers

If you have stand-alone Backup Exec for Windows Servers 10.0 media servers and you want to use them as managed media servers in a CASO environment, the stand-alone media servers need to be added to the central administration server database. Use the following steps to set the central administration server for the stand-alone media servers. To set the central administration server for a stand-alone media server: Note Before implementing these steps, make sure the central administration server is running. 1. Start Backup Exec at the stand-alone media server. 2. From the Tools menu, click Set Central Administration Server. 3. Enter the name of the central administration server. An informational alert appears stating that the media server will be managed by the specified central administration server. 4. Click OK. 5. Click Close. 6. Restart the Backup Exec media server. 7. At the central administration server, start Backup Exec. 8. From the navigation bar, click Media Servers. The new managed media server appears in the All Media Servers node.
837
Migrating from Network Storage Executive v8.6 (NSE)

Migrating an existing Network Storage Executive 8.6 installation to Backup Exec for Windows Servers and the CASO option requires you to install Backup Exec for Windows Servers 10.0 with the Central Admin Server Option over the existing NSE 8.6 installation on the NSE Master. Note Backup Exec for Windows Servers 10.0 only supports the migration of Network Storage Executive 8.6; earlier versions of Network Storage Executive cannot be migrated. After migrating the NSE Master to a Backup Exec central administration server, you then migrate each NSE Backup Server by installing Backup Exec for Windows Servers 10.0 with the Managed Media Server feature enabled, over the existing NSE 8.6 installation. During the migration process, all NSE policy definitions and tasks that reside in the NSE Masters BENSE database are migrated into the central administration servers Backup Exec Database. During the migration, NSE policy definitions are converted to Backup Exec policies, while the NSE tasks inside those policy definitions are converted to Backup Exec templates inside the new Backup Exec policies. For example, a NSE policy definition consisting of three tasks is converted to a Backup Exec policy containing three templates. In order to maintain the precedence order among the tasks within a NSE policy definition during the migration process, Backup Exec applies the template rule, If start times conflict to some of the NSE tasks it converts during the conversion process. After finishing the migration process, the new Backup Exec policies will contain the required template rules required to support the implied NSE task precedence that was implemented in the original NSE policy definition. Note When you upgrade from NSE to Backup Exec, the NSE Management Information Base (MIB) and Windows Management Instrumentation (WMI) files are removed. For information about how MIB and WMI files were used in NSE, refer to the NSE 8.6 Administrators Guide. Caution If you are migrating from NSE and you have many protected servers to be migrated, the migration process can take an extreme amount of time, as each protected server must be accessed. For more information, see the Symantec Technical Support website. Related Topics: Setting Template Rules on page 373
838
Using CASO to Maintain Backup Exec Network Storage Executive 8.6 Functionality on page 827 Upgrading a Backup Exec Media Server to a Central Administration Server on page 836 Installing Managed Media Servers on page 832
Uninstalling Backup Exec from the Central Administration Server

Uninstalling Backup Exec from a central administration server must be done in the following sequence: 1. From the central administration server, delete each media server from the Media Servers view. For more information, see Deleting a Managed Media Server from the Media Servers View on page 852. 2. After deleting all managed media servers, uninstall Backup Exec on the central administration server. For more information, see Uninstalling Backup Exec on page 93. Caution Failure to uninstall in this sequence may result in long delays when shutting down Backup Exec services during the uninstall of Backup Exec on the managed media servers.
Uninstalling Backup Exec from a Managed Media Server

1. From the central administration server, delete the managed media server from the Media Servers view. For more information, see Deleting a Managed Media Server from the Media Servers View on page 852. 2. After deleting the managed media server from the Media Servers view on the central administration server, uninstall Backup Exec from the managed media server. For more information, see Uninstalling Backup Exec on page 93.
839
Configuring the Central Admin Server Option

This section guides you through the configuration options for the Central Admin Server Option. These options include:
Configuring Managed Media Server Time Thresholds and Catalog Storage Locations on page 840 Setting Job Log and Job History Options for Managed Media Servers on page 844 Configuring CASO Alerts on page 845 Configuring CASO Notification on page 847
Configuring Device Pools

Device pools are an integral component of the CASO job delegation feature. Without them, the load balancing component of the job delegation feature will not work. If you want to use the CASO job delegation feature, it is important that you create one or more device pools. Related Topics: Using Device Pools on page 132. Creating Device Pools on page 133.
Configuring Managed Media Server Time Thresholds and Catalog Storage Locations
You can set managed media server time threshold options and catalog storage locations for each managed media server being managed by the central administration server. These options include:

Setting time thresholds for handling unresponsive managed media servers. Setting the time between job status updates. Setting time drift alerts. Setting the catalog storage location.
Communication Statuses and Time Thresholds In a CASO environment, communications about jobs that occur between managed media servers and the central administration server can sometimes be disrupted even if network communications between both computers are fine. If job-related communication disruptions occur between a managed media server and the central
administration server, the managed media servers communication status changes from Enabled to Stalled, and the jobs waiting to be processed by the managed media server are held in the managed media servers job queue until the communications are restored. You can set the amount of time that Backup Exec waits before changing the managed media servers status if it becomes unresponsive. The configuration settings use time thresholds, which, if exceeded, change the managed media server statuses that are reported to the central administration server. These statuses include Stalled and No Communication. When a managed media servers status changes to Stalled or No Communication, the central administration server changes the way it handles present and future jobs delegated to the stalled managed media server. For example, if communications from a managed media server are not received at the central administration server after five minutes, the central administration server marks the media servers communication status as Stalled, and suspends the delegation of future jobs to the managed media server as it continues to wait for the managed media server to return to an Enabled status. At this point, although there are still jobs in the central administration server job queue waiting on the stalled managed media server, future jobs will be delegated to other managed media servers that are represented in the target device pool. CASO continues to monitor the amount of time during which no communications are received from the managed media server. After a total of 15 minutes passes from the time a Stalled status appears, CASO then changes the status of the managed media server to No Communication. When this occurs, CASO marks the jobs as Failed and then begins the job recovery process by invoking the custom error handling rule, Recovered Jobs for any job that is active at the time the No Communication status appears. Note The settings on the managed media servers Configuration tab can be used to fine-tune the performance of managed media server communications with the central administration server in a wide area network (WAN) environment. Job Update Status By default, managed media servers send job updates to the central administration server every 10 seconds. You can change the frequency of job update statuses by adjusting the amount of time (in seconds) that pass before another job update status is sent. With many backup jobs running, you can preserve network bandwidth by adjusting the amount of time allocated before job update status messages are sent. Specifying more time causes fewer updates to be sent, while specifying less time results in more updates being sent.
841
Time Drifts CASO monitors the internal computer clocks on both the managed media servers and the central administration server. If time differences, or time drifts, develop between the central administration server and the managed media servers, jobs could run at unexpected times. To prevent job problems caused by time drifts, the time reported on managed media server clocks should match the time reported on the central administration server clock. If you receive time difference alerts, reset the managed media server system clock to match the system clock on the central administration server. Catalog Storage Locations By default, all Backup Exec catalogs are stored locally at the managed media server where the backup jobs occur. Using the Store catalogs on option enables you to change the catalog storage location from the managed media server to the central administration server. After changing the catalog storage location, the catalogs that presently reside on the managed media server are immediately moved to the central administration server for storage. In addition, future catalogs created at the managed media server are moved to the central administration server for storage. If you change the storage location from the central administration server back to the managed media server, the catalogs that are stored on the central administration server remain at the central administration server. After the catalog location changes however, all future catalogs produced by the managed media server will be stored locally, at the managed media server where they are produced. If you decide to restore data at the managed media server by remotely connecting to it, only the catalogs produced after the storage location is changed back to the managed media server are available for restore operations. The catalogs that remain on the central administration server cannot be used for restore operations if you remotely connect to the managed media server To set managed media server time thresholds and the catalog storage location for all managed media servers: 1. At the central administration server, start Backup Exec. 2. From the navigation bar, click Media Servers. 3. In the selections pane, click Media Servers. 4. In the task pane, under Media Server Tasks, click Configure managed media server defaults. 5. Click the Configuration tab.
6. Select the appropriate options as follows.

Configuration Tab Options Item Description
Managed media server status Communication Stalled (no more jobs are queued to the managed media server) No Communication (Jobs are recovered from the managed media server) If the managed media server becomes unresponsive, this option sets the amount of time that will pass before the unresponsive media servers status changes to Communication Stalled. The default threshold is five minutes. See Communication Statuses and Time Thresholds on page 840. If the managed media server becomes unresponsive, this option sets the amount of time that will pass before the unresponsive media servers status changes from Communication Stalled to No Communication. The default threshold is 15 minutes. See Communication Statuses and Time Thresholds on page 840.
Seconds between Enables you to adjust the number of seconds that a managed media sending job status server waits between sending job status updates to the central updates administration server. See Job Update Status on page 841. Display alert when the difference in seconds between the clocks on the managed media server and the central administration server is more than: Store Catalogs On Managed media server Central administration server Select this option to store catalogs on the managed media server. Select this option to enable Backup Exec to create an alert if the clock on the managed media server differs from the clock on the central administration server. Then set the number of seconds that, if exceeded, will cause the alert to be generated. See Time Drifts on page 842.
Select this option to store catalogs on the central administration server. See Catalog Storage Locations on page 842.
843
Setting Job Log and Job History Options for Managed Media Servers
During and after job processing, job log and job history information is generated for each job processed at each managed media server. By default, this information is stored locally at the managed media server where the jobs are processed. However, both job log and job history information can be automatically copied and moved to the central administration server, based on the options you select in the Job Logs and Histories tab. To set job log and job history information: 1. At the central administration server, start Backup Exec. 2. From the navigation bar, click Media Servers. 3. In the selection pane, click Media Servers. 4. In the task pane, under Media Server Tasks, click Configure managed media server defaults. 5. Click Job Logs and Histories. 6. Select the appropriate options as follows.
Job Logs and History Tab Options Item Description
Send job logs to central administration server Never By selecting this option, all job logs remain at the managed media server where the jobs ran and where the logs were produced. Selecting this option creates copies of the job logs, which are produced locally at the managed media server. These copies are then moved to the central administration server every day at the time you specify. Selecting this option creates copies of the job logs, which are produced locally at the managed media server. These copies are then moved to the central administration server when the jobs complete.
Every day at
On job completion
844
Configuring the Central Admin Server Option Job Logs and History Tab Options (continued) Item Description
Only if the job fails Selecting this option creates copies of the job logs, which are produced locally at the managed media server. These copies are then moved to the central administration server only if the job fails. Send job history details to central administration server Only when required by job type The job types, Set Copy and Synthetic Backup, require job histories to be stored on the central administration server. Selecting this option will create and move a copy of job histories to the central administration server when jobs that contain one or both of these job types are processed by the managed media server. Selecting this option creates copies of the job history, which are produced locally at the managed media server. These copies are moved to the central administration server every day at a specified time. Selecting this option creates copies of the job history, which are produced locally at the managed media server. These copies are then moved to the central administration server when the jobs complete.
Every day at
On job completion
Only if the job fails Selecting this option creates a copy of a jobs history, which is produced locally at the managed media server. The copies of the job history are then moved to the central administration server only if the job fails.
7. Click OK.
Configuring CASO Alerts

In a CASO environment, alerts generated on managed media servers are automatically rolled up to the central administration server. However, in order to see those alerts at the central administration server, you must enable the Backup Exec alert feature on each of the managed media servers in the CASO environment, and on the central administration server itself. After responding to and clearing the active alert at the central administration server, the alert will also be cleared on the managed media server as well.
845
If you enable the Backup Exec alerts feature at the managed media servers without enabling the alerts feature at the central administration server, alerts will only appear at the managed media servers where they are generated; they will not appear on the central administration server. You can enable and configure alerts at the central administration server and then use the Backup Exec feature Copy Settings to Media Servers to copy the exact alert configurations to the managed media servers in your CASO environment. After copying the alert configurations, alerts appear at both the managed media servers and at the central administration server when the alert is generated at a managed media server. When starting Backup Exec on the central administration server, the central administration server synchronizes with each managed media server in order to reconcile the existing alerts that are common on each computer. Related Topics: Alerts and Notifications on page 501 Copy Configuration Settings and Logon Information on page 396
Configuring Alerts on the Central Administration Server and Managed Media Servers
Use the following steps as an example of how to configure centralized alerts between the central administration server and managed media servers. To configure specific alerts on the central administration server: 1. Start Backup Exec at the central administration server. 2. From the Tools menu, click Alert Categories. 3. Scroll down the list of alert categories until you find the category you want to configure. 4. From Category Properties, select the check box Enable alerts for this category. 5. Click OK. To copy specific alerts to managed media servers. 1. From the Tools menu, select Copy Settings to Media Servers. 2. Under Select Settings to Copy, select the check box for Alert Configuration.
846
3. Click Add. 4. Enter the name of a managed media server to which the configuration will be copied. 5. Click OK. 6. On the Copy Settings dialog box, click OK. An alert on the central administration server will confirm that the copy succeeded. 7. Click OK to clear the active alert. Related Topics: Alerts and Notifications on page 501 Copy Configuration Settings and Logon Information on page 396.
Configuring CASO Notification

Backup Exec has several methods of notifying you when alerts occur during operations. The notification methods enable you to determine the means by which a recipient will receive a notification. In a CASO environment, Backup Exec notification can be configured at either the central administration server or at the managed media servers. Regardless of where they are configured, notifications are triggered at the central administration server. Related Topics: Alerts and Notifications on page 501
847
Running Managed Media Server Operations from the Central Administration Server
You can run managed media server operations from the central administration server. These operations include the following:

Pausing and Resuming a Managed Media Server on page 848 Disabling and Enabling Communications with the Central Administration Server on page 849. Stopping and Starting Backup Exec Services on the Managed Media Server from the Central Administration Server on page 850 Remotely Connecting to a Managed Media Server on page 851 Deleting a Managed Media Server from the Media Servers View on page 852 Viewing Managed Media Server Properties on page 852.
Pausing and Resuming a Managed Media Server

You can pause and resume a managed media server from the central administration server. Pausing a managed media server prevents the central administration server from delegating jobs to it. When paused, the managed media servers status changes from Online to Paused, and is reflected as such in the Media Server Status column of the Results pane. Caution When installing Backup Exec options at a managed media server, the managed media server must be paused, so that no further jobs are delegated to it from the central administration server while the installation process occurs. If jobs are presently running, let them finish or cancel them before beginning the option installation. To pause and resume a managed media server: 1. Start Backup Exec on the central administration server. 2. From the navigation bar, click Media Servers. 3. Select the managed media server you want to pause or resume. 4. From the task pane, under Media Server Tasks, click Paused.
848
The managed media server status changes from Online to Paused in the Media Servers Status column, and an icon representing a managed media server in a paused state appears. 5. To resume job delegation to a managed media server, from the task pane, under Media Server Tasks, click Paused. The check mark appearing before the Pause selection is removed, and the managed media server status changes from Paused to Online in the Media Servers Status column. An icon representing a managed media server in an online state appears. Related Topics: Communication Statuses and Time Thresholds on page 840 CASO Error Codes and the Recovered Jobs Custom Error-Handling Rule on page 872 CASO Icons on page 856
Disabling and Enabling Communications with the Central Administration Server

You can disable and enable managed media server communications from the central administration server using the following steps. To disable and enable communications: 1. Start Backup Exec on the central administration server. 2. From the navigation bar, click Media Servers. 3. Select the managed media server you want to disable or enable. 4. To disable communications, from the task pane, under Media Server Tasks, click Communication Enabled. Communications are disabled between the managed media server and the central administration server. The managed media servers communications status changes from Enabled to Disabled in the Communications Status column. Its status change is also reflected in the Media Server Status column, which changes from Online to Unavailable. Finally, an icon representing a disabled managed media server appears. 5. To re-enable communications, from the task pane, under Media Server Tasks, click Communication Enabled.
849
The managed media servers communications status changes from Disabled to Enabled in the Communications Status column. Its status change is also reflected in the Media Server Status column, which changes from Unavailable to Online. Finally, an icon representing a fully functioning managed media server appears. Related Topics: Communication Statuses and Time Thresholds on page 840 CASO Error Codes and the Recovered Jobs Custom Error-Handling Rule on page 872 CASO Icons on page 856
Stopping and Starting Backup Exec Services on the Managed Media Server from the Central Administration Server
You can manually start and stop the Backup Exec services on managed media servers from the central administration server using the following steps. To stop or start Backup Exec services: 1. Start Backup Exec on the central administration server. 2. From the navigation bar, click Media Servers. 3. Select the managed media server for which you want to start or stop services. 4. From the task pane, under Media Server Tasks, click Backup Exec Services. 5. Select the appropriate options.
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 stop all Backup Exec services and then restart the services for the selected server.
Start all services Stop all services Restart all services
850
Running Managed Media Server Operations from the Central Administration Server Backup Exec Services Manager options Item Services credentials Description 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.
Refresh Remove Server(s)
Remotely Connecting to a Managed Media Server

To run administrative tasks on a managed media server from the central administration server, connect to the managed media server using the Backup Exec feature, Connect to Media Server. To connect to a managed media server: 1. Start Backup Exec on the central administration server. 2. From the navigation bar, click Media Servers. 3. Select the managed media server to which you want to connect. 4. From the task pane, under Media Server Tasks, click Connect to media server. 5. If the managed media server name does not appear, enter the computer name in the Server field. 6. Enter administrator or administrator equivalent logon information for the managed media server. 7. In the Domain field, enter the computer name of the managed media server. 8. Click OK. Connection to the managed media server occurs.
851
Note After making a remote connection to a managed media server, the central administration server console is closed and the managed media server console becomes the active interface. To return to the central administration server console, close the managed media server console and restart Backup Exec on the central administration server.
Deleting a Managed Media Server from the Media Servers View

You can delete managed media servers from the Media Servers view using the following steps. Deleting a managed media server removes it from the direct control of the central administration server and makes it a standalone Backup Exec media server. To make a media server a managed media server again, see Setting a Central Administration Server for Stand-alone Media Servers on page 837. To delete a managed media server: 1. Start Backup Exec on the central administration server. 2. From the navigation bar, click Media Servers. 3. Select the managed media server you want to delete. Note You must disable communications on the managed media server before you can delete it. To disable communications, right-click the managed media server, and then clear the Communication Enabled check box 4. On the task pane, under General Tasks, click Delete.
Viewing Managed Media Server Properties

You can view properties for managed media servers in the Media Servers view. To view properties for managed media servers located in the Media Servers view: 1. Start Backup Exec on the central administration server. 2. From the navigation bar, click Media Servers. 3. Select the managed media server for which you want to view properties. 4. On the task pane, under General Tasks, click Properties. 5. Click OK when finished viewing the properties.
CASO Changes to Backup Exec

This section explains the specific changes to Backup Exec after the Central Admin Server Option is installed.
The CASO Media Servers View

After the Central Admin Server Option is installed, a Media Servers view appears on the Backup Exec navigation bar. As with the views within the Backup Exec Administration Console, the Media Servers view is divided into multiple panes:
Task pane. The Media Servers task pane contains tasks related to the configuration and management of managed media servers. Selection pane. The Selection pane is where you select items to work with. Preview pane. The Preview pane displays general and/or system information about an item selected in either the Selection pane or the Results pane.
Related Topics: Columns in the Media Servers View on page 853 Using the Administration Console on page 110 Centralized Catalog Storage with CASO on page 826
Columns in the Media Servers View

New columns appear in the Results pane of the Media Servers view. These columns are described in the following table.
Column descriptions Item Name Description Shows the computer name of the managed media server or central administration server. Along with the name, an icon representing a managed media server or central administration server is used to help you quickly differentiate between Backup Exec machine types. For more information on icons, see CASO Icons on page 856. Shows a user-defined description of the managed media server or the central administration server.
Description
853
CASO Changes to Backup Exec Column descriptions (continued) Item Communication Status Description Shows the status of communications between the managed media server and the central administration server. Statuses include:
Enabled - Communications about jobs between the managed media server and the central administration server are working properly. Disabled - Communications between the managed media server and the central administration server have been disabled by the user. Stalled - Communications between the managed media server and the central administration server have not occurred within the configured time threshold. See Communication Statuses and Time Thresholds on page 840. No communication - No communication about jobs is being received at the central administration server from the managed media server. The configured time threshold has been reached. Jobs targeted to the managed media server are recovered. Possible causes could range from a network failure to hardware failure in either the managed media server or the central administration server. See Communication Statuses and Time Thresholds on page 840 and Recovering Failed Jobs on page 871. N/A - This status appears when the computer displayed in the Name column is a central administration server.
Media Server Status
Shows the present status of a managed media server. Valid statuses include:
Online - All managed media server services are running and communication with the central administration server is functioning as expected. Paused - Managed media servers have been placed in a Paused state by the user. Jobs are not delegated to the managed media server when it is in a Paused state. Unavailable - A state where no communications have been received by the central administration server from the managed media server. Offline - All managed media server services have been stopped; the media server cannot run jobs in an offline state.
Media Server Type
Shows the Backup Exec description of the media server. It can be either a managed media server or a central administration server. Shows the version of Backup Exec for Windows Servers installed and running on the media server.
Version
854
CASO Changes to Backup Exec Column descriptions (continued) Item Operating System Description Shows the type of operating system installed and running on the media server. Shows the build number of the operating system installed on the media server. Shows the storage location of managed media server-produced catalogs. If the catalogs are stored locally at the managed media server, No appears. If the catalogs are stored at the central administration server, Yes appears. By default, catalogs are stored locally at the managed media server where the backup jobs are run. However, to use the CASO centralized restore feature, catalogs must be stored at the central administration server. See Store Catalogs On on page 843.
Operating System Build
Centralized Catalogs
855
Changes to the Job Monitor/Job History View with CASO

After CASO is installed, a new column named Media Server appears in both the Job Monitor view and the Job History view. In the Job Monitor view, the Media Server column displays the name of the managed media server currently running the job. In the Job History view, it displays the name of the managed media server where the job was processed. Related Topics: Viewing and Changing Active Jobs on page 415
CASO Icons
Icons are used in the Media Server view to help you quickly identify the operational status of Backup Exec managed media servers that appear in the Results pane. These icons include the following:
Identification Icons Icon Description Central Administration Server - This icon represents a Backup Exec central administration server. Paused Central Administration Server - This icon represents a Backup Exec central administration server that has been placed in a Paused state. Managed Media Server - This icon represents a Backup Exec media server that has been converted to a Backup Exec CASO-configured managed media server. Paused Managed Media Server - This icon represents a managed media server that has been placed in a Paused state. Disabled Managed Media Server - This icon represents a disabled managed media server. No Icon Appears- A computer name appearing without an associated icon is marked as Unknown.
856
Backing Up with the Central Admin Server Option

In the CASO environment, the central administration server becomes the centralized focal point of the Backup Exec enterprise. It is the media server where you make decisions on what data and servers are to be protected in your environment. It is also the media server where the building blocks of job creation take place - the creation of policies and the association of selection lists to those policies. Manual Run Now jobs are also configured at the central administration server. After you configure jobs, which are created from the association of selection lists with policies at the central administration server, the central administration server automatically delegates each job to an available managed media server and its attached storage devices using load balancing technology. If a managed media server has multiple storage devices attached, the jobs will be load balanced among its available storage devices. As storage devices become available, additional jobs are delegated to them. If a media server is unavailable, the central administration server will automatically find an available media server and delegate jobs to it. Note One-button backup is not available on central administration servers. Related Topics: Policies and Templates on page 361 Creating a New Policy on page 362 Setting Template Rules on page 373 Creating Jobs Using Policies on page 378
Setting Media Server Property Options for CASO Backup Jobs

After CASO is installed, a new property named Media Server appears in the Properties pane of the following dialog boxes:

Backup Job Properties New Backup Selection List
The options in this property enable you to specifically target a managed media server or a media server pool at which to process your backup jobs. The Media Server property also gives you the opportunity of allowing Backup Exec to make the managed media server selection for you. In either case, the managed media server or media server pool selected must be able to access the storage devices at which the backup jobs are targeted in order for the backup jobs to run.
857
The following options are available in the property, Media Server.

Media Server Property Options Item Media Server Any media server. Allow Backup Exec to choose. Enables Backup Exec to choose a managed media server at which to back up selection lists. Note Any managed media server selected for job processing must be able to access the storage devices at which the jobs are targeted in order to run the jobs. This media server only. Limits backup of selection lists to a specific managed media server. Note The specified managed media server must be able to access the storage devices at which the jobs are targeted in order to run the jobs. Any media server in the pool. Allow Backup Exec to choose. Limits backup of selection lists to a specific media server pool. Backup Exec will select a managed media server from the media server pool to process the jobs. Note The selected managed media server must be able to access the storage devices at which the jobs are targeted in order to run the jobs. Description
Setting the Default Network Interface for Delegated Jobs

A new CASO-related global application option called Default network interface for delegated jobs is available for managed media servers that have multiple network interface cards installed in them. With multiple network interface cards installed, managed media servers are able to communicate with multiple networks (subnets). Default network interface for delegated jobs can be used to determine which subnet should be used when a managed media server connects to a computer running the Remote Agent for Windows Servers, in order to back up its data. When the job runs on the managed media server, the managed media server will use the selected network interface card for the remote agent backup. To set the default network interface for delegated jobs: 1. Start Backup Exec on the central administration server. 2. On the Tools menu, click Options.
858
3. In the Properties pane, under Job Defaults, click Network and Firewall. 4. At the bottom of the dialog box under Default network interface for delegated jobs, select the appropriate options as follows.
Default Network for Delegated Jobs Item Use any available network interface Description Select this option to use any network interface card installed in the managed media server. Using this option enables Backup Exec to use any available network interface on the media server. Select this option if you want CASO delegated backup jobs to be processed using the network interface card configured as the default in the managed media server.
Use the default network interface for the managed media server
5. Click OK. Related Topics: Specifying Default Backup Network and Firewall Options on page 336.
859
Restoring Data Using the Central Administration Server
Device and Media Options for CASO Jobs

Although there are no specific CASO options in Device and Media, this property must be considered if device pools have been configured, and you want to use them with the CASO job delegation and load balancing feature. When configuring new Run Now jobs or creating templates for use with policies, a device pool must be specified in the Devices field for the devices you want to run the jobs. Related Topics: Using Device Pools on page 132. Backing Up with the Central Admin Server Option on page 857

By default, restoring data in a CASO environment is done at the managed media server, just as it is done in a non-CASO Backup Exec stand-alone media server environment. However, using Backup Exec and the Central Admin Server Option, you can centrally initiate, run and manage restore operations from the central administration server. During central restore operations, you can restore complete backup sets of data or individual files to their original locations, or you can redirect the restore of this data to different locations on your network. For more information about restoring data from a managed media server, see Restoring Data on page 451. Related Topics: Requirements for Restore When Using the Central Administration Server on page 862 How Centralized Restore Works on page 862 How CASO Restores Data That Resides on Multiple Storage Devices on page 863
860
CASO Restore Operations and Centralized Catalogs

In order to initiate and manage restore jobs from the central administration server, backup catalogs produced at the managed media servers must be stored on the central administration server. By default, catalogs are stored locally at the managed media servers where they are originally created. If you changed the default catalog storage locations of each of the managed media servers in your CASO environment to the central administration server, then you can begin central administration server restore operations when you are ready to restore data. However, if catalogs are currently being stored on the managed media servers, then you must move the existing catalogs from the managed media servers to the central administration server. For more information on catalog storage options, see Catalog Storage Locations on page 842. Resource and Media Catalog Views You can make choices from the Backup Exec catalogs by Resource view or Media view. To change views, right-click anywhere in the Results pane and select the view you want from the shortcut menu that appears. Or you can click Resource or Media under View by on the Restore Job Properties page. To expand the view, click the (+) control. To collapse the view, click the (-) control. Using the Resource view: In Resource view, restore selections are listed by the resource from which they were backed up. Using the Media view: Media view enables you to view and make restore selections from all cataloged media in the system. Related Topics: How Centralized Restore Works on page 862 How CASO Restores Data That Resides on Multiple Storage Devices on page 863
861
Requirements for Restore When Using the Central Administration Server

Before restore operations from the central administration server can be initiated, the following requirements must be met:

Managed media server catalogs must reside on the central administration server. Managed media server communications must be operating properly, with all communication statuses showing Enabled. Managed media servers must be online with all media server statuses showing Online.
Related Topics: Restoring Data Using the Central Administration Server on page 860 How Centralized Restore Works on page 862 How CASO Restores Data That Resides on Multiple Storage Devices on page 863
How Centralized Restore Works

Depending on whether the required storage media resides in storage devices or is stored offsite, initiating restore operations from the central administration server can be an automated process with little user intervention necessary. How Centralized Restore Works with Online Media You make restore selections and set job properties at the central administration server. During the data selection process, CASO determines the media required to complete the restore operation, and then queries ADAMM to determine the identity of the storage device where the primary media required for the job currently resides. After you make your selections, set restore job properties, and launch the restore job, CASO begins the restore operation by delegating the jobs to the managed media servers that control the selected storage devices. If the data being restored spans multiple storage media, you will be prompted to load additional media as needed to successfully complete the restore operation. How Centralized Restore Works with Offline Media You make restore selections and set job properties at the central administration server. During the data selection process, CASO determines the media required to complete the restore operation, and then queries ADAMM to determine the identity of the storage device where the primary media required for the job currently resides. If the media is not found in a storage device, the media is considered offline. CASO then presents you
with a selection of drive pools and storage devices that are compatible with the type of media being used during the restore operation, thus giving you the flexibility of choosing a storage device in which to load your media. After noting the identity and location of the storage device you have selected to run the job, you:

Submit the restore job on hold as a scheduled job Retrieve the media, place it in the storage device Remove the job from hold at the central administration server, at which time the restore job begins.
CASO then delegates the job to the managed media server that controls the selected storage device. If the data being restored spans multiple storage media, you will be prompted to load additional media as needed to successfully complete the restore operation. Related Topics: Managing Media on page 213
How CASO Restores Data That Resides on Multiple Storage Devices

If the data selected for restore is located on a single device attached to a managed media server, then a single restore job is created at, and then delegated from, the central administration server. However, if during the data selection process, CASO determines that the data being selected for restore is located on multiple storage devices in the CASO environment, then the single restore job is split into separate restore jobs, depending on the number of unique storage devices involved. All split restore jobs adopt the name of the original job, and are differentiated and linked using a subscript numeral, which is appended to the job name. For example, if you create a restore job and the data you select for restore resides in one storage device on a managed media server, CASO creates one restore job. However, if you create one restore job and the data you select resides on two or more unique storage devices that are attached to a managed media server, CASO creates two or more restore jobs.
863
Restoring Data Using the Central Administration Server Example of subscript numerals linking split restore jobs
Single restore job split into multiple jobs, are visually linked using a subscript numeral appended to the original job name.
For data stored on a single storage device

1. Data selections for restore are made at the central administration server.
2. For data that resides on one storage device....
4. The job is delegated and processing begins. 3. ...CASO creates one restore job, which will be delegated for processing at the managed media server where the data resides.
864
Restoring Data Using the Central Administration Server For data stored on multiple storage devices
1. Data selections for restore are made at the central administration server. 2. For data that resides on multiple storage devices...
4.Jobs are delegated and processing begins.
3. ..CASO creates multiple restore jobs, which will be delegated for processing to the managed media servers where the data resides.
Using the Device and Media Property with Centralized Restore Jobs
When using the CASO centralized restore feature, the Device and Media property under Restore Job Properties must be considered. When the data selected for restore resides on media that is online, the Device and Media property page shows the name of the media required for the restore job, the device location and name of the storage device that will process the job. When media is online, clicking Run Now starts the restore operation, with no further user intervention necessary. When the data selected for restore resides on media that is stored offline, the Device and Media property page shows the name of the media required for the restore job. In the Location of First Media column, Unknown appears because the media cannot be found in any of the compatible storage devices that are candidates to run the job. The Device column lists storage devices that are compatible with the media being restored, and are possible candidates to process the restore job.
865
Using Media Server Pools in CASO
After retrieving the media from the offline location, you select a storage device from the Device column list box and then place the media in the device. Set other restore job properties from the Properties pane, and then click Run Now. No further user intervention is necessary to complete the restore job. Note If data to be restored resides on multiple media in a media family, the name of each piece of media required to complete the restore operation appears in the Media column. After retrieving the offline media, you must place the first piece of media from the media family in the selected storage device for the restore job to start successfully. Related Topics: How Centralized Restore Works on page 862

CASO enables you to group multiple managed media servers together into optional media server pools. Media server pools can be used to restrict backup jobs to a specific set of managed media servers and their attached storage devices. And because media server pools are associated with selection lists, the restrictions the media pools follow are defined by the selection lists being protected. For example, you want to back up computers running Microsoft SQL Server. Because only Backup Exec managed media servers that have Symantec Backup Exec for Windows Servers - Agent for Microsoft SQL Server installed are eligible to back up the SQL Server databases, these managed media servers can be placed in a specific media server pool designated as a Microsoft SQL Server-only media server pool. All jobs that back up SQL Server databases would then be sent to the managed media servers in that pool. Media server pools can also be used with the CASO job delegation feature by enabling Backup Exec (with CASO installed) to delegate jobs to the idle storage devices on each of the managed media servers in the media server pool. If a storage device in the media server pool is busy, CASO looks for an idle storage device in the pool. When it finds an idle device, it sends a job to it. Using the previous SQL Server example, CASO can delegate the specific SQL Server jobs to any managed media server in the SQL Server-only media server pool. If one storage device is busy, other idle storage devices will process the queued jobs. Although media server pool configurations typically contain multiple managed media servers, they can contain a single managed media server. In addition, a single managed media server can belong to more than one media server pool.
866
Using Media Server Pools in CASO An example of a CASO-configured media server pool inside a corporate network Central Administratio n Server
Media Server Pool
Related Topics:
Adding Additional Managed Media Servers to a Media Server Pool on page 868 Renaming a Media Server Pool on page 869 Deleting a Media Server Pool on page 869 Removing a Managed Media Server from a Media Server Pool on page 870
Creating a Media Server Pool and Adding Managed Media Servers

Use the following steps to create a media server pool, and then add managed media servers to it. To create a media server pool and add media servers: 1. At the central administration server, start Backup Exec. 2. On the Tools menu, select Media Server Pools. 3. Click New. 4. Enter a media server pool name and description. 5. From the Available media servers pane, select the media servers you want to add to the pool, and then click Add.
867
Note Because the central administration server also can be used as a managed media server, it also appears in the list of media servers. Be sure to select the central administration server (if it has attached storage devices) if it is also to be used as a managed media server during job delegation. 6. Click OK. Related Topics: Adding Additional Managed Media Servers to a Media Server Pool on page 868 Renaming a Media Server Pool on page 869 Deleting a Media Server Pool on page 869 Removing a Managed Media Server from a Media Server Pool on page 870
Adding Additional Managed Media Servers to a Media Server Pool

Use the following steps to add additional managed media servers to an existing media server pool. To add additional managed media servers to an existing media server pool: 1. At the central administration server, start Backup Exec. 2. On the Tools menu, click Media Server Pools. 3. Select a media server pool where you want to add managed media servers, and then click Edit. 4. From the Available media servers pane, select the media servers you want to add to the pool, and then click Add. 5. Click OK. The managed media server now appears in the media server pool. Related Topics: Renaming a Media Server Pool on page 869 Creating a Media Server Pool and Adding Managed Media Servers on page 867 Deleting a Media Server Pool on page 869 Removing a Managed Media Server from a Media Server Pool on page 870
868
Renaming a Media Server Pool

Use the following steps to rename a media server pool. To rename a media server pool: 1. At the central administration server, start Backup Exec. 2. On the Tools menu, click Media Server Pools. 3. Select a media server pool you want to rename, and then click Edit. 4. In the Name field, enter a new name for the media server pool. 5. Click OK. The media server pool is renamed. Related Topics: Adding Additional Managed Media Servers to a Media Server Pool on page 868 Creating a Media Server Pool and Adding Managed Media Servers on page 867 Removing a Managed Media Server from a Media Server Pool on page 870
Deleting a Media Server Pool

Use the following steps to delete a media server pool. To delete a media server pool: 1. At the central administration server, start Backup Exec. 2. On the Tools menu, click Media Server Pools. 3. Select a media server pool you want to delete, and then click Delete. 4. Click Yes when prompted to confirm the delete operation, and then click Close. The media server pool is deleted. Related Topics: Adding Additional Managed Media Servers to a Media Server Pool on page 868 Creating a Media Server Pool and Adding Managed Media Servers on page 867 Removing a Managed Media Server from a Media Server Pool on page 870
Appendix C, Symantec Backup Exec - Central Admin Server Option 869
Removing a Managed Media Server from a Media Server Pool

You can remove managed media servers from a media server pool using the following steps. Removing a managed media server deletes it from a media server pool, but does not remove it from the All Managed Media Servers node. To remove a managed media server from a media server pool: 1. Start Backup Exec on the central administration server. 2. On the Tools menu, click Media Server Pools. 3. Select a media server pool from which you want to remove managed media servers, and then click Edit. 4. From the Media servers in pool pane, select the media servers you want to remove from the pool, and then click Remove. 5. Click OK. The managed media server no longer appears in the media server pool. Related Topics: Adding Additional Managed Media Servers to a Media Server Pool on page 868 Creating a Media Server Pool and Adding Managed Media Servers on page 867 Deleting a Media Server Pool on page 869
Configuring Device Pools for Use with CASO Media Server Pools
Before a media server pool can be used for job processing, the storage devices attached to each managed media server in the media server pool must be configured as a device pool. After the device pool is created, it can be associated to the media server pool when configuring backup job properties in the Job Properties dialog box. If you want to use the CASO job delegation feature to process your backup jobs, the media server pool and its associated device pool can be targeted as the devices to process jobs. If you have multiple devices attached to each of the managed media servers in the media server pool, you can create multiple, smaller device pools made up of fewer storage devices. Using this method, some jobs can be targeted to a particular device pool in the media server pool, while other jobs can be targeted to a different device pool using the same media pool.
870
Special Considerations
Related Topics: Adding Additional Managed Media Servers to a Media Server Pool on page 868 Creating a Media Server Pool and Adding Managed Media Servers on page 867 Deleting a Media Server Pool on page 869 Removing a Managed Media Server from a Media Server Pool on page 870
This section provides information about the following CASO topics:

Recovering Failed Jobs on page 871. Pausing Storage Devices on Managed Media Servers from the Central Administration Server on page 873. Backup Duplicate Data and Synthetic Backup Templates Considerations on page 873.
Recovering Failed Jobs

The error-handling rule, Recovered Jobs, is a custom error-handling rule that is used by Backup Exec and CASO to recover jobs that failed because of issues with internal job communications. This rule is created during the Backup Exec installation, and is enabled by default. The retry options for this rule are to retry the job twice, with an interval of five minutes between the retry attempts. During the first retry attempt, CASO attempts to re-delegate the jobs to another available managed media server in the All Managed Media Server node. If this attempt fails, CASO makes a second attempt at finding another online managed media server at which to process the jobs. If no other managed media servers are online, the final job disposition is to place the job on hold until you have fixed the error condition. Note If you are targeting jobs to a media server pool containing multiple managed media servers, and job failures occur, the job recovery process will recover the jobs using only the managed media servers in the media server pool. Managed media servers that are not members of the media server pool will not be used in job recovery situations.
871
When viewing the Job History tab on the central administration server, CASO jobs that are failed and then recovered by Backup Exec because of No Communication statuses are displayed differently in Backup Exec than CASO jobs that are failed due to errors in normal daily activities. The jobs that are failed and recovered due to No Communication statuses are not indicated in red text in the job history as other failed jobs are. Instead, these jobs are displayed in gray text, along with a job status of Recovered. When the job history entry is opened, the error category will list Job Errors as the reason for the failure, along with an explanation of the type of internal communication error that occurred. The job history entry will also indicate that the job was recovered. Note Job logs are not created for jobs that are recovered. Related Topics: Error-Handling Rules on page 439 Custom Error-handling Rule for Recovered Jobs on page 443 Communication Statuses and Time Thresholds on page 840 CASO Error Codes and the Recovered Jobs Custom Error-Handling Rule on page 872
CASO Error Codes and the Recovered Jobs Custom Error-Handling Rule
The following table describes the CASO-related error codes that are selected by default for the Recovered Jobs custom error-handling rule:
Error codes for Recovered Jobs custom error-handling rule Error code 0xE000881B JOBDISPATCH 0xE000881D JOB_CASO_QUEUE FAILURE Description The displayed message is: Job failed while being dispatched. The job will be recovered. The displayed message is: The job could not be delegated to the destination managed media server. The managed media server may not be online, or there may be a communications failure. The job will be recovered.
0xE000881E The displayed message is: The job failed to start on the JOB_CASO_REMOTEMMS destination managed media server, possibly because a _STARTFAILURE database error occurred. The job will be recovered.
872
Pausing Storage Devices on Managed Media Servers from the Central Administration Server
After pausing managed media server storage devices at the central administration server, the storage devices appear in the Devices view with both a Paused Managed Media Server status icon, and the word Paused. However, when viewing the list of storage devices under the Devices view at the managed media server, the storage devices that were paused at the central administration server do not appear as Paused. You must refresh the managed media servers Devices view by pressing F5 at the managed media server in order to see the actual state of the storage devices. Related Topics: CASO Icons on page 856 Managing Devices on page 123
Backup Duplicate Data and Synthetic Backup Templates Considerations

Recurring jobs from job families produced from a multiple template policy that includes either or both of the templates Backup Duplicate Data and Synthetic Backup must be run at the same managed media server where the jobs were originally delegated. To function correctly, the jobs produced from these templates require access to the media that contains the backup sets that were produced from the preceding jobs. If you change the target device of the templates within a policy, the job family then becomes eligible for delegation to a different managed media server. However, if the current managed media server is still a valid candidate for delegation, it will be used. If you do not change the target devices in the templates, and if the currently selected managed media server is unavailable, the jobs will remain queued, waiting for the currently selected managed media server to become available. If the currently selected managed media server is no longer configured as a managed media server, then the job family becomes eligible for re-delegation. Related Topics: Policies and Templates on page 361 Adding a Duplicate Backup Template to a Policy on page 382 Creating a Synthetic Backup By Copying the Example Policy for Synthetic Backup on page 881
873
Disaster Recovery Using Intelligent Disaster Recovery (IDR) with CASO
Disaster Recovery Using Intelligent Disaster Recovery (IDR) with CASO

The Symantec Backup Exec for Windows Servers - Intelligent Disaster Recovery Option can be used to protect both managed media servers and the central administration server in a CASO environment. To protect the computers in your CASO environment, see Symantec Backup Exec Intelligent Disaster Recovery Option on page 901. Before implementing the IDR option in a CASO environment, review the following:
In a CASO environment, all disaster preparation files (*.dr files) created for each managed media server are centrally located on the central administration server. To create recovery media for any managed media server or central administration server, the IDR Preparation Wizard must be run at the central administration server. Or if running on remote administration environment, connect to the central administration server. If you want managed media servers to be protected using a bootable tape image, you must run the IDR Preparation Wizard at each of the managed media servers where a bootable tape device is installed. For CASO, two options appear on the Welcome screen when the IDR Prep Wizard is run on a managed media server. These options include:
Yes, create the bootable tape image now - For details on creating bootable tape images, see Creating a Bootable Tape Image on page 924. No, connect to a central administration server - If a bootable tape drive is not detected on a managed media server, only this option appears.
A central administration server must be backed up and restored locally.
874
Appendix
Symantec Backup Exec Advanced Disk-based Backup Option

The Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) is installed as a separate, add-on component of Backup Exec for Windows Servers. The Advanced Disk-based Backup Option provides the following features:
Synthetic backup - This feature uses a policy to enable a full backup to be assembled, or synthesized, from a baseline and subsequent incremental backups that are also contained in a policy. The benefits of using a synthetic backup include:
A reduced backup window since the synthetic backup can be scheduled outside of the time-critical backup window. Reduced network traffic since the synthetic backup does not need to access the network.
Offhost backup - This feature enables the backup operation to be processed on a Backup Exec media server instead of on the remote computer, or host computer. Moving the backup from the remote computer to a media server enables better backup performance and frees the remote computer as well.
Related Topics: About the Synthetic Backup Feature on page 876 About the Offhost Backup Feature on page 888
Installing the Advanced Disk-based Backup Option

ADBO is enabled on the media server by entering the ADBO serial number. To install the ADBO on a local media server, see Installing Backup Exec Options to the Local Computer on page 71.
875
About the Synthetic Backup Feature
About the Synthetic Backup Feature

The synthetic backup feature eliminates the need to perform recurring full backups for supported remote resources. A policy created for the synthetic backup feature enables the synthetic backup to be assembled from a full backup (called a baseline) and subsequent incremental backups that are also contained in the policy. The resulting synthetic backup then becomes the new baseline, so only incremental backups are required until the next synthetic backup is created. The synthetic backup is as current as the last incremental backup that it contains. The components of the policy for synthetic backup are: a. Baseline. The first backup to run that is associated with the synthetic backup. The baseline backup runs one time only, and will always back up all of the files on the selected resources when it runs.
b. Recurring incremental backups. Subsequent backups that back up files that are changed after the baseline backup. After the baseline backup completes, at least one incremental backup is necessary. c. Recurring synthetic backups. The process that combines the data from the baseline backup and the incremental backups to form a synthesized full backup of the selected resources. This synthesized full backup becomes a new baseline backup, which can then be combined with subsequent incremental backup sets to form the next synthesized full backup.
a. Baseline backup is run from the synthetic backup policy Network Backup Exec media server Resource selected for backup from the media server
Tape library Storage device
Baseline backup (can be backed up to disk or tape)
876
About the Synthetic Backup Feature b. Incremental backups are run from the synthetic backup policy Network Backup Exec media server Incremental backups
Resource selected for backup from the media server Baseline backup (can be backed up to disk or tape)
Tape library Storage device
c. Synthetic backup is run from the policy and assembled from the baseline and incremental backups Network Backup Exec media server Incremental backups Synthetic backup Storage device
Resource selected for backup from the media server Baseline backup (can be backed up to disk or tape)
Tape library
Synthetic backups can only be created within a policy. You can use the Policy Wizard to create a policy that will contain the necessary job templates for the synthetic backup feature, or you can copy the example policy for synthetic backup and then modify it to suit your specific needs, or you can manually create a policy, and then add the necessary job templates. For all of the associated synthetic backup templates in a policy, you can also use a Duplicate Backup Set template to create a multi-stage backup strategy for backing up data to disk and then copying it to tape. For details, seeAbout Duplicate Backup Set Templates on page 381. Related Topics: Best Practices for Synthetic Backup on page 879
Appendix D, Symantec Backup Exec - Advanced Disk-based Backup Option
877
Requirements for Synthetic Backups
Creating A Synthetic Backup on page 880 Collecting Additional Information for Synthetic Backup on page 879

Synthetic backups and their associated templates can only be created in policies. Backup templates that create incremental backup jobs must have Backup-to-Disk folders as destination devices. Before you can save a policy that contains the synthetic backup templates, you must have a Backup-to-Disk folder that you can select as the destination device for the required incremental backup jobs. Additionally, in order for the example policy for synthetic backup to be displayed after installation, you must create a Backup-to-Disk folder when the First Time Startup Wizard is run. If the example policy for synthetic backup is not displayed, create a Backup-to-Disk folder, and then on the Tools menu, click Re-create Example Policies. The example policy will be displayed in the Policies pane in the Job Setup view.
The option Collect additional information for synthetic backup must be selected for backup templates for incremental and full backup jobs created for synthetic backup. This option is on the General page of the Backup Job Template properties (for details, see Creating a Synthetic Backup By Adding Templates to a Policy on page 883). If the baseline backup job was written to tape, and if you also want to write the synthetic backup job to tape, two tape drives are required: one to mount the source job on (the baseline backup) and one to mount the destination job on (the synthetic backup job). Only file system resources are supported for synthetic backup. If a backup selection list contains resources that are not supported, such as databases, and the selection list is associated with a policy that contains the synthetic backup template, the jobs for the synthetic backup will not be created. If the Central Admin Server Option is installed, the synthetic backup job template and any associated full and incremental job templates must be run on destination devices that can all be accessed by the media server that runs the synthetic backup job. For more information, see Backup Duplicate Data and Synthetic Backup Templates Considerations on page 873.
Following are limitations when running synthetic backups:
878
The option Checkpoint Restart is not supported when the option Collect additional information for synthetic backups is selected. For more information on Checkpoint Restart, see Using Checkpoint Restart on Microsoft Cluster Server Failover on page 665.
Related Topics: Collecting Additional Information for Synthetic Backup on page 879 Creating a Synthetic Backup By Copying the Example Policy for Synthetic Backup on page 881 Creating a Synthetic Backup By Adding Templates to a Policy on page 883
Best Practices for Synthetic Backup
A separate backup template for the baseline backup is optional. If you want the destination device for the baseline backup to be different from that of the recurring incremental backups, or if you want the baseline job to run at a different time than the recurring incremental backups, you must create a separate backup template for a full backup job to be the baseline backup. Make sure that none of the synthetic backup-related job templates, that is, the baseline backup template, the recurring incremental backup template, and the synthetic backup template, run at the same time. You can use template rules to enforce when these templates are allowed to run. For more information, see Setting Template Rules on page 373.
Related Topics: About the Synthetic Backup Feature on page 876 Creating a Synthetic Backup By Copying the Example Policy for Synthetic Backup on page 881 Policies and Templates on page 361
Collecting Additional Information for Synthetic Backup

All of the backup job templates that are created for synthetic backup must have the option Collect additional information for synthetic backup selected. This option can be selected on the General page on the backup job template properties when a policy is being created. This option specifies that Backup Exec collects the information required to detect files and directories that have been moved, renamed, or newly installed since the last backup, and then includes those files and directories in the backup jobs. If this option is not
879
Creating A Synthetic Backup
selected, Backup Exec skips these files and directories if their archive bits are unchanged. With this option selected, Backup Exec compares path names, file names, modified times, and other attributes with those from the previous full and incremental backups. If any of these attributes are new or changed, then the file or directory is backed up. The first backup that is associated with the synthetic backup always backs up all of the files, even if it is an incremental backup. Backup Exec starts collecting the additional information beginning with the next incremental backup that is associated with the synthetic backup. Note Any job templates using the incremental backup method and the Collect additional information for synthetic backup option must use a Backup-to-Disk folder as the destination device. Related Topics: About the Synthetic Backup Feature on page 876 Creating A Synthetic Backup on page 880 Adding a Backup Template to a Policy on page 367

A synthetic backup can only be created in a policy. There are different methods you can use to create a policy that contains the necessary job templates for a synthetic backup:
Use the Policy Wizard. See Creating a Synthetic Backup By Using the Policy Wizard on page 881. Make a copy of the synthetic backup policy example and then modify the job templates to suit your specific needs. See Creating a Synthetic Backup By Copying the Example Policy for Synthetic Backup on page 881. Manually create a policy, and then add the necessary job templates for the synthetic backup feature. See Creating a Synthetic Backup By Adding Templates to a Policy on page 883.
Before creating a synthetic backup, review the requirements in Requirements for Synthetic Backups on page 878. Related Topics: About the Synthetic Backup Feature on page 876 Best Practices for Synthetic Backup on page 879
880
Creating a Synthetic Backup By Using the Policy Wizard

You can use the policy wizard to help you create the all of the templates necessary for a synthetic backup. You can set up the policy to use:

A weekly synthetic backup with daily incremental backups. A monthly synthetic backup with a weekly synthetic or incremental backup and daily incremental backups.
To create a policy for synthetic backup using the Policy Wizard: 1. On the navigation bar, click Job Setup. 2. In the task pane, under Policy Tasks, click New policy using wizard. 3. On the Welcome page, click Next. 4. On the Backup Strategy page, select the weekly or monthly strategy, and then select the option Use synthetic backups instead of full backups. 5. Click Next to continue, and follow the instructions in the wizard to complete the policy. All of the necessary job templates for synthetic backup will be created in the new policy. Related Topics: About the Synthetic Backup Feature on page 876 Requirements for Synthetic Backups on page 878 Best Practices for Synthetic Backup on page 879
Creating a Synthetic Backup By Copying the Example Policy for Synthetic Backup
Backup Exec provides example policies that contain standard settings for different tasks. The example policy for synthetic backup contains the standard settings and job templates that are required to run a synthetic backup. You can copy this example policy, rename it, and change the times when the templates are scheduled to run. For instructions on how to copy an example policy, follow the steps in Using an Example Policy on page 365.
881
Note In order for the example policy for a synthetic backup to be displayed after installation, you must configure a Backup-to-Disk folder when the First Time Startup Wizard is run. The backup template that creates the incremental backup must have a Backup-to-Disk folder as the destination device. If the example policy for synthetic backup is not displayed, create a Backup-to-Disk folder, and then on the Tools menu, click Re-create Example Policies. The example policy for synthetic backup will be displayed in the Policies pane in the Job Setup view. To view the synthetic backup policy example, on the navigation bar, click Job Setup. In the Policies pane, double-click Example: Synthetic Backup. The example policy for synthetic backup contains the following templates:
Baseline Backup - the backup template that creates the baseline backup job. This job runs once only. Incremental Backup - the backup template that creates the subsequent incremental backup jobs and runs after the baseline backup job runs. Synthetic Backup - the backup template that creates the synthetic backup job.
The example policy displays the template rules that you can use to set the order in which the templates should run. All template rules are optional, but they can help you make sure that the templates run in the proper sequence. In the example policy, because a full backup template is included to act as the baseline, it should be the first template to run, and it should only run once. Therefore, the following rules were added:
<First Template> must complete at least once before any other templates will be allowed to start. Baseline Backup is selected as the <First Template>. If start times conflict, <First Template> will start and upon completion, starts <Second Template>. Incremental Backup is selected as the <First Template> and Synthetic Backup is selected as the <Second Template>. Run <First Template> only once. Baseline Backup is selected as the <First Template>.
Related Topics: Requirements for Synthetic Backups on page 878 Setting Template Rules on page 373 About the Synthetic Backup Feature on page 876 Best Practices for Synthetic Backup on page 879
882
Creating a Synthetic Backup By Adding Templates to a Policy

Creating a new policy for a synthetic backup involves choosing a name and description for the policy, adding the necessary job templates for synthetic backup to the policy, and setting up relationships between the templates. After you set up all of the templates for a synthetic backup in a policy, you can combine the policy with a selection list to create jobs. Before creating a synthetic backup, review the requirements in Requirements for Synthetic Backups on page 878. To create a synthetic backup by adding templates to a policy: 1. On the navigation bar, click Job Setup. 2. On the task pane, under Policy Tasks, click New policy. The New Policy dialog box appears. 3. Type a policy name and description for this synthetic backup policy, and then click New template. The Template Selection dialog box appears. 4. Select Backup Template, and then click OK. 5. On the Properties pane, under Settings, click General, and specify either of the following backup methods for the baseline.
Select Full - Back up files - Using archive bit (reset archive bit) to add an optional baseline full backup template. Select Incremental - Back up changed files since last full or incremental Using archive bit (reset archive bit) to add a recurring, incremental backup template.
6. Select the option Collect additional information for synthetic backup. Note If you selected an incremental backup method, then under Destination, click Device and Media and select a Backup-to-Disk folder as the destination device. 7. Under Frequency, click Schedule and set the scheduling options you want to use (for details, see Setting the Schedule for a Template on page 369). If you added the optional full backup template for the baseline backup in step 5, you must configure it to be the first backup template to run, and it must run only once.
883
If you added an incremental backup template, you must configure it to be a recurring job so that the first instance can become the baseline backup. 8. Select other options as appropriate, and then click OK. For details on these options, see Adding a Backup Template to a Policy on page 367. Note Backup templates that create incremental backup jobs must have Backup-to-Disk folders as destination devices. 9. Do one of the following:
If you added the optional full backup template for the baseline backup in step 5, then continue with the next step to create a backup template for an incremental backup job. If you added a recurring incremental backup template, go to step 15 on page 884 to add the synthetic backup template
10. On the New Policy dialog box, click New template, and then on the Template Selection dialog box, select Backup Template again, and then click OK. 11. On the Properties pane, under Settings, click General, and select the backup method Incremental - Back up changed files since last full or incremental - Using archive bit (reset archive bit). 12. Select the option Collect additional information for synthetic backup. 13. Under Frequency, click Schedule and set the scheduling options you want to use (for details, see Setting the Schedule for a Template on page 369). 14. Select other options as appropriate, and then click OK. For details on these options, see Adding a Backup Template to a Policy on page 367. Note Backup templates that create incremental backup jobs must have Backup-to-Disk folders as destination devices. 15. On the New Policy dialog box, click New template, select Synthetic Backup Template, and then click OK. 16. On the Properties pane, under Destination, select Device and Media, and complete the options as described in Device and Media Options for Backup Jobs and Templates on page 266.
884
17. On the Properties pane, under Settings, click General, and complete the appropriate options as follows:
General options for synthetic backup Item Template name Backup set description Preferred source device Description Type the name for this job template. Type a description of the information you are backing up. Select the device used as the destination device for the original backup job.
18. On the Properties pane, under Settings, click Advanced, and complete the appropriate options as follows:
Advanced options for synthetic backup 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.
885
Creating A Synthetic Backup Advanced options for synthetic backup (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. If the data was backed up using software compression, then it is copied in its software compression form. Using some form of data compression can help expedite backups and preserve storage media space. Hardware data compression should not be used in environments where devices that support hardware compression are used interchangeably with devices that do not have that functionality. For example, if a drive that does not support hardware compression is added to a cascaded drive pool that includes drives supporting the feature, hardware compression is automatically disabled. You can manually re-enable hardware compression on the drives that support it, but this results in media inconsistency. If the drive that supports hardware compression fails, the compressed media cannot be restored with the non-compression drive
Hardware [if available, otherwise none]. Select this option to use hardware data compression (if the storage device supports it). If the drive does not feature data compression, the data is backed up uncompressed.
19. 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 Notification on page 534). 20. Do one or both of the following
Under Frequency, click Schedule to set the scheduling options you want to use (for details, see Setting the Schedule for a Template on page 369). Create template rules, explained in step 1 in the following procedure (Recommended) Create template rules to run job templates for synthetic backup: on page 886.
(Recommended) Create template rules to run job templates for synthetic backup: Note You may want to review the topic Setting Template Rules on page 373 before creating template rules.
886
1. On the New Policy dialog box, under Template rules, click New Rule. 2. On the Template Rule Properties dialog box, click the template rules drop down list, and then do one of the following:
If you created a backup template for a full backup job to run as the baseline backup, select Run <First template> only once. Click the First template drop down list and select the name of the template that you want to run as the baseline backup, and then click OK. If you created a backup template for a recurring incremental backup job to run as the baseline backup, go to step 4.
3. Click New Rule again to add another rule. 4. On the Template Rule Properties dialog box, click the template rules drop down list, and then select <First template> must complete at least once before any other templates will be allowed to start. 5. Click the First template drop down list, select the template name of the baseline backup, and then click OK. 6. Click New Rule again to add another rule. 7. On the Template Rule Properties dialog box, click the template rules drop down list, and then select If start times conflict, <First Template> will start and upon completion, starts <Second Template>. 8. Click the First template drop down list, and select the template name of the incremental backup. 9. Click the Second template drop down list, select the template name of the synthetic backup, and then click OK. 10. On the New Policy dialog box, click OK. The policy is displayed on the Job Setup view, in the Policies pane. After you create a policy and set up templates in it, you should combine the policy with a selection list to create jobs. When a policy is combined with a selection list, Backup Exec creates jobs based on the settings in the templates. For details on how to create jobs using this policy, see Creating Jobs Using Policies on page 378. Related Topics: About the Synthetic Backup Feature on page 876
Appendix D, Symantec Backup Exec - Advanced Disk-based Backup Option 887
About the Offhost Backup Feature
Requirements for Synthetic Backups on page 878 Best Practices for Synthetic Backup on page 879

The offhost backup feature enables Backup Exec to move backup processing from the host computer, which is the remote computer that contains the volumes selected for backup, to the Backup Exec media server. The offhost backup creates a snapshot of the volume or volumes that are selected for backup on the remote computer. The snapshots are then imported to the media server, where they are backed up. The following illustrates the basic method for performing an offhost backup.
Offhost Backup
Remote computer Backup Exec media server
Attached SAN device
1 3
Tape library 1. A snapshot of the selected volume on the remote computer is mirrored to the attached SAN device. 2. The mirror is split and the snapshot is imported to the media server. 3. The media server backs up the snapshot.
After the backup, the snapshots are deported from the media server and mounted back on the remote computer and resynchronized with the source volume. This process requires solutions from hardware or software providers that can support transportable
snapshots, that is, snapshots that can be imported to and deported from the media server. The Microsoft Volume Shadow Copy Services (VSS) provider that you select is used for each volume in the offhost backup. An offhost backup job is performed on one remote computer at a time. Offhost backup supports the following:

Microsoft Volume Shadow Copy Service (VSS). VERITAS Storage Foundation for Windows (VSFW). Backups for NTFS volumes that use the full, incremental, and differential backup methods. Microsoft SQL Server 2000 database backups by the Backup Exec Agent for SQL Server. For more information, see Using the ADBO With the SQL Agent on page 1024. Microsoft Exchange Server 2003 (Service Pack 1) database backups by the Backup Exec Agent for Exchange Server. For more information, see Using Snapshot Technology With the Exchange Agent on page 1074.
Related Topics: Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider on page 890 Setting Offhost Backup Options for Backup Jobs on page 892 Troubleshooting the Offhost Backup on page 896 Browsing Remote Computers for Installed Snapshot Providers on page 894 Restoring Offhost Backup Data on page 895
Requirements for Offhost Backup

The following requirements must be met to use offhost backup. The media server:

Must have Backup Exec for Windows Servers version 10.0 or later installed. Must have the Advanced Disk-based Backup Option installed.
The remote computer:
Must have the Backup Exec Remote Agent for Windows Servers version 10.0 or later installed.
889
The media server and the remote computer:
Must both have Microsoft Windows Server 2003, Datacenter or Enterprise Edition installed. Must both have the selected Microsoft Volume Shadow Copy Services (VSS) hardware or software provider installed. Otherwise, the snapshots of the volumes cannot be deported to the media server. Must both be able to access disks that are shared between them.
Note The option Checkpoint Restart is not supported for the offhost backup feature. For more information on Checkpoint Restart, see Using Checkpoint Restart on Microsoft Cluster Server Failover on page 665. Related Topics: About the Offhost Backup Feature on page 888 Best Practices for Using Offhost Backup on page 891 Troubleshooting the Offhost Backup on page 896 Browsing Remote Computers for Installed Snapshot Providers on page 894
Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider
If you are using the VERITAS Storage Foundation for Windows (VSFW) FlashSnap option provider, read the following before running an offhost backup:
VSFW version 4.1 must be installed on the media server and on the computer that contains the volumes that you want to back up. The VSFW FlashSnap option must be installed on the computer that contains the volumes that you want to back up. Use the VSFW FlashSnap Snap Start command to mirror the volumes on the remote computer. The offhost backup option does not create mirrored volumes or resynchronize volumes that are already created and split. For details on using Snap Start, see Using Snap Start on a VERITAS Storage Foundation for Windows Volume on page 1005. Confirm that the mirrored volumes that you create with the VSFW FlashSnap option reside on disks that are shared between the remote computer (the computer containing the volumes to be backed up) and the media server.
890
All volumes selected for offhost backup using the VSFW FlashSnap provider must belong to the same disk group. A maximum of seven volumes can be snapped at one time. Do not select dynamic volumes and basic volumes for the same offhost backup job because the VSFW FlashSnap option cannot perform snapshots of basic volumes. Symantec recommends that you use other backup methods for backing up basic volumes if the VSFW FlashSnap provider is selected. If the computer on which you want to perform an offhost backup is in an environment with the Central Admin Server Option and the Symantec Cluster Server installed, and if failover occurs to a Symantec Cluster Service node, you may need to manually clean up the snapshots before restarting the offhost backup on the failover node. Refer to the VSFW documentation for details.
Related Topics: Troubleshooting the Offhost Backup on page 896 Browsing Remote Computers for Installed Snapshot Providers on page 894
Best Practices for Using Offhost Backup
Keep source volumes and snapped volumes from sharing the same physical disks. If this is not maintained, then any attempt to split the snapshot volume from the original volume fails. Most hardware and software providers have some limitation about the types of volumes that are transportable. Therefore, Symantec recommends that you use offhost backup jobs only for backing up data for which all dependent volumes, or mounted volumes, can be imported and deported. The offhost backup will fail if any one volume that you select for backup is only supported by a Microsoft Volume Shadow Copy Services (VSS) provider and cannot be imported or deported, or if the required VSS hardware provider is not on a Symantec-approved compatibility list. You can choose to continue the backup if the offhost backup fails. If the Central Admin Server Option (CASO) is installed, for jobs that use offhost backup, you must manually select the destination device that will run the job rather than allowing the job to be delegated by the central administration server. Otherwise, the job could be delegated to a media server that does not have offhost capability. See Setting Media Server Property Options for CASO Backup Jobs on page 857. When performing an offhost backup in a Microsoft Cluster Server (MSCS) or Symantec Cluster Services environment, the media server and the remote computer must not be in the same cluster group. The cluster applications cannot support
891
devices logical unit numbers (LUNs) that have duplicate signatures and partition layouts, therefore, the snapshots containing the LUNs must be transported to a host, or remote computer, that is outside the cluster. See Using Symantec Backup Exec with Server Clusters on page 657. Related Topics: About the Offhost Backup Feature on page 888 Requirements for Offhost Backup on page 889 Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider on page 890 Setting Offhost Backup Options for Backup Jobs on page 892 Browsing Remote Computers for Installed Snapshot Providers on page 894 Troubleshooting the Offhost Backup on page 896
Setting Offhost Backup Options for Backup Jobs

You can set the offhost backup options for each backup job, or you can set defaults that are used for every backup job. For details on how to create a backup job, and for definitions of all other backup options, see Creating a Backup Job on page 261. Note If the Central Admin Server Option (CASO) is installed, for jobs that use offhost backup, you must manually select the destination device that will run the job rather than allowing the job to be delegated by the central administration server. Otherwise, the job could be delegated to a media server that does not have offhost capability. See Setting Media Server Property Options for CASO Backup Jobs on page 857. To set offhost backup options for backup jobs: 1. Do one of the following:
To set offhost backup options for a single backup job, on the navigation bar click Backup, and then on the Properties pane, under Settings, click Advanced Disk-based Option. To set offhost backup options for all backup jobs, on the Tools menu, click Options. On the Properties pane, under Job Defaults, click Advanced Disk-based Backup Option.
The Advanced Disk-based Backup options dialog box appears.
892
2. Select the appropriate options, described in the following table, and then click OK.
Advanced Disk-based Backup default options Item Use offhost backup to move backup processing from remote computer to media server Snapshot provider Description Select this check box to enable offhost backup. If you are enabling this for a single job, or as a default for all backup jobs, then an offhost backup of all volumes will be performed if all requirements are met. For more information about offhost backup, see About the Offhost Backup Feature on page 888. Automatic - Use hardware if available; otherwise use software. Select this option to enable VSS to select the best provider for the selected volume. Software - Use VERITAS Storage Foundation for Windows. Hardware - Use technology provided by hardware manufacturer: If you select Software or Hardware as the snapshot provider, then:

The provider must support transportable snaps. If multiple volumes are selected, then all volumes must be snappable by the same type of provider. Software and hardware providers cannot both be used to snap different volumes in the same job. You must either create another job, or select the option Process logical volumes for offhost backup one at a time.
Job disposition: If any of the selected resources do not support offhost backup:
Continue the backup job (offhost backup is not used): Select this to allow the backup job to complete even if any of the volumes selected do not support offhost backup, or if an error that is related to the snapshot or volume import occurs. The backup will run according to all the other options that have been set for this job. Fail the backup job (further selections are not backed up after failure occurs): Select this to terminate the offhost backup job if any of the selected volumes do not support offhost backup, or if an error that is related to the snapshot or volume import occurs.
893
About the Offhost Backup Feature Advanced Disk-based Backup default options (continued) Item Description
Process logical volumes Enables the backup of multiple volumes in one job, while creating a for offhost backup one snapshot of only one logical volume at a time. To ensure database at a time integrity, or if a volume contains mount points, multiple volumes may need to be snapped at one time. After the logical volume is snapped and backed up, the snapshot is deleted before the next logical volume is snapped. This option increases the ability to meet the minimum quiet time needed to complete a snapshot. A logical volume can comprise multiple physical volumes. A single logical volume can encompass all of the volumes on which databases reside.
Related Topics: About the Offhost Backup Feature on page 888 Requirements for Offhost Backup on page 889 Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider on page 890 Best Practices for Using Offhost Backup on page 891 Troubleshooting the Offhost Backup on page 896
Browsing Remote Computers for Installed Snapshot Providers

You can view which snapshot providers are installed on a remote computer before running an offhost backup for selected resources on that computer. The Microsoft Volume Shadow Copy Services (VSS) hardware or software provider that you select when creating an offhost backup must also be installed on the remote computer that you want to back up. If the snapshot provider is not installed on the remote computer, the snapshots of the volumes cannot be imported to the media server. To browse the remote computers for installed snapshot providers: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Source, click Selections. 3. On the backup selections tree, right-click the remote computer that contains the volumes you want to back up, and then click List Snapshot Providers.
894
The Snapshot Providers dialog box appears. 4. View the list of the available snapshot providers on the remote computer. Related Topics: Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider on page 890 Requirements for Offhost Backup on page 889 Best Practices for Using Offhost Backup on page 891 Setting Offhost Backup Options for Backup Jobs on page 892
Restoring Offhost Backup Data

Restoring data backed up with the offhost backup method is a standard restore operation. Data is restored directly from the backup media to the original volumes on the remote computer
Backup Sets for restoring offhost backup data.
Related Topics: Restoring Data on page 451

Appendix D, Symantec Backup Exec - Advanced Disk-based Backup Option 895
Troubleshooting the Offhost Backup

Offhost backup requires that the VSS providers and the volumes that are to be transported are set up correctly. In order to troubleshoot offhost backup issues, Symantec recommends that you use the tools that are available from the VSS provider to verify the setup that is required for offhost backup. The minimum setup requirements are:

All volumes to be backed up are snappable. Volumes are shared between the remote computer and the media server.
For example, when using VERITAS Storage Foundation for Windows (VSFW) as the provider, you can use the VERITAS Enterprise Administrator (VEA) to verify snapshots of the volumes, split the snapped volumes into a different Disk Group (DG), deport the DG from the remote computer and import it to the media server. All providers will have similar administration console or command-line tools that will allow you to take a snapshot of volumes, and deport and import volumes. It is also required that an offhost backup job contain only volumes that can be transported to the media server for backup. Please read the requirements section carefully. For more information, see Requirements for Offhost Backup on page 889 and Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider on page 890. Other factors to consider are:
Microsoft Windows Server 2003 Enterprise or Data Center edition must be installed on both the media server and the remote computer. Microsoft XML Core Services (MSXML4) must be installed and running on both the media server and the remote computer.
Troubleshooting offhost backup Troubleshooting offhost backup issues depends to an extent on the VSS provider used for the snapshots, but there are setup issues that are common to all providers that may cause offhost backup to fail:
Volumes are not shared For offhost backup to work, all volumes must reside on disks that are shared between the remote computer and the Backup Exec media server. It is the backup administrator's responsibility to confirm this. If the volumes are not shared, the import operation will fail, and you may need to clean up the snapshots and resynchronize the volumes manually.
VSS Provider installation
896
The provider used for snapshot must be installed on both the media server as well as on the remote computer. If the provider is not installed on the media server, the import operation will fail, and you may need to clean up the snapshots and resynchronize the volumes manually.
All volumes are not transportable All volumes selected for backup must be transportable to the media server. If Microsoft SQL or Exchange, or other database applications are selected for backup, make sure that the databases and log files reside on transportable volumes.
VSS Provider selection In addition to being transportable, all volumes selected for backup must be snappable by the same provider. It is the backup administrator's responsibility to ensure that all volumes in a backup job are supported by the same VSS provider.
Log path location Log files created by the provider or by its supporting application during normal snapshot operation should not reside on any of the volumes being snapped. This prevents VSS from flushing the write buffers, and the snapshot will time-out. Change the log path to another volume.
Provider or VSS services not started Make sure that the provider service is running and make sure that the Microsoft Windows "Volume Shadow Copy" service has not been disabled.
Credentials Make sure that the machine-level credentials used for the job are the same on both the media server and the remote computer. Incorrect credentials will cause snapshots or the backup to fail.
Central Admin Server Option (CASO) environment If a backup job is configured in a CASO environment, you must target the job to media servers on which the selected VSS provider is installed rather than allowing the job to be delegated by the central administration server. Otherwise, the job could be delegated to a media server that does not have offhost capability. See Setting Media Server Property Options for CASO Backup Jobs on page 857.
Clusters When performing an offhost backup in a Microsoft Cluster Server (MSCS) or Symantec Cluster Services environment, the media server and the remote computer must not be in the same cluster group. The cluster applications cannot support devices' logical unit numbers (LUNs) that have duplicate signatures and partition layouts; therefore, the snapshots containing the LUNs must be transported to a media server that is outside the cluster in which the host cluster resides. See Using Symantec Backup Exec with Server Clusters on page 657.
897
Offhost backup failures when using VSFW as a provider Following are the most common causes of snapshot failure and offhost backup failure when using the VERITAS Storage Foundation for Windows (VSFW) software provider:
Volume has not been snap started. Backup Exec requires that you first snap start all volumes using the VERITAS Enterprise Administrator administration console or command-line interface before attempting an offhost job (see Using Snap Start on a VERITAS Storage Foundation for Windows Volume on page 1005). If you already performed the snap start for a previous snapshot operation, you must either snap start the volume again (to another physical disk) or snap back the previous snapshot volume. For details on how to snap back, refer to the documentation for the VERITAS Storage Foundation for Windows (VSFW) software provider. Volumes to be backed up are basic volumes. VSFW allows only dynamic volumes to be snapped. You are trying to back up a volume that resides on a disk with other volumes and so the disk group cannot be deported. Any attempt to split the snapshot volumes from the source volumes will fail if the snapshot volumes and the source volumes share the same physical disks. The administrator must keep the source volumes and the snap volumes from sharing the same physical disks. Offhost backup requires that VSFW version 4.1 or later be installed on both the remote computer and on the media server. Previous releases are not supported. Compatible VSFW software versions must reside on both the media server and the remote computer. It is recommended that the same version of VSFW be installed on both computers. All dynamic volumes designated for backup must be in the same Disk Group (DG). Multiple disk groups in the same offhost job are not supported. Ensure that there are no more than seven volumes in a single snapshot operation. When more volumes are installed, they cannot all be snapped within the ten-second time-out that VSS imposes for snapshots to complete, and the snapshot will fail. Basic volumes and dynamic volumes cannot be mixed in a backup job that uses the offhost feature. A workaround is to select the option Process logical volumes for offhost backup one at a time. This restriction also applies to dynamic volumes that are mounted by mount points on basic volumes. Dynamic boot and system volumes are restricted from VSFW FlashSnap functionality for compatibility reasons. Therefore, dynamic boot and system volumes are not supported for an offhost backup.
Note Most VSS providers have some limitation about the types of volumes that are transportable. Therefore, it is recommended that you do not use offhost backup jobs for complete system protection. A best practice is to use offhost backup jobs
to back up databases and logs when all of the dependent volumes on which data resides are transportable. Any volumes that are used to host mount points for data volumes must also be transportable because the offhost backup must snap both the data volumes and the volume with the mount point for backup. Offhost backup issues when using a hardware provider Hardware disk array vendors may support VSS snapshots and the transporting of volumes to the media server for backup in a SAN environment. Using hardware providers requires a sound understanding of how disk arrays are configured for shared access between the remote computer and the media server in a SAN. Consult the documentation for your hardware disk array on how to set up such disk arrays for offhost backup. Specifically, note any limitations on using the disk arrays in context with VSS snapshots, and note how to verify if the volumes are transportable. It is highly recommended that you make use of any tools provided by the vendor to help verify the setup and for troubleshooting issues. Related Topics: Requirements for Offhost Backup on page 889 Requirements for Offhost Backup When Using the VERITAS Storage Foundation for Windows Provider on page 890 Best Practices for Synthetic Backup on page 879
899
900
Appendix
Symantec 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 hard drive failure. The IDR wizards guide you in preparing for disaster recovery and in recovering a local or remote computer to its pre-disaster state. IDR can protect 32-bit computers and 64-bit Intel Itanium computers. Before you can recover computers, you must prepare for a disaster by performing the following: 1. On the media server, use the IDR Configuration Wizard to specify a location where a copy of the computer-specific disaster recovery file (*.dr file, where the asterisk represents the name of the computer being protected) will be stored. 2. Run full backups of the hard drives on the computers to be protected. Include System State for Windows 2000 and Windows XP computers and Shadow Copy Components for Windows 2003 computers. Do not exclude any files from the full backups; otherwise the *.dr file will not be created. 3. Run the IDR Preparation Wizard to create bootable media and recovery diskettes for each computer. The IDR Configuration Wizard starts automatically the first time you start Backup Exec after you install IDR. The IDR Configuration Wizard guides you through setting an alternate data path for the *.dr file. The default data path for the *.dr file is on the media servers hard drive, but Symantec recommends that you specify an alternate data path to store another copy of the *.dr file in case the media servers hard drive is damaged. Backup Exec creates the *.dr file during a full backup and stores it in the default and alternate storage locations. Catalog entries from subsequent backups are added to the *.dr file as these backups are completed.
901
Requirements for Using IDR
The IDR Preparation Wizard guides you through the preparation of the bootable media that you will use to recover protected computers and copies the *.dr file and other recovery information to the Intelligent Disaster Recovery diskette. After you have performed these steps for each computer you want to protect, you are prepared to recover those computers using any of the following recovery methods:

Restore a media server (Backup Exec server) using a locally attached storage device. Restore a Windows computer by moving the media and the storage device to the computer being restored, and then restoring the computer through the locally attached storage device. Restore a remote Windows computer using a network connection to the media server
Related Topics: Getting Started with IDR on page 906 About Creating and Updating Recovery Media on page 912
Requirements for Using IDR
Symantec Backup Exec for Windows Servers. See the requirements for using Backup Exec in Introducing Backup Exec on page 43. The Symantec Backup Exec Remote Agent for Windows or NetWare Servers (Remote Agent) or Backup Exec must be installed on any remote computers to be protected with IDR. Windows 2000/XP/Server 2003 recovery requires sufficient hard drive space to hold an entire Windows installation (600 MB to 2 GB).
Note Disaster recovery from virtual devices, such as Backup-to-Disk devices, must be done via Remote IDR using a media server with access to the virtual device. Mixed media loaders are not supported for local IDR. Related Topics: Requirements for Running the IDR Preparation Wizard on page 913 Using an Evaluation Version of the IDR Option on page 903 Symantec Backup Exec - Remote Agent for Windows Servers on page 789
902
Installing the IDR Option
Installing the IDR Option

You can install IDR as an option during the initial installation of Backup Exec for Windows Servers, or it can be installed later. All IDR serial numbers, both local and remote, are entered on the local media server. The Remote Agent must be purchased separately from the IDR option, and must also be installed on any remote computer you want to protect with IDR. The Remote Agent is a system service that runs on remote servers and enhances backup and restore performance. It is required for IDR functionality. For instructions on installing the IDR option on the local media server, see Installing Backup Exec Options to the Local Computer on page 71. For instructions on installing IDR on a remote resource, see Installing Backup Exec Agents to Remote Computers on page 77. For instructions on installing the Remote Agent, see Installing the Remote Agent to Remote Windows Computers on page 793. 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. Related Topics: Getting Started with IDR on page 906
Using an Evaluation Version of the IDR Option

The Intelligent Disaster Recovery option can be installed and evaluated for up to 60 days or until Backup Exec and IDR are licensed, but you must recreate the IDR recovery media after the IDR option has been purchased and installed. The recovery media includes the boot media and the Intelligent Disaster Recovery diskettes. 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, unless you recreated IDR recovery media after IDR was licensed.
Appendix E, Symantec Backup Exec - Intelligent Disaster Recovery Option
903
Preparing Computers for IDR

The key to successfully recovering computers after a disaster is to carefully and properly prepare those computers for a disaster. Preparing computers for IDR involves: 1. Using the IDR Configuration Wizard to determine the alternate location where a copy of the *.dr file will be stored. 2. Performing backup jobs on the computer to be protected. 3. Creating the bootable recovery media using the IDR Preparation Wizard.
Use the Configuration Wizard to set the alternate data path.
Tape
Do you want to create bootable tape,

CD, or diskettes?
Diskettes
Yes
Did you create a tape image with the Config. Wizard? No Run the IDR Prep Wizard to create a tape image.
CD
Run a full backup Run a full backup
Run the IDR Prep
Wizard to create
Run the IDR Prep Wizard to create the bootable CD. Run the IDR Prep Wizard again to update DR diskettes.
bootable diskettes.
Run an overwrite backup job.
Run the IDR Prep Wizard again to update DR diskettes.
904
You can create three types of bootable media with the IDR Preparation Wizard:

Diskettes (not supported for Windows XP or Windows Server 2003) CD-R (CD-Recordable) or CD-RW (CD-Rewritable). For 64-bit computers, CDs are the only supported bootable media. 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

Disadvantages
Works on most computers. Can also be used to protect remote Windows computers on the network. Can create bootable diskettes for remote computers. Requires less preparation and recovery time than diskettes. Can also be used to protect remote Windows computers on the network. Can create bootable CD images for remote computers. Requires less preparation and recovery time than diskettes.
Requires more preparation and recovery time than CDs and tapes. Not supported for Windows XP or Windows Server 2003.
CD-R, CD-RW
Requires a BIOS that supports booting from a CD. Requires a CD burner.
Bootable tape
Requires a BIOS that supports booting from a SCSI CD and a bootable tape device that emulates a SCSI CD drive. Cannot create bootable tape images for remote computers.
905
Getting Started with IDR

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, mass storage controller information, and Network Interface Card information. A list of catalog entries that identify the backup media used to recover the computer. For Windows XP and Windows Server 2003 computers, Windows Automated System Recovery (ASR) configuration information files (asr.sif and asrpnp.sif). The ASR files are necessary to recreate partitions on Windows XP and Windows Server 2003 computers during the recovery process.
To run the IDR Configuration Wizard: 1. On the Welcome screen, click Next. Backup Exec automatically creates a *.dr file for the IDR-protected computer when it is backed up and stores it in the default location on the media servers hard drive, which is: C:\Program Files\VERITAS\Backup Exec\NT\IDR\Data\<computer name>.dr. The Enter An Alternate Data Path screen enables you to specify an alternate location where a copy of the *.dr file can be stored so that the *.dr file is available even if the media server has been damaged.
906
Getting Started with IDR Enter an Alternate Data Path dialog box
Symantec recommends 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. 2. Enter the alternate location where a copy of the *.dr file will be stored, and then click Next. Symantec recommends that you enter a mapped network location. Note If you are using IDR to protect a media server in a cluster, or any remote media server, set the alternate data path to a shared drive or to a drive outside the cluster. 3. 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. Click Finish, and then go to About Creating and Updating Recovery Media on page 912 to continue disaster recovery preparation. If a bootable tape device is detected, you are prompted to create a bootable tape image.
907
Getting Started with IDR Bootable Tape Device Detected dialog box
4. Do one of the following:
Click Yes, create the image now (recommended), click Next, and then continue with step 5. 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; otherwise the tape will not be bootable. Click Finish, and then go to About Creating and Updating Recovery Media on page 912 to continue disaster recovery preparation.
5. When the Starting Tape Image Creation screen appears, the option Let IDR automatically partition the boot and system drive during restore is selected by default for a Windows 2000 media server. This option enables 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. 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. See Using IDR To Recover Windows 2000 Computers on page 941. 6. 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. 7. Click Finish, and then go to About Creating and Updating Recovery Media on page 912 to continue disaster recovery preparation. Related Topics: Recovering a Computer Using IDR on page 942 About Creating and Updating Recovery Media on page 912 Creating a Bootable Tape Image on page 924 Backing Up Data on page 259
Manually Setting Data Paths for the *.dr Files

If you did not use the IDR Configuration Wizard to set an alternate data path for the *.dr files, you can set it manually. Copies of the *.dr files, which contain the computer-specific information for the computer being protected, are necessary to automate the recovery of an IDR-protected computer. Backup Exec automatically creates the *.dr file during a backup and stores it in the Disaster Recovery Data Path default location on the media servers hard drive, which is C:\Program Files\VERITAS\Backup Exec\NT\IDR\Data\<computer name>.dr. Symantec recommends that you do not change this default. You can also specify an alternate location where a second copy of the *.dr file is stored so that the *.dr file is available even if the media server has been damaged. It is recommended that the alternate location be on another computer or on a different physical drive than the default location, and that it be a mapped network drive. To 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.
909
Getting Started with IDR Intelligent Disaster Recovery Path Options
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.
910
Getting Started with IDR Intelligent Disaster Recovery Options - Set Application Defaults (continued) Item Alternate path Description Enter an alternate directory path where a copy of the *.dr files for the protected computers will be stored. Backup Exec automatically creates or updates the *.dr file during a backup and stores it in the specified location during a backup. It is recommended that you specify an alternate data path that is not on the media server, or is on a different physical drive than the default location. During a recovery, you can copy the *.dr file from the alternate path to a diskette to recover the target computer if the media servers hard drive is unavailable.
If you are specifying a remote computers hard drive as the alternate data path, it is recommended that you map a drive letter to the remote computer. When mapping the drive letter, be sure to select the Reconnect at Logon option so that you can reconnect to the drive letter every time you log on. Check the directory later to make sure the *.dr files were copied. If you are specifying a directory on a different physical hard drive on the local computer, browse to or type the drive name and the path: d:\drfiles
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.
911
About Creating and Updating Recovery Media

Before running the IDR Preparation Wizard to create or update the recovery media, run a full backup of the hard drive (unless you are creating bootable tape media - see Creating a Bootable Tape Image on page 924 for details). The *.dr file is created when a full backup of the entire hard drive is run. Note If you exclude files from backups, the *.dr file is not created. After the *.dr file is created, Backup Exec automatically updates it with data from all subsequent backups (except copy backups) in its default location on the computer and in the alternate location you specified. For each backup set that is backed up, an alert appears reminding you to use the IDR Preparation Wizard to 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 For the local media server, update the bootable media after every successful full backup. For remote computers, you do not need to create or update bootable media until a disaster occurs, as long as a *.dr file for the remote computer is available on the media server. 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. 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 Recovering a Computer Using IDR on page 942.
912
The bootable media also contains a text file called <computer name>-diskconf.txt, which contains information about the computers hard disk layout.
The recovery diskettes, which you can create and update separately from the bootable media by using the IDR Preparation Wizard, are labeled the Intelligent Disaster Recovery diskette 1 and 2, and contain:
One or more *.dr files, which include computer-specific information such as hardware-specific information, and catalog entries that identify the media necessary to recover the computer. For XP and Windows Server 2003 computers, Windows Automated System Recovery (ASR) configuration information is also included and is required in order to recreate critical partitions on these computers during the recovery process. Any necessary drivers. The Disaster Recovery Wizard. These items are copied to the Intelligent Disaster Recovery diskettes. Create and update this diskette separately from the bootable media. At times, the *.dr file may not fit on the Intelligent Disaster Recovery diskettes. If this occurs, copy the *.dr file to a separate diskette.
Related Topics: Creating A Full Set of Diskettes on page 917 Creating a Bootable CD Image on page 920 Creating a Bootable Tape Image on page 924 Creating the Intelligent Disaster Recovery Diskettes Only on page 927 Updating the Full Set of Disaster Recovery Diskettes on page 931 Updating the Intelligent Disaster Recovery Diskettes Only on page 934 Updating Bootable Media on page 929
Requirements for Running the IDR Preparation Wizard

Please note the following before running the IDR Preparation Wizard:
Run a full backup of the hard drive before creating the boot and recovery media (unless you are creating a bootable tape image). When running full backups for IDR preparation:
Make sure that volumes (C, D, etc.) have been backed up. The *.dr files are not created or updated if only individual directories are backed up. Additionally:
For Windows 2000 and Windows XP, back up System State.

913

For Windows Server 2003, back up Shadow Copy components. For 64-bit Intel Itanium computers, back up the EFI system partition. If the server is also the media server, back up the Backup Exec SQL instance.
Make sure that if utility partitions are present on the computer, they are selected for backup. Utility partitions are usually small partitions installed on the hard disk by OEM vendors and contain system diagnostic and configuration utilities. For more information on selecting utility partitions for backup, see Backing Up Utility Partitions on page 350. 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 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.
Running the IDR Preparation Wizard

The IDR Preparation Wizard guides you through the process of creating or updating both the bootable media used to recover protected computers and the Intelligent Disaster Recovery diskettes. 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 on which the IDR option is installed is used by default to create or update the disaster recovery media. However, if the computer does not have the IDR option installed locally, select Choose a media server that has the IDR option installed to select another media server on which the IDR option is installed in order to create or update the media. Related Topics: About Creating and Updating Recovery Media on page 912 Requirements for Running the IDR Preparation Wizard on page 913 Preparing IDR Media Via Other Media Servers on page 937 Creating A Full Set of Diskettes on page 917 Creating a Bootable CD Image on page 920 Creating a Bootable Tape Image on page 924 Creating the Intelligent Disaster Recovery Diskettes Only on page 927 Updating the Full Set of Disaster Recovery Diskettes on page 931
Creating Recovery Media After a Disaster

If a disaster occurs on a computer before you create the recovery media for it, you can still create recovery media if you made a full backup of the computer before the disaster. Note For remote computers, this feature is available only if the Remote Agent version 10.0 is installed on the remote computer. When you create a full backup of a computer, IDR creates a *.dr file that contains system and catalog information. IDR uses the *.dr file to create the recovery media needed to recover the computer. If a disaster occurs on the local media server, you can create recovery media for it after a disaster if you have another media server and a copy of the *.dr file from the local media server in an alternate location. Also, you can use the Remote Administrator to recover the local media server. To create recovery media after a disaster: 1. On the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard. 2. By default, the IDR Preparation Wizard uses this computer to create the disaster recovery media.
If this computer does not have the IDR option installed locally, select Choose a media server that has the IDR option installed, and then see Preparing IDR Media Via Other Media Servers on page 937 for instructions on how to create bootable media. If this computer has the IDR option installed locally, click Next to create bootable media.
3. In the Available Computers area, select the computer for which you want to create bootable media, and then click the right arrow to move the computer to the Selected Computers area. As long as a *.dr file exists for the computer, it should display in the Available Computers area. 4. On the Create IDR Boot Media dialog box, select the type of recovery media you want to create, and then follow the instructions in the wizard. For more information about creating recovery media, see the topic for the type of media you are creating:

Creating a Bootable CD Image on page 920 Creating a Bootable Tape Image on page 924 Creating A Full Set of Diskettes on page 917 Creating the Intelligent Disaster Recovery Diskettes Only on page 927
915
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 2003, but the computer for which you want to prepare recovery media is running Windows 2000, then you must have a Windows 2000 installation CD with the same language and type of licensing that is on the Windows 2000 computer.
For Windows 2000, XP, and Windows Server 2003: 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.
Related Topics: Including or Excluding Files for Backup Using Advanced File Selection on page 288 Creating A Full Set of Diskettes on page 917 Creating a Bootable CD Image on page 920 Creating the Intelligent Disaster Recovery Diskettes Only on page 927 Creating a Bootable Tape Image on page 924 Updating the Full Set of Disaster Recovery Diskettes on page 931 Updating the Intelligent Disaster Recovery Diskettes Only on page 934 Updating Bootable Media on page 929. Updating the Intelligent Disaster Recovery Diskettes Only on page 934
916
Creating A Full Set of Diskettes

Use the IDR Preparation Wizard to create the bootable diskettes and the Intelligent Disaster Recovery diskettes. The IDR Preparation Wizard also enables you to update the *.dr file on the Intelligent Disaster Recovery diskettes 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 913, note the following:

For Windows XP or Windows Server 2003, bootable diskettes are not supported. At least six blank, formatted 1.44 MB diskettes are required for each set of disaster recovery diskettes to be created. 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 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 during restore 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 941. For instructions on updating the Intelligent Disaster Recovery diskette, see Updating the Intelligent Disaster Recovery Diskettes Only on page 934.
Prior to a disaster, test the bootable diskettes to ensure that the computer can boot from them.
To create bootable diskettes: Note This option is available only for Windows 2000. 1. Verify that the computer to be protected has been backed up. 2. On the Tools menu, click Wizards, and then click Intelligent Disaster Recovery Preparation Wizard. 3. By default, the IDR Preparation Wizard uses this computer to create the full set of disaster recovery diskettes.
Appendix E, Symantec Backup Exec - Intelligent Disaster Recovery Option 917
If this computer does not have the IDR option installed locally, select Choose a media server that has the IDR option installed, and then see Preparing IDR Media Via Other Media Servers on page 937 for instructions on how to create bootable media. If this computer has the IDR option installed locally, click Next to create bootable diskettes.
4. In the Available Computers area, select the computer for which you want to create bootable media, and then click the right arrow to move the computer to the Selected Computers area. If the computer you want to protect does not display in the Available Computers area, click Browse to search for the computer, or type the name of the computer in the field next to the Add button, and then click Add.
Select Computers to Protect dialog box.
5. Click Next. 6. Under Create, select Full set of diskettes to boot the Windows Installation CD, and then click Next.
918
About Creating and Updating Recovery Media Create IDR Boot Media dialog box
7. Enter the path to the Windows operating system files for this computer, and then click Next. 8. Label a diskette "Windows 2000 Setup Boot Diskette", insert it into the floppy disk drive, and the click Next. 9. When the first diskette completes, insert the next blank diskette, and then click Next. 10. Repeat step 9 until all the diskettes are used. 11. Type the Windows product key, and then click Next. 12. Insert the Windows Setup Boot Diskette that you created in step 8, and then click Next. 13. If the option Let IDR automatically partition the boot and system drive during restore has been selected, insert Windows Setup Disk 4, and then click Next. 14. When the Windows Setup Boot Diskette is complete, insert the IDR diskettes to store computer-specific disaster recovery files for the computer being protected, and then click Next. 15. When the Finish screen appears, click View Disk Configuration to display the Disk Configuration Report. This report is also automatically copied to the diskette that has the *.dr file on it. Related Topics: Recovering a Computer Using IDR on page 942
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 diskettes on a regular basis and to recreate the bootable CD image whenever hardware, SCSI drivers, or tape drivers change on the computer. For Windows Server 2003 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. For Windows XP computers, you will be prompted to insert a diskette for ASR files. Adding the ASR files to the CD image may make the recovery process easier since all the files are in one location. In addition to the requirements listed in Requirements for Running the IDR Preparation Wizard on page 913, note the following:
Backup Exec includes support for burning the disaster recovery CD image to supported CD-R and CD-RW drives. If a CD-R or CD-RW drive is not supported by this component, use a third party ISO 9660-compliant application. You should verify the image created by third-party CD burning software before you need it for disaster recovery. CD-R is the recommended media for creating a bootable CD image. If CD-RW media is used, the CD drive must have MultiRead ability; otherwise, inconsistent behavior may occur when running IDR. Test the media with the CD drive before relying on it for disaster recovery. A blank, writable or rewritable CD is required if the Symantec 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 during restore 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 941.
Prior to a disaster, test the bootable CD to ensure that the computer can boot from it.
920
To create a bootable CD image: 1. Verify that the computer to be protected has been backed up. 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 create a bootable CD image. If this computer does not have the IDR option installed locally, select another media server on which the IDR option is installed to create a bootable CD image. 3. Do one of the following:
To use another computer to create the bootable CD image, select Choose a media server that has the IDR option installed, and see Preparing IDR Media Via Other Media Servers on page 937 for details. To use this computer to create the bootable CD image, on the Welcome screen, click Next.
4. In the Available Computers area, select the computer for which you want to create bootable media, and then click the right arrow to move the computer to the Selected Computers area. If the computer you want to protect does not display in the Available Computers area, click Browse to search for the computer, or type the name of the computer in the field next to the Add button, and then click Add
5. Click Next.
6. Under Create, select Bootable CD Image for use with CD Writers (ISO 9660), and then click Next.
.Create IDR Boot Media dialog box
7. Enter the location to store the bootable CD image, and then click Next. 8. Enter the location where copies of the operating system setup files are located, and then click Next. You can enter one of the following:

If the files are on a CD, type the CD drive letter. If the files are stored on a network or the local computers hard drive, type the path to files. If an .ISO image for operating system CD is available, specify the path to that image.
922
About Creating and Updating Recovery Media Select Path to Windows operating system installation files dialog box
9. Type the Windows product key in the Enter the Windows Product Key dialog box, and then click Next. If you do not enter the product key now, you may have to enter it during disaster recovery. 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 to help diagnose why IDR restore issues. 10. If the computer you want to protect uses Windows XP or Windows 2003, label a diskette "Windows Automated System Recovery" and then insert it into drive A. Click Next to create the diskette, which will store the ASR files. 11. To create the bootable CD now, select a CD writer from the Select a CD Writer to create the CD with option, insert a blank CD into the CD writer, and then click Create a bootable IDR CD. If you do not want to create the CD now, click Next. 12. When the bootable CD image is complete, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskettes. Related Topics: Recovering a Computer Using IDR on page 942 Creating the Intelligent Disaster Recovery Diskettes Only on page 927
923
Creating a Bootable Tape Image

Note This option is available only for the local media server with a compliant bootable tape device. Use the IDR Preparation Wizard to create a bootable tape image, and then run an overwrite backup job so that the image is written to the tape. Next, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskettes. For details on how to specify a backup job as an overwrite job, see Device and Media Options for Backup Jobs and Templates on page 266. The IDR Preparation Wizard also enables you to update the *.dr file on the Intelligent Disaster Recovery diskettes 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 913. To create a bootable tape image: Note A bootable tape drive and its driver must be detected by the Intelligent Disaster Recovery Preparation Wizard before the option to create a bootable tape image is displayed. 1. 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. 2. Do one of the following:
To use another computer to create the bootable tape image, select Choose a media server that has the IDR option installed, and see Preparing IDR Media Via Other Media Servers on page 937 for details. To use this computer to create the bootable tape image, on the Welcome screen, click Next.
924
About Creating and Updating Recovery Media Create IDR Boot Media dialog box
3. Under Create, select Bootable Tape Image for use with bootable tape devices, and then click Next. 4. Read the Starting Tape Image Creation screen, and then click Next. 5. Enter a location to store the bootable image until you perform a full backup, and then click Next.
.Select Location for Bootable Tape Image dialog box
6. Enter the path for the location of the Windows operating system files, and then click Next.
7. Enter the Windows product key, and then click Next. 8. For Windows XP, label a diskette "Windows Automated System Recovery" and insert it into drive A, and then click Next. 9. When the bootable tape image has completed, run an overwrite backup job so that the bootable image is written to the tape. For details on specifying a backup job as an overwrite job, see Device and Media Options for Backup Jobs and Templates on page 266. 10. When the backup job has completed, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskettes. Related Topics: Updating Bootable Media on page 929 Recovering a Computer Using IDR on page 942 Backing Up Data on page 259
926
Creating the Intelligent Disaster Recovery Diskettes Only

Create just the Intelligent Disaster Recovery (IDR) diskettes 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 diskettes include necessary drivers, the Disaster Recovery Wizard, and the computer-specific *.dr file. The Intelligent Disaster Recovery Preparation Wizard creates two diskettes. When the Intelligent Disaster Recovery diskettes are complete, click View Disk Configuration to display the Disk Configuration Report. To create the Intelligent Disaster Recovery diskettes 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 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 Intelligent Disaster Recovery diskettes. 2. Do one of the following:
To use another computer to create the Intelligent Disaster Recovery diskettes, select Choose a media server that has the IDR option installed, and see Preparing IDR Media Via Other Media Servers on page 937 for details. To use this computer to create the Intelligent Disaster Recovery diskettes, on the Welcome screen, click Next.
3. In the Available Computers area, select the computer for which you want to create bootable media, and then click the right arrow to move the computer to the Selected Computers area. If the computer you want to protect does not display in the Available Computers area, click Browse to search for the computer, or type the name of the computer in the field next to the Add button, and then click Add
927
4. Click Next. 5. Under Create, select IDR diskettes only (includes ASR files for Windows XP/Windows 2003), and then click Next.
Create IDR Boot Media dialog box
6. Label a blank diskette "Intelligent Disaster Recover Diskette 1", insert it into drive A, and then click Next.
928
7. Label a blank diskette "Intelligent Disaster Recovery Diskette 2", insert it into drive A, and then click Next. 8. Insert a diskette that you created previously for the computer you selected in step 3, and then click Next. 9. When the Finish screen appears, click View Disk Configuration to display the Disk Configuration Report. 10. Remove the diskette from the drive and store both with the rest of the disaster recovery media. Both diskettes will be labeled as Intelligent Disaster Recovery. Related Topics: Updating the Intelligent Disaster Recovery Diskettes Only on page 934
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 920. 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 931. 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. 2. Do one of the following:
929
To use another computer to update the bootable tape image, select Choose a media server that has the IDR option installed, and see Preparing IDR Media Via Other Media Servers on page 937 for details. 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.
Create IDR Boot Media dialog box
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 Let IDR automatically partition the boot and system drive during restore, 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. 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 complete, run an overwrite backup job so that the image is written to the tape. For details on specifying a backup job as an overwrite job, see Device and Media Options for Backup Jobs and Templates on page 266. 8. When the backup job is complete, run the IDR Preparation Wizard again to create the Intelligent Disaster Recovery diskettes. Related Topics: Recovering a Computer Using IDR on page 942 Backing Up Data on page 259
Updating the Full Set of Disaster Recovery Diskettes

Symantec recommends 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 diskettes only option, or manually copy the *.dr file from the default or alternate locations to the Intelligent Disaster Recovery diskette #2 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. For more information, see Alerts and Notifications on page 501. When you have finished updating the recovery diskettes, click View Disk Configuration to display the Disk Configuration Report. When updating diskettes for a Windows 2000 computer, all of the diskettes need to be 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 volume (C, D, etc.) have been backed up. The *.dr files are not created or updated if only individual directories are backed up. Additionally:
For Windows 2000 and Windows XP, back up System State.
931

For Windows Server 2003, back up Shadow Copy components. For 64-bit Intel Itanium computers, back up the EFI system partition. If the server is also the media server, back up the Backup Exec SQL instance.
Make sure that if utility partitions are present on the computer, they are selected for backup. Utility partitions are usually small partitions installed on the hard disk by OEM vendors, and contain system diagnostic and configuration utilities. For more information on selecting utility partitions for backup, see Backing Up Utility Partitions on page 350. 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 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 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:
To use another computer to update the disaster recovery diskettes, select Choose a media server that has the IDR option installed, and see Preparing IDR Media Via Other Media Servers on page 937 for details. To use this computer to update the disaster recovery diskettes, on the Welcome screen, click Next.
4. Select Update Media, and then click Next. 5. Under Update, select Full set of diskettes used to boot the Windows Installation CD, and then click Next twice.
932
About Creating and Updating Recovery Media Update IDR Boot Media dialog box
6. Select the computer for which you want to update disks, and then click Next
.Update Disks dialog box
7. Insert a diskette that you created previously for the computer you selected in step 6, and then click Next. 8. When the Finish screen appears, click View Disk Configuration to display the Disk Configuration Report.
933
9. 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.
Updating the Intelligent Disaster Recovery Diskettes Only

Select this option to update the Intelligent Disaster Recovery diskettes. You do not have to recreate the Intelligent Disaster Recovery diskettes, only update them. When you select this option, the following is updated:
Hardware-specific information for each computer, such as hard disk partition information, 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 Windows Server 2003 computers, Windows Automated System Recovery (ASR) configuration files are contained in the asr.sif and asrpnp.sif files. The ASR files are necessary to recreate partitions on Windows XP and Windows Server 2003 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 updating the Intelligent Disaster Recovery diskettes, click View Disk Configuration to display the Disk Configuration Report. To update the Intelligent Disaster Recovery diskettes 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 and Windows XP, back up System State. For Windows Server 2003, back up Shadow Copy components. For 64-bit Intel Itanium computers, back up the EFI system partition. If the server is also the media server, back up the Backup Exec SQL instance.
934
Make sure that if utility partitions are present on the computer, they are selected for backup. Utility partitions are usually small partitions installed on the hard disk by OEM vendors, and contain system diagnostic and configuration utilities. For more information on selecting utility partitions for backup, see Backing Up Utility Partitions on page 350. 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 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 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 Intelligent Disaster Recovery diskettes. 3. Do one of the following:
To use another computer to update the Intelligent Disaster Recovery diskettes, select Choose a media server that has the IDR option installed, and see Preparing IDR Media Via Other Media Servers on page 937 for details. To use this computer to update the Intelligent Disaster Recovery diskettes, on the Welcome screen, click Next.
4. Select Update Media, and then click Next. 5. Under Update, select IDR diskettes only (includes ASR files for Windows XP/Windows 2003), and then click Next.
935
About Creating and Updating Recovery Media Update IDR Boot Media dialog box
6. Select the computer for which you want to update disks, and then click Next
.Update Disks dialog box
7. Insert a diskette that you created previously for the computer you selected in step 6, and then click Next. 8. When the Finish screen appears, click View Disk Configuration to display the Disk Configuration Report. The Intelligent Disaster Recovery diskettes are now updated.
936
9. Remove diskette #2 from the drive and store both diskettes with the rest of the disaster recovery media.
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.
Welcome to the IDR Preparation Wizard dialog box
2. On the IDR Preparation Wizard Welcome screen, select the Choose a media server that has the IDR option installed, and then click Next.
937
About Creating and Updating Recovery Media Select a Server dialog box
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.
938
Preparing to Recover from a Disaster Using IDR

When a disaster occurs, you can use IDR to return the computer to its pre-disaster state. Recovering a computer is a multi-step process that involves both manual and automatic processes. To recover a computer, you must follow these steps in order: Caution Disconnect any storage area network (SAN) or cluster that is attached to the computer being recovered; otherwise, the hard drives on those computers may also be repartitioned and reformatted. 1. Plan any hardware changes to the computer to be recovered. For more information, see Changing Hardware in the Computer to be Recovered on page 940. 2. Review additional requirements for IBM computers and Windows 2000 computers, if the computer to be recovered is an IBM or Windows 2000 computer. For more information, see Using IDR To Recover IBM Computers on page 941 and Using IDR To Recover Windows 2000 Computers on page 941. 3. Boot the computer using the bootable media created with the IDR Preparation Wizard to install a minimal version of Windows on the computer. Then, if Windows Setup did not automatically repartition and reformat the system, do it now. For more information, see Recovering a Computer Using IDR on page 942. 4. Use the Disaster Recovery Wizard to restore the computer to its pre-disaster state and restore the data files. For more information, see Using the Disaster Recovery Wizard on page 945. 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.
939
Floppy and CD devices cannot be external PC-card drives. Because external PC-card devices are not supported during the GUI-mode Windows Setup phase, they cannot be used to access data, and recovery cannot be completed. If a *.dr file is unavailable for the computer being restored, you can still use IDR to recover the computer, but you must first manually restore the non-critical partition information, including utility partitions. IDR does not recover software mirrored volumes or any kind of software RAID with the auto-partitioning feature. You must manually apply the mirror with the Disk Manager. In addition, hardware RAID components must be set up before you perform the disaster recovery.
Related Topics: Changing Hardware in the Computer to be Recovered on page 940 Recovering a Computer Using IDR on page 942 Using the Disaster Recovery Wizard on page 945
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 you use should be the same size or larger than the original drive; otherwise repartitioning problems may occur. Processors. The computer you want to recover should have the same number of processors as the original, and should be the same type of processor. 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. To install OEM third-party SCSI drivers, select the Custom Setup option during IDR and then add the drivers manually. For more information, see Recovering Computers Requiring OEM-Specific SCSI Drivers on page 950. 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.
940
Using IDR To Recover IBM Computers

To recover an IBM computer equipped with an IBM ServeRAID card, perform the following additional procedures before starting the IDR process:
Install and configure the IBM ServeRAID controller card and ServeRAID software so that a boot partition will be visible to the Windows operating system. Start the server using the IBM servers ServeRAID Configuration and Management CD in the CD-ROM drive prior to using the IDR bootable media. This will start IBM ServeRAID utilities configuration and installation process to view and update the current BIOS and firmware levels.
Refer to the IBM ServeRAID documentation for complete installation instructions for installing Windows on an IBM Server with the ServeRAID controller. Create and initialize the ServeRAID disks in order for partitions to be visible to the Windows operating system.
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 during restore 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 automatically repartitioned after Windows is installed on the system by the IDR Restore Wizard. 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 to the original by the Disaster 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 manually repartitioned later by using Windows Disk Administrator. For example, on the pre-disaster computer, partition C was the boot partition on the first disk and partition D was the system partition on the second disk. When the boot media was created, the Let IDR automatically partition the boot and system drive during restore option was not selected. During disaster recovery, the disks are replaced and in the new configuration, partition C is the boot partition as well as the system partition. In this case, since the drive layouts are not compatible, the disks will not be repartitioned.
941
Recovering a Computer Using IDR
Only basic disks and upgraded dynamic disks (upgraded from basic) are supported. However, any partitions created after upgrading the basic disks to dynamic are not supported. After disaster recovery, the disks that were upgraded dynamic 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 Let IDR automatically partition the boot and system drive during restore option 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 Recovering a Computer Using IDR on page 942.

Recovering a computer using IDR is a multi-step process that involves:
Booting the computer using the bootable diskettes, tape, or CD created with the IDR Preparation Wizard. Using Windows Setup to prepare the computer for recovery. Using the Disaster Recovery Wizard to restore the computer to an operational state and to restore the computers data from the last backup set.
942
To recover a computer using IDR: 1. Locate the type of bootable media you are using in the table below and follow the instructions provided for that type of media:
Bootable media options For this type of media Diskettes Do this
At the computer being recovered, insert the first bootable diskette. Replace the bootable diskettes as prompted. When prompted, insert the Windows installation CD in the computers CD-ROM drive, and then press ENTER. Proceed to step 3. At the computer being recovered, insert the last full backup media that contains the bootable image into the tape drive. Follow the bootable tape drive manufacturers instructions for booting from the tape drive.
Tape
Note You may need 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. CD
At the computer being recovered, insert the Backup Exec IDR bootable CD into the CD-ROM drive.
Note Be sure that the BIOS is enabled to boot from a CD. CD on EFI-aware 64-bit Intel Itanium computer
At the computer being recovered, insert the Backup Exec IDR bootable CD into the CD-ROM drive. On the EFI Boot Manager menu, select the option to boot from CD.
2. For bootable tape or CD, when the Backup Exec Intelligent Disaster Recovery for Windows screen displays, press ENTER to begin the disaster recovery process. The Windows Setup process will occur first, followed by the restoration of data using the Disaster Recovery Wizard Caution When you press ENTER, the computers hard disks may be repartitioned and reformatted, and all existing data may be destroyed.
943
3. If the computer being recovered uses Windows XP or Windows Server 2003, you must press F2 on the Windows Setup screen to enter Automated System Recovery (ASR) mode. IDR uses Windows ASR to restore the critical partitions that were on the computer previously. The partitions are created as they were defined in the ASR configuration file. Note This F2 prompt may display for a very short time. Be sure to look at the bottom of the Windows Setup screen for this prompt and press F2 as soon as you are prompted. 4. If the computer being recovered contains OEM-specific, third-party SCSI or RAID drivers, press F6 when prompted on the Windows Setup screen to manually add the drivers before loading Windows. If you do not add the drivers before loading the operating system, hard drive partitions and tape devices on the computer may not be recognized by Windows. 5. If the computer being recovered is Windows 2000, do one of the following:
If the option Let IDR automatically partition the boot and system drive during restore was selected during the IDR preparation, then all partitions on all critical disks are 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 during restore 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 941.
After selecting a file system, press ENTER. 6. Remove any diskettes or CDs from the drives, and then press ENTER to reboot the computer. Note For a diskette-based IDR on Windows 2000 only, you must insert the Intelligent Disaster Recovery diskettes when prompted. 7. Continue with Using the Disaster Recovery Wizard on page 945.
944
Using the Disaster Recovery Wizard

The Disaster Recovery Wizard guides you through:
Restoring the computer to an operational state. You can 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 is unavailable or if the *.dr file is not current, you can still use IDR to recover the computer. Instructions for recovering the computer without using a *.dr file are included in the following procedure. To restore using the 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.
To use the Disaster Recovery Wizard: 1. After reading the Welcome screen, place the diskette containing the *.dr file into drive A and then click Next. Note If you are recovering a 64-bit Itanium computer, see About Recovering 64-bit Itanium Computers with IDR on page 955 for special considerations. 2. Choose a level of assistance, and then click Next.
Disaster Recovery Assistance Level options Option Automated Description 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.
945
Recovering a Computer Using IDR Disaster Recovery Assistance Level options Option Assisted Description 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 951.
Clear this check box if you replaced any of the hardware on the computer you are restoring. Select this option if the system configuration is the same except for the hard drives. Any hard drives being added must be the same size or larger than the drive being replaced. Otherwise, repartitioning problems may occur.
Restoring to the exact same system
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 or alternate 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. Note If the evaluation period has expired, enter a valid serial number after you select a *.dr file. 4. For Windows XP and Windows Server 2003, go to step 5. For Windows 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 2000 computer, and you receive messages that one or more of the hard drives are smaller than the originals, the version of Windows 2000 that runs the Recovery Wizard may have detected the hard drives in a different order than they were originally configured.
946
If the original configuration does not match, then to a certain extent, you can control the hard drive numbering scheme that Windows 2000 devises. The following chart lists the normal order that Windows 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 Disaster Recovery Wizard cannot detect the hard drive order properly, set up hard drive partitions manually using the Windows Disk Administrator option within the Disaster Recovery Wizard. Then, continue with the automated restore of the backup media. For more information, see Using IDR To Recover Windows 2000 Computers on page 941. 5. 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.
947
To make changes to the hard disk layout, click Run Disk Management. 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 949. If a *.dr file does not exist for the computer being recovered, click Run Disk Management and manually repartition the hard drive to match the partition layout found on the original computer.
6. If you are restoring with bootable CD or diskettes, select one of the following methods to access the storage device: Note If you are using bootable tape, only the Use locally attached media device option is available.
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. Follow all prompts to acquire network connectivity.
7. After media devices are detected, click Next. A Finish screen appears. If changes were made to the partitions, the computer is rebooted. 8. Select the device containing media 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 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 951. 9. Select the device that contains the restore media. 10. 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 used for the restore. 11. Remove any diskettes and CDs from the drives.
948
12. 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. The Edit BOOT.INI option is not available for 64-bit Itanium computers. Caution Modifying the boot.ini file incorrectly may prevent the computer from restarting. 13. Click Finish to exit the Recovery Wizard and restart the computer. Related Topics: Changing Hardware in the Computer to be Recovered on page 940
Altering Hard Drive Partition Sizes

When recovering a Windows 2000 computer, IDR restores the hard drive partitions to the same sizes they were before the disaster. There may be unused and unallocated space. If the hard drive in the target computer is larger than the hard drive that was in place before the disaster occurred, run the Windows Disk 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 during restore 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. Related Topics: Changing Hardware in the Computer to be Recovered on page 940 Backup Exec Utility on page 717
949
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 and tape devices on the computer may not be 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. Related Topics: Changing Hardware in the Computer to be Recovered on page 940
950
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: Note If you are restoring Windows 2000 computers that have utility partitions, first recreate the utility partitions using the OEM-supplied media. 1. Follow step 1 through step 8 in Using the Disaster Recovery Wizard on page 945. 2. If you provided a *.dr file, verify that the I will provide my own media option 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. It is recommended that you do not use drive C for the alternate location. 5. Do one of the following:
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 reappears 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. Click Skip Set to skip the restoration of this backup set and search the media for another backup set from which to restore. Click Skip Media to eject the media and replace it with different media.
6. After the last backup set is restored, click Finish to end the recovery process and exit Intelligent Disaster Recovery.
951
Related Topics: Recovering Computers Requiring OEM-Specific SCSI Drivers on page 950 Changing Hardware in the Computer to be Recovered on page 940
Performing Remote IDR

Remote IDR restores data to a Windows computer over a network from a Backup Exec media server. To recover a computer using a remote media server: 1. Follow step 1 through step 6 of Using the Disaster Recovery Wizard on page 945. 2. On the Connect to Media Server screen, enter Backup Exec service account information to log on to a media server where the storage device is located. Be sure that the service account you specify can run Backup Exec jobs normally and does not have a blank password. 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. In an environment that has no DHCP, remote IDR requires that the network adapter in the computer being recovered is the same one from the original system. If the original network adapter is not available, click View Network Connections to view a list of available network adapters. Select the network adapter you want to change, and then click Properties to change the IP address to static or dynamic. 3. Click Next. 4. To restore automatically, select the drives to recover; otherwise select I will provide my own restore media. 5. Click Next. 6. If you selected I will provide my own restore media, then on the navigation bar on the media server click Restore, and on the Restore Job Properties dialog box, select the backup set to restore. 7. On the Properties pane, under Source, click Resource Credentials, and change the Backup Exec logon account to the Temporary IDR User logon account.
The Temporary IDR User logon account was created by the IDR Recovery Wizard on the Connect to Media Server dialog box in a previous step. Related Topics: Microsoft SQL Server Recovery Notes on page 953 Microsoft Exchange Recovery Notes on page 954 Using IDR To Recover IBM Computers on page 941 Recovering Computers Requiring OEM-Specific SCSI Drivers on page 950 Changing Hardware in the Computer to be Recovered on page 940 Using Backup-to-Disk Folders and Files on page 176
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. Related Topics: Using Snapshot Technology With the SQL Agent on page 1022 Understanding the Advanced Open File Option on page 991
953
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. Related Topics: Disaster Recovery for Exchange 2000 and 2003 on page 1108 Disaster Recovery for Exchange Server 5.5 on page 1111
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. Related Topics: Disaster Recovery of a SharePoint Portal Server on page 1370
Citrix Metaframe Recovery Notes

Backup Exec supports IDR of Citrix Metraframe 1.8, XPa, XPe, and XP computers with the following exceptions:
IDR of a remote computer is not supported if Citrix is installed on the media server and drive C on the media server is remapped. If other drives on a Citrix computer were remapped prior to IDR, the drives must also be remapped during the IDR process before any files are restored.
If you selected Automated or Assisted during the IDR process and selected a *.dr file, Backup Exec automatically remaps the drives. If you selected Automated, Assisted, or Manual during the IDR process, but did not select a *.dr file, you must manually remap the drives.
954
Using IDR with the Central Admin Server Option

If you have purchased and installed the Central Admin Server Option (CASO), you can perform IDR of the managed media servers (MMS) in a CASO environment. To prepare recovery media for the managed media servers, you must run the IDR Preparation Wizard on the Central Admin Server (CAS). The *.dr files are stored on the CAS. During IDR recovery of an MMS, all restore jobs are submitted from the CAS. The CAS will then send the restore jobs to the appropriate managed media server. Related Topics: Disaster Recovery Using Intelligent Disaster Recovery (IDR) with CASO on page 874
Using IDR with VERITAS Storage Foundation for Windows

If you use VERITAS Storage Foundation for Windows on Windows 2003, IDR can restore the dynamic volumes. During backup, IDR gathers the applications and components necessary to restore the dynamic volumes and adds them to the recovery media. During recovery, the gathered applications are run as part of the Windows Automated System Recovery (ASR) process in order to bring back the dynamic volumes. After the dynamic volumes are recovered, the data recovery on the volumes proceeds as usual.
About Recovering 64-bit Itanium Computers with IDR

Note the following when recovering 64-bit Itanium computers:
Extensible Firmware Interface (EFI) partitions, which are present on all 64-bit Intel Itanium computers, need to be restored. Because the operating system boot loader is present on the EFI partitions, these partitions are critical for booting the system. Only bootable CDs are supported for IDR on 64-bit Itanium computers. Most 64-bit Itanium computers do not have floppy drives. When creating bootable CDs, verify that a floppy drive is present on the 64-bit Itanium computer before copying the .asr files to a diskette. 64-bit Itanium computers can only be recovered remotely by connecting to a 32-bit media server.
Related Topics: Performing Remote IDR on page 952
955
Best Practices for IDR
Best Practices for IDR
Remote IDR
If you want to perform disaster recovery on a remote computer, the Remote Agent must be purchased separately and must be running on the remote computer. Always verify that the *.dr file was created in the alternate data path that you selected. When creating bootable tape, run the IDR Preparation Wizard and create the bootable image before you run a full backup. When creating bootable CD or floppy disks, run a full backup before you create the bootable media. Have the Windows license key available. The license key is needed to install the operating system. If the backup media resides on another Backup Exec media server, select the option Choose a media server that has the IDR option installed on the first IDR Preparation Wizard screen. For local IDR, do not use Backup-to-Disk. Floppy disks cannot be used for IDR on Windows 2003 and Windows XP computers. Have at least 6 blank floppies available. Windows 2000/2003/XP must have at least 2 GB of hard drive space available. The new partition layout must be the same size or larger than the original. Have the latest RAID, SCSI, or NIC (if remote) drivers available on disks.
Creating Bootable Media
Disaster Recovery

956
Appendix
Symantec Backup Exec - SAN Shared Storage Option

The Symantec 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 Switched Fabric (FC-SW) or iSCSI. To allow for sharing of storage devices and media between multiple media servers, a shared Advanced Device and Media Management (ADAMM) database resides on one media server called the database server or primary server. All media servers on the SAN connect to this database to obtain a single, unified view of all shared devices and media. Backup Exec uses this shared database to arbitrate all device and media requests with comprehensive overwrite protection policies to prevent accidental media overwrites. To resolve potential access conflicts between multiple media servers, Backup Exec reserves robotic arms and tape devices while operations are being performed. Media catalogs are shared between media servers, so restore operations can be performed using any media servers that share catalogs. If the media must be moved from one device to another on the SAN, the media does not have to be cataloged again. In a shared storage environment, secondary storage devices also can be attached to the local SCSI 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-SW through a fibre to SCSI bridge (router) to secondary storage devices (SCSI robotic libraries).
957
Example of the SAN Shared Storage Option using FC-SW
Workstation LAN Server A Database Server Server B Server C
Fibre Channel Switched Fabric Hub Fibre-to-SCSI Bridge
SCSI Tape
SCSI Tape
You can use any media server to change the names of the robotic libraries and drives to names that are more descriptive of your operations. If you have multiple SANs, it is recommended that you treat each SAN independently, with each SAN having its own Backup Exec database server for the shared ADAMM database and catalogs for that loop. Using a single Backup Exec database server for more than one SAN increases the number of single-point failures that can affect the system. Job completion statistics or errors can be viewed through any administration console attached to the server that ran the job. RELATED TOPICS: Sharing Media on page 971. Scheduling and Viewing Jobs on page 970 Requirements for the SAN Shared Storage Option on page 959
958
Requirements for the SAN Shared Storage Option
Requirements for the SAN Shared Storage Option

The following are the minimum system requirements for running this release of the SAN Shared Storage Option:

Windows 2000 or Windows Server 2003 must be installed. Physical Memory Available, as shown in the Windows Task Manager, plus the File Cache should exceed 256 MB. The SAN Shared Storage Option must be locally installed at each server that will be sharing secondary storage devices. The devices in your SAN must be on the supported device list at http://support.veritas.com/rd/bews-compatibility.htm All hardware drivers must be up to date and started. See http://support.veritas.com/rd/bews-drivers.htm The primary server must have enough space for the catalogs of all the servers in the SAN. 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).
For a fibre channel-connected installation, note the following additional requirements:
Note If the SAN Shared Storage Option is installed on a media server, Backup Exec disables all fibre channel-connected devices in Removable Storage. You cannot re-enable the devices in Removable Storage until the SAN Shared Storage Option and VERITAS device drivers are uninstalled. Related Topics: Installing the SAN Shared Storage Option on page 960
Appendix F, Symantec Backup Exec - SAN Shared Storage Option
959
Installing the SAN Shared Storage Option
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 on page 65. If you have already installed Backup Exec, follow the procedures described in Installing Backup Exec Options to the Local Computer on page 71. If installing to the database server, select Primary. You can install the Backup Exec device drivers as part of the Backup Exec installation. If the SAN Shared Storage Option has already been installed to the primary, or database, server, and you are installing to a secondary server, select Secondary and enter the name of the database server. If you installed Backup Exec on the database server, reboot the database server before loading Backup Exec on other servers. The server containing the shared database must be running before other media servers can be installed properly. The first time you run Backup Exec, the First Time Startup 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 appropriate 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 93. Related Topics: Symantec Backup Exec - Remote Agent for Windows Servers on page 789 Starting Backup Exec on page 108 Scheduling and Viewing Jobs on page 970 Best Practices for SAN SSO on page 979
960
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 the Tools menu, 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 Fibre Channel Switched Fabric (FC-SW). FC-SW is a fibre channel configuration in which the devices are connected in a network using a fibre channel switch. Storage devices are categorized as either robotic libraries or stand-alone drives. The Library Expansion Option is required to support robotic libraries with multiple tape drives (see Symantec Backup Exec - Library Expansion Option on page 1115). 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 supported for shared storage environments. Related Topics: Using Drive Pools with the SAN Shared Storage Option on page 963 Using Device Operations with the SAN Shared Storage Option on page 964
Appendix F, Symantec Backup Exec - SAN Shared Storage Option 961
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. You can also run the Device Summary report to monitor drives in the SAN Shared Storage Option. To view drive properties for shared devices, follow the steps in Viewing and Using Device Properties and Statistics on page 151. With shared devices, the Write single block mode and Write SCSI pass-through mode options are selected by default. Selecting these options decreases the chances of dropping critical blocks of data and provides more detailed information when write errors occur. These options are required for FC-connected tape drives. Related Topics: Policy Jobs Summary Report on page 590 Viewing Drive Configuration Properties on page 154
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 126. Related Topics: Using Drive Pools with the SAN Shared Storage Option on page 963 Using Device Operations with the SAN Shared Storage Option on page 964 Scheduling and Viewing Jobs on page 970
962
Using Drive Pools with the SAN Shared Storage Option

When Backup Exec is installed, the All Drives (<Server Name>) is created by default. In a non-shared storage environment, this default drive pool contains the servers locally attached drives. In a shared environment, this default drive pool is created for each server using the SAN Shared Storage Option, and contains both locally attached and shared devices. Symantec recommends creating a shared storage drive pool, which contains only shared devices. To create a drive pool, see Creating Device Pools on page 133. 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. Related Topics: Managing Devices on page 123 Creating Device Pools on page 133
963
Using Device Operations with the SAN Shared Storage Option

Device operations allow you to manage the physical drives attached to the media servers and perform some operations on the media in the drives. The steps for deleting drives, pausing and resuming drives, completing the inventory drive process, cataloging media, labeling media, and erasing media are identical in the shared and non-shared storage environments. Related Topics: Managing Devices on page 123 Scheduling and Viewing Jobs on page 970 About Devices in the Shared Storage Environment on page 961 Sharing Media on page 971
Renaming Robotic Libraries and Drives

You cannot rename a server, but you can rename robotic libraries and drives to make them more easily identifiable. You may want to use names that are more descriptive of your operations, or you may want to identify the device by the user or location, such as DATA_CENTER_ROBOTIC LIBRARY. The names of all servers attached to the SAN appear when Devices is selected from the navigation bar. Press F5 to manually refresh the screen and view new names. The robotic libraries and drives can be renamed from any server sharing the ADAMM database, and the new names will appear on all servers on the SAN. Note The Device Management window on other Backup Exec administration consoles may need to be manually refreshed before the new names appear on them. Related Topics: Pausing, Resuming, and Renaming Devices on page 130
964
Sharing Robotic Libraries Between Backup Exec for NetWare Servers and Backup Exec for Windows Servers
Backup Exec for NetWare Servers and Backup Exec for Windows Servers SAN Shared Storage Options inside the same fibre environment can share robotic libraries, which lowers hardware costs. With robotic library sharing, you first create partitions 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 Servers. You can view NetWare servers from a NetWare console and Windows servers from a Windows console. If a Backup Exec for NetWare Servers job is targeted to a drive being used for a Backup Exec for Windows Servers job, the drive appears as reserved. Related Topics: Viewing Devices on page 125 Library Sharing Prerequisites on page 965 Configuring Media Servers for Robotic Library Sharing on page 966
Library Sharing Prerequisites

Before you can share libraries, you must have the following installed:

Backup Exec for Windows Servers on the Windows media servers. Backup Exec for NetWare Servers version 9.0 or later on the NetWare media servers. The Backup Exec for Windows Servers SAN Shared Storage Option on each Windows media server you want to operate in the shared environment. Backup Exec for NetWare Servers SAN Shared Storage Option on each NetWare media server you want to operate in the shared environment. The Backup Exec for Windows Servers Library Expansion Option or the Backup Exec for NetWare Servers Library Expansion Option.
Note The drive licenses you purchase for your robotic library are not platform-specific for this implementation. For example, if you plan to share a ten-drive robotic library, you can purchase nine Backup Exec for Windows Servers or Backup Exec for NetWare Servers drive licenses (the first drive in a robotic library does not require a Library Expansion Option license). In order to successfully share robotic libraries, you need a working knowledge of both Backup Exec for Windows Servers and of Backup Exec for NetWare Servers. You also should have complete access to hardware and the ability to restart media servers.
965
Before proceeding with the robotic library sharing configuration, plan how you want to use your robotic library in this shared environment. For example, if you have a robotic library that has 100 slots in it, you may want to partition your robotic library so Backup Exec for Windows Servers uses 50 slots and Backup Exec for NetWare Servers uses 50 slots. Factors affecting how many slots you use for each operating system include media rotation schemes, the number of servers you are protecting, and the types of data stored on each server. Label your media according to operating system or Backup Exec type. Color-coded or unique bar codes identifying whether the tapes are being used with Backup Exec for Windows Servers or Backup Exec for NetWare Servers is recommended. This will help you identify the media when you need to restore data or rotate the media back into your media rotation schedule.
Configuring Media Servers for Robotic Library Sharing

You must ensure that no backup activity is occurring during robotic library sharing configuration. Note If you are running Backup Exec for NetWare Servers 9.1 on any of the media servers that will be sharing the library, all Backup Exec for NetWare Servers media servers in the shared storage environment must be installed in the same media handling mode. To configure 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. On the navigation bar, click Devices. The tree pane contains a list of any fibre-attached or locally-attached devices. 3. Select the robotic library you want to share. 4. Under Robotic Library Tasks in the task pane, select Configure partitions. 5. Set up your partitions following the steps provided in Creating Robotic Library Partitions on page 172. 6. From the Devices tree pane, select the drive in this partition that will not be used by your Backup Exec for Windows Servers media servers. 7. Delete the drive to ensure no jobs run to the unused partition.
966
8. Repeat steps 6 and 7 for all drives in the unused partition. 9. Reboot all other Windows servers and make sure you can see the shared robotic library on each server. Note No fibre activity or backup jobs should be run until all Backup Exec for Windows Servers and all Backup Exec for NetWare Servers are configured for robotic library sharing. To configure Backup Exec for NetWare Servers 9.x running in the partition management mode: 1. From the Administration Console, ensure you are connected to the Primary Group Server and that you are running in partition management mode. From the Administration Console for NetWare at the Primary Group Server, ensure you are running in partition management mode. 2. Delete existing partitions. To delete a partition from the Administration Console: a. Click Drives.
b. Click Partitions. c. Right-click the partition you want to delete, and click Delete.
d. When prompted, click OK. e. Repeat step c and step d for each partition you want to delete.
To delete a partition from the Administration Console for NetWare: a. Select Drives.
b. Select Partitions. c. Select the partition you want to delete, and press DEL.
d. When prompted, press Y. e. Repeat step c and step d for each partition you want to delete.
3. Create the partitions in the shared library to be used by Backup Exec for NetWare Servers.
To create a partition from the Administration Console: a. From the Administration Console, click Drives.
b. Right-click Partitions. c. Click New Partition.
d. Enter options on the New Partition dialog box. e. Click OK.
4. Enter options in the New Partition General dialog box. 5. Enter options in the New Partition Configuration dialog box. 6. Click OK. To create a partition from the Administration Console for NetWare: a. From the Administration Console for NetWare, select Drives.
b. Select Partitions. c. Press INS.
d. Select a drive to be included in this partition. e. Ensure Configuration is selected, and press ENTER to view or edit options on the Configuration dialog box. Press F2 to return to the General dialog box. Select Advanced Configuration and then press ENTER to view or edit options on the Advanced Configuration dialog box.
f. g.
h. Press F2 to return to the General dialog box. i. Press F2.
7. If you plan to share more than one library, repeat step 2 and step 3 for each library that will be shared. 8. Restart Backup Exec for NetWare Servers on the group servers and make sure you can see the shared library on each server.
To configure Backup Exec for NetWare Servers 9.x running in the media management mode: 1. From the Administration Console, ensure you are connected to the Primary Group Server and that you are running in media management mode. From the Administration Console for NetWare at the Primary Group Server, ensure you are running in media management mode. 2. Select Drives. 3. Select Drive Pools. 4. Select All Drives. 5. From the Administration Console, right-click the robot you want to share, and then click Properties. From the Administration Console for NetWare, select the robot you want to share, and press F4. 6. Select Configuration. 7. Enter the starting slot and number of slots to be used by NetWare servers. 8. From the Administration Console, click OK. From the Administration Console for NetWare, press F2. 9. Restart Backup Exec for NetWare Servers on the group servers and make sure you can see the shared library on each server. Related Topics: Symantec Backup Exec - Library Expansion Option on page 1115
969
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. Note If your job is awaiting a storage device, the Job Monitor window will not display a Device Name. Also, if the Job Status displays as Queued, the job is awaiting an available storage device. With the SAN Shared Storage Option enabled, all of the media servers share access to the storage devices through the shared ADAMM database. The server that reserves the storage device first runs its job first. Therefore, a job scheduled by a server may not run exactly when scheduled if all the storage devices are being used by other servers. When a server releases control of a device, there is a short delay before the server looks for additional jobs to process. This delay provides a window of opportunity for other media servers to reserve the shared storage device. If a device fails during a nonrecurring job, that job will fail and will be rescheduled on hold. If a device fails during a recurring job, the job is rescheduled. The device is then released for the next job scheduled for that device. But, depending on why the device failed, the second job may become trapped. This might prevent other jobs from seeing the device, running to normal completion, or failing and being rescheduled to an "on hold" status. If you determine that a device is malfunctioning, you may want to retarget jobs to another drive or quickly replace the failed drive and resume the jobs that were placed on hold. Related Topics: Backing Up Data on page 259 Restoring Data on page 451 Monitoring Jobs on page 405 Viewing and Changing Completed Jobs on page 427
970
Sharing Media
The Backup Exec servers can share media within the shared storage devices, but not simultaneously. For example, media server A can write a backup to a media, and when that job is finished, media server B can append another backup to the same media. Or, if overwrite protection is not enabled, media server B may overwrite that media. Media sets are not server-centric. In the shared storage environment, all users have a view of all media and media sets. Each media set can contain media in the shared devices and media in any local devices attached to servers. Note The default media overwrite protection is not server-centric; this option is set in the shared ADAMM database and affects all media, including media in locally attached devices. For example, if media overwrite protection is set to None by one server, all media in the shared storage environment including media in other servers locally attached devices are immediately available for overwriting. Media stored in locally-attached secondary storage devices are not accessible by other media servers.
Cataloging Media in SAN SSO Environments

The SAN Shared Storage Option uses a shared catalog database. A tape that has already been cataloged can be physically moved from one device to another and will not have to be recataloged. If the primary server is not available over the network when a secondary server generates catalog information, the information is stored temporarily on the secondary server until automatic catalog synchronization occurs. Because catalogs are shared, information can be restored using any server that has access to a device where the tape resides. If the tape resided in a shared device, or in a local device on the server where you want to perform the restore, simply start a restore job. Otherwise, you have to move the tape into a drive that is accessible. Related Topics: Cataloging Media in a Drive on page 452
971
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.
Related Topics: Scheduling and Viewing Jobs on page 970
972
Designating a New Database Server and Setting Up Servers

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

A newer, faster server has become available. The database server has stopped functioning.
If the current database server is functioning, you should consider specifying the current database server when installing SAN Shared Storage Option to the new system. This will allow you to test the fibre connections before designating a new database server. If the current database server is not functioning, installing the new system as the database server is recommended. For steps on designating a new database server, see Running Backup Exec Utility SAN SSO Tasks on page 751.
Tips for Maintaining the Database Server and the ADAMM Database
The ADAMM database and the database server are important components of the SAN Shared Storage Option. To protect against possible loss of the ADAMM and catalog databases, you should run frequent backup jobs of the entire Backup Exec directory tree on the shared database server. When scheduling backups of the database servers Backup Exec directory, base the frequency of these backup jobs on the rate at which backup sets are being created and the number of tapes affected by all of the media servers on the SAN. All backup sets and tapes affected since the last shared database/catalog server backup would have to be recataloged if all information on the database server was lost. Create a special media set just for backing up the Backup Exec directory tree and the Windows operating system on the database server. This will reduce the number of tapes that must be cataloged to find the files for restoring the ADAMM database and catalogs. Caution If you allow the backups of these files to go to a large media set, you may have to catalog every tape in that large media set in order to find the latest versions of the ADAMM database and catalogs to restore. If the database server is not operational, Backup Exec is unusable on all of the servers on the SAN. The Intelligent Disaster Recovery Option is strongly recommended for protecting the database server. Should this entire system be lost, you can use IDR to quickly recover this system.
If you deem the Backup Exec functions to have a high availability requirement, you should consider setting up one of the other media servers on the storage network as a standby primary server.
Creating a Standby Primary Database Server

You should have a standby server configured and available in case your primary server fails. To avoid data loss if the primary database server fails, Symantec recommends that you save the bedb.bak file and the Catalogs directory to a separate server after the scheduled daily database maintenance. To create a standby primary SAN SSO server: 1. Use BEUtility to add all the SAN servers that will use the new primary SAN SSO server (see Add a New Media Server on page 722.) 2. Use BEUtility to create a media server group that contains all the servers you added in step 1 (see Create a New Media Server Group on page 723.) Note Do not select the Create group from SAN SSO configuration option. 3. Use BEUtility to promote a new SAN SSO server to primary in the media group you created (see Promote a Media Server to a Primary SAN SSO Server on page 754.) 4. Use BEUtility to stop the Backup Exec services on all media servers in the media server group (see Stop Services on page 734.) 5. On the media server that you promoted to primary, navigate to \Program Files\VERITAS\Backup Exec\NT\Data Directory and rename the bedb.bak file to indicate that this is the original file. Example originalbedb.bak or bedborg.bak 6. On the original primary server, navigate to \Program Files\VERITAS\Backup Exec\NT\Data Directory. Copy the bedb.bak file to the same directory on the new primary server. If the original primary server is unavailable, locate the latest copy of the bedb.bak file and copy it to the new primary server. 7. On the media server that you promoted to primary, navigate to \Program Files\VERITAS\Backup Exec\NT. Rename the Catalogs directory to indicate that this is the original.
974
8. On the original primary server, navigate to \Program Files\VERITAS\Backup Exec\NT. Copy the Catalogs directory to the same directory on the new primary server. If the original primary server is unavailable, locate the latest copy of the Catalogs directory and copy it to the new primary server. 9. Use BEUtility to restore the database you copied in step 6 (see Recover a Media Server Database on page 760.) Be sure to select the Drop existing database and reload from backup option. 10. Use BEUtility to start the Backup Exec services on all the media servers in the media server group (see Start Services on page 734.) Related Topics: Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901 Promote a Media Server to a Primary SAN SSO Server on page 754 Creating a Manual Restore Job by Configuring Job Properties on page 458 Move the Primary SAN SSO Server on page 755
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 92 and Running Backup Exec Utility Services Tasks on page 733.
975
Troubleshooting and Recovering Failed Components

Various problems can occur at any location in a SAN. In order for Backup Exec to work properly, a device has to be recognized in three locations; the bridge/router must recognize it as a SCSI device, the operating system must recognize it as a device, and Backup Exec must recognize it as a supported device. In some cases, there will be a problem with your hardware that will require you to contact your hardware vendor for technical support. You may need to replace a component of your SAN, such as a bridge or hub. For specific steps for replacing your equipment, refer to your hardware vendors documentation. Related Topics: Checklist for Troubleshooting Devices That Have Gone Offline on page 976
Checklist for Troubleshooting Devices That Have Gone Offline

If a device in your SAN has gone offline, follow these steps to determine the source of the problem. 1. Before you begin troubleshooting, verify that your devices are on the Backup Exec supported device list, which is located at http://support.veritas.com/rd/bews-compatibility.htm. Also verify that all hardware drivers are up to date and started. 2. Use the Windows Device Manager to verify that the operating system recognizes the device. If the device is not recognized, see SAN Hardware Tips on page 977. 3. For robotic libraries, verify that robotic library support is installed. 4. Check the system event log for the following errors, which indicate SAN communication errors: SCSI errors 9, 11, and 15, or timeout errors relating to storage. Check the application event log for multiple events 33152. These events indicate SAN communication errors. See SAN Hardware Tips on page 977 or contact your hardware vendor. 5. If the library is online, but some or all of the drives are offline, use Backup Exec to initialize the library. To initialize the library: a. On the navigation bar, click Devices.
b. Select the library, and then under Robotic Library Tasks, click Initialize
976
6. If initializing the library does not bring the devices online, check the library for the following: an error display on the front panel, mechanical problems, or tapes inappropriately in the drives. Correct any errors that you find. 7. If no errors exist on the library or if you corrected the errors and the devices are still offline, stop Backup Exec services and then restart them when all Backup Exec jobs are inactive in the SAN. 8. If restarting the services does not bring the devices online, restart the operating system. Be sure that no Backup Exec jobs are running when you restart. 9. If restarting the operating system does not bring the devices online, reset the SAN to help identify problem tape devices. Recycling the SAN may also resolve fibre problems. Related Topics: Resetting the SAN on page 978
SAN Hardware Tips

The following is a list of common hardware errors that occur in a SAN environment. If you find errors with your hardware, please contact your hardware vendor for specific instructions. 1. Verify that the proper device drivers were installed: 2. Verify that the fibre cable is securely connected to the HBA and the switch. 3. Verify that the SCSI bridge is properly connected to the library and the switch. Apply normal SCSI troubleshooting techniques at the fibre to SCSI bridge. Use a bridge administration tool to verify that the bridge recognizes all of the devices. Also verify that the bridge firmware is up to date. 4. If some of the servers in the SAN recognize the tape devices, but other servers do not, check for a failed hardware component between the server and the switch. If none of the servers in the SAN recognize the tape devices, check for a failed hardware component between the switch and the tape devices. 5. Reset the SAN, which may identify problem hardware components and may resolve fibre problems.
977
Resetting the SAN

To reset the SAN: 1. Power down all servers, libraries, and SCSI to fibre bridges in the SAN. Note In rare cases, you may need to power down the switch also. If you need to power down the switch, you should power it on before any other components and wait for all checks to complete before powering on other components. 2. Power on the library. 3. After the library initialization is complete, power on the bridge. 4. Verify that the library recognizes the switch. 5. Power on the primary SSO server. 6. Verify that the operating system recognizes the library and drives. 7. Power on one of the secondary SSO servers. Wait for the secondary server to boot before powering on the other secondary SSO servers.
Bringing Devices Online After an Unsafe Device Removal Event

If a device is in use by Backup Exec at the time of an unsafe device removal event, the device will go offline in Backup Exec. To bring a device online after an unsafe device removal event: 1. Verify that no Backup Exec jobs are running in the SAN. 2. If the library is online, but the drives are offline, use Backup Exec to initialize the library. If initializing the library brings the drives online, you have completed this procedure. If initializing the library does not bring the drives online, proceed to step 3. 3. If the library is offline or if the drives are offline after initialization, stop all Backup Exec services and then restart them. 4. If steps 1-3 do not bring the device online again, see SAN Hardware Tips on page 977.
978
Best Practices for SAN SSO
Before installing Backup Exec, be sure that all hardware in the SAN is working and configured properly. Make sure that the primary server is the fastest server and has the fewest extraneous operations. Use a separate primary server for each SAN. Make sure that the HBA drivers, SCSI to fibre bridges, and library firmware have been updated to the hardware vendors most current release. Make sure that all HBA cards on the SAN are using the same and the most current firmware and driver levels. Keep the servers in the SAN in the same Microsoft Administration domain. Cross-domain environments can cause authentication problems during install and can block access to resources during backups. Change the display names of libraries and drives to names that reflect the servers or jobs for which you will use them. Do not use cascaded drive pools in a SAN environment. Run frequent backups of the entire Backup Exec directory tree on the shared database server. Create a separate media set to use only for backups of the Backup Exec directory tree and the Windows operating system on the database server. This will reduce the number of tapes you need to catalog to find the files to restore the ADAMM database and catalogs. Use a switch administration tool to verify that each server is in a zone configuration with the tape devices. Disable the operating systems removable storage service.
979
980
Appendix
Symantec Backup Exec ServerFree Option

The Symantec 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. 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.
981
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 Symantec 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 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.
982
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 G, Symantec Backup Exec - ServerFree Option
983
ServerFree Backup Configuration

The ServerFree Option works in conjunction with other Symantec high performance options including the SAN Shared Storage Option (SSO) and a snapshot provider such as the Symantec 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 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. Symantec 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 Symantec 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
Software To install the ServerFree Option on a media server, you need to purchase the following Symantec Software products:

Backup Exec for Windows Servers SAN Shared Storage Option ServerFree Option (includes the Advanced Open File Option)
984
Note ServerFree Option by default, uses the included Symantec Volume Snapshot Provider from the Advanced Open File Option, to create a snapshot of the volume on the fibre disk array. Alternatively, VERITAS Storage Foundation for Windows FlashSnap Option can be used to create the snapshot of the volume on the fibre disk array.

(Optional) VERITAS Storage Foundation for Windows 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.
Related Topics: Installing Backup Exec Options to the Local Computer on page 71 Supported Operating Systems for the media server
Windows 2000
Note Consult your hardware documentation for Windows XP and Windows Server 2003 compatibility. Supported Symantec Backup Exec Agents and Options The ServerFree Option works with the following:

Symantec 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.
985
ServerFree Backup Component Configuration Network
Fibre channel host bus adapter (HBA)
Fibre-to-SCSI bridge or router
- Backup Exec for Windows Servers - Symantec SAN Shared Storage Option - Symantec ServerFree Option - Windows 2000
- (optional) VERITAS Storage Foundation for Windows FlashSnap Option
Fibre Channel Switch with attached fibre channel storage
SAN-attached
Installing the ServerFree option

To install the ServerFree Option, see Installing Backup Exec Options to the Local Computer on page 71. Note The SAN Shared Storage Option must be installed on the media server before you can install the ServerFree Option.
986
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 Symantec Volume Snapshot Provider by default. Note Microsoft Volume Shadow Copy Service cannot be used in a ServerFree backup job configuration. Note The VERITAS Storage Foundation for Windows (VSFW) FlashSnap Option is compatible with Windows 2000 only. The volumes you want to back up with the VSFW FlashSnap Option must first be snap-started using the Symantec Enterprise Administrator. For more information, see Using Snap Start on a VERITAS Storage Foundation for Windows Volume on page 1005. 6. Select Use ServerFree Option. Start the backup job or select other options from the Properties pane. Note If the Verify after Backup option is enabled, the byte count reported by the verify operation will be substantially smaller than that reported when the backup completes. Since file data is moved directly from disk to tape during a ServerFree backup, no checksums can be generated and subsequently verified. As a result, the byte count for a verify operation does not count the file data.
Appendix G, Symantec Backup Exec - ServerFree Option 987
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 Symantec Volume Snapshot Provider by default. Note Microsoft Volume Shadow Copy Service cannot be used in a ServerFree backup job configuration. Note The VERITAS Storage Foundation for Windows (VSFW) FlashSnap Option is compatible with Windows 2000 only. The volumes you want to back up with the VSFW FlashSnap Option must first be snap-started using the VERITAS Enterprise Administrator (VEA). For more information, see Using Snap Start on a VERITAS Storage Foundation for Windows Volume on page 1005. 5. Select Use ServerFree Option.
988
Restoring A ServerFree Backup

ServerFree restore jobs are done in the same manner as any other 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 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. Related Topics: Restoring Data on page 451
989
990
Appendix
Symantec Backup Exec Advanced Open File Option

The Symantec Backup Exec for Windows Servers - Advanced Open File Option (AOFO) is installed as a separate, add-on component of Backup Exec for Windows Servers. The Advanced Open File Option uses advanced open file and image technologies designed to alleviate issues that are sometimes encountered during backup operations, such as protecting open files and managing shortened backup windows. Related Topics: Understanding the Advanced Open File Option on page 991 Supported Snapshot Technologies on page 994 Best Practices for Using the Symantec Volume Snapshot Provider on page 1006 Symantec Backup Exec - ServerFree Option on page 981
Understanding the Advanced Open File Option

When a job is submitted for backup with Advanced Open File selected, a snapshot of each volume is created, providing a point-in-time record of the data. When creating a snapshot, Backup Exec uses advanced snapshot technologies to momentarily suspend write activity to a volume so that a snapshot of the volume can be created. If the files selected for backup reside on more than one volume, by default Backup Exec creates a snapshot for each volume that contains data to be backed up. For example, if the data to be backed up resides on a single volume, a single snapshot is created. If data resides on four volumes, four snapshots are created. After creating a snapshot, the data is backed up from the snapshots, and then the snapshots are deleted.
991
During the backup, files can be open and data can be changed. Depending on the snapshot provider that you are using, open files are handled using different methods. For details on how the Symantec Volume Snapshot Provider handles open files during a backup, see Best Practices for Using the Symantec Volume Snapshot Provider on page 1006.
Advanced Open File Option with Symantec Snapshot Provider Backup Exec media server
3 2
Volume C: Snapshot C:
Original Word file (open) Start of backup job Data Block During the backup, data is changed A B 1 2 B i D End of backup job Data Block A 1 D 2 C 3 iii Changed file C 3 B ii Cache file for original data
The illustration represents the following: 1 - A backup begins for volume C on a Windows server using the Advanced Open File Option.
992
2 - A snapshot is taken of volume C, that provides a point-in-time record of the data. 3 - After the snapshot is taken, the backup job starts and the data from volume C is written to tape. During the backup job, files can be opened, and data can change. The Advanced Open File Option allows data to change by making a copy of the original data, named a cache file. The snapshot tracks the data changes, as illustrated in the cache file diagram. For example, an open file such as a Microsoft Word document contains the data A, B, and C in blocks 1, 2, and 3. i - During the backup job, "B" changes to "D" in block 2. ii - The original data in block 2 is copied to a cache file. In this case, "B" is the original data. iii - The changed file is now the most current file. 5 - When the snapshot comes to a changed block, it replaces these changed blocks with the original data from the cache file before being sent to tape. The snapshot then sends the point-in-time data to Backup Exec. The data is then written to tape. When the backup is complete, the snapshot is deleted. Symantec strongly recommends that Backup Exec database agents be used to back up databases. Backup Exec database agents provide selective restores of data and more integration with the database application while preventing backups of partial transactions. Agents also enable backups on a database that is spread across multiple disk volumes. If the Advanced Open File Option is selected for a backup job on Microsoft SQL or Microsoft Exchange Servers, all database files on these servers will automatically be excluded from the backup. For Oracle Server, to avoid backing up the database files twice, you should manually exclude any Oracle database files from backup jobs run with AOFO selected. You can use the Advanced Open File Option on the same volume as a database to provide open file support for other applications. The Advanced Open File Option provides generic protection for flat files when Backup Exec agents are not used, and provides protection for Microsoft Outlook PST files. The Advanced Open File Option is not available for use with Extensible Firmware Interface (EFI) system partition backups. Related Topics: Symantec Backup Exec - Agent for Microsoft Exchange Server on page 1065 Symantec Backup Exec - Agent for Microsoft SQL Server on page 1013
Appendix H, Symantec Backup Exec - Advanced Open File Option
993
Symantec Backup Exec - Agent for Oracle Server on page 1297 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Best Practices for Using the Symantec Volume Snapshot Provider on page 1006
Supported Snapshot Technologies

To use snapshot technologies with Backup Exec, you must install the Advanced Open File Option. After making backup selections and choosing the Advanced Open File Option, you can configure Backup Exec to use the snapshot technologies installed on your computers. Backup Exec supports the following snapshot technologies:
Symantec Volume Snapshot Provider (VSP). Installing AOFO will install the Symantec Volume Snapshot Provider (VSP) only. VERITAS Storage Foundation for Windows (VSFW), formerly known as VERITAS Volume Manager (VM), FlashSnap Option. Microsoft Volume Shadow Copy Service (VSS). For Microsoft Volume Shadow Copy Service (VSS), you must be using the Windows Server 2003 platforms. Third party software vendors also provide additional components that work in conjunction with the Microsoft Volume Shadow Copy Service. These components, called Writers, are used to flush application data or file data (if a file is open) residing in the computers memory before the Microsoft Volume Shadow Copy Service makes a snapshot of the volume to be backed up. See your software documentation for information about VSS Writers that may be provided by the application software vendor.
Related Topics: Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Changing the Default Settings for the Symantec Volume Snapshot Provider on page 1008 Using Snap Start on a VERITAS Storage Foundation for Windows Volume on page 1005 Best Practices for Using the Symantec Volume Snapshot Provider on page 1006 Symantec Volume Snapshot Provider Cache File Location on page 1007
994
Requirements for Using the Advanced Open File Option

The following requirements must be met to use the Advanced Open File Option with snapshot technology. You must purchase the Advanced Open File Option for each remote Windows computer that you want to back up. The media server must have:

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

Windows 2000 or Windows Server 2003 Advanced Open File Option Backup Exec Remote Agent for Window Servers (AOFO automatically installs the Remote Agent)
The volumes you want to back up with the Advanced Open File Option must have:
Enough free disk space to start the AOFO operation. Free disk space should at least equal the size of the backup job in MBs being backed up. An NTFS, FAT32, or FAT file system. At least one NTFS partition is required to use Symantec Volume Snapshot Provider (VSP).
Note The Advanced Open File Option cannot be used on CD-ROM, floppy diskettes, removable media, or remote shares. Additionally, the Checkpoint Restart option is not supported by the AOFO. For more information about Checkpoint Restart, see Enabling or Disabling Checkpoint Restart on page 667. When backing up encrypted files with the Advanced Open File Option on Windows 2000 computers, a drive letter for the snapshot will display in Windows Explorer and on the Backup Exec Administration Console. Do not attempt to access or back up this drive letter. If no drive letters are available, encrypted files are backed up from the original volume, and the job is logged as Complete with Exceptions. To protect remote and local computers, the Backup Exec Remote Agent for Windows Servers must be installed. The Remote Agent is installed by default on the media server.
995
Installing the Advanced Open File Option
If you are installing the Advanced Open File Option locally to protect data on the media server, you can uninstall the Remote Agent license that was included with the Advanced Open File Option installation from the media server, and install it on one remote Windows server so that resource can be protected by Backup Exec. 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 cannot install it on another Windows server. For instructions on installing the Remote Agent to another Windows computer, see Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line on page 794. Related Topics: Understanding the Advanced Open File Option on page 991 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Changing the Default Settings for the Symantec Volume Snapshot Provider on page 1008 Using Snap Start on a VERITAS Storage Foundation for Windows Volume on page 1005 Best Practices for Using the Symantec Volume Snapshot Provider on page 1006 Symantec Volume Snapshot Provider Cache File Location on page 1007

The Advanced Open File Option (AOFO) is enabled from the media server by entering the AOFO serial number or numbers. You must reboot the computer on which you are installing AOFO after completing the installation. Before installing AOFO to a remote computer, enable the remote registry service on the remote computer. Make sure that the logon account used has permissions to modify remote servers registries. A 64-bit version of the Advanced Open File Option is also available, and can be installed with the 64-bit Remote Agent for Windows Servers. Caution Backup Exec for Windows Servers cannot use versions of the Advanced Open File Option that are previous to version 9.0. You must upgrade the Advanced Open File Option by purchasing and re-installing it on the local media server and on all remote computers on which it currently resides. To install the Advanced Open File Option on a local media server, see Installing Backup Exec Options to the Local Computer on page 71.
996
To install the Advanced Open File Option on a remote media server, see Installing Backup Exec Agents to Remote Computers on page 77. To install the 64-bit Advanced Open File Option using the 64-bit installation program, see Installing the Remote Agent on a 64-bit Computer Using the Installation Program on page 793. To install the 64-bit Advanced Open File Option using a command script, see Installing and Uninstalling the 64-bit Remote Agent and Advanced Open File Option Using a Command Script on page 795. You can also install and uninstall the Advanced Open File Option on remote servers using the Windows command line. See Installing and Uninstalling the Advanced Open File Option to Remote Windows Computers Using the Command Line on page 997. Related Topics: Upgrading Backup Exec Options on Remote Computers on page 105
Installing and Uninstalling the Advanced Open File Option to Remote Windows Computers Using the Command Line
You can install the Advanced Open File Option (AOFO) using silent mode on a remote computer using the Windows command line. Note Silent mode runs the installation operation without the benefit of a user interface. To use the Windows command line to install the AOFO on a remote computer: 1. Move to a remote server. 2. Map a drive letter to the Backup Exec for Windows Servers media server and change directories to the Advanced Open file Option install directory using the following path: \Program Files\VERITAS\Backup Exec\NT\Agents\RANT32 or copy the RANT32 directory locally. 3. Open a command prompt and enter the drive letter you mapped in step 2. 4. To install AOFO without advertising enabled, run the following command: setup.exe /AOFO: -s -boot To install AOFO with advertising enabled, run the following command:
997
setup.exe /AOFO: -s /ADVRT: <media server name 1> <media server name 2> 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 your computer. If you want to do this, add the parameter -boot; if not, you must reboot the computer manually at your convenience in order to activate the Advanced Open File Option. 5. The AOFO files are installed on the remote computer in the following directory: \Program Files\VERITAS\Backup Exec\RANT 6. The AOFO installation log file is created in \WINNT\bkupinst.log or on Windows Server 2003 platforms, in \WINDOWS\bkupinst.log. After the installation finishes, reboot the computer at your convenience in order to activate the Advanced Open File Option. To use the Windows command line to uninstall the AOFO from a remote computer: 1. At the remote computer, open a command prompt window. 2. Map a drive to the media server and change directories to the AOFO install directory using the following path: \Program Files\VERITAS\Backup Exec\NT\Agents\RANT32 or copy the RANT32 directory locally. 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 the 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 computer. After the uninstall finishes, reboot the computer at your convenience in order to de-activate the Advanced Open File Option.
998
Setting Defaults for the Advanced Open File Option for Backup Jobs
Uninstalling the Advanced Open File Option

If you uninstall Backup Exec, the Advanced Open File Option (AOFO) is uninstalled as well. You can also uninstall only the AOFO. To uninstall the Advanced Open File Option: 1. From the Start menu, point to Settings, and then click Control Panel. 2. Double-click Add/Remove Programs. 3. Select Symantec Backup Exec for Windows Servers, and then click Change/Remove. 4. Click Additional Options, and then click Next. 5. On the Symantec Backup Exec Serial Numbers dialog box, click Next. 6. In the Destination pane of the Symantec 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, and then click Install. 9. To confirm that the Advanced Open File Option has been uninstalled, from the Help menu in Backup Exec, select About Symantec Backup Exec for Windows Servers, and then click License Information.
You can set the Advanced Open File Option defaults for each backup job, or you can set defaults that are used for every backup job. Jobs saved before you installed the Advanced Open File Option will continue to use the previous settings for backing up open files. In order to use the Advanced Open File Option with these jobs, you must edit the job and on the Advanced Open File dialog box in the backup job properties, select Use Advanced Open File Option. After a job is completed, check the section Backup Set Detail Information in the job log to make sure that Advanced Open File was used during the backup.
999
To set the Advanced Open File defaults for backup jobs: 1. Do one of the following:
To set Advanced Open File backup options for a single backup job, on the navigation bar click Backup, and then on the Properties pane, under Settings, click Advanced Open File. To set Advanced Open File backup options for all backup jobs, on the menu bar click Tools, and then click Options. On the Properties pane, under Job Defaults, click Advanced Open File.
The Advanced Open File dialog box appears. 2. Select the appropriate options from the following:
Advanced Open File options Item Description
Use Advanced Open File Select this check box to enable Advanced Open File for backup Option jobs. If you are enabling this for a single job, or as a default for all backup jobs, then Advanced Open File backup will be performed if all requirements are met.
1000
Setting Defaults for the Advanced Open File Option for Backup Jobs Advanced Open File options Item Open file configuration Automatically select open file technology Enables Backup Exec to select the best snapshot method to use for the type of data being backed up. However, even if selected, a snapshot method may not be used if the resources do not meet the requirements for using snapshot methods. If the volume you select for backup does not meet the requirements for using the Advanced Open File Option, then the open file backup options (Never; If closed within 30 seconds; With a lock; Without a lock) will apply. For more information on the open file backup options, see Creating a Backup Job. When the option Automatically select open file technology is selected and Microsoft Volume Shadow Copy Service (VSS) provider is selected, then the first available hardware, software, or system provider is used to perform the snapshot for Microsoft Volume Shadow Copy Service (VSS). Note If you select this option for a Windows Server 2003 computer, Microsoft Volume Shadow Copy Service (VSS) is used when Shadow Copy Components and/or Microsoft SQL or Exchange databases are selected for backup, but Symantec Volume Snapshot Provider (VSP) is used in all other cases. If the Windows Server 2003 computer does not have VSP installed, Backup Exec uses VSS as the default. Symantec Volume Snapshot Provider Symantec Volume Snapshot Provider (VSP) is the default snapshot technology for Backup Exec. For details on configuring VSP, see Best Practices for Using the Symantec Volume Snapshot Provider on page 1006. Description
1001
Setting Defaults for the Advanced Open File Option for Backup Jobs Advanced Open File options Item VERITAS Storage Foundation for Windows FlashSnap Option Description VERITAS Storage Foundation for Windows (VSFW) was formerly known as Volume Manager (VM). Note The volumes you want to back up with the VSFW FlashSnap Option must first be snap-started using the VERITAS Enterprise Administrator (VEA), which must be purchased separately. For more information, see Using Snap Start on a VERITAS Storage Foundation for Windows Volume on page 1005. Note If the computer on which you are running a backup using the Advanced Open File Option is in an environment with the Central Admin Server Option and the Symantec Cluster Server installed, and if failover occurs to a Symantec Cluster Service node, you must manually clean up the snapshots before restarting the backup on the failover node. Refer to the VSFW documentation for details. Microsoft Volume Shadow Copy Service For use with vendor-specific, third party software, with Windows Server 2003. Microsoft Volume Shadow Copy Service (VSS) technology enables third party hardware and software vendors to create snapshot plugins for use with Microsofts technology. Microsoft, as well as other third party software vendors, often provide additional components that work in conjunction with VSS. These components, called Writers, are used to flush application data or file data (if a file is open) residing in the computers memory before the Microsoft Volume Shadow Copy Service makes a snapshot of the volume to be backed up. See your software documentation for information about VSS Writers that may be provided by the application software vendor. For more information, see Protecting Windows Server 2003 Systems on page 344.
1002
Setting Defaults for the Advanced Open File Option for Backup Jobs Advanced Open File options Item Snapshot provider Description Automatic - Allow VSS to select the snapshot provider Select this option to enable VSS to select the best provider for the selected volume. The order in which a snapshot provider is selected is hardware provider, software provider, and then the system provider. System - Use Microsoft Software Shadow Copy Provider Software - Use VERITAS Storage Foundation for Windows Hardware - Use technology provided by hardware manufacturer If you select Software or Hardware as the snapshot provider, then:
If multiple volumes are selected, then all volumes must be snappable by the same type of provider. Software and hardware providers cannot both be used to snap different volumes in the same job. You must either create another job, or select the option Process logical volumes for backup one at a time.
1003
Setting Defaults for the Advanced Open File Option for Backup Jobs Advanced Open File options Item Description
Process logical volumes Enables the backup of multiple volumes in one job, while creating a for backup one at a snapshot of only one logical volume at a time. To ensure database time integrity, or if a volume contains mount points, multiple volumes may need to be snapped at one time. A volume with mount points to other volumes is considered a logical volume for snapshot purposes. Therefore, that volume and the mount point volumes will be snapped together simultaneously. After the logical volume is snapped and backed up, the snapshot is deleted before the next logical volume is snapped. This option increases the ability to meet the minimum quiet time needed to complete a snapshot. A logical volume can comprise multiple physical volumes. A single logical volume can encompass all of the volumes on which databases reside. If this option is not selected, then a snapshot for all volumes in the backup job is created simultaneously. All volumes must meet the minimum quiet time. This option is only available for Symantec Volume Snapshot Provider (VSP) and Microsoft Volume Shadow Copy Service (VSS) jobs for logical volumes. Note On computers running Windows Server 2003, if the selection list for a backup job contains volumes as well as Shadow Copy Components (SCC), and the options Automatically select open file technology and Process logical volumes for backup one at a time are selected, the snapshots for volumes are created using VSP, and the Shadow Copy Components snapshots are created using VSS. This is reported in the job log and job history. Use ServerFree Option Enables Backup Exec to use third party copy support if your storage hardware supports it and you have a SAN environment. For more information, see Symantec Backup Exec - ServerFree Option on page 981.
3. If you are configuring the Advanced Open File Option for a specific backup job, you can start the backup job or select other backup options from the Properties pane. To monitor the operation while it is processing, click Job Monitor on the navigation bar, and then double-click the job to view the job activity. 4. If you are configuring the Advanced Open File Option as the default for all backup jobs, click OK.
1004
5. After the jobs have completed, check the job log to make sure the Advanced Open File Option is being used during the backup. Related Topics: Selecting Data to Back Up on page 284 Using Selection Lists on page 293 Creating a Manual Backup Job by Configuring Job Properties on page 262 Understanding the Advanced Open File Option on page 991 Best Practices for Using the Symantec Volume Snapshot Provider on page 1006 Changing the Default Settings for the Symantec Volume Snapshot Provider on page 1008 Checking the Job Log When Using the AOFO on page 1012
Using Snap Start on a VERITAS Storage Foundation for Windows Volume

To Snap Start a volume: 1. Start Symantec Enterprise Administrator. 2. In the left pane, expand the Localhost object. 3. Under the Localhost object, expand the Volumes object, and then right-click the volume to Snap Start. 4. On the short cut menu, select Snap, and then select Snap Start. 5. On the Snap Start Volume screen, select either Auto select disks or Manually select disks. Note Auto select disks enables VERITAS Storage Foundation for Windows (VSFW), to make the disk selection for you, while Manually select disks enables you to make the selection. 6. Click OK to begin the snap start of the volume. Note Snap Starting a volume only needs to be done once. The Snap Start procedure can take a considerable amount of time because it creates a mirror.
1005
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. Do not select a database or log at the volume level. Related Topics: Selecting Data to Back Up on page 284 Symantec Backup Exec - Agent for Microsoft SQL Server on page 1013 Symantec Backup Exec - Agent for Microsoft Exchange Server on page 1065
Best Practices for Using the Symantec Volume Snapshot Provider

Following are recommended best practices for using AOFO and the Symantec Volume Snapshot Provider (VSP):
Ideally, allow AOFO exclusive use of a disk. This disk should not have any user data, should never be backed up, and should have the AOFO cache file location directed to it. Make sure there is sufficient space on the disk to encompass all of the changed data. Changed data can include user files, system files, and the NTFS Master File Table (MFT). Exclude the cache file from real-time virus scanning software. Do not run regular scans or disk utilities such as scan disk or defragmenters during backups with AOFO. Avoid running any processes or programs that would write excessive data to the drive being protected. Avoid copying large amounts of data to the drive being protected.
Related Topics: Understanding the Advanced Open File Option on page 991 Requirements for Using the Advanced Open File Option on page 995 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Changing the Default Settings for the Symantec Volume Snapshot Provider on page 1008 Checking the Job Log When Using the AOFO on page 1012
1006
Symantec Volume Snapshot Provider Cache File Location

When the Symantec Volume Snapshot Provider (VSP) and the Advanced Open File Option (AOFO) are used, Backup Exec creates a cache file on the disk to save any changes that are made to the files on the volume while it is being snapped. Backup Exec automatically calculates the sizes of the cache files needed for the backup, as well as the location of the cache files. The cache file is created in a hidden folder named Backup Exec AOFO Store in the root of the selected volume. The cache file extension is .vsp. Backup Exec locates the Symantec Volume Snapshot Provider (VSP) cache files based on the following:
If you used the AOFO wizard to specify a location for the cache files, this location is used if it is not write-protected, and if it is not part of the resources that are being snapped. If multiple source volumes (the volumes to be snapped) are being snapped, then multiple cache files (one for each source volume) are located on the volume you specified (if that volume is not being snapped).
If you have not specified a location for the cache file, Backup Exec will attempt to locate the cache file on volumes other than the source volumes. These volumes must meet the following requirements. If any of these criteria are not met, the cache file is created on the source volume.

The volumes must be fixed drives. The volumes must use a recognized file system (FAT, FAT32, or NTFS). The volumes must be mounted locally. The volumes must be valid cache file locations. A valid cache file location:

Cannot be a location for a snapshot by another job that is currently running. Cannot contain another active cache file. Cannot be write-protected or disabled.
Related Topics: Understanding the Advanced Open File Option on page 991 Supported Snapshot Technologies on page 994 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Checking the Job Log When Using the AOFO on page 1012
1007
Changing the Default Settings for the Symantec Volume Snapshot Provider
To change the default settings for the configuration options for the Symantec Volume Snapshot Provider (VSP), use the Advanced Open File Option wizard on the Backup Exec Administration Console. Caution Use caution when you manually enter a specific size for the cache file since that size is used regardless of the size of the volume being backed up, and the job could fail if there is not enough space. It is recommended that in most situations, you allow Backup Exec to automatically calculate the size and location of the cache file for each backup. To change the Symantec VSP default settings using the AOFO wizard: 1. On the Tools menu, select Wizards, and then click Advanced Open File Option Wizard. Click Next to continue past the Welcome page. The Server Selection dialog box appears. 2. Select a server that the Advanced Open File Option has been installed on, and enter a user name and password. Make sure the domain is correct. You can type another domain name, or click the drop-down arrow to select another domain, and then click Next. The Cache File Settings dialog box appears. 3. Do one of the following:
To use the default cache file location, make sure Use default is selected, and then click Next. The default location for the cache file is on the volume that has the most free space, and that is not selected to be snapped in this Advanced Open File Option backup. However, if the volume that is being snapped is the only volume with enough available space, then the cache file is placed on it.
Note Symantec strongly recommends that you do not change the defaults.
To specify alternate locations for the cache files, clear the Use default check box. Type a drive and a path that are located on the computer that is being backed up, or click the browse button to browse to a local drive and path, click Insert, and then click Next.
1008
To change or delete existing cache file locations, select the location and then click Edit or Delete. After making changes, click Next. The Advanced Open File Option Configuration dialog box appears. 4. On the Advanced Open File Option Configuration screen, enter new defaults using the following table, and then click Next.
Settings for Symantec Volume Snapshot Provider (VSP) Item Have Backup Exec calculate the initial and maximum size of the cache file Description Enables Backup Exec to automatically calculate the initial and maximum size of the cache file for each backup. If the cache file is located on the volume that is being snapped, Backup Exec uses the following calculations: For the initial size, Backup Exec calculates 10 percent of the used space and 50 percent of the free space, and then uses the smaller number. For the maximum size, Backup Exec calculates 30 percent of the used space and 90 percent of the free space, and then uses the smaller number. If the cache file is located on a different volume than the volume that is being snapped, Backup Exec uses the following calculations: The initial size is zero. For the maximum size, Backup Exec calculates 30 percent of the free space on the target volume and uses that figure. The maximum size cannot be smaller than the initial size. If the maximum size is calculated to be smaller than the initial size, Backup Exec sets the maximum size to match the initial size. Both the initial size and the maximum size must be at least 50 MB. For information on where the cache file will be located, see Symantec Volume Snapshot Provider Cache File Location on page 1007.
1009
Changing the Default Settings for the Symantec Volume Snapshot Provider Settings for Symantec Volume Snapshot Provider (VSP) (continued) Item Initial size of the cache file (1 - 100 percent): Description Sets the initial size of the cache file. If you choose not to use the default, then type the percentage of free space that you want the Advanced Open File Option (AOFO) to use to create the cache file. Increase this percentage if you receive an error message stating that the AOFO is out of disk space. This increase enables additional free space to be allocated on the volume, which can then be used during the backup. Symantec recommends that you set the maximum size before setting the initial size. Maximum size that the cache file can grow to: Sets the maximum size of the cache file. If you do not use the default, then type the maximum percentage to allow for the cache file. If the snapshot exceeds the maximum percentage, the job will fail and the error will be listed in the job log. If the cache file is located on the volume that is being snapped, Backup Exec uses the number that you type in this field to calculate the percentage of used space on the volume. Backup Exec also calculates 90 percent of the free space on the volume and uses the smaller number. If the cache file is located on a different volume than the volume that is being snapped, Backup Exec uses the number that you type in this field to calculate the percentage of free space on the volume and uses that number. The maximum size cannot be smaller than the initial size. If the maximum size is calculated to be smaller than the initial size, Backup Exec sets the maximum size to match the initial size. The maximum size must be at least 50 MB. Number of seconds during which there can be no disk activity before the snapshot is created Sets the minimum length of quiet time in seconds, in which the application waits for disk inactivity before the snapshot is created. During this time, AOFO is waiting for there to be no drive activity to ensure that all buffers have been flushed, and therefore all the data on the drive should be consistent. The default quiet time is five seconds. In some cases it is necessary to lower this setting, but this increases the risk of the data on the drive becoming inconsistent. Decrease this setting if you have an active disk so that the snapshot can be created before reaching the maximum length of quiet time.
1010
Changing the Default Settings for the Symantec Volume Snapshot Provider Settings for Symantec Volume Snapshot Provider (VSP) (continued) Item Description The recommended minimum length is five seconds, but you can choose between two and four seconds. This setting should never be lowered below two. Instead, investigate what applications or services may be causing excessive disk writes. You may also want to select the option Process logical volumes for backup one at a time. This option enables the backup of multiple volumes in one job, while creating a snapshot of only one logical volume at a time and increases the ability to meet the minimum quiet time needed to complete a snapshot. See Process logical volumes for backup one at a time on page 1004 Number of seconds that the application tries to obtain the minimum quiet time, after which the job fails Sets the maximum length of time that AOFO waits for disk inactivity before terminating the creation of the snapshot. Increase this setting if a backup fails repeatedly with the message that it could not obtain the minimum quiet time. Increasing this setting maximizes the length of time used to create the snapshot. The default is 2,000 seconds.
A summary of changes made is displayed. 5. Review the summary screen. If the configuration is satisfactory, click Finish. To make more changes, click Back. After you click Finish, the Advanced Open File Option settings for the Symantec Volume Snapshot Provider are saved, and you are prompted to set up another server. Related Topics: Understanding the Advanced Open File Option on page 991 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Best Practices for Using the Symantec Volume Snapshot Provider on page 1006 Symantec Volume Snapshot Provider Cache File Location on page 1007
1011
Checking the Job Log When Using the AOFO
Checking the Job Log When Using the AOFO

When a backup completes successfully while using the Advanced Open File Option (AOFO), information is displayed in the job log. Check the section Backup Set Detail Information in the job log to make sure that AOFO was used during the backup. If the backup included more than one volume, this information is repeated for each volume. If the AOFO fails on initialization, the backup still runs but the job is logged as Completed with Exceptions in the job log. If the AOFO fails during the backup of a device, that backup set is terminated and is reported as an error. Note Failed AOFO jobs using the Symantec Snapshot Provider (VSP) may leave an active image on the computer, causing subsequent jobs to fail with an unknown error. If this occurs, reboot the computer to clear the active image. Related Topics: Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 Best Practices for Using the Symantec Volume Snapshot Provider on page 1006 Symantec Volume Snapshot Provider Cache File Location on page 1007
1012
Appendix
Symantec Backup Exec Agent for Microsoft SQL Server

The Symantec 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. The SQL Agent provides support for:
Database, transaction log, differential, and filegroup backups, as well as database recovery and replacement. An automated restore of the master database. The Intelligent Disaster Recovery option, which automates the disaster recovery process of SQL 2000 or SQL 7.0, depending upon which SQL version is installed. Backups of multiple instances. For use with the Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) and the Advanced Open File Option (AOFO). ADBO and AOFO are separate, add-on components of Backup Exec. The use of ADBO and AOFO can reduce both restore time and backup impact on the server. Standby database. If the primary SQL server fails, or is shut down for maintenance, another database called a standby database can be brought online. The standby database contains a copy of the primary server's databases so that users can 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.
1013
In SQL 2000 installations, the SQL Agent provides support for:

Requirements for Using the SQL Agent
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.
Database Consistency Checks (DBCC) for each backup and restore job, including a fast database consistency check of only the physical consistency of the database. Full, bulk-logged, and simple recovery models. The simple recovery model is similar to setting the truncate log on checkpoint option in SQL 7.0. With the simple recovery model, copies of the transactions are not stored in the log file, which prevents transaction log backups from being run. Therefore, you can recover the database to the point of the last backup, but you cannot restore the database to the point of failure or to a specific point in time. Restores of transaction logs to a specific point in time or to a named transaction when log marks are used. Database Consistency Checks (DBCC) before and after each backup job. Restores of transaction logs to a specific point in time.
In SQL 7.0 installations, the SQL Agent provides support for:

Related Topics: Installing the SQL Agent on page 1015
Requirements for Using the SQL Agent

The following are required for the SQL Agent:
Backup Exec must have access rights to read both of the following SQL registry keys:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer
If Backup Exec does not have access to these registry keys, a restore to the default directory may not work, and the Automate master database restore option on the Restore Job Properties for SQL dialog box will not work. To ensure that Backup Exec has access rights, verify that the logon account used has administrator rights to the Windows server that the SQL instance is installed on.

The media server must have access to the SQL installation. The credentials stored in the Backup Exec logon account used for backing up and restoring SQL must have been granted the System Administrator role on the SQL instance.
1014
Installing the SQL Agent
Installing the SQL Agent

The Symantec Backup Exec Agent for Microsoft SQL Server is installed locally as a separate, add-on component of Backup Exec for Windows Servers, and can protect local or remote 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. The 64-bit Remote Agent can protect 64-bit SQL databases. Note The 64-bit Remote Agent does not protect SQL 7.0 databases. For instructions on installing the SQL Agent on the local media server, see Installing Backup Exec Options to the Local Computer on page 71. For instructions on installing the 32-bit Remote Agent on a remote resource, see Installing Backup Exec Agents to Remote Computers on page 77. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line on page 794. For instructions on installing the 64-bit Remote Agent to protect remote 64-bit SQL databases, see Installing the Remote Agent on a 64-bit Computer Using the Installation Program on page 793
Using Backup Exec Logon Accounts for SQL Resources

To back up SQL, use a Backup Exec logon account that stores the credentials of a Windows user account. The Windows user account must have been granted the System Administrator role on the SQL instance.
Appendix I, Symantec Backup Exec - Agent for Microsoft SQL Server
1015
Using Backup Exec Logon Accounts for SQL Resources
In the backup selections list or in the resource credentials list, apply that logon account to the Windows server that SQL is installed on, not to the actual SQL instance.
How logon account is applied
The Backup Exec logon account containing the Windows credentials is applied to the Windows server that SQL is installed on.
If you are using SQL Server Authentication, then add a Backup Exec logon account that stores the credentials of the SQL user account. In the backup selections list, apply the Backup Exec logon account for the Windows user account to the Windows server that SQL is installed on, and then apply the logon account for the SQL user account to the SQL instance.
1016
Backup Strategies for SQL Applying SQL user account credentials
The Backup Exec logon account containing the SQL user account credentials is applied to the SQL instance.
If you use a Backup Exec logon account that does not have the proper rights, you will receive an error message stating that the username and password are invalid. Related Topics: Changing and Testing Logon Accounts for Resources on page 292 Configuring Logon Accounts on page 386
Backup Strategies for SQL

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.
1017
Backup Strategies for SQL
In large environments, consider running daily differential database backups, weekly full database backups, and transaction log backups as necessary. Many shops run full backups on a weekly basis, preferring to run differential backups throughout the week to keep backup run time to a minimum. Extremely large environments may need to run filegroup backups in order to split the full backup over several days. Log backups are required to be able to recover a system from a filegroup backup.
The trade-off with running fewer full backups and running more differential backups occurs at recovery time when you must recover using the full database backup as well as the last differential database backup, and all log backups made after the last differential database backup. What will work best for you will be based on the size of your environment, the number of transactions processed each day, and the expectations of your users when a recovery is required. You should also separate SQL backup jobs from other backup jobs. When developing a SQL backup strategy, consider the following:
Recommendations for backing up SQL 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.
When you upgrade, run new full database backups.
If you upgrade SQL, run new full database backups. You may not be able to restore backups from one version or service pack level of SQL to other versions.
1018
Backup Strategies for SQL Recommendations for backing up SQL (continued) SQL Server backup strategies: Run consistency checks after backups. Description:
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.
Note The option to run a physical check only is only available if running SQL 2000.
A physical check only. Another low-overhead check, this method checks only the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
Back up the master Back up the master database whenever procedures are run that database whenever data change information in the database, especially after: is changed in the master New databases are created. 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.
1019
Backup Strategies for SQL Recommendations for backing up SQL (continued) SQL Server backup strategies: For SQL 2000 only: 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. If these databases become corrupted or are missing, and SQL cannot be started, you can replace them with the copies of the master and model databases, and then start SQL. After SQL is running again, you can restore the latest copy of the master database using Backup Execs Automate master database restore option, and then restore any other databases, if needed. If you purchased the Intelligent Disaster Recovery (IDR) option, then during an IDR recovery of the C: drive, it will automatically replace the damaged databases with the copies of the master and model databases that you made. If you have filegroups, back them up instead of databases. Do not back up filegroups and databases. For SQL 7.0 only: Create a copy of the master and model databases, and place the copies in the same directory that the databases are in. Make copies of the master and model databases and place the copies in the same directory that the master and model databases are in. Then, if the master database becomes critically damaged and SQL cannot be started, instead of running the Rebuild Master utility or reinstalling SQL, you can replace the corrupted or missing databases with the copies of the master and model databases, and then start SQL. After SQL is running again, you can restore the latest copy of the master database using Backup Execs Automate master database restore option, and then restore any other databases, if needed. If you purchased the Intelligent Disaster Recovery (IDR) option, then during an IDR recovery of the drive C, it will automatically replace the damaged databases with the copies of the master and model databases that you made. For details, see To create copies of the SQL 7.0 master and model databases: on page 1058. 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. Description:
1020
Consistency Checks for SQL Recommendations for backing up SQL (continued) SQL Server backup strategies: If you have filegroups, run at least one full database backup first, then back up the filegroups instead of databases. Do not back up filegroups and databases. Description:
When databases grow too large to be backed up all at once, filegroups can provide an alternative backup method. Different filegroups can be backed up at different times and frequencies. However, SQL 7.0 databases cannot be restored using only filegroup and log backups. SQL 7.0 databases must have at least one full database backup in order to be restored. If the database has been deleted or does not exist, restore the full database backup, and then restore all the filegroup and log backups.
Consistency Checks for SQL

If you back up a database, transaction log, or filegroup that contains errors, these errors will still exist when the backup is restored. In some cases, this can prevent a successful restore. Backup Exec enables you to check the logical and physical consistency of the data before and after a backup. SQL reports any consistency check failures in the Backup Exec job log. Symantec strongly recommends that you always run a consistency check either before or after the backup. Backup Execs consistency check uses the following SQL consistency check utilities:

CHECKDB CHECKCATALOG CHECKFILEGROUP PHYSICAL_ONLY
CHECKDB, CHECKCATALOG, and PHYSICAL_ONLY are performed for database-related operations. Note PHYSICAL_ONLY is not available for SQL 7.0. CHECKFILEGROUP is performed for filegroup-related operations. For more information concerning these utilities, see your Microsoft SQL documentation. Related Topics: Setting Backup Options for SQL on page 1024
1021
Using Snapshot Technology With the SQL Agent

The SQL Agent supports snapshot technology for SQL 2000 through the use of the Symantec Backup Exec for Windows Servers - Advanced Open File Option (AOFO) and the Advanced Disk-based Backup Option (ADBO). ADBO can only be installed on Windows 2003. The use of ADBO and AOFO can reduce both restore time and backup impact on the server. With snapshot technology, a point in time view of the SQL database is "snapped" and then backed up, leaving the actual SQL database open and available for users. Symantec recommends that SQL backup jobs be run separately from AOFO or ADBO backup jobs because SQL backups made with snapshot technology are considerably bigger than regular SQL backups. Performing consistency checks before backup is highly recommended (see Consistency Checks for SQL on page 1021). The SQL Agent only supports full snapshot backups; filegroup snapshots, log snapshots, and differential snapshots are not supported. If a filegroup, differential, or transaction log backup method is selected, AOFO or ADBO Backup Job Properties are ignored and a traditional differential or transaction log backup will be performed. With the SQL Agent, snapshot and traditional backups are interoperable when restoring SQL data. For the Intelligent Disaster Recovery Option to work with SQL backups, copies are made of the master and model databases. Copies are only made when non-snapshot backups of master and model are run. If you are using AOFO or ADBO for SQL backups, make at least one backup of the master and model databases without using AOFO or ADBO. If SQL is upgraded, refresh the copies with another non-snapshot backup. SQL backups made using AOFO or ADBO will fail if multiple databases are selected for backup and SQL Service Pack 2 is not installed. If SQL Service Pack 2 is installed, you can select multiple databases at the same time for backup. Snapshot backups of the master database cannot be redirected. While performing database consistency checks both before and after backups impacts the time required for the backup jobs
1022
Using AOFO With the SQL Agent

When using the SQL Agent together with AOFO, depending on which operating system you are running, you can select to use the VERITAS Storage Foundation for Windows FlashSnap Option, the Microsoft Volume Shadow Copy Service, and the ServerFree Option. What happens when the Automatically select open file technology option is selected, also depends on the operating system being used.
Protecting SQL on Windows 2003

The SQL Agent supports Microsofts Volume Shadow Copy Service (VSS), a snapshot provider service only available on Windows 2003 or later, and the VERITAS Storage Foundation for Windows FlashSnap Option. In order for the SQL Agent to use VSS, the SQL Agent must be installed and running on the SQL server. VSS can use different providers, including Default, System, Hardware, and Software. In order for the SQL Agent to use the FlashSnap Option, the SQL Agent, VERITAS Storage Foundation for Windows, and the Advanced Open File Option (AOFO) must be installed and running on the SQL server. Related Topics: Understanding the Advanced Open File Option on page 991
Protecting SQL on Windows 2000

When protecting Windows 2000, the SQL Agent only supports the VERITAS Storage Foundation for Window FlashSnap Option and the ServerFree Option. In order to protect the SQL server using the FlashSnap Option, the SQL Agent, VERITAS Storage Foundation for Windows, and the Advanced Open File Option (AOFO) must be installed and running on the SQL server. If you are using the ServerFree Option, you must install Symantec ServerFree Option. You can select the FlashSnap or ServerFree options through the Advanced Open File options dialog box. If Automatically select open file technology is selected on the Advanced Open File options dialog box when running Windows 2000, Backup Exec attempts to use the FlashSnap Option to perform the backup. If the FlashSnap option is not available, the job will fail. If you select the Symantec Volume Snapshot Provider or Microsoft Volume Shadow Copy Service options, a non-snapshot backup is performed. Also, when using AOFO with FlashSnap and ServerFree note the following:
The SQL user data and log files must exist on the mirrored volume (plex) in order for the snapshot to occur.
1023
Setting Backup Options for SQL
To protect system databases, the system database files must reside on the mirrored volume (plex).
Related Topics: Understanding the Advanced Open File Option on page 991 Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999
Using the ADBO With the SQL Agent

In order to protect the SQL server using ADBO, both the SQL Agent and ADBO must be installed. ADBO, which can only be installed on Windows 2003, can use different snapshot providers, including hardware and software. You can select the provider to be used through the Advanced Disk-based Backup options when creating the backup job. In order to use the Software - Use VERITAS Storage Foundation for Windows option, VERITAS Storage Foundation for Windows (VSFW) must be installed. If Automatic - Use hardware if available; otherwise use software is selected, the first available the first available hardware provider is used. If a hardware provider is not available, then the first software provider is used. If neither a hardware nor a software provider are available, the job status will depend the job disposition option set on the Advanced Disk-based Backup dialog box. Also, when using ADBO note the following:
The SQL user data and log files must exist on the mirrored volume (plex) in order for the snapshot to occur. To protect system databases, the system database files must reside on the mirrored volume (plex).

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 261. To select backup job properties for SQL: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click Microsoft SQL.
1024

Backup job properties for SQL Item Backup method: Description
Full - Back up entire database or filegroup. Select this option to back up the entire database or filegroup. See Backing Up SQL Databases on page 1029. This option is selected by default. Log - Back up transaction log. Select this option to back up only the data contained in the transaction log; it does not back up database data. After the transaction log is backed up, committed transactions are removed (truncated). Select this option to be able to select No recover or Standby under Enable SQL 2000 advanced log backup options. See Backing Up SQL Transaction Logs on page 1033.
Log No Truncate - Back up transaction log - no truncate. Select this method only when the database is corrupted or database files are missing. Since the Log No Truncate method does not access the database, you can still back up transactions that you may not be able to access otherwise when the database is in this state. You can then use this transaction log backup along with the database backup and any previous transaction log backups to restore the database to the point at which it failed; however, any uncommitted transactions are rolled back. The Log No Truncate method does not remove committed transactions after the log is backed up. See Backing Up SQL Transaction Logs on page 1033. Differential - Back up database or filegroup changes only. Select this option to back up only the changes made to the database or filegroup since the last full backup. Because differential backups allow the restore of a system only to the point in time that the differential backup was created, you should also create multiple log backups between the differential backups.
1025
Setting Backup Options for SQL Backup job properties for SQL (continued) Item Consistency check before backup Description Select a consistency check to run before a backup.
None. Select this option if you do not want a consistency check to run before a backup. Symantec strongly recommends that you always run a consistency check either before or after the backup. This option is selected by default. Full check, excluding indexes. Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked. Full check, including indexes. Select this option to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000 only). Select this option to perform a low overhead check of the physical consistency of the SQL 2000 database. This option only checks the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
Continue with backup if consistency check fails
Select this option to continue with the backup operation even if the consistency check fails. You may want to continue with the backup when the consistency check fails if you think that a backup of the database in its current state is better than no backup at all, or if you are backing up a very large database with only a small problem in a table.
1026
Setting Backup Options for SQL Backup job properties for SQL (continued) 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 option if you do not want a consistency check to run after a backup. Symantec strongly recommends that you always run a consistency check either before or after the backup. This option is selected by default. Full check, excluding indexes. Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked. Full check, including indexes. Select this option to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000). Select this option to perform a low overhead check of the physical consistency of the SQL 2000 database. This option only checks the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
Enable SQL 2000 advanced log backup options
This option is available only if running SQL 2000 and 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.
No recover - Place Select this option to put the database in a loading state when the database in loading state log file backup completes. Users cannot connect to or query the database while it is in a loading state. Note This option is only available if running SQL 2000 and if Enable SQL 2000 advanced log backup options has been selected.
1027
Setting Backup Options for SQL Backup job properties for SQL (continued) Item Description
Standby - Place database Select this option to put the database in standby mode when the in standby state log file backup completes. Users can connect to and query the database when it is in standby mode, but cannot update it. 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. Note This option is only available if running SQL 2000 and if Enable SQL 2000 advanced log backup options has been selected. Guide Me Click this to start a wizard that helps you select backup job properties for SQL.
Related Topics: Selecting Data to Back Up on page 284 Using Selection Lists on page 293 Consistency Checks for SQL on page 1021

If you select a volume that contains SQL data for backup, the SQL Agent determines which SQL data should not be included in a volume level backup. For example, .MDF and .LDF files should not be part of the backup because they are opened for exclusive use by the SQL system. These files will be automatically excluded for backup by a feature called Active File Exclusion. If this exclusion did not happen during a non-snapshot backup, these files would appear as in use - skipped. If this exclusion did not happen during a snapshot backup, the files would be backed up in a possible inconsistent state, which could create restore issues. While it is not recommended, if you want to include SQL data in a volume level backup, you must first dismount the database you want backed up. Then, run the backup job.
1028
Backing Up SQL 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, and are using SQL 2000, use the simple recovery model for the database so that the transaction log is automatically truncated when a checkpoint occurs in the database. This helps prevent transaction logs from becoming full since with other recovery models the logs are not cleared after a database backup. With the simple recovery model, copies of the transactions are not stored in the log file, which prevents transaction log backups from being run. If you want to run database backups only, and are using SQL 7.0, use SQL Enterprise Manager to enable the database option truncate log on checkpoint for each database you are backing up. Enabling this option causes the transaction log to be automatically truncated whenever a checkpoint occurs in the database. If you do not run transaction log backups, you can recover the database to the point of the last backup, but you cannot restore the database to the point of failure or to a specific point in time. The master database can only be backed up with the full method; you cannot use the log or differential methods to back up the master database. To back up SQL databases: 1. 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.
1029
For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL Resources on page 1015. 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. 4. To select the SQL backup job properties, on the Properties pane, under Settings, click Microsoft SQL. 5. Select options for the backup job. For details on these options, see Setting Backup Options for SQL on page 1024. 6. Start the backup job or select other backup options from the Properties pane, and then start the backup job. Related Topics: Backing Up Data on page 259 Backing Up SQL Transaction Logs on page 1033 Setting Backup Options for SQL on page 1024
1030
Backing Up SQL Filegroups

When databases grow too large to be backed up all at once, filegroups can provide an alternative backup method. Filegroups can be backed up at different times and frequencies. Filegroups that change often can be backed up more frequently than filegroups that remain more static. In certain situations, filegroup backups can greatly reduce restore time. For example, if a nonprimary filegroup is destroyed or corrupted, only that filegroup has to be restored. Backup Exec includes two methods for backing up filegroups: full and differential. The full method backs up the entire filegroup. The differential method backs up only the changes made to the filegroup since the last full backup. A differential backup is smaller and faster than a full backup, so differential backups can be run more often than full backups. Consider using differential backups when only a relatively small amount of data changes between full filegroup backups, or if the same data changes often. Because differential backups allow the restore of a system only to the point that the differential backup was created, you should also create multiple log backups between the differential backups. Using transaction log backups enables you to recover the filegroup to the exact point of failure. A combination of full and differential filegroup backups and transaction log backups provides complete database protection. Log backups are required to be able to recover a system from a filegroup backup. Caution SQL 7.0 databases cannot be restored using only filegroups and log backups. SQL 7.0 databases must have at least one full database backup in order to be restored. If the database has been deleted or does not exist, restore the full database backup, and then restore all the filegroup and log backups. 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 Microsoft SQL. 3. Select Display filegroups when creating new backup jobs. To back up SQL 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.
1031
For information on using logon accounts when making backup selections, see Using Backup Exec Logon Accounts for SQL Resources on page 1015. 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.
Selections options
4. To select SQL backup job properties, on the Properties pane, under Settings, click Microsoft SQL. 5. After selecting job options, start the backup job or select other backup options from the Properties pane, and then start the backup job.
Related Topics: Backing Up Data on page 259 Setting Backup Options for SQL on page 1024.
1032
Backing Up SQL 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 If using SQL 2000, 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. If using SQL 7.0, do not run a log backup using either method if the SQL database option truncate log on checkpoint is enabled. When this option is enabled, every time a checkpoint occurs in the database, the transaction log is truncated without the truncated part of the transaction log being backed up, which prevents more transaction log backups from being created. You should run a database or differential backup instead. To check the database properties, from the Enterprise Manager on the SQL Server, right-click the database, click Properties, click the Options tab, and then view the configuration settings.
1033
If using SQL 7.0, do not run a log backup using either method f the SQL database select into/bulkcopy option is enabled, and nonlogged operations have occurred in the database since the last database backup was created. Nonlogged operations break the sequence of transaction log backups. The restore of a database using database and transaction log backups is successful only if there is an unbroken sequence of transaction log backups after the last database or differential backup. If these conditions are present, you should run a database or differential backup and then start running log backups again in order to save any changes necessary to restore the database. To back up SQL transaction logs: 1. On the navigation bar, click 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 Resources on page 1015. 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 Microsoft SQL. 5. After selecting job options, start the backup job or select other backup options from the Properties pane, and then start the backup job.
Related Topics: Setting Backup Options for SQL on page 1024 About Restoring SQL Databases and Filegroups on page 1040 Restoring from SQL Transaction Logs Up to a Point in Time on page 1042 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1043
1034
Restore Options for SQL
Restore Options for SQL

This procedure details how to select restore job properties for SQL, and provides definitions for SQL-specific restore options. For details on how to create a restore job, and for definitions of all other restore options see Restoring Data on page 451. To select restore job properties for SQL: 1. On the navigation bar, click Restore. 2. On the Properties pane, under Settings, click Microsoft SQL. 3. Select the appropriate options as follows:
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. Leave database nonoperational but able to restore additional transaction logs (No Recovery) Leave database read-only and able to restore additional transaction logs (Standby) Select this option during transaction log and database restore to create and maintain a standby database. See your SQL documentation for information on standby databases. Select this option during a restore if you have additional differential or transaction log backups to be restored in another restore job.
1035
Restore Options for SQL Restore job properties for SQL (continued) Item Take existing target database offline (SQL 2000) Description Select this option if you want Backup Exec to automatically take the SQL 2000 database offline before the restore job runs. If this option is not selected and there are active connections to the SQL database, the restore job will fail. 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 this option is not selected. 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 Automate master database restore option on the restore job properties for SQL will not work. To ensure that Backup Exec has access rights, verify that the logon account used has administrator rights to the Windows server that the SQL instance is installed on.
Replace databases or filegroups
Automate master database restore
1036
Restore Options for SQL Restore job properties for SQL (continued) Item Consistency check after restore Description
None. Select this option if you are doing sequential restores. Do not run a consistency check after a restore until all sequential restores have been done. If a consistency check is selected during a restore, the restore will complete but the consistency check will not be done. Check the job log for this information. If you need to recover the database after restores are complete, select one of the following consistency checks when you select the Leave database operational option.
Full check, excluding indexes. Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked. Full check, including indexes. Select this option to include indexes in the consistency check. Any errors are logged. This option is selected by default. Physical check only (SQL 2000 only). Select this option to perform a low overhead check of the physical consistency of the SQL 2000 database. This option only checks the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
1037
Restore Options for SQL Restore job properties for SQL (continued) Item Description
Default drive for Use this option to select a default drive to which SQL database restoring database files: 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 files to the target instances data location Select this checkbox to restore files to the default data and log directories of the destination instance. For example, if you are restoring a database to a different instance of SQL, you would select this option to move the database files to the correct location for the new instance. If this option is not selected, then the files are restored to the directory that the master database is in. 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.
1038
Restore Options for SQL 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 named Select this checkbox to restore transactions from a transaction transaction (SQL 2000) log up to a named transaction (or named mark) in the transaction log; after that, recovery from the transaction log is stopped. The named transactions are case-sensitive. Check your client application event log to find dates and times of named transactions. 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.
Note This option is only available if you are running SQL 2000 and the Restore log up to named transaction option has been selected.
Found after Select this check box to specify a date and time after which the restore operation is to search for the named transaction. For example, if you specify a restore from a log up to the named transaction AfternoonBreak, found after 6/02/2000, 12:01 p.m., then the restore operation will not search for AfternoonBreak until after that time.
Note This option is only available if you are running SQL 2000 and the Restore log up to named transaction option has been selected.
Guide Me Click this to start a wizard that helps you select restore job properties for SQL.
Related Topics: About Restoring SQL Databases and Filegroups on page 1040.
Appendix I, Symantec Backup Exec - Agent for Microsoft SQL Server 1039
About Restoring SQL Databases and Filegroups
Restoring from SQL Transaction Logs Up to a Point in Time on page 1042 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1043 Restoring from SQL Filegroup Backups on page 1044

You can restore a database using one job or using multiple jobs to restore all of the backup sets, depending on the types of backup used to protect the database or filegroup. To restore a database using one job, select all the backup sets that you want to apply, including the full backup, any differential backups, and any log backups, and select the Leave database operational option. 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 primary filegroup, to restore the rest of the filegroup backup sets, and to restore the transaction logs.
Caution SQL 7.0 databases cannot be restored using only filegroups and log backups. SQL 7.0 databases must have at least one full database backup in order to be restored. If the database has been deleted or does not exist, restore the full database backup, and then restore all the filegroup and log backups.
Restoring a nonprimary filegroup. After running a Log No Truncate backup, separate restore jobs must be used to restore the missing filegroup from full and differential backups of the filegroups, and to restore the transaction logs.
If you use multiple jobs to restore a database, make sure that you specify the recovery completion state Leave 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.
1040
With very large databases this process can take several hours to complete. During this time Backup Exec reports that no data is being transferred, and the Byte count field in the Job Monitor view is not updated. When SQL has completed filling the files with zeros, the restore job continues. This occurs for all database restores but is noticeable only on very large databases. For steps on how to create the restore job, and for descriptions of all the options for restoring SQL data, see Redirecting Restores for SQL on page 1049. Note SQL 7.0 database backups can be restored to SQL 2000, but SQL 2000 backups cannot be restored to SQL 7.0. Related Topics: Restoring Data on page 451 Restoring from SQL Transaction Logs Up to a Point in Time on page 1042 Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1043 Restoring from SQL Filegroup Backups on page 1044 Redirecting Restores for SQL on page 1049
Restoring from SQL Database Backups

If the database is using the simple recovery model, there are no transaction log backups to restore. You only need to restore the most recent full database backup and if you were running differential database backups, restore the most recent differential database backup. For details on all other restore options, see Restoring Data on page 451. 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 Microsoft 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 on page 1035.
6. Start the restore job or select other restore options from the Properties pane. Related Topics: About Restoring SQL Databases and Filegroups on page 1040
Restoring from SQL Transaction Logs Up to a Point in Time

You can restore transactions from a transaction log up to and including a point in time in the transaction log. After the point in time is reached, recovery from the transaction log is stopped. To find dates and times of transactions, check your client application event log. If the specified point in time is later than the time contained in the most recent transaction log being restored, then the restore operation succeeds, but a warning is generated and the database remains in an intermediate state. If the specified point in time is before the time contained in the transaction log or logs being restored, no transactions are restored. To restore 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 Microsoft 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 on page 1035. 7. Start the restore job or select other restore options from the Properties pane.
Related Topics: Restoring Data on page 451 About Restoring SQL Databases and Filegroups on page 1040
1042
Restoring from SQL 2000 Transaction Logs Up to a Named Transaction

If you are running SQL 2000, 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 upperand lower-case characters when specifying a named transaction. 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 Microsoft 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. 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 on page 1049. 9. Start the restore job or select other restore options from the Properties pane. Related Topics: Restoring Data on page 451 About Restoring SQL Databases and Filegroups on page 1040
Restoring from SQL Filegroup Backups

With filegroup backups, you can restore the entire database, a primary filegroup, a filegroup containing a deleted or changed table, and a nonprimary filegroup. Caution SQL 7.0 databases cannot be restored using only filegroups and log backups. SQL 7.0 databases must have at least one full database backup in order to be restored. If the database has been deleted or does not exist, restore the full database backup, and then restore all the filegroup and log backups. The following are conditions for filegroup restores:
All filegroups must be restored to the same point in time. For example, if a table is deleted from a filegroup, you cannot restore that filegroup to a point in time before the table was deleted and then leave it at that time; you must continue restoring the filegroup to the same point in time shared by all existing filegroups. To be able to restore a filegroup to the same point in time as the other filegroups, run one of the following log backups:

If the database is intact, run a Log backup. 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.
1044
The options Restore all databases to default drive and Restore all database files to the target instances data location on the Restore Job Properties for SQL dialog box do not apply to filegroup restores. Filegroups must be restored to the same drive letter and path that they were backed up from.

When restoring from filegroup backups, separate restore jobs are required. Previous versions of Backup Exec cannot restore filegroup backups made with this release of Backup Exec. If using SQL 2000 and restoring from filegroup backups, separate restore jobs are required.
To restore the entire database (SQL 2000 only), a missing 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. 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 Microsoft 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 on page 1049. 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.
1045
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 451. To restore a missing or corrupted nonprimary 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 Microsoft 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, and then start the restore job. Related Topics: Restoring Data on page 451
1046
Restoring the SQL Master Database

If the master database is damaged, symptoms may include:

An inability to start SQL. Segmentation faults or input/output errors. A report generated by SQL Database Consistency Checker utility (DBCC).
If you can still start SQL, you can restore the latest copy of the master database backup using the Automate master database restore option in Backup Execs Restore Job Properties for SQL dialog box and then restore any other databases, if needed. If the master database is critically damaged and SQL cannot be started, rather than running the Rebuild Master utility, or reinstalling SQL to be able to restart SQL, you can replace the corrupted or missing databases with the copies of the master and model databases that Backup Exec automatically creates and updates whenever backups of those databases are run. After SQL is running again, you can restore the latest copy of the master database using Backup Execs Automate master database restore option, and then restore any other databases, if needed. If copies of the master and model databases were not made, then you must use Microsofts rebuildm.exe utility to rebuild the master database and start SQL. Because all changes made to the master database after the last backup was created are lost when the backup is restored, the changes must be reapplied. If any user databases were created after the master database was backed up, those databases cannot be accessed until the databases are restored from backups or reattached to SQL. To restart SQL using database copies: 1. Verify that the database copies are present. The database copies are named master$4idr, mastlog$4idr, model$4idr, and modellog$4idr. 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\*.* 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.
1047
2. Open a command prompt window, and delete the original master and model databases and their transaction logs. For example: C:\Program Files\Microsoft SQL Server\MSSQL\Data> del master.mdf mastlog.ldf model.mdf modellog.ldf or: C:\ mssql7\data> del master.mdf mastlog.ldf model.mdf modellog.ldf 3. Rename the copies of the databases back to their original names, and make sure they are not read-only files or the SQL services will not start. For SQL 2000, 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 For SQL 7.0, 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. If you are using SQL 2000, use the SQL Service Control Manager to start SQL Server. If you are using SQL 7.0, use the SQL Server Service Manager to start SQL. 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 Microsoft 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 be run after the restore. 7. Start the restore job. After the restore, SQL is restarted in multi-user mode. Related Topics: Restoring Data on page 451
Redirecting Restores for SQL

You can redirect the following:

A database backup to a different server, database, or instance. Differential and log backups to wherever the associated database is restored. 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.
1049
To redirect a restore: 1. Follow the instructions for the appropriate restore:

Restoring from SQL Database Backups on page 1041. Restoring from SQL Transaction Logs Up to a Point in Time on page 1042. Restoring from SQL 2000 Transaction Logs Up to a Named Transaction on page 1043. Restoring from SQL Filegroup Backups on page 1044.
2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Microsoft SQL Redirection. 3. Select the appropriate options as follows, and then start the redirected restore job or select other restore options from the Properties pane:
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 on page 1035).
To restore to a server, use a Backup Exec logon account that stores the credentials of a Windows user account. The Windows user account must have been granted the System Administrator role on the SQL instance. The default logon account is displayed. To use another logon account, click Change. For more information about logon accounts, see Using Backup Exec Logon Accounts for SQL Resources on page 1015.
1050
About Restoring SQL Databases and Filegroups Restore job properties for redirected SQL sets (continued) Item SQL logon account Description If you are using SQL Server Authentication, use a Backup Exec logon account that stores the credentials of the SQL user account. Apply the Backup Exec logon account for the Windows user account to the Windows server that SQL is installed on, and then apply the logon account for the SQL user account to the SQL instance. To use another logon account, click Change. To remove the SQL logon account displayed in this field, click Clear. For more information about logon accounts, see Using Backup Exec Logon Accounts for SQL Resources on page 1015. 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 on page 1049). 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.
Restore to database
Related Topics: Restoring Data on page 451 About Restoring SQL Databases and Filegroups on page 1040
1051
Setting Default Backup and Restore Options for SQL
Setting Default Backup and Restore Options for SQL

You can use the defaults set by Backup Exec during installation for all SQL backup and restore jobs, or you can choose your own defaults. You can also change the defaults for any specific backup or restore job. To change backup and restore defaults for SQL: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Microsoft SQL. 3. Select the appropriate options as follows:
Options - set application defaults for SQL Item Backup Backup method
Description
Full - Back up entire database or filegroup. Select this option to back up the entire database or filegroup. See Backing Up SQL Databases on page 1029. This option is selected by default. Log - Back up transaction log. Select this option to back up only the data contained in the transaction log; it does not back up database data. After the transaction log is backed up, committed transactions are removed (truncated). See Backing Up SQL Transaction Logs on page 1033. Log No Truncate - Back up transaction log - no truncate. Select this method only when the database is corrupted or database files are missing. Since the Log No Truncate method does not access the database, you can still back up transactions that you may not be able to access when the database is in this state. You can then use this transaction log backup along with the database backup and any previous transaction log backups to restore the database to the point at which it failed; however, any uncommitted transactions are rolled back. The Log No Truncate method does not remove committed transactions after the log is backed up. See Backing Up SQL Transaction Logs on page 1033.
1052
Setting Default Backup and Restore Options for SQL Options - set application defaults for SQL Item Description
Differential - Back up database or filegroup changes only. Select this option to back up only the changes made to the database or filegroup since the last full backup. Because differential backups allow the restore of a system only to the point that the differential backup was created, you should also create multiple log backups between the differential backups. See Backing Up SQL Databases on page 1029.
Consistency check before Select a consistency check to run before a backup. backup None. Select this option if you do not want a consistency check to run before a backup. Symantec strongly recommends that you always run a consistency check either before or after the backup. This option is selected by default.
Full check, excluding indexes. Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked. Full check, including indexes. Select this option to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000 only). Select this option to perform a low overhead check of the physical consistency of the SQL 2000 database. This option only checks the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
Continue with backup if consistency check fails
Select this option to continue with the backup operation even if the consistency check fails. You may want to continue with the backup when the consistency check fails if you think that a backup of the database in its current state is better than no backup at all, or if you are backing up a very large database with only a small problem in a table.
1053
Setting Default Backup and Restore Options for SQL 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 option if you do not want a consistency check to run after a backup. Symantec strongly recommends that you always run a consistency check either before or after the backup. This option is selected by default. Full check, excluding indexes. Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked. Full check, including indexes. Select this option to include indexes in the consistency check. Any errors are logged. Physical check only (SQL 2000 only). Select this option to perform a low overhead check of the physical consistency of the SQL 2000 database. This option only checks the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
Display filegroups when creating new backup jobs
Select this checkbox if filegroups exist that you want to select for backup. If this checkbox is not selected, filegroups are not displayed as backup selections.
1054
Setting Default Backup and Restore Options for SQL Options - set application defaults for SQL Item Restore Recovery completion state
Description
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 this option is not selected.
1055
Setting Default Backup and Restore Options for SQL Options - set application defaults for SQL Item Consistency check after restore Description
None. Select this option if you are doing sequential restores. Do not run a consistency check after a restore until all sequential restores have been done. If a consistency check is selected during a restore, the restore will complete but the consistency check will not be done. Check the job log for this information. If you need to recover the database after restores are complete, select one of the following consistency checks when you select the Leave database operational option.
Full check, excluding indexes. Select this option to exclude indexes from the consistency check. If indexes are not checked, the consistency check runs significantly faster but is not as thorough. Only the data pages and clustered index pages for each user table are included in the consistency check. The consistency of the nonclustered index pages is not checked. Full check, including indexes. Select this option to include indexes in the consistency check. Any errors are logged. This option is selected by default. Physical check only (SQL 2000 only). Select this option to perform a low overhead check of the physical consistency of the SQL 2000 database. This option only checks the integrity of the physical structure of the page and record headers, and the consistency between the pages' object ID and index ID and the allocation structures.
1056
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 drive C, it will automatically replace the damaged databases with the copies of the master and model databases. You can then restart SQL, and restore the latest master database backup and any other databases that are necessary. 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 if using SQL 2000, 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
Back up the system drives that contain SQL instances.

1057
Whenever you back up the system drive that contains a SQL instance, copies of the master and model databases are backed up. Backing up the system drive that SQL is on also backs up all the executables and registry settings needed for SQL to run.

Back up the master database whenever any changes are made to SQL. Keep records of any service packs that have been installed. Review Disaster Preparation of the Windows Computer on page 607 to make sure you are prepared to recover the entire server, not just SQL.
To prepare for disaster recovery if using SQL 7.0, do the following:
Create a copy of the master and model databases, and place the copies in the same directory that the databases are in (see To create copies of the SQL 7.0 master and model databases: on page 1058). 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 607 to make sure you are prepared to recover the entire server, not just SQL.
To perform a recovery, you will need:
The latest backup of the SQL directory (\Program Files\Microsoft SQL Server\MSSQL), and the Windows registry/System State. The SQL database or filegroup backups, and differential and log backups. An Administrator logon account (or an Administrator equivalent) during the recovery.
To create copies of the SQL 7.0 master and model databases: 1. Use the SQL Server Service Manager to stop the SQL services. 2. Open a command prompt window, and copy the original master and model databases and their transaction logs to the specified file names. In a default installation of SQL 7.0, the databases are in C:\MSSQL7\Data. Type the following:
1058
Disaster Recovery of SQL
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

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 953.
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 on page 1049.
1059
Manual Recovery of SQL

If necessary, restore the Windows computer by following the instructions in Manual Disaster Recovery of Windows Computers on page 610. After recovery of the Windows computer is complete, or after the new server installation is available, recovery of the SQL databases can begin. In order to restore SQL databases, SQL must be running; however, SQL cannot be started unless the master and model databases are present. You can restore the master and model databases and start SQL using one of the following methods:
Rename the files created by Backup Exec that replace the master and model databases. After the master and model databases are present on SQL, you must start SQL, restore the master database with the Automate master database restore option, and then restore all other databases. Run the Rebuild Master utility (\Program Files\Microsoft SQL Server\80\Tools\Binn\rebuildm.exe for SQL 2000 or \MSSQL7\binn\rebuildm.exe for SQL 7.0) to rebuild the master database. 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 1048. To restart SQL 2000 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.
1060
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, and make sure they are not read-only files or the SQL services will not start. 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 restart SQL 7.0 using database copies: 1. Verify that the database copies are present. The database copies are named master$4idr, mastlog$4idr, model$4idr, and modellog$4idr. In a default installation of SQL 7.0, the databases are in C:\MSSQL7\Data. If necessary, restore the master and model database copies from a backup set to the same directory that the original master and model databases are in. 2. 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, and make sure they are not read-only files or the SQL services will not start. 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 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 Microsoft 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.
1062
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 Filegroup Backups on page 1044. 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 Microsoft 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 on page 1049. When all of the restore operations have completed successfully, then the recovery of the SQL databases is complete. After the recovery has been completed, Symantec strongly recommends that a full database backup be performed as soon as possible. Related Topics: Restoring Data on page 451
1063
1064
Appendix
Symantec Backup Exec Agent for Microsoft Exchange Server

The Symantec Backup Exec for Windows Servers - Agent for Microsoft Exchange Server (Exchange Agent) enables network administrators to perform backup and restore operations on Exchange servers that are connected to a network. Exchange database backups can be integrated with network backups without separate administration or dedicated hardware. The Exchange Agent works with Exchange 2003, 2000, and 5.5 installations, and 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. 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. Backing up and restoring Exchange 2000 and Exchange 2003 resources. 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 single-instance storage for message attachments. Recovery of individual databases or storage groups using the Recovery Storage Group feature of Exchange 2003 for non-snapshot backups.
1065
In Exchange 2000 and 2003 installations, the Exchange Agent also provides support for:

Requirements for Using the Exchange Agent
On Exchange 2003 servers running Windows 2003, the Exchange Agent can be used with the Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) and the Advanced Open File Option (AOFO). ADBO and AOFO are separate, add-on components of Backup Exec (see on page 991 and Symantec Backup Exec - Advanced Disk-based Backup Option on page 875).
Related Topics: Installing the Exchange Agent on page 1067 Backup Strategies for Exchange on page 1068 Recommended Configurations for Exchange on page 1072 Symantec Backup Exec - Advanced Disk-based Backup Option on page 875 Understanding the Advanced Open File Option on page 991
Requirements for Using the Exchange Agent

To use the Exchange Agent, the media server must have access to the Exchange Server. If you are using Exchange 2000 or 2003:
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 or Windows Server 2003.
If you are using Exchange 5.5 and want 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. Related Topics: Using Resource Discovery to Search for New Resources on page 311
1066
Installing the Exchange Agent
Installing the Exchange Agent

The Exchange Agent is installed locally as a separate, add-on component of Backup Exec for Windows Servers to protect local or remote Exchange Server databases. 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 to the Local Computer on page 71. For instructions on installing the Remote Agent on a remote Exchange server, see Installing Backup Exec Agents to Remote Computers on page 77. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line on page 794.
Appendix J, Symantec Backup Exec - Agent for Microsoft Exchange Server
1067
Using Backup Exec Logon Accounts with Exchange Resources
Using Backup Exec Logon Accounts with Exchange Resources

In order to back up and restore Exchange Server resources, you must use a Backup Exec service account that has domain and 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 when using Exchange 2000 or 2003, 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). In order to back up and restore individual Exchange mailboxes and public folders when using Exchange 5.5, use Microsofts Exchange Administrator utility to grant the Service Account 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 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 share the first five 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 Related Topics: Backing Up Exchange Mailboxes and Public Folders on page 1082 Configuring Logon Accounts on page 386
Backup Strategies for Exchange

Backup Exec incorporates online, nondisruptive Exchange database protection as part of everyday backup routines, which increases the chance of data recovery and minimizes data loss without inhibiting daily activity. Backup Exec protects Exchange data, 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 recover from the full backup and from each incremental backup as well.
What will work best for you is based on the size of your environment, the number of transactions processed each day, and the expectations of your users when a recovery is required. Anti-virus software may impact backup performance and could result in incorrect job log errors. Mail messages and the attachments will be fully backed up and fully restorable despite job log errors that may be generated when verifying the attached files. 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. Separate Exchange backup jobs from other backup jobs.
1069
If using Exchange 2000 or 2003, it is recommended that, in addition to backing up Exchange storage groups, you also back up the following on a regular basis:
Backup selections for Exchange 2000 or 2003 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:\ 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 file system functions may not be replicated. Backup and restore operations are not recommended or supported.
Windows registry System State
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 284. If the entire server must be restored, you must restore System State to the server before you can restore Exchange 2000. Key Management Service Back up the Key Management Service database by selecting the KMS (KMS) database icon in Backup Selections, and then running a full backup. Local or remote backups can be performed on the KMS database. Note KMS is not available in Exchange 2003. Site Replication Services If Exchange 2000 or 2003 is running in an Exchange 5.5 environment, (SRS) database 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.
1070
Backup Strategies for Exchange Backup selections for Exchange 2000 or 2003 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 or 2003, 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 mailboxes and public folders on page 1082.
If using Exchange 5.5, in addition to backing up the Information Store and Directory Store, it is recommended 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. Back up the registry by selecting System State and running a full backup.
Windows registry
Key Management Service To back up the KMS database, stop the Key Management Server (KMS) database service 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.
1071
Backup Strategies for Exchange Backup selections for Exchange 5.5 configuration data (continued) Recommended backup selections for configuration data Directory Store for each Exchange Server Description
The Directory Store for each Exchange Server is unique, so it is critical to have a backup of the Directory Store for each Exchange Server.
Related Topics: Backup Options for Exchange on page 1075 Backing Up Exchange on page 1079 Backing Up Exchange Mailboxes and Public Folders on page 1082 Setting Default Backup and Restore Options for Exchange on page 1102 Preparing for Disaster Recovery of Exchange Server on page 1108
Recommended Configurations for Exchange

Before starting backups for Exchange, read the following recommendations for configuring Exchange 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 storage groups and databases are disabled, and recovery is only possible up to the point of the last full or copy backup.
Additional recommendations if using Exchange 2000 and 2003 include:
1072
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.
In order to enable backup operations for public folders in Exchange 5.5 using all available backup methods, the mailbox used by Backup Exec to access the folders must be granted the Owner role on each public folder to be backed up, either directly or through membership in a Distribution List. The mailbox is determined by the logon account you specify when selecting public folders for backup. The Exchange Administrator program can be used to set the necessary client permissions for the public folders on your Exchange servers. For more information on setting client permissions on public folders, refer to your Exchange server documentation. Related Topics: Reviewing Circular Logging on page 1081
1073
Using Snapshot Technology With the Exchange Agent
Using Snapshot Technology With the Exchange Agent

The Exchange Agent now supports Microsofts Volume Shadow Copy Service (VSS), a snapshot provider service only available on Windows 2003 or later. VSS allows the backing up of the Exchange database using snapshot technology. Through VSS, a point in time view of the Exchange database is "snapped" and then backed up, leaving the actual Exchange database open and available for users. In order for the Exchange Agent to use VSS, the Exchange Agent must be installed and running on the Exchange server. The Exchange Agent supports the AOFO backup option Process logical volumes for backup one at a time. However, the Exchange Agent does not support the AOFO backup options Symantec Volume Snapshot Provider, VERITAS Storage Foundation for Windows Servers FlashSnap Option, and Use ServerFree Option. The Exchange Agent supports the ADBO backup option Process logical volumes for offhost backup one at a time, but does not support the Job disposition options. The Exchange Agent using VSS only supports full and copy snapshot backups unless you have Exchange Server 2003 with Service Pack 1 installed. If Exchange Server 2003 with Service Pack 1 is installed, the Exchange Agent supports full, copy, differential, and incremental storage group level snapshot backup and individual database restore. Note Because of a Microsoft Exchange limitation, snapshot and traditional backups are not interoperable when restoring Exchange data. Therefore, if traditional (non-snapshot) backups are performed as part of a data protection scheme, then snapshot backups should not be performed. Also, if snapshot backups are performed, traditional backups should not be done. If the Exchange Agent snapshot fails, then the job fails. Also, if incremental or differential backup methods are selected, but the computer is not running Service Pack 1, the job fails. Performing consistency checks before backup is highly recommended (see Perform consistency check before backup when using Microsoft Volume Shadow Copy Service (VSS) snapshot provider on page 1078). The Exchange Agent only supports storage group level snapshots; if individual databases are selected for snapshot backups, then the job fails. Individual database restores are supported. In order to back up Exchange data from any node of a VCS cluster, the Exchange System Manager component must be installed on all nodes. The Exchange Agent snapshot does not support:

NAS configurations Circular logging

1074
Backup Options for Exchange
Exchange 2003 Recovery Storage Group feature
Related Topics: Protecting Windows Server 2003 Systems on page 344 Understanding the Advanced Open File Option on page 991 Symantec Backup Exec - Advanced Disk-based Backup Option on page 875

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 259. If you are using the Advanced Open File Option, see After completing the restore, it is recommended that a full backup of the restored databases be performed. on page 1113 and Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999. If you are using Advanced Disk-based Option, see Setting Offhost Backup Options for Backup Jobs on page 892. To select backup job properties for Exchange: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click Microsoft Exchange.
1075

Backup job properties for Exchange Server Item Exchange server backup method Description Select one of the following backup methods:
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 the default option for Backup Exec but can be changed by selecting Tools, and then selecting Options. 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. If you are using the Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) or the Advanced Open File Option (AOFO), using this backup method requires the installation of Exchange 2003 and Exchange 2003 Service Pack 1.
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. If you are using the Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) or the Advanced Open File Option (AOFO), using this backup method requires the installation of Exchange 2003 and Exchange 2003 Service Pack 1.
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 data.
1076
Backup Options for Exchange 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 incremental backup.
Enable single instance backup for message attachments (for mailbox and public folder backups only)
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 to be 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.
1077
Backup Options for Exchange Backup job properties for Exchange Server (continued) Item Guide Me Description Click Guide Me to start a wizard that helps you choose backup job properties for recreating user accounts and mailboxes. Select this option if you want a consistency check to be performed when using
Perform consistency check before backup when using Microsoft Volume Shadow Copy Service (VSS) snapshot provider Continue with backup if consistency check fails
the Symantec Backup Exec for Windows Servers - Advanced Disk-based

Backup Option (ADBO) or the Advanced Open File Option (AOFO). The consistency check, which is run on the snapshot, determines if possible data corruption exists. Select this option if you want the backup job to continue even if the consistency check fails. You might want the job to continue if you think a backup of the database in its current state is better than no backup at all or if you are backing up a very large database that may have only a small problem.
Related Topics: Backing Up Exchange on page 1079 Backing Up Exchange Mailboxes and Public Folders on page 1082 Reviewing Circular Logging on page 1081
1078
Backing Up Exchange
Backing Up Exchange
To back up Exchange 2000 and 2003, you can select:

Multiple storage groups Individual storage groups Individual databases (not supported if using snapshot technology and not recommended for non-snapshot backups)
It is recommended that you select individual storage groups for backup rather than selecting individual databases in storage groups. Although you can select individual databases in a storage group for backup, the transaction logs for the entire storage group are backed up for each database selected. For example, if you select four databases in a storage group for backup, the entire collection of transaction logs for the storage group is also backed up four times. The transaction logs are not deleted until a full backup is run on every database in the storage group. You can still restore an individual database from a storage group backup. To back up Exchange 5.5, you select the Microsoft Exchange Information Store and Microsoft Exchange Directory. To back up Exchange data: 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 Resources on page 1068. 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. 4. If backing up Exchange 2000 or 2003 storage groups, to select all storage groups in Exchange, click the check box preceding the Microsoft Information Store, or you can select specific storage groups by expanding the Microsoft Information Store icon, and then individually selecting storage groups.
1079
Backing Up Exchange
If backing up Exchange 5.5, click the check boxes preceding the Microsoft Exchange Information Store and Microsoft Exchange Directory. 5. To select the Exchange backup options, on the Properties pane, under Settings, click Microsoft Exchange. For details on these options, see Backup Options for Exchange on page 1075. Note To perform incremental and differential backups of storage groups, make sure that circular logging is not enabled on the storage group. 6. Select other backup options from the Properties pane or start the backup job. If you are using the Advanced Open File Option, see Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999. If you are using the Advanced Disk-based Option, see Setting Offhost Backup Options for Backup Jobs on page 892 Related Topics: Backup Strategies for Exchange on page 1068 Backing Up Exchange Mailboxes and Public Folders on page 1082 Reviewing Circular Logging on page 1081 Backing Up Data on page 259

If you select a volume that contains Exchange data for backup, the Exchange Agent determines which Exchange data should not be included in a volume level backup. For example, .EDB and .STM files, as well as any active .LOG files, should not be part of the backup because they are opened for exclusive use by the Exchange system. These files will be automatically excluded for backup by a feature called Active File Exclusion. If this exclusion did not happen during a non-snapshot backup, these files would appear as in use - skipped. If this exclusion did not happen during a snapshot backup, the files would be backed up in a possible inconsistent state, which could create restore issues. While it is not recommended, if you want to include Exchange data in a volume level backup, you must first dismount the storage groups you want backed up. Then, run the backup job.
1080
Backing Up Exchange
Reviewing Circular Logging

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 and 2003: 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. 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. 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. Related Topics: Backup Strategies for Exchange on page 1068
1081
Backing Up Exchange Mailboxes and Public Folders

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. 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. 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. To obtain the most efficiency and greatest performance in mailbox and public folder backups, consider the following:
Recommendations for backing up Exchange 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 288). 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 check box in the Advanced File Selection dialog box.
1082
Backing Up Exchange Mailboxes and Public Folders Recommendations for backing up Exchange mailboxes and public folders (continued) Recommendation Use single-instance storage for message attachments Description 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.
Do not back up special system mailboxes created by Exchange Although these special system mailboxes can be backed up, it is not necessary or useful. The following are common examples of special system mailboxes, but there may be others depending on the Exchange server configuration and environment.

System Attendant Any mailbox name starting with SMTP or System Mailbox (for Exchange 2000 or 2003) Microsoft Schedule+Free/Busy Connector (for Exchange 5.5) Directory Service (for Exchange 5.5)
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.
1083
Backing Up Exchange Mailboxes and Public Folders Recommendations for backing up Exchange mailboxes and public folders (continued) Recommendation Select public folders from only one Exchange server. Description The same public folders may be displayed for multiple Exchange servers since public folders can be replicated. Selecting public folders on multiple Exchange servers only increases the time and media required for the backup and does not provide any additional protection.
Mailboxes are displayed in a server-centric view; that is, only mailboxes on the selected Exchange server are displayed in the backup selections list. Public folders may be displayed on more than one server since public folders can be replicated to many servers. 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. For Exchange 2000 or 2003, 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. 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 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.
1084
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 Resources on page 1068. 6. To select the mailbox or public folders backup method, on the Properties pane, under Settings, click Microsoft Exchange. For details on these options, see Backup Options for Exchange on page 1075. 7. Select other backup options from the Properties pane or start the backup job. Related Topics: Using Backup Exec Logon Accounts with Exchange Resources on page 1068 Recommendations for backing up Exchange mailboxes and public folders on page 1082 Backing Up Data on page 259
1085
Restore Options for Exchange
Restore Options for Exchange

This procedure details how to select restore job properties for Exchange, and provides definitions for restore options specific to Exchange. For details on how to create a restore job, and for definitions of all other restore jobs, see Restoring Data on page 451. To select restore job properties for Exchange 2000 and 2003: 1. On the navigation bar, click Restore. 2. On the Selections pane, under Source, select the data to be restored. 3. On the Properties pane, under Settings, click Microsoft Exchange. 4. Select the appropriate options as follows:
Restore job properties Item Microsoft Exchange Automatically recreate user accounts and mailboxes Select this check box to recreate the user accounts and their mailboxes if they do not already exist on the target server. Otherwise, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this check box 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 Microsoft 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 Description
1086
Restore Options for Exchange Restore job properties Item No loss restore (Do not delete existing transaction logs) Description 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.
Restore public folder
Restore private mailboxes 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. Exchange 2000 and Exchange 2003 No loss restore (do not delete existing transaction logs) Select this check box to preserve the existing transaction logs on the Exchange 2000 or 2003 server. Transaction logs from the storage media are then restored and added to the existing set of transaction logs on the Exchange 2000 or 2003 server. When the restore operation finishes, Exchange 2000 or 2003 automatically updates its databases with the uncommitted transactions found in the existing and newly-restored transaction logs. This option is selected by default. If you are restoring individual databases into a storage group, the No loss restore check box should be selected. If this check box is not selected, uncommitted transactions for other databases in the storage group may be lost. Note This option is not applicable if using the Advanced Open File Option or the Advanced Disk-based Option.
1087
Restore Options for Exchange Restore job properties Item Description
Temporary location for log Type a location where the associated log and patch files are to be and patch files kept until the database is restored. The default location is \temp, and a subdirectory is created for each storage group. The log and patch files for each storage group are kept in the corresponding subdirectory. Make sure the temporary location for log and patch files is empty before you start a restore job. If a restore job fails, check the temporary location (including subdirectories) to make sure any previous log and patch files from a previous restore job were deleted. Note This option is not applicable if using the Advanced Open File Option or the Advanced Disk-based Option. Dismount database before Select this option if you want Backup Exec to automatically take restore the Exchange database offline before the restore job runs. If this option is not selected, you must manually take the database offline before the restore job can run. When restoring a snapshot backup, all databases in a storage group must be taken offline. Selecting this option automatically takes all databases in a storage group offline. Commit after restore completes If your selection contains the last backup set to be restored, select this check box 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). Note This option is not applicable if using the Advanced Open File Option or the Advanced Disk-based Option. Mount database after restore Select this check box to mount the database so that it is available to users. This check box is only available if Commit after restore completes is selected.
1088
Restoring Exchange Data Restore job properties Item Guide Me Description Click Guide Me to start a wizard that helps you choose restore job properties for Exchange data.
Related Topics: Restoring Exchange Mailboxes and Public Folders on page 1094
Restoring Exchange Data

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 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. Use the Exchange System Manager utility to manually dismount any databases that are being restored or select the Dismount database before restore option when creating the restore job. Check the temporary location for log and patch files to make sure it is empty before you start 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.
Following are requirements for restoring Exchange 2000 and 2003:
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 are restarted. Following are requirements for running a restore job for Exchange 5.5 Server:
1089
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 451 for information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs. If you need to restore Exchange data to a server other than the one from which it was backed up, see Redirecting Exchange Data on page 1096. To restore Exchange 2000 and 2003 databases: Note Use the Exchange System Manager utility to manually dismount any databases that are being restored or select the Dismount database before restore option when creating the restore job. 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 Microsoft Exchange. 5. Select the appropriate options. For details, see Restore Options for Exchange on page 1086.
1090
Do not select the Commit after restore completes check box and the Mount database after restore check box 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. 6. Start the restore job or select other restore options from the Properties pane. 7. Run a full backup of the restored databases. 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.

4. On the Properties pane, under Settings, click Microsoft Exchange. 5. Select the appropriate options. For details, see Restore Options for Exchange on page 1086. 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 467. 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. Run a full backup of the restored databases.
1091
Related Topics: Restoring Data on page 451 Backing Up Data on page 259 Redirecting Exchange Data on page 1096
Restoring Exchange 2003 Data Using the Recovery Storage Group

The Recovery Storage Group (RSG) feature in Exchange 2003 allows you to mount a second copy of an Exchange mailbox store on any Exchange server in the same Exchange Administrative Group as the original while the original store is still running and serving clients. This allows you to recover data from an older backup copy of the store without disturbing client access to current data. After the RSG is created and one or more stores are added to it, you can restore online backup sets to it. Then you can use a new version of the EXMerge utility to extract mailbox data from the stores into .PST files, and optionally merge the extracted data back into the online stores. Following are requirements for restoring Exchange 2003 data using the Recovery Storage Group (RSG):

Data being restored cannot be from a snapshot backup. Mailbox stores in the RSG must come from the same storage group. You cannot add mailbox stores from different storage groups to the RSG at the same time. Public Folder stores are not supported for restore using the RSG. Do not mount mailbox stores in the RSG before the restore. If you do mount the stores before the restore, then you must dismount them and select This database can be overwritten by a restore on the database property page in Exchange System Manager prior to restoring them. On the server that hosts the RSG, there must be a storage group with the same name as the original storage group for the data you are restoring. If no such storage group exists on the server, then you can use that name for the RSG when you create it. The Active Directory topology of the Exchange system must be intact and in the same state it was in when the backup was made. You cannot restore mailbox stores that were deleted and recreated. In addition, you cannot recover mailboxes from stores if the mailboxes were deleted and purged from the system or moved to other servers or mailbox stores. Only Exchange mailbox stores from Exchange 2000 SP3 or later can be restored to the RSG. Restored mailbox stores are upgraded to the store version currently running on the RSG server.
1092
When the RSG exists on a server, the mailbox stores that it contains are the only stores that can be restored on that server by default. Symantec recommends that you create the RSG only when you intend to recover data using it, and remove the RSG from the server after the data recovery is complete.
Refer to your Microsoft Exchange Server 2003 documentation for more information on the requirements and restrictions of recovering Exchange data using the RSG. To restore Exchange 2003 databases using the Recovery Storage Group: 1. Use the Exchange System Manager utility to create the Recovery Storage Group and add the mailbox stores you want to restore. 2. On the navigation bar in Backup Exec, click Restore. 3. On the Properties pane, under Source, click Selections. 4. In the restore selections list, select the backup sets you want to restore.

5. On the Properties pane, under Settings, click Microsoft Exchange. 6. Select the appropriate options. For details, see Restore Options for Exchange on page 1086. Do not select the Commit after restore completes check box and the Mount database after restore check box 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 after the restore. 7. If the RSG resides on a different Exchange server than the databases you are restoring, see Redirecting Exchange 2003 Restores Using the Recovery Storage Group on page 1099. 8. Start the restore job or select other restore options from the Properties pane. 9. When the restore is complete, use the EXMerge utility in Exchange 2003 to extract the mailbox data you need from the restored mailbox stores and optionally merge the data back into the online stores.
1093
Related Topics: Restoring Data to a Server or Workstation on page 457 Redirecting Exchange 2003 Restores Using the Recovery Storage Group on page 1099
Restoring Exchange Mailboxes and Public Folders

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:
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 Restores on page 1100. 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 462. Do not restore special system mailboxes created by Exchange.
1094
The following are common examples of special system mailboxes, but there may be others depending on the Exchange server configuration and environment.

System Attendant Any mailbox name starting with SMTP or System Mailbox (Exchange 2000 or 2003) Microsoft Schedule + Free/Busy Connector (Exchange 5.5) Directory Service (Exchange 5.5)
Before starting the restore job, review Restoring Data on page 451 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 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 Microsoft 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 check box 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 Microsoft Exchange. Select Automatically recreate user accounts and mailboxes, and then click Change password. 5. If using Exchange 2000 or 2003, start the restore job or select other restore options from the Properties pane. If using Exchange 5.5, after the 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 Jobs on page 464. When the Exchange server is back online, run the Directory
Appendix J, Symantec Backup Exec - Agent for Microsoft Exchange Server 1095
Redirecting Exchange Data
Store/Information Store (DS/IS) consistency adjuster in order to resolve any inconsistencies. Results of the consistency adjustment appear in the Windows Event Log. For more information concerning the DS/IS consistency adjuster, refer to your Exchange documentation. 6. After the restore is complete, run a full backup of the restored mailboxes. Related Topics: Restore Options for Exchange on page 1086 Redirecting Mailbox Restores on page 1100

With Backup Exec, you can restore Exchange data to the server from which it was backed up or redirect the Exchange data to another Exchange server. When redirecting Exchange data, the service pack on the Exchange server where data is being redirected should be the same as the service pack on the original Exchange server. Redirected restore jobs can be created for the following:
Exchange 2000 and 2003 storage group and database restores (see Redirecting Exchange 2000 and 2003 Storage Group and Database Restores on page 1098) Exchange 5.5 Information Store database (see Redirecting Exchange 5.5 Database Restores on page 1098) Exchange 2003 restores using the Recovery Storage Group feature (see Redirecting Exchange 2003 Restores Using the Recovery Storage Group on page 1099) Exchange mailboxes (see Redirecting Mailbox Restores on page 1100)
To redirect Exchange data: 1. Follow the instructions for the restore in Restoring Exchange Data on page 1089. 2. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click Microsoft Exchange Redirection.
1096

Restore job properties for redirected Exchange sets Item Redirect Exchange sets Description Select this check box 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 Resources on page 1068. Type the name of the mailbox to which you are redirecting data; the mailbox must already exist on the target server. To redirect to a mailbox, use a logon account that has rights to the target mailbox. To select a logon account, click Change.
Restore to server
Restore to mailbox
Mailbox logon account
4. Start the redirected restore job or select other restore options from the Properties pane. 5. If restoring Exchange 5.5: a. 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 464.
b. 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, Symantec recommends that you run a full backup of the restored databases.
1097
Redirecting Exchange 2000 and 2003 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. A version of Exchange server database to a different version of the database. Service packs for both Exchange servers should also be the same. Site Replication Service (SRS) and Key Management Service (KMS). These services are dependent on the computer they reside on; redirection to another computer is not supported and could result in the loss of functionality of these services.
You cannot redirect the restore of:
Note KMS is not available in Exchange Server 2003 Before starting the restore job, review Restoring Data on page 451 for information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs. After completing the restore, it is recommended that a full backup of the restored databases be performed. Related Topics: Redirecting Exchange Data on page 1096
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.
1098
Following are restrictions for redirecting Exchange 5.5 database restores:

Restrictions for redirecting restores of Exchange 5.5 databases Restriction The Site and Organization names of the original and destination servers must match. Description Backup Exec does not prevent redirection of an Information Store when the Site and Organization names differ. If the Site and Organization names are different, the redirected restore may appear to complete successfully but the IS service will fail to start afterward.
The No loss restore option cannot The No loss restore option must be cleared so that any be selected. transaction logs on the destination server are removed to avoid an incompatibility that would prevent the Information Store service from starting. The No loss restore option appears on the Restore Job Properties for Exchange 5.5 dialog box. To access this option, on the navigation bar, click Restore, and then in the Properties pane under Settings, click Microsoft 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.
Before starting the restore job, review Restoring Data on page 451 for information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs. Related Topics: Redirecting Exchange Data on page 1096
Redirecting Exchange 2003 Restores Using the Recovery Storage Group

Before starting the restore job, review Restoring Data on page 451 for information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs. After completing the restore, it is recommended that a full backup of the restored databases be performed. Related Topics: Redirecting Exchange Data on page 1096 Restoring Exchange 2003 Data Using the Recovery Storage Group on page 1092
1099
Redirecting Mailbox Restores

You can redirect the restore of individual mailboxes from backup sets created when individual mailboxes were backed up from the Microsoft Exchange Mailboxes selection. You cannot restore individual mailboxes 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 Resources on page 1068. 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.
1100
For example, Mailbox 1 consists of Top of Information Store, Inbox, and Folders 1 and 2, each containing some mail messages. If you back up Mailbox 1 and then you restore Mailbox 1 to the existing Mailbox 2, then all of Mailbox 1, including the Top of Information Store, Inbox, Folders 1 and 2, and messages, are restored to Mailbox 2. Note that Mailbox 1 itself is not created under Mailbox 2.
Redirecting the restore of Mailbox 1 to Mailbox 2
If you redirect the restore of Mailbox 1\Top of Information Store\Folder 2 to Mailbox 2, the contents of Mailbox 1\Top of Information Store\Folder 2, Message 5 and Message 6, are placed in Mailbox 2 in the same folder as they were in Mailbox 1, as illustrated in the following graphic.
Redirecting Mailbox 1\Top of Information Store\Folder 2 to Mailbox 2
Before starting the restore job, review Restoring Data on page 451 for information on finding and viewing specific data to restore, as well as for details on restore options and submitting restore jobs.
1101
Setting Default Backup and Restore Options for Exchange
Related Topics: Redirecting Exchange Data on page 1096 Restoring Exchange Mailboxes and Public Folders on page 1094

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. If you are using the Advanced Open File Option also, see Setting Defaults for the Advanced Open File Option for Backup Jobs on page 999 and Changing the Default Settings for the Symantec Volume Snapshot Provider on page 1008. If you are using the Advanced Disk-based Option, see Symantec Backup Exec - Advanced Disk-based Backup Option on page 875. To change backup and restore defaults for Exchange 2000 and 2003: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Microsoft Exchange.
1102

Microsoft Exchange Default Options Item Backup Exchange 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. If you are using the Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) or the Advanced Open File Option (AOFO), using this backup method requires the installation of Exchange 2003 and Exchange 2003 Service Pack 1.
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. If you are using the Symantec Backup Exec for Windows Servers - Advanced Disk-based Backup Option (ADBO) or the Advanced Open File Option (AOFO), using this backup method requires the installation of Exchange 2003 and Exchange 2003 Service Pack 1.
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. Appendix J, Symantec Backup Exec - Agent for Microsoft Exchange Server 1103
Setting Default Backup and Restore Options for Exchange Microsoft Exchange Default Options 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.
1104
Setting Default Backup and Restore Options for Exchange Microsoft Exchange Default Options 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 to be 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.
Restore public folder
1105
Setting Default Backup and Restore Options for Exchange Microsoft Exchange Default Options Item Description
Restore private mailboxes 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. Restore - Exchange 2000 Temporary location for log Type a location where the associated log and patch files are to be and patch files kept until the database is restored. The default location is \temp. If storage groups are being restored, a subdirectory in \temp is created for each storage group. The log and patch files for each storage group are kept in the corresponding subdirectory. If Commit after restore completes is selected for the restore job, the log and patch files in the temporary location are applied to the database, and then the current log files are applied. After the restore is complete, the log and patch files are automatically deleted from the temporary location (including any subdirectories). To select Commit after restore completes, on the navigation bar, click Restore, and then on the Properties pane, under Settings, click Microsoft 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.
1106
Setting Default Backup and Restore Options for Exchange Microsoft Exchange Default Options Item Automatic recreation Automatically recreate user accounts and mailboxes Select this check box to recreate the user accounts and their mailboxes if they do not already exist on the target server. Otherwise, the restore job will fail if a mailbox that is being restored does not exist on the target server. When this check box 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 1095. 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. Change password... Click this to specify a password to use when user accounts and mailboxes are automatically recreated on the target server. Description
Related Topics: Restoring Exchange Data on page 1089 Understanding the Advanced Open File Option on page 991
1107
Preparing for Disaster Recovery of Exchange Server
Preparing for Disaster Recovery of Exchange Server

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

An operating system configuration sheet A hard drive partition configuration sheet Any RAID configuration A hardware configuration sheet EISA/MCA configuration disks An Exchange configuration sheet A Windows emergency repair diskette 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 that were applied to the original installation
To perform the actual recovery, you will need:

Disaster Recovery for Exchange 2000 and 2003

This procedure guides you through a complete restoration of Exchange 2000 and 2003 using Backup Exec. You should have already performed all the appropriate preparation as detailed in Preparing for Disaster Recovery of Exchange Server on page 1108. 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. Other requirements include:
The storage groups and databases must already exist on the target server, and have the same names as the original storage groups or databases.
1108
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.
If you purchased the Intelligent Disaster Recovery option, see Microsoft Exchange Recovery Notes on page 954 for directions on using Intelligent Disaster Recovery to recover the Exchange server. To perform disaster recovery for Exchange 2000 or 2003: 1. Recover the Windows server first. For instructions, see Disaster Preparation of the Windows Computer on page 607. Note Make sure you restore the Exchange 2000 or 2003 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 or 2003 server. 2. From the Services applet, verify the Microsoft Exchange Information Store service is started. 3. Start Backup Exec. 4. Catalog the media that contains the latest full, incremental, and differential backups of the Exchange 2000 or 2003 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.
1109
9. On the Properties pane, under Settings, click Microsoft Exchange. 10. Clear the Exchange 2000 No loss restore (do not delete existing transaction logs) option. 11. In the Temporary location for log and patch files field, 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 check box 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). 13. If you want the databases to be immediately available to users after the recovery, select Mount database after restore. This check box 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.
1110
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 Server on page 1108. Always log on to Windows using the Administrator account (or an Administrator equivalent) during this procedure. To properly recover Exchange, the Directory Store needs to be restored to a server that has the same computer name, and Domain, Organization, and Site name as the original. If these conditions are not met, the recovery will not be successful. Even if the only Directory Store backup available is of the original Directory Store, restore it, and then backfill changes from another server in the site. If you purchased Intelligent Disaster Recovery, see Microsoft Exchange Recovery Notes on page 954 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 Preparation of the Windows Computer on page 607. 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 pause when there is no database to use because you have not restored it yet. However, if you have tools that can kill a process such as KILL or PVIEWER, then kill the DSAMAIN.EXE process and go to step 4 on page 1112.
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. For Windows NT, click Start, point to Settings, and then click Control Panel, and then double-click Services. Double-click Microsoft Exchange Directory service, change the Startup Type to Disabled, and then click OK.
3. Restart the computer.
1111
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. 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 Microsoft Exchange. 14. Select the Exchange 5.5 options Restore Public Folder and Restore Private Mailboxes. 15. Clear the check box for the Exchange 5.5 option No loss restore (do not delete existing transaction logs). 16. Start the restore job. 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 \setup\your processor type\bootenv directory on the Exchange CD to the \exchsrvr\mtadata directory on your hard drive: For example, assuming your Exchange installation is on drive C, your CD-ROM drive is drive D, and your processor type is Intel, you would type the following in a command window:
1112
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:

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.
1113
1114
Appendix
Symantec 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 Symantec Backup Exec for Windows Servers - Library Expansion Option (LEO). This option allows concurrent processing on multi-drive robotic libraries. Related Topics: Using Robotic Libraries with Backup Exec on page 164 Configuring Multi-drive Robotic Libraries on page 1116
Setting Up Robotic Library Hardware

Before installing Backup Exec, make sure that the robotic library hardware is configured properly.
Make sure the robotic arm is set to Random mode. Refer to your robotic library documentation for more information. If you have a multi-LUN robotic library, make sure that the controller card is set to support multiple LUNs (if supported). The SCSI ID of the robotic arm must precede the SCSI ID of the drives in the robotic library.
1115
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 IDs for each device. In addition to separate SCSI IDs, each drive in a multi-drive robotic library has unique drive element addresses. You must know each drives element address to properly configure the robotic library to work with Backup Exec (refer to your robotic library documentation to determine the drive element address for each storage device). After determining the drive considered to be the first drive in the robotic library (Storage Device 0), you will need to arrange the SCSI IDs to match the sequence of the drive element addresses. For example, if your robotic library has two drives, the drive with the lowest drive element address should be assigned the lower SCSI ID.
Example configuration for a Multi-drive robotic library Data Transfer Element (Storage Devices) Robotic Arm Storage Device 0 Storage Device 1 SCSI ID 4 5 6 Drive Element Address N/A 00008000 00008001
1116
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 to the Local Computer on page 71, adding the Library Expansion Option serial number.
Starting Backup Exec After Installing the Library Expansion Option

Information is displayed about the configuration of the 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. 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.
This item displays several dialogs, including the Welcome screen:
Appendix K, Symantec Backup Exec - Library Expansion Option
1117
Starting Backup Exec After Installing the Library Expansion Option Detected Hardware dialog box
Devices in the robotic library Robotic library
Drive Configuration dialog box
Make sure that each device in the robotic library is properly associated with the robotic library. Make sure that the drives in the robotic library appear in the device configuration wizard under the robotic library in the order matching their drive element address. The drive with the lowest drive element address should appear at the top of the list. If a robotic library storage device appears in the list as a stand-alone device, make sure the SCSI addresses of the robotic library and the storage device are configured properly.
1118
Starting Backup Exec After Installing the Library Expansion Option
Note During startup, if the storage devices in the robotic library contain media, Backup Exec attempts to return the media to its original magazine slot. If the media cannot be returned to the slot, you are prompted to eject the media from the storage device. Related Topics: Setting Up Robotic Library Hardware on page 1115 Using the Backup Exec Assistant on page 116 Viewing Drive Configuration Properties on page 154
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.
Appendix K, Symantec Backup Exec - Library Expansion Option
1119
Starting Backup Exec After Installing the Library Expansion Option Robotic library properties for Library|Configuration tab
After completing the configuration of your robotic library, perform an Inventory operation to update the Backup Exec media database. Related Topics: Inventorying Media in Devices on page 193
1120
Appendix
Backup Exec Desktop and Laptop Option

The Backup ExecDesktop and Laptop Option (DLO) provides automated file protection for desktops and laptops (collectively referred to as desktops). Protection is provided whether the computer is connected to the network or offline. When the desktop is not connected to the network, the files are backed up to a User Data Folder on the desktop. When the computer reconnects to the network, the files are backed up from the local Desktop User Data Folder to the designated Network User Data Folder. Users who have multiple computers can synchronize the data between their computers so the most up-to-date file versions are available on all of their computers. Note This product is intended to provide file level protection for desktop user data and is not intended to provide a full system backup.
How the Desktop and Laptop Option Works

DLO is comprised of the DLO Administration Console and database, which are managed by the Administrator, and the Desktop and Laptop Agent (Desktop Agent) which is installed and run on desktop computers. Note The DLO Administration Console and database are part of Backup Exec and run on the Backup Exec media server. The DLO Administration Console runs in a separate window that you access from Backup Exec. From the DLO Administration Console, the Administrator can:
1121
How the Desktop and Laptop Option Works
Create Profiles for groups of users or computers. Profiles enable you to control the desktop users level of interaction with the Desktop Agent, define the types of files that are able to be backed up, set the schedule for backups, and configure additional settings for the Desktop Agent. Create Network User Data Folders. Network User Data Folders are locations on the network that are assigned to Desktop Agent users where the data from their protected desktops is stored. DLO Storage Locations can be used to automatically create Network User Data Folders for each new Desktop Agent user, or you can use existing network shares as Network User Data Folders and add them manually to DLO. Create Automated User Assignments. Automated User Assignments determine the Storage Location and Profile to which users are assigned when they install the Desktop Agent. Note Automated User Assignments are not used if users are manually added to DLO.
Add users manually to DLO. Instead of using Automated User Assignments, you can manually add users to DLO and assign a Profile and Storage Location to them. This is particularly useful when network shares already exist for user data storage. Users can be added individually or multiple users can be added at the same time by importing them from a list. View history log files, receive alerts, and restore files to a desktop from the Administration Console.
The Desktop Agent resides on the desktops and laptops that you want to protect. The desktop users level of interaction with the Desktop Agent can vary depending on how the Administrator has configured the Profile assigned to the user. The Desktop Agent may run in the background, automatically protecting files. Alternatively, desktop users with full access to the Desktop Agent interface can schedule backups, select which types of files to back up, restore files, synchronize file versions between different computers, and view the status of their backups. Related Topics: Setting Up DLO on page 1145 Setting up a DLO Profile on page 1146 Managing Backup Selections on page 1155 Creating DLO Storage Locations on page 1165 Setting up Automated User Assignments on page 1168
1122
How the Desktop and Laptop Option Works Relationship Between Backup Exec and the Desktop and Laptop Option Components
- Backup Exec Administration Console
Administration Console on the media server or a remote server
- Backup Exec media server - Desktop Agent Install Share The BE and DLO Admin Consoles and DLO file servers can reside on the media server or remote servers.
Storage Locations and Network User Data
DLO File Server
If you use Backup Exec to protect the file servers that host the Network User Data Folders remotely, the Remote Agent for Windows Servers is required.
DLO File Server
- Desktop Agent - Desktop User Data Folder
Desktops and Laptops
- Desktop Agent - Desktop User Data Folder
Appendix L, Backup Exec Desktop and Laptop Option
1123
System Requirements for the Administration Console
System Requirements for the Administration Console

The following are the minimum system requirements for running this version of the DLO Administration Console.
Minimum System Requirements Item Operating System Description
Microsoft Windows 2000 Professional version, Windows 2000 Server version, Windows 2000 Advanced Server, or Windows 2000 Datacenter Microsoft Windows Server 2003 server family Microsoft Windows XP Service Pack 1 or later
Internet Browser Processor Memory
Internet Explorer 5.01 or later; however, version 5.5 is recommended Pentium system Required: 256 MB RAM Recommended: 512 MB (or more for better performance)
Disk Space
150 MB hard disk space required after Microsoft Windows is installed (typical installation)

Other Hardware
Network interface card CD-ROM drive Printer supported by Windows (optional) Mouse (recommended)
Note Novell E-Directory, NIS+ and other non-Windows Domain or Active Directory authentication schemes are not supported.
1124
Getting Started
Getting Started
The following topics address issues that should be considered before installing DLO.

Media Server Considerations Server Loading Authentication Considerations Using DLO with Firewalls Configuring DLO to Use a Specific Port for Database Access Excluding Files that are Always Open Using DLO with other Symantec Products Using Hidden Shares as Storage Locations
Media Server Considerations

The media server and DLO Storage Locations must be in a Windows Domain or Active Directory. Computers running the Desktop Agent can be outside of a Windows Domain or Active Directory, but they must authenticate with the domain or directory to access the media server or Storage Locations.
Server Loading
DLO can be treated as a network file server. The ideal server for DLO has a fast network connection and a fast set of disks. The CPU is not as critical as these other factors for the DLO file server. The number of Desktop Agents that can successfully back up to one DLO installation depends on many factors. Multi-client testing of DLO has found that when there are more than 400 clients attached to a DLO server running Windows 2000 Advanced Server, file operations may begin to fail when Paged Pool memory runs out. For this reason, it is not recommended to configure DLO to run more than 400 concurrent backups of this size.
1125
Getting Started
Authentication Considerations
DLO Administration Console The DLO Administration Console can be managed by any user who has full admin rights on the media server where DLO is installed. The users account must be a domain account and must have rights to create network shares and manage permissions of network shares and directories on any remote server used for Storage Locations or Network User Data Folders. This is commonly accomplished by using a domain admin account. See Creating Administrator Accounts on page 1137 for additional information. Desktop Agent DLO requires domain accounts. Every Desktop Agent user must log in to DLO using a domain account. If you have users who log in using local accounts, they can still use DLO, but they must have domain credentials to authenticate with DLO.
Using DLO with Firewalls

DLO is designed to work in firewall environments. In order for DLO to function properly in a firewall environment, network file shares must be visible after establishing a remote connection such as VPN. If file sharing is not allowed, DLO will not be able to transfer files to or from the Network User Data Folder. Desktop computer files will still be protected to the Desktop User Data Folder, and will be transferred when the Network User Data Folder is accessible.
Configuring DLO to Use a Specific Port for Database Access

It may be desirable to configure DLO to use a specific port for database access. This may be necessary, for example, if a fixed port is already being used for the SQL Server, requiring that DLO be configured to use the same port to access the DLO database. To configure DLO for alternate database access through a specific port: 1. Select a unique port number for the DLO database and then use svrnetcn.exe to set the new port number. 2. On computers that run the DLO Administration Console from outside the firewall, create the following registry key as a DWORD value if it does not exist and set the DBUseTCP flag to 1: HKLM\SOFTWARE\VERITAS\DLO\2.0\AdminConsole\DBUseTCP
Getting Started
3. On computers that run the Desktop Agent from outside the firewall, create the following registry key as a DWORD value if it does not exist and set the DBUseTCP flag to 1: HKCU\Software\VERITAS\DLO\2.0\Client\DBUseTCP or HKLM\SOFTWARE\VERITAS\DLO\2.0\Client\DBUseTCP 4. Set the DBTcpPort on the computers modified in steps 2 and 3 to the port number you set in step 1. 5. Restart the modified computers.
Excluding Files that are Always Open

On desktop computers running Windows XP and Windows 2000, the following folders and file types are generally always open and DLO is unable to back them up. Adding these files to the Global Excludes list, or Backup Selection exclude list will prevent them from always being listed in the pending files list on the Desktop Agent.

C:\Windows\System32\Config registry hives and logs, including *.DAT.LOG, *.LOG and the files system, SECURITY, default, SAM, and software C:\Windows\System32\wbem *.EVT *.LOG (in particular, STI_Trace.log, WIADEBUG.LOG, WIASERVC.LOG) *.DAT (in particular, NTUSER.DAT, USRCLASS.DAT)
Related Topics: Managing Backup Selections on page 1155 Configuring the Global Exclude List on page 1174
1127
Getting Started
Using DLO with other Symantec Products

DLO is compatible with other Symantec products. The following discusses known compatibility issues. Symantec Storage Exec Symantec Storage Exec is a policy based storage resource manager for controlling file and application disk usage in Microsoft Windows environments. DLO and Storage Exec are compatible, but care must be taken to avoid conflicts between DLO backup selections and Storage Exec policies. If DLO is configured to back up a specific file type and Storage Exec is set to prevent this file type from being copied to the server, a conflict will result. DLO will attempt to back up the file, but the operation will fail. The DLO history log will indicate that the file failed to copy to the Network User Data Folder. To prevent this conflict, DLO backup selections and Storage Exec policies must be reviewed to identify any potential conflicts. If a conflict is found, the policies must be manually revised to eliminate the conflict.
Using Hidden Shares as Storage Locations

DLO supports the use of hidden shares (for example; Share$) as Storage Locations on NTFS volumes or as Network User Data Folders for FAT32 volumes, but these shares must be manually created and configured. They cannot be created with the DLO Administration Console. Hidden shares cannot be used for FAT based Storage Locations. The following permissions should be used:
Permission Settings for Hidden Shares Drive Type User or Group Permissions
Share Permissions on NTFS Volumes Administrator Everyone Allow Full Control, Change, Read Allow Full Control, Change, Read
Security Permissions on NTFS Volumes Administrator Everyone Full control Allow Read & Execute Allow List Folder Contents Allow Read 1128 Administrators Guide
Getting Started Permission Settings for Hidden Shares (continued) Drive Type User or Group Special security permissions or advanced settings Permissions Allow Traverse Folder/Execute File Allow List Folder/Read Data Allow Read Attributes Allow Read Extended Attributes Allow Read Permissions Advanced Security Permissions on NTFS Volumes Administrator Everyone Allow Full Control Allow Traverse Folder / Execute File Allow List Folder / Read Data Allow Read Attributes Allow Read Extended Attributes Allow Read Permissions Share Permissions on FAT Volumes Administrator Owner Full Admin Group Allow Full Control, Change, Read Allow Full Control, Change, Read Allow Full Control, Change, Read
Limited Admin Group Allow Read
1129
Installing the Backup Exec Desktop and Laptop Option

The Symantec Backup Exec Desktop and Laptop Option is installed as a separate add-on component of Backup Exec for Windows Servers to protect data on desktops. To install DLO, see Installing Backup Exec Options to the Local Computer on page 71. If you prefer to install DLO from the Command Line (Silent Mode), see Installing Backup Exec Using the Command Line (Silent Mode) on page 81 and Command Line Switches for Backup Exec Silent Mode Installation on page 82. After you install and configure the settings for the desktop users, you can install the Desktop Agent or direct the desktop users on how to install it. The Desktop Agent is installed from the Desktop Agent install share, which is created when DLO is installed on the Backup Exec media server. Note The Backup Exec media server and any Storage Locations must be in a Windows Domain or Active Directory. Computers running the Desktop Agent can be outside of a Windows Domain or Active Directory, but they must authenticate with the domain or directory to access the media server or Storage Locations. You will be prompted to provide domain credentials. Related Topics: Setting Up DLO on page 1145 Deploying the Desktop Agent on page 1133 Installing the Desktop Agent on page 1233 Note Novell E-Directory, NIS+ and other non-Windows Domain or Active Directory authentication schemes are not supported. Before installing DLO, review Getting Started on page 1125. This section discusses a number of topics that should be considered before installing DLO.
1130
Updating DLO
Updates to Backup Exec are periodically provided by VERITAS Update or released on CD. As applicable, these updates include updates to the Desktop Agent install set, although the Desktop Agent updates are not automatically installed. To update the DLO Administration Console: 1. Install the DLO Administration Console as directed in Installing the Backup Exec Desktop and Laptop Option on page 1130. 2. Start the DLO Administration Console and set a recovery password using the Password Recovery Wizard which automatically starts the first time DLO version 10.0 is opened after installation. 3. If you are updating from DLO version 9.1 to version 10.0 run the following commands using the DLO command line interface:
Run the -keytest command to determine if there is any existing backup data that cannot be recovered because the user has been deleted. See -KeyTest Command on page 1218 for more information. Run the -createrecoverykeys command to assign recovery keys to existing users. See -CreateRecoveryKeys Command on page 1228 for more information.
Updating the Desktop Agent

As soon as the media server is updated, either through a full install, hotfix or Service Pack release, the Desktop Agents will need to be updated in one of the following ways: From the Desktop Agent Computer:
To manually update the Desktop Agents, from the Desktop Agent machine, run the following: \\<media server>\DLOAgent\update_10.0\Setup.exe.
From the Backup Exec Administration Console:
The Desktop Agent updates can also be remotely installed using the Backup Exec push install feature.
From the DLO Administration Console:
The DLO Command Line Interface Tool can automatically offer updates to the Desktop Agents using the publish command.
1131
To upgrade Desktop Agents using the Command Line Interface Tool: 1. Update the media server as directed in the update documentation. 2. From the command line on the server, change to the DLO installation directory. Example C:\Program Files\veritas\Backup Exec\NT 3. Run DLOCommandu.exe with the update option to add the configuration file and make note of the ID number returned when this command is run: DLOCommandu -update -add -f Note DLOAgentUpdate_BE.iniIf the configuration file has been moved or renamed, you will need to specify the full path and file name in the command above. Sample output: ID=3 Name= 10.0 Update Description=Updates Backup Exec DLO Desktop Agent from 9.1 to 10.0 Version=2.0 Build=1.XX.XX srcPath=\\MediaServerName\DLOAgent\update_10.0 cmdPath=%DOWNLOADDIR% cmdName=setup.exe cmdArgs=-s 4. Run DLOCommandu.exe with the publish command to make the update available to Desktop Agent users. DLOCommandu -update -publish -UI y -U UserName DLOCommandu -update -publish -UI y -P ProfileName Where 'y' is the ID number returned when the 'add' command was run in step 3. Using a '*' in place of UserName or ProfileName will publish the update to all users. When this command is executed, it will return a list of all users targeted for update. Users will be updated the next time the Desktop Agent application is started. Note For more information on the -update command and additional command options, see -Update Command on page 1222.
1132
Related Topics: DLO Command Line Interface Management Tools on page 1213
Deploying the Desktop Agent

When you install DLO from the Backup Exec installation CD, the Desktop Agent install set is created on the Backup Exec media server in a directory that is shared and available via a UNC path. There are several ways to deploy the Desktop Agent from the Desktop Agent install share to the desktop computer.
Desktop Agent Deployment Methods Deployment Methods Push Install Description The Desktop Agent can be push installed using the Backup Exec installer (see Installing Backup Exec Agents to Remote Computers on page 77). Note After a push install of the Desktop Agent, it may take up to two minutes for the Desktop Agent to start up on the desktop computer. E-mail Send a hypertext link to the install files or include the install files as an attachment. Place the install files on your companys intranet. Create a file that includes commands for installing the Desktop Agent. Then assign the script to the User Properties for the employees who need to use DLO. The commands are executed automatically when the user logs on to the network. For more information about logon scripts, refer to your Microsoft Windows documentation. Use this automated system to distribute the Desktop Agent install set to the desktop computers, which then initiate the installation. For more information about SMS, refer to your Microsoft documentation. To distribute the Desktop Agent installation files on a CD-ROM, place the contents of the \\media server\DLO Agent share on the CD-ROM. Users can then run setup.exe from the CD-ROM. The installed Desktop Agent will be correctly associated with the media server.
Web page Logon scripts
Microsoft Systems Management Server (SMS) CD-ROM
Related Topics: Installing the Desktop Agent on page 1233

Appendix L, Backup Exec Desktop and Laptop Option 1133
Using the DLO Administration Console

The DLO Administration Console is used to configure DLO and manage desktop backup and restore operations. To access the DLO Administration Console from Backup Exec or the Backup Exec Web Administration Console (BEWAC): 1. On the navigation bar, click Overview. 2. Under Desktop and Laptop Backups in the task pane, click Configure desktop and laptop backups.
Accessing DLO from the Backup Exec Administration Console
Related Topics: Setting Up DLO on page 1145 Creating DLO Storage Locations on page 1165 Setting up a DLO Profile on page 1146 Setting up Automated User Assignments on page 1168 Managing Desktop Agent Users on page 1177
1134
Setting a Recovery Password

When the DLO Administration Console opens for the first time, the Recovery Password Wizard will opens. You must set a recovery password using this wizard or DLO will not run. If you upgraded from a previous revision and previously set a recovery password, you will not be prompted to set a recovery password. DLO will use the existing password. The recovery password enables you to retrieve encrypted data that would otherwise be lost if the DLO database is damaged or corrupted. Once set, this recovery password can only be changed using the DLO command line interface tools. Related Topics: Data Integrity Scanner on page 1135 -SetRecoveryPwd Command on page 1225 -EmergencyRestore Command on page 1224
Data Integrity Scanner

The Data Integrity Scanner simplifies the process of scanning network user data to detect unrestorable backup data, verifying that all data is encrypted using the most recent user key, and ensuring that all data has the correct recovery key for emergency restoration. These functions could previously only be performed using the command line interface. When Desktop Agents are upgraded, they will automatically perform a data integrity check. When the Administration Console is opened, it identifies Desktop Agents that have not been checked for integrity. If any are found, a dialog will open stating that one or more computers have not yet been validated by the Data Integrity scanner and ask if they should be scanned. To run the Data Integrity Scanner: 1. From the Tools menu, select Wizards and then Data Integrity Scanner. 2. Click Next.
1135
3. Click Advanced if you would like to set advanced options. Select the desired options described below and click Next.
Data Integrity Scanner Advanced Options Item Permanently remove previously quarantined data Description Check to cause all previously quarantined data to be deleted.
Quarantine data Check to quarantine all files with outdated keys. If this encrypted with outdated option is not checked, data is scanned without being keys quarantined. After the data is quarantined, the Desktop Agent will back up a new version of the file with the correct encryption key. Include computers that have already been validated Verbose output Check to force all data to be rescanned, even if it has previously been validated.
Check to receive detailed information from the scan.
4. Click Start to begin the scan. 5. Review the scan results. If the scan identified data encrypted with outdated keys but you did not choose to quarantine the data, you can run the scan again after setting advanced options to quarantine this data. 6. Click Next. 7. Click Finish. Related Topics: Setting a Recovery Password on page 1135 -SetRecoveryPwd Command on page 1225 -EmergencyRestore Command on page 1224
1136
Creating Administrator Accounts

The DLO Administration Console can be managed by any user who has full admin rights on the media server where DLO is installed. The users account must be a domain account and must have rights to create network shares and manage permissions of network shares and directories on any remote server used for Storage Locations or Network User Data Folders. This is commonly accomplished by using a domain admin account. An administrator on the media server can also create and configure DLO administrator accounts for users using the DLO Administrator Account Management dialog as explained in To create and configure DLO administrator accounts: on page 1138. Adding DLO Administrator accounts allows additional users to use the DLO console without adding them to the administrators group on the media server. If a DLO administrator attempts to access a Network User Data Folder, but is not logged in with an account with rights to access to this folder, DLO will prompt for credentials. If credentials are input, they will be used to access the folder, but will not be saved. Automated Permissions Management When searching for files to restore, or viewing history logs, the DLO Administration Console accesses the Network User Data Folders using the credentials of the currently logged in user. If this user does not have the correct permissions to access a resource, a dialog is displayed explaining this. To configure DLO to automatically manage permissions for accessing Network User Data Folders, the Automatically grant DLO administrators access to network user data folders check box must be selected and two valid fully qualified domain groups chosen. The domain groups must already exist or be created by a domain administrator. For DLO, we recommend using the groups DLOFullAdmin and DLOLimitedAdmin. Once enabled all existing and future DLO administrators will be automatically added to a domain group depending upon whether the configured administrators are granted full or limited restore rights. The full admin group is used to grant administrators read access to users data, whereas the limited admin group only supplies list access, thus protecting the users data from unauthorized access. When accessing a Network User Data Folder, the DLO console automatically checks the folder to ensure it can read the files and data within. If the Console is unable to access the folder, DLO uses the specified domain admin group to set permissions on the files and folders it needs to access. By making these files and folders a member of the specified DLO admin group, all DLO administrators are thus automatically granted permissions to access the necessary resources. Limited Restore By default, DLO administrators cannot restore a desktop users files to an alternate location, providing an additional level of data security. A DLO administrator can be granted full restore privileges, which allows the administrator to restore data to an alternate location.
1137
To create and configure DLO administrator accounts: 1. On the DLO Administration Console Network menu, select Administrator Accounts to open the Administrator Account Management dialog.
Administrator Account Management Dialog
2. Click Add to open the Add Administrator Account dialog.

Add Administrator Account Dialog
1138
3. Define the administrator account as follows:

Add Administrator Account Options Item User Name Description Type the name of the user you want to give administrative rights to using the format DomainName\UserName Type a description for this administrator account. Make any relevant notes regarding the administrator account. Check to allow this DLO administrator full restore privileges, including the ability to restore desktop user data to an alternate location. Note Allowing someone other than the desktop user who owns the data to restore files to an alternate location can compromise data security.
Description Notes Grant administrator full restore privileges
4. Click OK. 5. To modify the permissions for DLO administrators, click Permissions. If you do not want to set permissions at this time, skip to step 9. 6. Check the Automatically grant DLO administrators access to network user data folders checkbox if you want all DLO administrators to be able to access Network User Data Folders containing desktop user files. Caution Granting access to Network User Data folders allows DLO administrators to access desktop users backup files.
1139
Using the DLO Administration Console Permissions Dialog
7. To grant DLO administrators in a specified domain group full restore privileges including the ability to restore a desktop users files to an alternate location, enter or browse to a fully qualified domain group in the For DLO administrators with full restore privileges, use the domain group field. Example Enterprise\DLOAdmins 8. To grant DLO administrators in a specified domain group limited restore privileges that do not include the ability to restore a desktop users files to an alternate location, enter or browse to a fully qualified domain group in the For DLO administrators with limited restore privileges, use the domain group field. 9. Click OK. To modify a DLO administrator account: 1. On the DLO Administration Console Network menu, select Administrator Accounts. 2. Click on the account you want to modify. 3. Click Edit. 4. Modify the administrator account as necessary as instructed in To create and configure DLO administrator accounts: on page 1138.
1140
To delete an administrator account: 1. On the DLO Administration Console Network menu, select Administrator Accounts. 2. Click on the account you want to delete. 3. Click Remove. 4. When asked if you are sure you want to remove the account, click Yes to continue or No to cancel.
Connecting to DLO on a Backup Exec Media Server

In order to connect to DLO on a different Backup Exec media server, the user account needs to have full admin rights to the media server and it must also be a domain account. See Creating Administrator Accounts on page 1137 for more information on DLO administrator accounts. To connect to DLO on a Backup Exec media server: 1. On the DLO Administration Console Network menu select Connect to Media Server. 2. Select the appropriate options as follows:
Connect to media server dialog box options Item Server Description Type the name of the media server you want to connect to, or select a media server from the drop-down menu.
Login information User name Enter the user name for an account with administrator access to the media server. Enter the password for this account. Enter the domain for this account.
Password Domain
3. Click OK.
1141
The DLO Overview View

The DLO Overview view summarizes the DLO status.
Backup Exec DLO Console Overview
1142
The following table summarizes the contents of the Overview view:

Overview View Content Item Description
Desktop Computer Status Summary Last Backup Result Summarizes the completion status of the last operation performed on each computer protected by DLO. Totals are provided for the number of computers that completed the last job successfully, with errors, with warnings, or for which the last job was canceled.
With Errors - The last operation was completed, but errors were generated. With Warnings - The last operation was completed, but warnings were generated. Canceled - The job was canceled by selecting cancel or refreshed during the job. Successful - The job was successfully completed without warnings or errors, and it was not canceled or refreshed during the job.
Note Errors take precedent over warnings, so if there are both errors and warnings, the last backup result will say With Errors. See Monitoring Alerts on the DLO Administration Console on page 1200 for additional information on alerts. Pending Jobs Lists restore jobs requested by the DLO administrator that have not yet been run.
Alert Summary Active Alerts Lists alerts that have not been cleared by the DLO administrators and have not yet been removed by the alert grooming process. Alert grooming is managed from the Backup Exec Administration Console (see Configuring Alert Category Properties on page 511).
1143
Using the DLO Administration Console Overview View Content (continued) Item Server Summary Server Status Server Load Lists the status of each DLO server. Lists the number of desktops being protected by DLO and the total number of installed Desktop Agent users. These numbers may not be the same if some users are protecting multiple computers with DLO. Both online and offline users are counted. Description
1144
Setting Up DLO
Setting Up DLO
In order for DLO to back up user data, you must set up the following options in the following order: 1. Create a Profile, which determines what files are backed up, when the files are backed up, and the level of interaction the desktop user has with the Desktop Agent. For additional information, see Setting up a DLO Profile on page 1146. 2. Determine where user data will be stored on the network. DLO requires an individual User Data Folder on the network for each desktop user. If Storage Locations are used, they will automatically create Network User Data Folders for each new Desktop Agent user. If network data storage folders already exist for each user, they can be added to DLO individually or many users can be imported at one time using a list. For additional information, see Creating DLO Storage Locations on page 1165 and Managing Desktop Agent Users on page 1177. 3. Create an Automated User Assignment to automatically assign a Storage Location and Profile to new users or configure new users manually. For additional information, see Setting up Automated User Assignments on page 1168. You can set up DLO by using the Desktop and Laptop Configuration Wizard, or by setting options manually. The DLO configuration wizard provides a series of wizards that help you set up DLO in the correct order. The configuration wizard appears when the DLO Administration Console is opened unless the Always show this wizard at startup box is unchecked. The configuration wizard can also be accessed as described below. To access the Configuration Wizard: 1. On the DLO navigation bar, click Setup. 2. Under Getting Started on the task pane, select DLO Configuration using wizard. 3. If you want the Configuration Wizard to display each time the DLO Administration Console is started, select Always show this wizard at startup. Related Topics: Setting up a DLO Profile on page 1146 Creating DLO Storage Locations on page 1165
Setting Up DLO
Setting up Automated User Assignments on page 1168 Managing Desktop Agent Users on page 1177
Setting up a DLO Profile

Profiles are used to customize settings for specific groups of similar users. For example, a group of highly technical users may require the ability to modify the backup selections and schedules while less experienced users may require a fully automated backup service. In a Profile, you can set the following:

Backup file and folder selections Desktop and Network User Data Folder storage limits Backup schedules The desktop users level of interaction with the Desktop Agent Logging options Network bandwidth usage
You cannot modify settings for individual DLO users from the DLO Administration Console unless an individual user is the only user assigned to a Profile. However, you can grant permission to Desktop Agent users to modify their own settings. DLO provides two default Profiles. One is for desktop computer users and the other is for laptop computer users. Both back up the My Documents directory by default. The primary difference between the two Profiles is in the number of revisions retained in the Desktop User Data Folder.
DLO Default Profiles Profile Desktop Users Description The Desktop Users Profile uses the My Documents (Desktops) backup selection, which retains zero versions in the Desktop User Data Folder and three versions in the Network User Data Folder by default. This minimizes disk space requirements for DLO on desktop computers and assumes that DLO will be able to access backup files in the Network User Data Folder. The Laptop Users Profile uses the My Documents (Laptops) backup selection, which retains one version in the Desktop User Data Folder and three versions in the Network User Data Folder by default. This provides offline protection for all files in the laptop My Documents folder.
Laptop Users
1146
Setting Up DLO
To create a new Profile: 1. On the DLO navigation bar, click Setup. 2. In the Settings pane, click Profiles. 3. Under Profile Tasks in the task pane, click New Profile. 4. From the General tab in the New Profile dialog box, select the appropriate options as follows.
General Profile Properties Item Profile Name Description Type the name of the new Profile that you want to create. The Profile name cannot contain any of the following characters: \@#$%^&*()=+|/{}[] Type a description for the Profile. Clear this check box to disable the Profile. Profiles are enabled by default.
Description Enable Profile
User Bandwidth Settings Limit bandwidth (KB/sec) Limiting the bandwidth for DLO data transfer is a means to manage the trade-off between backup speed vs. the impact of backups on the local machine, network, and server. The default limit is meant to be a conservative setting to minimize the impact of backups, but many factors come into play, such as network speed, connection type, the amount of data backed up and the total number of machines backing up to DLO. If machine performance is not impacted, but DLO data transfer is slow, a higher bandwidth setting may be more suitable. If machine performance is noticeably impacted during backups, a lower value will reduce the impact of backups on machine performance, but backups will take longer to complete. Select Limit bandwidth (KB/sec) and enter a specific maximum bandwidth setting to throttle the rate at which data is sent to the Network User Data Folder. Data transfer is only limited when data is written to the Network User Data Folder, not when it is written to the Desktop User Data Folder.
1147
Setting Up DLO General Profile Properties (continued) Item Description
Yield bandwidth Select this to enable DLO to reduce data transfer over the network when to other programs other applications on the desktop computer are transferring data. DLO automatically resumes normal data transfer rates when other applications are not using this resource. Note Selecting this option can improve system performance when other network-intensive applications are running at the same time. Data transfer is only limited when data is written to the Network User Data Folder, not when it is written to the Desktop User Data Folder. Storage Limits Limit network Select to limit the disk space available to store DLO backup files and type user data folder to the amount of space you want to use for storage. (MB) Enable desktop user data folder Check to enable the use of the Desktop User Data Folder. When Enable desktop user data folder is checked, files are copied to the Desktop User Data Folder first, and then they are copied to the Network User Data Folder from the Desktop User Data Folder. This is true even when DLO is configured to keep zero revisions in the Desktop User Data Folder. When Enable desktop user data folder is unchecked, files are copied straight to the Network User Data Folder from the original location. Advantages to enabling the Desktop User Data Folder:
Offline protection is provided because revisions can be stored locally as well as on the network. Because files are more quickly saved to the local computer than to the network, the time a file is held open for backup is reduced. If local revisions are not desired, this option will prevent backup files from being stored in the Desktop User Data Folder. No revisions are saved in the Desktop User Data Folder even if backup selections specify that a certain number of revisions should be stored locally. Works well for desktop users with very limited disk space.
Advantages to disabling the Desktop User Data Folder:
Note The synchronization process uses the Desktop User Data Folder for file storage and conflict detection. For this reason, the Desktop User Data Folder may contain files that support synchronization, even though Enable desktop user data folder has not been selected.
1148
Setting Up DLO General Profile Properties (continued) Item Description
Limit desktop user Select to limit the disk space available to store DLO backup files and type data folder to the amount of space you want to use for storage. Once selected, you will be able to choose from the following options: A percentage of the total disk space (%) Select this option and enter a percentage to limit the amount of disk space used for storing backup files in the Desktop User Data Folder to a percentage of the local drive. A size (MB) Select this option and enter a size in MB to limit the Desktop User Data Folder to a specific maximum size. Note While limiting available disk space for the Desktop User Data Folder can prevent overloading of the desktop hard drive, backups can fail to run if the Desktop User Data Folder space limit is reached.
5. From the Backup Selections tab, check the backup selections that you want to apply to users of this Profile. You can add, modify, and delete backup selections for a Profile from this dialog. When a new backup selection is created, it is available for selection in all Profiles. Changes made to a backup selection in one Profile will impact all other Profiles that use the backup selection. Similarly, when a backup selection is deleted, the change impacts all Profiles that use the backup selection. For more information, see Managing Backup Selections on page 1155.
1149
Setting Up DLO
6. From the User Settings tab, select the appropriate options as follows:
Profile User Settings Dialog Box Item Desktop Agent display settings Description Select one of the following options to determine the desktop users level of interaction with the Desktop Agent:
Display the complete interface. Select this option to enable desktop users to access all Desktop Agent options. Display only the status. Select this option to enable desktop users to view the status of backup jobs. With this option, desktop users cannot change settings for the Desktop Agent or access any options other than the status. Desktop users can right click the system tray icon to open the status view or exit the program.
Display only the system tray icon. Select this option to display the Desktop Agent icon in the system tray in the lower right corner of the screen. Desktop users can right click on the system tray icon to exit the program.
Do not display anything. Select this option to run the Desktop Agent in the background. The desktop user cannot view the Desktop Agent.
Allow Users to
Select the options below to enable desktop users to configure the following features of the Desktop Agent When selected, users in this Profile will be able to disable the Desktop Agent from the tray icon. They will also have the ability to re-enable the Desktop Agent once it has been disabled. When selected, users in this Profile will be able to restore their backed up files. For more information, see Restoring Files Using the Desktop Agent on page 1264.
Disable Desktop Agent
Restore data
Synchronize files
When selected, users in this Profile will be able to synchronize data across all of their computers that run the Desktop Agent. For more information, see Synchronizing Desktop User Data on page 1254.
1150
Setting Up DLO Profile User Settings Dialog Box (continued) Item Change encryption settings Description When selected, users in this Profile will be able to turn backup file encryption on or off. For more information, see Backup Selection Options on page 1245. Modify backup selections For more information, see Modifying Backup Selections in the Standard View on page 1239 or Modifying Backup Selections in the Advanced View on page 1245. Profile backup selections are backup selections that were created by the DLO administrator and included in the Desktop Agent users Profile. For more information, see Modifying Backup Selections in the Advanced View on page 1245. When selected, users in this Profile will be able to limit the amount of disk space that can be used to store backup files in the Desktop User Data Folder. For more information, see Setting Customized Options on page 1252. Modify backup schedule When selected, users in this Profile will be able to modify the schedule on which their files are backed up. For more information, see Changing Backup Job Schedule Options on page 1250. Suppress error messages from users desktop When selected, error messages generated by the Desktop Agent on computers using this Profile will not be displayed in the DLO Administration Console. This will minimize the number of times the Desktop Agent accesses the DLO database, reducing the load on the DLO server.
Modify Profile backup selections
Customize local disk quota
1151
Setting Up DLO
7. From the Schedule tab, select the appropriate options as follows:

Profile Schedule Dialog Box Item Run backups Whenever a file changes Select this option to back up files whenever they change. On NTFS drives, backups will occur automatically whenever a file changes. For FAT drives, you must enter a backup interval in the Back up changed files every field. According to a schedule Select this option to back up files according to a customized schedule. Click Edit schedule to configure the backup schedule. The backup schedule is configured in step 8. When initiated by the user Log on/off options Automatically back up when logging on Automatically back up when logging off Select this to begin a backup after the desktop user logs on to the computer. Select this to begin a backup when the desktop user logs off the computer. Select this option to enable desktop users to determine when to back up their files. Description
8. If you selected Edit schedule in the previous step, select the appropriate options as follows, and then click OK:
Backup Schedule Dialog Box Items Run on these days Frequency Run once at Select this option to run a single backup on the days you selected at the time specified. Select this option to run backups at the specified time interval on the days you selected. Description Select the days on which you want to back up files.
Run every
1152
Setting Up DLO Backup Schedule Dialog Box (continued) Items From Description If you selected Run every, select the beginning of the time interval over which you want backups to begin. If you selected Run every, select the end of the time interval over which you want backups to begin. Note This field specifies the end of the time period within which backups will begin. If a backup is in progress at this time, it will continue to run to completion. Start backup jobs over a Select this option to stagger start times for backup jobs. Rather period of than starting all backup jobs at exactly the time indicated, DLO will distribute the start times over the specified interval, better distributing the demands on the server and network.
Until
9. From the Options tab, select the appropriate options as follows: Note Events such as file copies, file grooms, errors and warnings are logged by DLO and can be viewed as discussed in Monitoring Alerts on the DLO Administration Console on page 1200.
Additional Profile Options Item Log file maintenance Keep log files for a minimum of (days) Specify the minimum number of days to keep log files. Log files will not be deleted until they are at least as old as specified. Note Log files will not be deleted until their combined size exceeds the setting for the combined size of all log files, which is discussed below. After minimum number Enter the maximum combined size of all log files to be retained of days, delete oldest log before the oldest log files are deleted. files when combined size Note You may have more than the specified number of MB of log exceeds (MB) files stored if none of the log files is as old as specified in the keep log files for a minimum of (days) setting. Logging options Log groom messages Check to create logs for grooming operations. Description
1153
Setting Up DLO Additional Profile Options (continued) Item Log information messages for backup Log warning messages Mail options Enable incremental backups of Outlook PST files Check to enable incremental backups of Microsoft Outlook Personal Folder (PST) files. Incremental backups must be enabled to allow PST files to be backed up while they are open. If this option is not checked, PST files that are configured in Outlook will be fully backed up each time the PST file is saved, which generally occurs when Outlook is closed. When Outlook PST files are backed up incrementally, only one revision is maintained regardless of the number of revisions set in the backup selection. Note DLO is unable to perform incremental backups of Outlook PST files unless Outlook is your default mail application. When you restore Microsoft Outlook PST files, the restored PST file will differ from the original PST file as explained in Restoring Microsoft Outlook Personal Folder Files on page 1268. Note Synchronized files cannot be backed up incrementally. For additional information, see Backing up Outlook PST files on page 1247. Description Check to create logs for all backup operations.
Check to create logs for all operations that generate warnings.
10. When the Profile configuration is complete, click OK. Related Topics: Modifying Desktop Agent Settings on page 1249 Monitoring Alerts on the DLO Administration Console on page 1200
1154
Setting Up DLO
Modifying a Profile
Profiles can be modified as required to meet the changing needs of user groups. Note Modifications to a Profile will cause users of that Profile to cancel jobs, load settings, restart backup engines and scan their backup selection tree. To modify a Profile: 1. On the DLO navigation bar, click Setup. 2. Click Profiles in the Settings pane. 3. In the Results pane, select the Profile you want to modify. 4. Under General Tasks in the task pane, click Properties. 5. Modify the Profile properties as desired. For detailed information on available Profile properties, reference the process for creating a new Profile, beginning with step 4 on page 1147. 6. Click OK.
Managing Backup Selections

Backup selections specify which files and folders you want to back up on desktops. You define backup selections within Profiles. If you have provided users with full access to the Desktop Agent, they can modify the backup selections using the Desktop Agent. The following topics are covered in this section:

Managing Revisions on page 1156 Adding a Backup Selection on page 1157 File Grooming on page 1164 Using DLO Macros in Backup Selections on page 1162 Modifying a Backup Selection on page 1163 Deleting Backup Selections on page 1164
1155
Setting Up DLO
Managing Revisions
Revisions are versions of a file at a specific point in time and they are configured within backup selections. When a file is changed and backed up, DLO stores a new revision. DLO will store and maintain a specific number of revisions for all files in a backup selection. Because backup selections are configured separately, the number of revisions retained in each backup selection can vary. When the number of revisions is exceeded, DLO removes the oldest revision, maintaining only the specified number of revisions in the Desktop and Network User Data Folders. You can limit the number of revisions retained in a given period of time. If you are working on a document and backing it up frequently, all of your revisions could potentially be just a few minutes apart. By specifying that you want to retain only two revisions every 24 hours, at least 120 minutes apart, you can retain older revisions for a longer period of time. While some intermediate versions will not be retained, it does support situations in which returning to an older revision is needed. Another consideration in determining the number of revisions to retain is the amount of storage space required to store the data. The amount of space required for backups can be estimated by multiplying the number of revisions retained by the amount of data protected. Example If you are have 10 MB disk space consistent retaining three revisions of each file and of data to back up, approximately 30 MB of will be required if file sizes remain between revisions.
Although compression can improve the space utilization, it varies significantly with file type and other factors. Typical compression ratios are approximately 2:1, so in the previous example, the maximum disk space usage might be reduced to approximately 15 MB. Caution Symantec strongly recommends that you consider disk space when choosing backup selections for desktops and laptops. A large number of local copies may cause the Desktop Agent user's computer to run out of disk space. For example, you may want to avoid selecting entire drives for backup or synchronization.
1156
Setting Up DLO
Adding a Backup Selection

When a new backup selection is created for a Profile, that Profile backup selection is available for selection in all other Profiles. To add a backup selection: 1. On the DLO navigation bar, click Setup. 2. In the Settings pane, clickProfiles. 3. In the Results pane, select the Profile for which you want to add a backup selection. 4. Under General Tasks in the task pane, click Properties. 5. From the Backup Selections tab in the Profile Properties dialog box, click Add. A dialog box explains that if you customize NTFS permissions or directory attributes such as compression or encryption for backed up files or folders, these settings will not be backed up. You must reapply these settings after restoring the files. If you use a password for a Microsoft Outlook PST file, you must reset the password after restoring a PST file. 6. Click OK to indicate that you understand this message and to open the Backup Selection dialog.
Backup Selection Dialog Box
1157
Setting Up DLO
7. From the General tab in the Backup Selection dialog box, select the appropriate options as follows:
Backup Selection General Dialog Box Item Name Description Description Type a descriptive name for the backup selection. Type a clear description of the backup selection. This description may include, for example, the folder selected, the group of users it was created for, or the purpose for creating the backup selection.
Folder to back up Type a folder name Select this option to add a specific folder to the backup selection. Type the path to the folder, including the folder name. For example, to add a folder named MyData on drive C, type C:\MyData. Note Once a Backup Selection is created, the folder cannot be modified. Note See Using DLO Macros in Backup Selections on page 1162 for information on using macros to define the folders backed up by a backup selection. Select a pre-defined folder Select this option to choose a pre-defined folder from the list provided. Note See Using DLO Macros in Backup Selections on page 1162 for information on the macros used to define the pre-defined folders. Include subfolders Select this option to also back up all subfolders in the specified directory. This option is selected by default.
8. From the Include/Exclude tab, select the appropriate options as follows:

Backup Selection Include/Exclude Dialog Box Item Include all file types Description Select this option to include all file types in this backup selection.
Include and exclude only Select this option to include or exclude only specific files or file the items listed below types.
1158
Setting Up DLO
9. To add a filter to the Include/Exclude list, verify that you selected Include and exclude only the items listed below in step 8, and click Add Include or Add Exclude. 10. If you selected Add Exclude, you will be notified that all previously backed up files matching this exclude will be deleted from this backup selection. Click Yes to continue or No to cancel. 11. Select the appropriate options as follows:
Add Include Filter and Add Exclude Filter Dialog Box Options Item Add file name extensions Description Select this option to add common file types to your include or exclude list. To select multiple file types, click one item and press <Ctrl> or <Shift> while clicking the other items. Select this option to add a custom file or file type to your include or exclude list. Specify the filter options as described below. Select Files to apply this filter to files or Folders to apply this filter to folders. Type the name of the file or the folder, or a wildcard description of the file or folder that you want to include or exclude from backup selections. Type a description of the custom filter.
Add a custom filter
Apply to
Filter
Description
12. Click OK. 13. From the Revision Control tab, select the appropriate options for both the Desktop and Network User Data Folders:
Backup Selection Revision Control Dialog Box Item Description
Specify the number of revisions to keep in the Desktop and Network User Data Folders Desktop User Data Folder Type the number of revisions to keep in the Desktop User Data Folder for each file in the backup selection. Note When Outlook PST files are backed up incrementally, only one revision is maintained regardless of the number of revisions set in the backup selection. Appendix L, Backup Exec Desktop and Laptop Option 1159
Setting Up DLO Backup Selection Revision Control Dialog Box (continued) Item Limit to Description Check this option to limit the number of revisions retained in a given amount of time, and specify the following:

Revisions. Select the number of versions to retain. Within the last x hours. Select the time period during which you want to retain the versions. At least x minutes apart. Select the minimum amount of time that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created that exceeds one of these limits. Network User Data Folder Limit to Select the number of revisions to keep in the Network User Data Folder for each file in the backup selection. Check this option to limit the number of revisions retained in a given amount of time, and specify the following:

Revisions. Select the number of versions to retain. Within the last x hours. Select the time period during which you want to retain the versions. At least x minutes apart. Select the minimum amount of time that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created that exceeds one of these limits.
1160
Setting Up DLO
14. From the Options tab, select the appropriate options as follows:
Backup Selection Options Item Compress the files stored in the Network User Data Folder Description Select this option to compress files in this backup selection for data transfer over the network and for storage in the Desktop and Network User Data Folders. This affects files created after this feature is activated. Previously stored files will not be compressed. Encrypt the files for transmission and storage Select this option to encrypt files for transfer and to store files from this backup selection in an encrypted format in the Network User Data Folder. This affects files transmitted and stored after this feature is activated. Previously stored files will not be encrypted. The AES (Advanced Encryption Standard) and a 128 bit key length are used. If enabled, versions are stored unencrypted in the Desktop User Data Folder, and encrypted in the Network User Data Folder. Transfer over the network is encrypted. When source files are deleted, delete the backed up files from the: Desktop User Data Folder after Indicate the number of days after which DLO will delete all file versions from the Desktop User Data Folder after the source file has been deleted from the desktop. Indicate the number of days after which DLO will delete all file versions from the Network User Data Folder after the source file has been deleted from the desktop.
Network User Data Folder after
1161
Setting Up DLO
Using DLO Macros in Backup Selections

You can type macros into the Type a folder name field of the Backup Selection dialog to automatically back up specific folders. The Type a folder name field is configured in the Backup Selection General Dialog Box as discussed on page 1158. The following macros are supported:
Folder Macros for use with Backup Selections Backup Selection Macro %LOCALFIXEDDRIVES% Folders backed up All local fixed drives. Note DLO is not designed to back up removable media. Attempting to back up a floppy disk or CDROM may result in errors. %MACHINENAME% Represents the desktop user's machine name. Example: C:\documents\%machinename% represents C:\documents\UsersMachineName. %CURRENTUSERNAME% Represents the username of the currently logged-on user. Example: If the local administrator is logged-on to the machine, C:\documents\%currentusername% represents 'C:\documents\Administrator' %CURRENTUSERPROFILE% All files and folders in the C:/Documents and Settings/current user profile directory The My Documents directory for the user who is logged on
%CURRENTUSERMYDOCS%
The following additional pre-defined folders have been added to the Backup Selection dialog:
Macros for Pre-defined Folders in the Backup Selection dialog Pre-Defined Folder Macro %CURRENTUSERMYDOCS% Folders Backed Up The My Documents directory for the user who is logged on. All local fixed drives The Favorites directory for the user who is logged on
%LOCALFIXEDDRIVES% %CURRENTUSERFAVORITES%
1162
Setting Up DLO Macros for Pre-defined Folders in the Backup Selection dialog (continued) Pre-Defined Folder Macro %CURRENTUSERPRINTHOOD% %CURRENTUSERNETHOOD% Folders Backed Up The Printers directory for the user who is logged on. The Network Locations directory for the user who is logged on. The Desktop directory for the user who is logged on. The Recent Files directory for the user who is logged on.
%CURRENTUSERDESKTOP% %CURRENTUSERRECENT%
Modifying a Backup Selection

Profile backup selections can be modified from the DLO Administration Console. Note If you edit a Profile backup selection to include a folder that is underneath an exclude, a new backup selection is created. If you then go back to using the original Profile backup selection, the new backup selection is not deleted, and it has precedence over the profile backup selection. To return to the original configuration, you must manually delete the new backup selection as explained in Deleting Backup Selections on page 1164. 1. On the DLO navigation bar, click Setup. 2. Click Profiles in the Settings pane. 3. In the results pane, click the Profile you want to modify. 4. Under General Tasks in the task pane, click Properties. 5. From the Backup Selections tab, select the backup selection you want to modify, and then click Modify. Note The Type a folder name field in the General tab is grayed out in this view. If the path in this field is longer than the display, hold the curser over the path for a moment to display the entire path. 6. Click OK to indicate that you read the message stating that modifying this backup selection will change all Profiles that are using this selection. 7. Change the backup selection as needed, and then click OK. For more information, see step 7 on page 1158.
Setting Up DLO
Deleting Backup Selections

Before you can delete a backup selection, you must be sure that it is not in use by any Profiles. When you delete a backup selection from one Profile, DLO deletes it from every Profile. When you delete a backup selection, the backup versions are deleted in the same manner as when source files are deleted. They will be groomed after the number of days specified in the backup selection. For additional information, see Backup Selection Options on page 1161. To delete a backup selection: 1. On the DLO navigation bar, click Setup. 2. Click Profiles in the Settings pane. 3. In the results pane, click the Profile that contains the backup selection you want to delete. 4. Under General Tasks in the task pane, click Properties. 5. From the Backup Selections tab, select the backup selection you want to delete. 6. Click Delete. 7. Click Yes to verify that you want to delete this backup selection, or click No to cancel.
File Grooming
The Desktop Agent grooms revisions based on backup selection settings and does this as new revisions are created. The oldest revision is deleted when a new revision is created that exceeds the limit. See step 13 on page 1159 for revision control settings. Maintenance grooming is the process of removing backups of deleted files. It occurs at most once every 24 hours. Maintenance grooming occurs during the first backup that runs after 24 hours have passed since the last maintenance grooming.
1164
Setting Up DLO
Creating DLO Storage Locations

The Desktop and Laptop Option stores each users data in two places. First, it is stored in the Desktop User Data Folder on the user's computer to provide protection and restore capabilities even when the computer is disconnected from the network. The data is then additionally stored in a Network User Data Folder, which is located on the network. This provides an additional level of protection, and enables the files to be backed up to secondary media when the server is backed up. When a user is automatically added to DLO using an Automated User Assignment, a Network User Data Folder is created in a Storage Location as specified in the Automated User Assignment. Storage Locations are simply locations on network computers where Network User Data Folders are automatically created. If network shares already exist for desktop users, they can specified as Network User Data Folders when users are manually added to DLO. If existing network shares are used as Network User Data Folders, Storage Locations are not used. DLO Storage Locations are created from the DLO Administration Console. For additional information on utilizing existing network shares, see Managing Desktop Agent Users on page 1177.
Storage Location Configuration Support

The following table summarizes supported configurations for DLO Storage Locations:
Storage Location Configuration Support Configuration All DLO Administration Server platforms Windows 2000 NAS/SAK NAS devices Local media server direct-attached Storage SAN Windows-networking accessible NAS Devices (Quantum, Network Appliance, etc.) FAT, FAT32 and NTFS partitions are supported as Storage locations, although FAT and FAT32 are not recommended. NTFS is the preferred file system for Storage Locations Supported X X X X X Not Supported
1165
Setting Up DLO Storage Location Configuration Support (continued) Configuration NetWare 3.1x, 4.x, or E-Directory Storage Locations UNIX file systems or SAMBA shares on UNIX systems Supported Not Supported X X
Things to Consider Before Creating DLO Storage Locations

A Storage Location should be used by only one media server. If you set up multiple media servers to use the same Storage Location and the Storage Location is deleted from one media server, the other media server no longer be able to access it. Storage Locations must be in a Windows Domain or Active Directory. Computers running the Desktop Agent can be outside of a Windows Domain or Active Directory, but they must authenticate with the domain or directory to access the media server or Storage Locations. You will be prompted to provide domain credentials when the Desktop Agent is launched. If your original files reside on an NTFS volume, then the Desktop User Data Folder and the Network User Data Folder should also be NTFS. If your original files are on NTFS and either the Desktop User Data Folder or Network User Data Folder are on a FAT or FAT32 volume, you may see duplicate entries in the Restore and Restore Search screens. If duplicates do appear, you can select either file to restore. Once created, Storage Locations cannot be modified, but they can be deleted if there are no users or Automated User Assignments assigned to them. You can move users to new Storage Locations. For more information, see Moving a Desktop Agent User on page 1182. Note If you receive errors when creating Storage Locations, verify that the logon account for the service named MSSQL$BKUPEXECDLO has sufficient rights to create directories and change permissions for the Storage Locations. Use the Windows Service Control Panel to change the login account for the MSSQL$BKUPEXECDLO instance. You can avoid these problems if you specify a domain account when you install Backup Exec. To create DLO Storage Locations: Note After you create Storage Locations, you cannot modify them. 1. On the DLO navigation bar, click Setup. 2. Click Storage Locations in the selection pane.
Setting Up DLO
3. Under Storage Location Tasks in the task pane, click New Storage Location. 4. Select the appropriate options as follows.
New Storage Location Dialog Box Item Computer name Description Type a computer name or browse to a computer on which to create the Storage Location. Type or browse to a location on the computer where the Storage Location will be created. Note Storage Locations should be in the same domain as the media server or in a domain that trusts the media servers domain. Storage Location name Type a name for the new Storage Location. The name cannot contain any of the following characters: \@#$%^&*()=+|/{}[] The Summary field automatically displays the location and format of Network User Data Folders that will be created for new users assigned to this Storage Location. Network User Data Folders are automatically created in the Storage Location. DLO uses the %USERDOMAIN% and %USERNAME% variables to determine the actual folder path for each user who is assigned to a Storage Location. DLO uses the users domain and user name to create a unique Network User Data Folder name for that user. If the user is logged on with credentials that do not allow access to the Storage Location, the user will be prompted to enter alternate domain credentials. The network administrator can access this folder, but cannot configure the variables.
Path
Summary
5. Click OK.
Deleting DLO Storage Locations

Before you can delete DLO Storage Locations, you must delete or reassign users and Automated User Assignments that use the Storage Location. The Storage Location associated with a user or Automated User Assignment is listed when you select Users or Automated User Assignments from the Setup view.
1167
Setting Up DLO
Note When a Storage Location is created using an existing share on a remote machine and DLO does not have full machine rights, the Storage Location cannot be deleted from the Administration Console. To remove the Storage Location, first delete the Storage Location share and then delete the Storage Location from the Administration Console. To delete Storage Locations: 1. Click Setup on the DLO navigation bar. 2. Click Storage Locations in the selection pane. 3. In the results pane, click the Storage Location you want to delete. 4. Under General Tasks in the task pane, click Delete. 5. Click Yes to delete the Storage Location or No to cancel. Related Topics: Managing Desktop Agent Users on page 1177 Modifying Existing Automated User Assignments on page 1171 Deleting Automated User Assignments on page 1173
Setting up Automated User Assignments

Automated User Assignments are instructions that are applied when the Desktop Agent is first run on a desktop. The Automated User Assignment assigns a Profile and Network User Data Folder to each user who is automatically configured by DLO. These settings can be changed from the DLO Administration Console at a later time if necessary. Note If a user is added manually to DLO, a Storage Location and Profile are selected by the DLO administrator. The Automated User Assignment will not be used. For more information, see Managing Desktop Agent Users on page 1177. You specify a domain and group for each Automated User Assignment. Because users may belong to several groups, Automated User Assignments are prioritized. When the Desktop Agent is run for the first time, the Desktop Agent users domain and group credentials are checked against those of the Automated User Assignment starting with the highest priority assignment. When a match is made, the share and Profile specified in that Automated User Assignment are assigned to the new user.
1168
Setting Up DLO
Modifying Automated User Assignments does not affect users who have already been configured. Only new users configured with the Automated User Assignment will use the new settings. You can create, reorder, and modify Automated User Assignments from the Setup view in the DLO Administration Console.
Viewing Automated User Assignments
Automated User Assignments listed in order of priority
For information on modifying Automated User Assignment priorities, see Changing the Priority of Automated User Assignments on page 1171. To create a new Automated User Assignment: 1. On the DLO navigation bar, click Setup. 2. Click Automated User Assignments in the selection pane. 3. Under Automated User Assignment Tasks in the task pane, click New user assignment.
1169
Setting Up DLO New Automated User Assignment Dialog Box

New Automated User Assignment Dialog Box Options Item User Assignment User assignment name Type a name for the Automated User Assignment. The Automated User Assignment name cannot contain the following characters: \@#$%^&*()=+|/{}[] Description
Domain and Group this user assignment will apply to Domain Select the domain to which this Automated User Assignment will apply. Select the group to which this Automated User Assignment will apply.
Group
Storage Location/Profile Storage Location Select a Storage Location to be assigned to the users in the selected domain and group. Select a Profile to be assigned to the users in the selected domain and group.
Profile
1170
Setting Up DLO
Modifying Existing Automated User Assignments

Modifying an existing Automated User Assignment affects only users added to the assignment after it has been modified. Existing Desktop Agent users are unaffected. Settings for existing Desktop Agent users can be modified from the Setup view of the DLO Administration Console. For more information see Modifying DLO Desktop Agent User Properties on page 1180. To modify an existing Automated User Assignment: 1. On the DLO navigation bar, click Setup. 2. Click Automated User Assignments in the selection pane. 3. In the results pane, select the Automated User Assignment you want to modify. 4. Under General Tasks in the task pane, select Properties. 5. Modify the Automated User Assignment properties. For more information see New Automated User Assignment Dialog Box Options on page 1170.
Changing the Priority of Automated User Assignments

When you create an Automated User Assignment, DLO assigns a priority to it so that when a user is a member of more than one domain and group, it is clear which Automated User Assignment will be used. The most recently created Automated User Assignments have the lowest priority. You can change the priority of Automated User Assignments. To change the priority of Automated User Assignments: 1. On the DLO navigation bar, click Setup. 2. Click Automated User Assignments in the selection pane. 3. In the results pane, select the Automated User Assignment for which you want to change the priority. 4. Under Automated User Assignment Tasks on the task pane, select Move priority up or Move priority down.
1171
Setting Up DLO Changing the Priority of an Automated User Assignment
Viewing Automated User Assignment Properties

To view Automated User Assignments: 1. On the DLO navigation bar, click Setup. 2. Click Automated User Assignments in the selection pane. 3. In the results pane, select an Automated User Assignment. 4. Under General Tasks in the task pane, select Properties.
1172
Setting Up DLO
Deleting Automated User Assignments

You can delete Automated User Assignments when you no longer need them. To delete an Automated User Assignment: 1. On the DLO navigation bar, click Setup. 2. Click Automated User Assignments in the selection pane. 3. Click the Automated User Assignment to be deleted. 4. In the task pane under General Tasks, click Delete. 5. Click Yes to delete the Automated User Assignment. Related Topics: Setting up Automated User Assignments on page 1168 Modifying Existing Automated User Assignments on page 1171 Changing the Priority of Automated User Assignments on page 1171 Moving a Desktop Agent User on page 1182 Modifying DLO Desktop Agent User Properties on page 1180
1173
Setting Up DLO
Configuring the Global Exclude List

From the Tools menu in the DLO Administration Console, you can set up the global exclude list. Global excludes enable you to configure the files that you want to exclude from all backups. You can exclude all files of a certain type, such as .tmp files, or a specific file, such as pagefile.sys. The files you exclude are listed on the Include/Exclude tab in the Advanced view on the Desktop Agent and on the Include/Exclude tab for a Profile's backup selection on the DLO Administration Console. Items configured for the global exclude list are not available for selection on the selection list. Caution Adding a global exclude will cause all previously backed up files matching the global exclude to be deleted. To add a Global Exclude: 1. From the Tools menu in the DLO Administration Console, select Global Excludes. 2. Click Add. 3. Read the message explaining that adding a global excludes will result in the deletion of all backup files matching the global exclude. 4. Click Yes to continue. 5. Complete the Add Global Exclude dialog as described in the following table.
1174
Setting Up DLO
6. Enter a filter, file name or folder name to be excluded from all backups. Wildcards are supported. See Using DLO Macros to Define Global Excludes below for additional information on using macros as global exclude filters.
Add Global Exclude Dialog Item Filter Description The filter determines which files or folders will be affected by the global exclude. Filters can be file names, wildcards or macros. Examples: Wildcard: *.tmp File name: pagefile.sys Macro: %WINDIR% Note When using wildcards you must use the * wildcard. For example, *.tmp will return all results with the .tmp extension while .tmp will return only files explicitly named .tmp. Description Apply to Type a description of the global exclude. Indicate whether this global exclude should apply to files, folders, or both files and folders.
7. Enter a description for the global exclude. 8. Specify if the global exclude should apply to files, folders or both files and folders. 9. Click OK to create the global exclude. To delete a Global Exclude: 1. From the Tools menu in the DLO Administration Console, select Global Excludes. 2. Click on the global exclude you want to delete. 3. Click Delete. 4. Click Yes to delete the global exclude.
1175
Setting Up DLO
Using DLO Macros to Define Global Excludes

The following macros are typically used for excluding files using the global exclude option, but can also be used in backup selections.
Global Exclude Macros Macro %TEMP% %WINDIR% Folder The temp directory for the current logged on user The Windows directory. Example: C:\Windows or C:\Winnt %WEBTEMP% %RECYCLED% %SYSTEM% The web cache for the current logged on user Recycle bins The Windows system directory. Example: C:\Windows\system or C:\Winnt\system
1176
Setting Up DLO
Managing Desktop Agent Users

The DLO Administrator manages Desktop Agent users from the DLO Administration Console. From this interface, users or groups of users can be manually added to DLO, enabled or disabled, moved to a new network share, or assigned a different Profile. Desktop Agent users are added to DLO either automatically using Automated User Assignments, or manually from the DLO Administration Console. Related Topics: Setting up Automated User Assignments on page 1168 Adding a Single Desktop Agent User to DLO on page 1178 Importing Multiple Desktop Users Who Have Existing Storage Locations on page 1179 Viewing DLO Users on page 1180 Modifying DLO Desktop Agent User Properties on page 1180 Disabling or Enabling DLO Access For a Desktop User on page 1181 Removing a User from DLO on page 1181 Moving a Desktop Agent User on page 1182
Creating a New Network User Data Folder

If network shares already exist for desktop user backups, they can be added to DLO as Network User Data Folders, or new shares can be created and added to DLO for this purpose. To create or use an existing network share as a Network User Data Folder, the folder must have the appropriate security attributes according to the organizations needs. For example, to specify which users can access the folder. To create a new Network User Data Folder and set security attributes: 1. Create a network share on the computer where backup files will be stored. 2. Right-click the share you created in step 1, and then select Properties. 3. Click Permissions. 4. Select the following permissions for user Everyone: Full Control, Change, Read 5. Click OK. 6. Select Security.
Setting Up DLO
7. Clear the Allow inheritable permission from parent to propagate to this object check box. 8. Add Administrator and Everyone and give them full control permissions. 9. Create a data folder for each user who will use this Storage Location. 10. Right-click the data folder you created in step 9, select Properties and then select Security. 11. Clear the Allow inheritable permission from parent to propagate to this object check box. 12. Add Administrator and the user who will be assigned to the user data folder to the share permission list. 13. Set full permission for Administrator and the user.
Adding a Single Desktop Agent User to DLO

Desktop users can be configured manually rather than with Automated User Assignments (see Setting up Automated User Assignments on page 1168). This allows the use of existing network folders that are dedicated to storing backup data for specific users. These network folders become the DLO Network User Data Folders. Storage Locations are not required when a user is added manually to DLO. The purpose of a Storage Location is to automatically create User Data Folders. When a single Desktop Agent user is added to DLO, the User Data Folders are added manually so Storage Locations are not required, but they can be used if it is desirable to place the Network User Data Folder in this location. After adding a desktop user manually, the settings that you assign (the User Data Folder and the Profile) are applied when the desktop user runs the Desktop Agent the first time. To add a single DLO user: 1. On the DLO navigation bar, click Setup. 2. Click Users in the selection pane. 3. Under User Tasks in the task pane, click New user.
1178
Setting Up DLO
4. Enter information in the fields as described in the following table:

New User Properties Item Enable User Description Select this option to enable this user to use the Desktop Agent, or clear it to prevent the user from using the Desktop Agent. Browse to the username or type it in the form DomainName\UserName. Select the Profile that you want to assign to this user. Do one of the following: Select this option and type the path or browse to an existing Network User Data Folder where this desktop users backup files will be stored. This must be an existing folder, and the security attributes must be set for the folder according to your organizations needs. For example, determine which users can access the folder. Note A Storage Location is not required when an existing network share is used as the Network User Data Folder. Storage Location Select this option to choose an existing Storage Location. The Network User Data Folder for the new user will be placed in this Storage Location.
User
Profile User Data Folder Network User Data Folder
Importing Multiple Desktop Users Who Have Existing Storage Locations

If you want to configure multiple users who already have an existing network Storage Location, you can import a list of users from a comma separated values (CSV) file. The file must be in the following format and have the following information for each user: user name, domain, Profile, User Data Folder Example JSmith,enterprise,Default,\\Server1\Userdata\jsmith To import multiple DLO users from a file: 1. On the DLO navigation bar, click Setup. 2. Click Users in the selection pane. 3. Under User Tasks in the task pane, click Import users using wizard.
Setting Up DLO
4. Follow the wizard prompts.
Viewing DLO Users

1. On the DLO navigation bar, click Setup. 2. Click Users in the selection pane to list users in the results pane.
Modifying DLO Desktop Agent User Properties

1. On the DLO navigation bar, click Setup. 2. Click Users in the selection pane. Users are listed in the results pane. 3. Select the user you want to modify. 4. Under General Tasks in the task pane, select Properties.
User Properties dialog box
5. Modify the user properties as described in the following table:

User Properties Item Enable User Description Select this option to enable this user to use the Desktop Agent, or clear it to prevent the user from using the Desktop Agent. The name of the user. This field cannot be edited.
User
1180
Setting Up DLO User Properties (continued) Item Profile Network User Data Folder Description Select a Profile to apply to this user. This is the location where the users backup files are to be stored. It cannot be modified. To move a user to a new location, see Moving a Desktop Agent User on page 1182.
Disabling or Enabling DLO Access For a Desktop User

This option prevents a user from backing up the desktop via the Desktop Agent. 1. On the DLO navigation bar, click Setup. 2. Click Users in the selection pane. Users are listed in the results pane. 3. Select the user you want to modify. 4. Under General Tasks in the task pane, select Properties. 5. Clear the Enable user checkbox to prevent the desktop user from backing up the desktop, or select the check box to enable the desktop user to back up the desktop.
Removing a User from DLO

If you want to permanently remove a user from the DLO database, you can delete the users entry from DLO. Before deleting the user from the DLO Administration Console, you should uninstall the Desktop Agent from the users desktop. Otherwise, the user will automatically be re-added if the Desktop Agent is run by the user and a matching user assignment exists in DLO. If you cannot uninstall the Desktop Agent from the users computer, disable the user (see Disabling or Enabling DLO Access For a Desktop User on page 1181). To delete a user from the DLO database: 1. On the DLO navigation bar, click Setup. 2. Click Users in the selection pane. Users are listed in the results pane. 3. Click the user you want to delete.
1181
Setting Up DLO
4. Under General Tasks in the task pane, click Delete. 5. To delete the data stored in the User Data Folder, check Delete data stored in the user data folder. When the Delete data stored... option is selected, backup data is deleted from the Network User Data Folder, but not from the Desktop User Data Folder. When the Desktop Agent is uninstalled from the desktop computer, an option is provided to delete the Desktop User Data Folder. 6. Click Yes to delete the user, or click No to cancel. Note If you delete a user from the DLO Administration Console without first uninstalling the Desktop Agent from the users desktop, the Desktop Agent on that user's computers will close automatically.
Moving a Desktop Agent User

When a Desktop Agent user is moved to a new Network User Data Folder, the contents of the original Network User Data Folder are moved to a new directory. The new directory can be an existing Storage Location or another directory on the network. After the data is successfully moved, the data in the old Network User Data Folder is deleted. Subsequent backups will be stored in the new location. To move a Desktop Agent user to a new Network User Data Folder: 1. On the DLO navigation bar, click Setup. 2. Select Users in the selection pane. 3. Select the user to be moved. 4. Under User Tasks in the task pane, click Move Network User Data Folder.
1182
Setting Up DLO Move User
5. Enter information in the appropriate fields as described in the following table:

Move User Item User From Destination Move the user data folder to an existing Storage Location Select this option to choose an existing Storage Location from the drop down list. Description Lists the domain and user name of the currently logged on user. Lists the current Network User Data Folder location.
Move the contents of the Select this option to specify a new Storage Location. Type the user data folder to an path in the box provided, or click Browse and navigate to the alternative location new location.
6. Click Start.
1183
Setting Up DLO
Managing Desktop Computers

Desktop computers can be easily enabled, disabled or deleted using the DLO Administration Console. In addition, an immediate backup can be run on one or more selected computers.
Enabling or Disabling a Desktop Computer

When a computer is disabled, the Desktop Agent will still be installed on the desktop computer. The Desktop Agent can be used to restore files and view history, but backups are disabled and the user cannot modify Desktop Agent settings. To enable or disable a desktop computer: 1. On the DLO navigation bar, click Setup. 2. Click Computers in the selection pane. Computers running the Desktop Agent are listed in the results pane. 3. Select one or more computers to be enabled or disabled. 4. Right click on the selected computers and click Enable to enable the Desktop Agent to run on the selected computers, or click Disable to prevent the Desktop Agent from running on the selected computers.
Deleting a Desktop Computer from DLO

Deleting a desktop computer from DLO removes the computer from the DLO database and deletes the backed up files. This feature is most commonly used for a desktop computer that is no longer in use. Deleting a computer does not disable the Desktop Agent software. If subsequent backups are performed by the Desktop Agent, the computer entry will be added back to DLO. To prevent further backups from the computer, disable the computer rather than deleting it. To delete a desktop computer from DLO: 1. On the DLO navigation bar, click Setup. 2. Click Computers in the selection pane. Computers running the Desktop Agent are listed in the results pane. 3. Select one or more computers to be deleted. 4. Under General Tasks in the task pane, click Delete.
Setting Up DLO
5. When asked if you want to delete each selected computer and all backup files, click Yes to continue or No to cancel.
Running an Immediate Backup on a Desktop Computer

The DLO Administration Console can be used to run an immediate backup on one or more desktop computers. This allows the administrator to force a backup of a computer running in manual or scheduled mode. To run an immediate backup on a desktop computer: 1. On the DLO navigation bar, click Setup. 2. Click Computers in the selection pane. Computers running the Desktop Agent are listed in the results pane. 3. Select one or more computers on which to run an immediate backup. 4. Under General Tasks in the task pane, click Run backup now.
1185
Restoring Files and Folders from the DLO Administration Console

The administrator can restore files and folders to a desktop computer from the DLO Administration Console. To restore files and folders from the DLO Administration Console: 1. On the DLO navigation bar, click Restore.
Restore view
2. In the Computer pane, click the desktop from which the data to be restored originated. 3. In the Backup Folder pane tree view, highlight the folder containing the files you want to restore. 4. To restore the entire folder, check the folder in the Backup Folder pane. 5. To restore specific files, check the files in the File Version pane.
1186
Note A red x in a checkbox indicates a deleted file. 6. If multiple versions exist for a file, select the radio button for the file version you want to restore. In some cases, the Restore Search view may contain duplicate entries for the same file. If this occurs, you can select either file to restore and receive the same outcome. Note When a desktop user deletes an original file, the backup files are retained until they are deleted by the file grooming process. If an original file has been deleted, but backup files are still available, the icon for the file in the restore view will have a small red x to indicate the deletion of the original file. See File Grooming on page 1164 for additional information. 7. Under Restore Tasks in the task pane, click Restore files to open the Restore dialog.
Restore Dialog Box
1187
8. Select the appropriate options as follows, and then click OK:

Restore Dialog Box Item Restore destination Restore to desktop computer Select this option to restore the selected files or folders to the desktop from which they were originally backed up. Note When files or folders are restored to the original desktop computer, the job is submitted to the Desktop Agent and is run when the Desktop Agent connects to the media server. This may be immediately if the desktop computer is currently on the network, or the job may be pending for some time if the desktop computer is not connected to the network. Restore to original folder Select this option to restore the file or folder to its original location. Select this option to restore the file or folder to a different location on the same desktop. Click on Browse to browse to the folder where you would like to restore the file. Redirect the restore to a folder on an alternate computer Select this option to restore the selected items to a network or local drive on a computer other than the one from which they were originally backed up. Note When files or folders are restored to a folder on an alternate computer, the restore job is processed immediately from the Network User Data Folder by DLO. The job is not queued to the Desktop Agent. Preserve folder structure Check this box to restore the data with its original directory structure intact. If you clear this option, all data (including the data in subdirectories) is restored to a single folder in the path you specify. Description
Redirect the restore to an alternate folder
1188
Restoring Files and Folders from the DLO Administration Console Restore Dialog Box (continued) Item Restore Options If file already exists: Select Do not overwrite to cancel the restoration of files that already exist in the destination folder. Select Prompt to be prompted before overwriting the file if it already exists in the destination folder. Select Overwrite to overwrite the file without prompting if it already exists in the destination folder. Description
9. Click OK. Note If you customize NTFS permissions or directory attributes such as compression or encryption for files or folders, you must reapply these settings after restoration. If you use a password for your PST file, you must reset the password after restoring your PST file. 10. In the Restore Summary dialog box, review the selected restore settings, and then click Print to print a copy of the restore summery, or Restore to continue with the restore. 11. Click OK when the restore job completes.
Searching for Desktop Files to Restore

To search for desktop files and folders to restore: 1. On the DLO navigation bar, click Restore. 2. In the Computer pane, click the desktop on which you would like to search for files to restore. 3. Under Restore Tasks in the task pane, click Search for files to restore.
1189
Restoring Files and Folders from the DLO Administration Console Search Dialog Box

Search Dialog Box Options Item Search for file names with this text in the file name Description Type all or part of the file name or folder you want to find. Wildcard entries are accepted, for example *proj.doc. Select this option to search for files that were modified during a specific time frame, and then select the time frame. Select this option to search for files modified on the current calendar day. Select this option to search for files modified in the last calendar week. Select this option to enter dates to search a range of days.
Modified
Today
Within the past week
Between
1190
Restoring Files and Folders from the DLO Administration Console Search Dialog Box Options (continued) Item Of the following type Description Select this check box to select a file type from the list provided. Select this check box and then enter information as follows:
Of the following size
Select from equal to, at least, or at most in the first drop-down menu. Type a file size. Select KB, MB, or GB.
Deleting a Desktop Computer from DLO

When a desktop is deleted from DLO, the backed up data from that computer is deleted from the users Network User Data Folder. To delete a desktop and its backup data: 1. On the DLO navigation bar, click Restore. 2. In the Computer pane, click the desktop you want to delete. 3. Under General Tasks in the task pane, click Delete. 4. When prompted to delete this desktop and all its backup files, click Yes to continue or click No to cancel the operation. Related Topics: Restoring Files Using the Desktop Agent on page 1264
1191
Monitoring DLO Job Histories

Use the History view on the DLO Administration Console to view information about the status of Desktop Agent jobs. These jobs include backup, restore, synchronization, and move user jobs. History logs are generated by each desktop running the Desktop Agent and are viewed in either the DLO Administration Console or the Desktop Agent Console. You can filter history logs so that old or less important messages are not displayed, or you can choose to view only information about backup or restore jobs.
Viewing the DLO Job History

By default, the history logs are updated when a job runs and an hour has passed since the last update. However, if the job's status changes, the history log is updated immediately to reflect the new status. To display the History view in the DLO Administration Console:
On the DLO navigation bar, click History.

DLO Administration Console History View
1192
The History view includes a computer history and a job history for each desktop that is displayed. The Computer History pane displays all desktops that are backed up with the Desktop Agent and provides the following summary information:
Computer History pane Item User Computer Last Backup Result Description The user name of the desktop user who generated this message. The name of the desktop that generated this message. The outcome of a completed backup, for example, Success, Warnings, Failed, Canceled. For descriptions of possible backup outcomes, see Desktop Computer Status Summary on page 1143. Profile The Profile to which the desktop user who generated the message belongs. For more information on Profiles, see Setting up a DLO Profile on page 1146 Backup Mode Describes the backup mode specified in the Profile. Backup modes include:

Continuous. The backup occurs whenever a file changes. Scheduled. The backup occurs according to a schedule. Manual. The backup occurs when initiated by the desktop user.
Desktop Data Folder Size Network Data Folder Size Network Data Folder Path
The current size of the Desktop User Data Folder.
The current size of the Network User Data Folder.
The location of the Network User Data Folder.
1193
The Job History pane displays the following information:

Job History pane Item Start Time End Time Operation Status Description The time the job was started. The time the job ended. The operation performed in this job, such as backup or restore. The current status of the job, such as active, completed, completed with errors, completed with warnings, canceled, or failed. The number of files copied during the job. The total bytes of data copied during the job. The number of errors, if any, that were generated during the job.
Files Transferred Size Transferred Errors
Setting Job History View Filters

The job history view can be filtered to show only the type of jobs you wish to view. You can filter jobs by type, alerts received during the job, or by the time period in which the job was run. To set job history view filters: 1. On the DLO navigation bar, click History. 2. Click the desktop for which you want to view the history.
1194
3. Determine the type of jobs to view by selecting one of the following filters under Job History View Filters on the task pane:
Type of Jobs Viewed in the History View Item List all jobs Description Lists history logs for all jobs that have run on the selected desktop. These may include backup, synchronization, restore, or move user jobs. Lists history logs only for backup jobs that have run on the selected desktop. Lists history logs only for restore jobs that have run on the selected desktop.
List backup jobs only
List restore jobs only
4. Filter job history logs based on alerts received by selecting one or more of the following:
Selections to Filter Job Histories Based on Alerts Received Item Show successful jobs Description Lists history logs for all successful jobs on the selected desktop.
Show jobs with warnings Lists history logs for all jobs that generated warnings on the selected desktop. Show jobs with errors Lists history logs for all jobs that generated errors on the selected desktop. Lists history logs for all jobs that were canceled on the selected desktop.
Show canceled jobs
1195
5. Select a time frame for filters to be viewed by selecting one of the following:
Time Frame for Job Histories viewed Item Show last 24 hours Description Lists history logs that have been generated in the last 24 hours, and that meet all other filtering criteria. Lists history logs that have been generated in the last 7 days, and that meet all other filtering criteria. Lists all history logs that have been generated in the last 24 hours, and that meet all other filtering criteria.
Show last 7 days
Show all
To view a history log in the DLO Administration Console: 1. On the DLO navigation bar, click History. Jobs that meet the current filtering criteria for the History view are displayed in the Job History window. For additional information on filtering, see To set job history view filters: on page 1194. 2. In the History pane, select the computer for which you want to view a history log. 3. Click on the log you want to view in the Job History pane. 4. Under General Tasks on the task pane, click View history log file to display the log file viewer with all log messages for this job.
1196
Monitoring DLO Job Histories Log File Viewer
5. In the Show box, select one of the following:

Log File Viewer Filtering Options Item Search for log entries in All log files Current log file Select this option to show all log entries in the log file viewer. Select this option to search only those log entries in the current log file. Check the With Timestamp box to search only those log entries within a specified time period. The options include: Today - Show only log files that were created today. Within the last week - Show all log files created in the last week. Between dates - Show all log files created between the dates entered. Description
With timestamp
1197
Monitoring DLO Job Histories Log File Viewer Filtering Options (continued) Item With Type Description Check the With Type checkbox to show only logs of the indicated type. You may select one of the following types:

Backup Restore Move User Maintenance Error Warning
With Filename like
Check the With Filename like checkbox to enter a filename, or filename type. Wildcard entries are supported. Example: *gold.doc Note When using wildcards you must use the * wildcard. For example, *.tmp will return all results with the .tmp extension while .tmp will return only files explicitly named .tmp.
Filter All entries except maintenance Failed entries only Warning entries only Maintenance entries only Select this option to display all entries other than those for maintenance operations such as the grooming of deleted files. Select this option to display only entries for failed operations. Select this option to display only for entries with warnings. Select this option to show only maintenance operations such as the grooming of deleted files.
Local data folder entries Select this option to display all log entries for Desktop User Data only Folders. Failed local data folder entries only Network data folder entries only Select this option to only display entries for failed Desktop User Data Folder operations. Select this option to display all log entries for Network User Data Folders.
1198
Monitoring DLO Job Histories Log File Viewer Filtering Options (continued) Item Failed network data folder entries only Debug entries only Description Select this option to only display entries for failed Network User Data Folder operations. Select this option to display debug entries only. Debug entries are used for troubleshooting.
6. Click Close to close the Log File Viewer.
1199
Monitoring Alerts on the DLO Administration Console

Alerts help the DLO administrator understand the current condition of DLO jobs by displaying information on jobs that did not run as expected. When a task such as a backup or restore does not run as expected, an alert is generated. Alerts contain information about the problem that occurred, and in some cases, recommendations on how to fix the problem. You can filter Alerts to remove less important or older alerts from the Alerts view. Alerts are filtered by the Desktop Agent in order to minimize the load on DLO. By default, alerts are limited to one of each type in 24 hours. For example, you will see only one Local Out of Disk Condition alert in a 24-hour period from a desktop running the Desktop Agent. Note Backup/Restore complete alerts cannot be filtered. If you enable these alerts, they are generated each time a backup or restore job completes. Active alerts that are older than a specified number of days are cleared and moved into the alert history. The alerts in the history will be deleted if they have been cleared for more than a specified number of days. When alerts in the history have been cleared for a given number of days, which by default is seven days, they are deleted by a Backup Exec archive operation. If an alert is manually cleared, it is moved into the alert history. Deleting an alert manually removes it permanently.
1200
Monitoring Alerts on the DLO Administration Console DLO Administration Console Alerts View
Following are descriptions of the types of alerts:

Alert Categories Alert Type Informational Description Notifies you that an expected action has occurred, such as the successful completion of a backup or restore job. Notifies you of a potential issue. For example, an alert is generated when a backup has not been completed on a desktop within a given time frame, or if the disk quota limitations are being approached. Notifies you of an active or pending danger to the application or its data. An error would be generated, for example, if a backup failed to complete, or if a desktop has exceeded its disk quota limitations.
Warning
Error
1201
Possible alerts are listed in the following table:

DLO Alerts Type Name Description
Server Alerts Warnings Queued Restore Job Has Not Completed Client Backup Has Not Completed Appears when a queued restore job has not completed within a pre-determined time (7 days, 14 days, or 28 days). Appears when a specific desktop has not completed a backup within a pre-determined time (7 days, 14 days, or 28 days).
Informational Restore Job Queued Appears when a restore job is initiated from the DLO Administration Console.
Desktop Agent Alerts Errors Configuration of User Failed Exceeded Local Disk Quota Appears when a new user connects and for an unknown reason cannot be configured properly. Appears when attempting to add a new version to the Desktop User Data Folder, which would exceed the specified disk storage limit. Appears when attempting to add a new version to Network User Data Folder which would exceed the specified disk storage limit. Appears when the available disk space on the desktop computer reaches a pre-determined percentage. Appears when the available disk space on the network computer reaches a pre-determined percentage. Appears when a running backup job is unable to be completed and fails.
Exceeded Share Disk Quota
Local Out of Disk Condition Share Out of Disk Condition Backup Job Failed
1202
Monitoring Alerts on the DLO Administration Console DLO Alerts (continued) Type Name Restore Job Failed Description Appears when a running restore job is unable to be completed and fails.
Warnings No Matching User Assignment Appears when a new user connects and no matching combination of domain and/or group could be found within the defined User Assignments. Appears when a users Desktop User Data Folder is approaching the specified size limit. Appears when a users Network User Data Folder is approaching the specified size limit. Appears when the available disk space on the desktop computer reaches a pre-determined percentage.
Approaching Local Disk Quota Approaching Share Disk Quota Approaching Local Low-Disk-Space Condition Approaching Share Low-Disk-Space Condition Backup Job Completed with Errors Backup Job Completed with Warnings Restore Job Completed with Errors Restore Job Completed with Warnings Informational Job Completed Successfully
Appears when the available disk space on the network computer reaches a pre-determined percentage.
Appears when a backup job completes with errors.
Appears when a backup job completes with warnings.
Appears when a restore job completes with errors.
Appears when a restore job completes with warnings.
Appears when a backup job completes successfully.
1203
Monitoring Alerts on the DLO Administration Console DLO Alerts (continued) Type Name Restore Job Completed Successfully User Configured Successfully Description Appears when a restore job completes successfully.
Appears when a new user connects and is successfully configured.
Configuring Alerts
The DLO Administrator can select the type of alerts to display in the DLO Administration Console. To configure DLO alerts: 1. On the DLO navigation bar, click Alerts. 2. Under General Tasks in the task pane, click Configure alerts.
Configure Alerts Dialog Box
3. Select the alerts you want to receive, and clear the check boxes for the alerts you do not want to receive. 4. Click OK.
Managing Alerts
From the Alerts view in the DLO Administration Console, you can view a subset of alerts, clear alerts, and move alerts from the administration console to a history log. To view DLO alerts: 1. On the DLO navigation bar, click Alerts. 2. Under Views in the task pane, click Active alerts to view active alerts, or Alert history to view alerts that have been cleared. Note Alerts that are older than a specified number of days are cleared and moved into alert history. The number of days is specified in the Backup Exec Administration Console. 3. To filter alerts by type, select one or more options from Active Alerts View Filters or Alert History View Filters in the task pane as described below:
Active Alerts View Filters Item Show errors Show warnings Show information Description Lists error alerts for the selected view. Lists warning alerts for the selected view. Lists informational alerts for the selected view.
4. To view the properties of an alert, select the alert in the Active Alerts of Alert History list. Properties are displayed in the Alert Properties pane. To clear alerts: 1. On the DLO navigation bar, click Alerts. 2. If desired, filter the Alerts view as described in To view DLO alerts: on page 1205. 3. From the alert list, select one or more alerts that you want to clear. 4. Under Alert Tasks in the task pane, select Respond to clear only the selected alerts, or to change the status of all alerts to cleared, select Respond OK to all.
1205
DLO Reports
DLO Reports
DLO provides 12 standard reports that show detailed information about your DLO operations. When you generate a report, you can specify filter parameters or a time range for the data that you want to include in the report. You can also view general properties for each report. Reports are generated using Crystal Reports. If Adobe Acrobat is detected, reports are displayed in Adobe Portable Document Format (PDF). If Adobe Acrobat is not detected, the reports are displayed using HTML. Both PDF and HTML reports can be saved and printed. To view the list of available reports: 1. On the navigation bar, click Reports. 2. The Reports pane lists the report name, a description, and a category for each report. You can sort the reports in alphabetical or reverse alphabetical order by clicking Name.
DLO Reports Report Name Active Alerts by Machine Active Alerts by Time Description Lists all active alerts sorted by machine. Lists all active alerts chronologically, displaying the most recent alerts first. Lists all alerts sorted alphabetically by machine. Lists the alert history by computer. The most recent alerts are shown first. Lists the alert history in chronological order. The most recent alerts are shown first. Lists the alert history sorted by the user of the computer that generated the alert. Lists all machines running the Desktop Agent that failed the last backup. The list is sorted by desktop computer name. Note Only the last backup result is stored in the DLO database, so it is only possible to report the last backup result for each desktop computer and not a complete history of failed jobs. 1206 Administrators Guide
Active Alerts by User Alert History by Machine
Alert History by Time
Alert History by User
Failed Backup Jobs by Machine
DLO Reports DLO Reports (continued) Report Name Description
Failed Backup Jobs by Time Lists all machines running the Desktop Agent that failed the last backup. The list is sorted by time. Note Only the last backup result is stored in the DLO database, so it is only possible to report the last backup result for each desktop computer and not a complete history of failed jobs. Failed Backup Jobs by User Lists all machines running the Desktop Agent that failed the last backup. The list is sorted by Desktop Agent user name. Note Only the last backup result is stored in the DLO database, so it is only possible to report the last backup result for each desktop computer and not a complete history of failed jobs. Last Backup Status by Machine Lists all computers running the Desktop Agent and their last backup status. The list is sorted by desktop computer name.
Last Backup Status by Time Lists all the machines and their last backup status. The list is sorted by last backup time. Last Backup Status by User Lists all the machines and their last backup status. The list is sorted by Desktop Agent user.
Related Topics: Viewing Report Properties on page 1208 Running a Report on page 1209
1207
DLO Reports

Report properties provide a summary of information about each report. The properties can be viewed, but not edited. To view Report Properties: 1. On the navigation bar, click Reports. 2. On the Reports pane, select the report for which you want to view properties. 3. 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:

Alerts Last Backup Status Failed Jobs
Author Subject
The creator of the report.
The version of the product for which the report was created.
The primary information used to categorize the report.
Keywords File name File size Creation Date
The location of the report template. The size of the report template. The date the report was installed on the system.
4. Click OK after you have finished viewing the properties.
1208
DLO Reports
Running a Report
When you run a report, you can specify filtering criteria to determine which items will be included in the report. After the report is generated, only the items that match the entered criteria appear in the report. If no criteria are entered, all available entries are included in the report. To run a report: 1. On the navigation bar, click Reports. 2. On the Reports pane, select the report you want to run. 3. Under Report Tasks in the task pane, click Run report now. 4. Select the appropriate parameters for the data you want to include in the report from the following available parameters:
Report Filters Item Computer Description Check this box and enter a desktop computer name to generate a report for the specified desktop computer only. Check this box and enter a user name to generate a report for the specified Desktop Agent user only. Check this box and enter the number of days you would like the report to reflect.
User
Days
5. Click OK to run the report. The report can be printed or saved before it is closed. 6. Click OK to close the report.
1209
Maintaining the DLO Database
Maintaining the DLO Database

The Desktop and Laptop Option uses an MSDE database instance named BKUPEXECDLO, which operates separately from the Backup Exec database instance. You can maintain both the Backup Exec database and the DLO database using the Backup Exec database maintenance options. Use BEUtility to perform database operations on BKUPEXECDLO. The DLO database is backed up and restored automatically each time the Backup Exec database is backed up or restored. If you use BEUtility to repair or recover the DLO database, all DLO Administration Consoles must be closed. Otherwise, the operation will fail. For more information about performing database maintenance, see Configuring Database Maintenance on page 447. For more information about using BEUtility to perform database operations, see Backup Exec Utility on page 717.
Clustering the Desktop and Laptop Option

In order to cluster DLO in a Backup Exec cluster configuration, you must install DLO on each cluster node. You cannot add DLO to an existing Backup Exec cluster. Either add DLO when you configure a cluster, or uncluster an existing cluster, add DLO, and then reconfigure the cluster. If the DLO Agent was installed from a cluster node that is now inactive, it will not reconnect to the cluster following the unclustering process. To reconnect to a cluster node after you uncluster DLO: 1. In the .dlo\.notify directory on the desktop user's Storage Location, create a text file named NewMediaServerDesktopMachineName. For example, in the file named NewMediaServerAdmin123, the desktop machine name is Admin123. 2. In the text file, type the name of the new DLO server on the first line and save the file. 3. Repeat steps 1 and 2 for all desktops that will use a new DLO server. If the desktop is running, it should connect to the new server. If the desktop is not running, it should connect to the new server the next time it runs.
1210
To move a Storage Location in a DLO cluster environment: Note These steps must be performed before you take DLO out of the cluster. 1. If the Storage Location is on a shared drive or virtual server, you must move the user data for all of the Storage Location users. Move the user data to a Storage Location on the local node. 2. Modify all automated user assignments that are configured to use the Storage Location on the shared drive or virtual server so that they use another Storage Location on the local node. 3. Verify that all user data was moved off the Storage Location on the shared drive or virtual server and then delete it from the shared drive or virtual server. To upgrade an existing Backup Exec 9.x cluster and add DLO to the cluster: 1. Install Backup Exec 9.x on the active Backup Exec cluster node. Do not select the DLO option. 2. Install Backup Exec 9.x on each failover node. Do not select the DLO option. Note Install Backup Exec when the node has access to the shared Backup Exec cluster disk. 3. Use the Cluster Configuration Wizard on the active Backup Exec cluster node to uncluster all nodes. Click No when you are prompted to remove data on the shared drive. Click Yes when you are prompted to make the data available to the local node. 4. Install DLO on all cluster nodes. All nodes must have DLO before you can recluster them. 5. From the server you used in step 3, use the Cluster Configuration Wizard to reconfigure cluster-aware Backup Exec with the same virtual server name. 6. Add all cluster nodes that were upgraded. The DLO services are added to the Cluster Administrator.
1211
To upgrade an existing Backup Exec 8.x cluster and add DLO to the cluster: 1. Uninstall Backup Exec 8.x and the Remote Agent for Windows from all failover nodes. 2. Uninstall the Remote Agent for Windows from the active Backup Exec cluster node. 3. Reboot the active Backup Exec cluster node. 4. Install Backup Exec 9.x on the active Backup Exec cluster node. Do not select the DLO option. When the upgrade completes, the server is the only node in the Backup Exec 9.x cluster configuration. See also: Using Symantec Backup Exec with Server Clusters on page 657 Installing the Backup Exec Desktop and Laptop Option on page 1130 Installing Backup Exec on a Microsoft Cluster Server on page 660
1212
DLO Command Line Interface Management Tools

DLO provides a number of powerful command line system tools to manage DLO server operations as outlined in the following sections:

DLO Command Syntax on page 1213 Commands in Detail on page 1214
DLO Command Syntax

DLO Command Line Interface commands are run from the installation directory and are executed with the DLOCommandu command. The default installation directory is: C:\Program Files\VERITAS\Backup Exec\NT\DLODLOCommandu is executed as follows: DLOCommandu [remote-server-options] command [command-options-and-arguments] [log-file-option]
General Command Options

The general command options are discussed within the individual DLO Command Line Interface commands (see the following sections).
Remote Server Options

Remote server options allow you to specify the name of the remote server on which you want to run a command. You can also enter your username and password if required. Remote server options are as follows:
Remote Server Options Option C <computer> N <user> Description remote computer name, default to local computer fully qualified user name, e.g. Enterprise\GFord. The default is the current user user password if n is specified
W <password>
1213
Commands in Detail
See the following topics for detailed information on available commands:

-AssignSL Command on page 1214 -EnableUser Command on page 1216 -ChangeServer Command on page 1217 -KeyTest Command on page 1218 -ListProfile Command on page 1218 -ListSL Command on page 1219 -ListUser Command on page 1220 -LogFile Command on page 1221 -Update Command on page 1222 -EmergencyRestore Command on page 1224 -SetRecoveryPwd Command on page 1225 -DisableNCOM Command on page 1225 -RenameUser Command on page 1225 -NotifyClients Command on page 1227 -InactiveAccounts Command on page 1227 -CreateRecoveryKeys Command on page 1228
-AssignSL Command
The AssignSL command is used to assign a new Storage Location to existing users when the existing Storage Location is no longer available. Caution The Move User command should be used to move users to new Storage Locations if the existing Storage Location is accessible. See Moving a Desktop Agent User on page 1182 for additional information. Desktop Agent Users can be assigned to new Storage Locations based on User account name, Profile name, Profile ID, Storage Location, Storage Location ID, and File server. The Desktop Agent that is being moved will be disabled until the media server is notified that the move is complete.
1214
Backup data is not moved from the old Storage Location to the new Storage Location with this command. Syntax: DLOCommandu assignsl NI [A | F | P | PI | S | SI | U ] Note Wildcard matches (*) are permitted in Profile, Storage Location and user names. Quotations are required around names if the name contains a space or colon.
Command Options:
AssignSL Options Option NI <newSLID> A F <file server> Description New storage location ID Assigns new storage location to all users Assigns new storage location to users with storage locations on the named file server Assigns new storage location to users with named profile Assigns new storage location to users with given profile id Assigns new storage location to users with named storage location Assigns new storage location to users with given storage location id Assigns new storage location to named user account only
P <profile name> PI <profile id> S <SL name>
SI <SL id>
U <user>
Examples: DLOCommandu assignsl NI DLO_SL02 A DLOCommandu assignsl NI DLO_SL03 U mmouse
1215
-EnableUser Command
The -EnableUser command is used to enable or disable a user. User(s) can be enabled or disabled by All, file server (all storage locations), profile name, profile ID, storage location name, storage location ID or username. Use this command if you want to force the desktop computer to refresh from the media server. Syntax: DLOCommandu -enableuser [ E | D ] [ A | F | P | PI | S | SI | U ] Note Wildcard matches (*) are permitted in Profile, Storage Location and user names. Quotations are required around names if the name contains a space or colon.
Command Options:
EnableUser Command Options Option A E | D Description Enables or disables all user on your media server Enables or disables a user account. The default value is to enable a user (i.e. E). Enables or disables users with storage locations on the named file server Enables or disables users with named profile Enables or disables users with given profile id Enables or disables users with named storage location Enables or disables users with given storage location id Enables or disables named user account only
F <file server>
P <profile name> PI <profile id> S <SL name> SI <SL id> U <user>
Examples: DLOCommandu enableuser E A
1216
DLOCommandu enableuser D U mmouse
-ChangeServer Command
The -ChangeServer command is used to switch users to another media server. Syntax: DLOCommandu ChangeServer M <media server> [ A | F <file server> | P <profile name> | PI <profile id> | S <SL name> | SI <SL id> | SP <SL path> | U <user> ] Note Wildcard matches (*) are permitted in Profile, Storage Location and user names. Quotations are required around names if the name contains a space or colon.
Command Options:
ChangeServer Command Options Option A F <file server> M <media server> P <profile name> PI <profile id> S <SL name> SI <SL id> SP <SL path> U <user> Description Switches all user (default) Switches users with storage locations on the named file server The new media server name Switches users based on profile name Switches users based on profile id Switches users based on storage location name Switches users based on storage location id Switches users based on storage location path Switches users based on user name
Examples: DLOCommandu ChangeServer M sunshine P Desktop* DLOCommandu ChangeServer M sunshine SP \\moonlight\EngDept

DLOCommandu ChangeServer M sunshine SP \\moonlight\EngDept\EnterpriseMNoel
-KeyTest Command
The -KeyTest command scans network user data to identify encrypted data that cannot be restored with the current encryption key. Syntax: DLOCommandu KeyTest <quarantinepath> Note Wildcard matches (*) are permitted in Profile, Storage Location and user names. Quotations are required around names if the name contains a space or colon.
Command Options:
KeyTest Command Options Option <quarantinepath> Description If specified, unrestorable data is quarantined to this path. Once the unrestorable files are quarantined, the DLOAgent will back up the original files again with the new encryption key. The quarantine folder will be created if it does not exist, and should not specify an existing storage location. If not specified, the data is scanned without being quarantined, and a report will be generated.
Examples: DLOCommandu keytest DLOCommandu keytest C:\Quar_folder_name
-ListProfile Command
The -ListProfile command is used to list profiles of DLO users. Syntax: DLOCommandu listprofile [ A | P ]
1218
Note Wildcard matches (*) are permitted in Profile, Storage Location and user names. Quotations are required around names if the name contains a space or colon.
Command Options:
ListProfile Command Options Option A P <profile name> Description Lists settings for all profiles (default) Lists settings for only named profile
Examples: DLOCommandu listprofile A DLOCommandu listprofile P yourprofile
-ListSL Command
The -ListSL command is used to list the DLO storage locations. Syntax: DLOCommandu listsl [ A | F | S ] Note Wildcard matches (*) are permitted in Profile, Storage Location and user names. Quotations are required around names if the name contains a space or colon.
1219
Command Options:
ListSL Command Options Option A F <file server> S <SL name> Description Lists all storage locations (default) Lists storage locations for the named server Lists only the named storage location
Examples: DLOCommandu listsl A DLOCommandu listsl F yourserver DLOCommandu listsl S yourSL
-ListUser Command
The -ListUser command is used to list by All, file server, profile name, profile ID, storage location name, storage location ID or username. Syntax: DLOCommandu listuser [ A | F | P | PI | S | SI | U ] Note Wildcard matches (*) are permitted in Profile, Storage Location and user names. Quotations are required around names if the name contains a space or colon.
1220
Command Options:
ListUser Command Options Option A F <file server> Description Lists settings for all users (default) Lists settings for users with storage locations on the named file server Lists settings for users by profile name Lists settings for users by profile id Lists settings for users by storage location name Lists settings for users by storage location id Lists settings for users by user name
P <profile name> PI <profile id> S <SL name> SI <SL id> U <user>
Examples: DLOCommandu listuser A DLOCommandu listuser P yourprofile DLOCommandu listuser U mmouse DLOCommandu listuser U m*
-LogFile Command
The LogFile option allows administrators to change the path or name of the LogFile. And, since every command overwrites the LogFile, in order to track all events (logs), you must change the path\name of the next LogFile in order to retain older versions. The default path is the \Logs folder under the installed path: C:\Program Files\VERITAS\Backup Exec\NT\DLO\Logs Syntax: LogFile <path\file>
1221
Command Options:
LogFile Command Options Option <path> <file> Description Specifies the path to the new LogFile Specifies the filename for the new LogFile
Examples: DLOCommandu logfile test.log DLOCommandu logfile c:\test.log
-Update Command
The -Update command is used to list, add, remove and publish client updates. See Updating DLO on page 1131 for additional information on updating DLO. Syntax: DLOCommandu update [ list | add | remove | publish ]
1222
Subcommands:
Update SubCommands SubCommand List [-A|UI <update id>] Add F <file name> Description Lists settings for previously used updates. Adds an update definition file to the updates list and assigns it a unique UI. Removes a file or files from the list. Makes updates specified by the update definition file available to the users, and specified by P | PI | U.
Remove [-UI <update id>|A] Publish [-R] UI <update id> [P <profile name>|PI <profile id>|U <user>]
1223
Command Options:
Update Command and Sub-Command Options Option A F <file name> U <user name> Description Updates all Specifies a text file that contains update records Specifies a fully qualified user name, such as Enterprise\JFord Specifies a profile name Specifies a profile record id Designates to unpublish Specifies an update record id
P <profile name> PI <profile id> R UI <update id>
Examples: DLOCommandu -update -add -f cntlfile.txt DLOCommandu -update -list DLOCommandu -update -remove -UI 3 DLOCommandu -update -publish -UI 63 -P yourprofile DLOCommandu -update -publish -R -UI 33
-EmergencyRestore Command
The -Emergency Restore command uses the DLO administrators recovery password to restore user data that would otherwise be unavailable if the DLO database is damaged or corrupted. The recovery password must be known to execute this command. The data will be restored to the specified location in the original data structure, but it will no longer be encrypted. See Setting a Recovery Password on page 1135 for more information. Syntax: DLOCommandu EmergencyRestore <usersharepath> -W <recovery password> -AP <destination path>
1224
Command Options:
Update Command and Sub-Command Options Option <usersharepath> -W <recovery password> -AP <destination path> Description Specifies the full path to the user share directory Specifies the recovery password
Specifies the path to which data will be restored
-SetRecoveryPwd Command
The -SetRecoveryPwd command is used to change the recovery password. The -CreateRecoveryKeys command is automatically executed when -SetRecoveryPwd is run. See Setting a Recovery Password on page 1135 for more information. Syntax: DLOCommandu SetRecoveryPwd <password>
-DisableNCOM Command
The -DisableNCOM command prevents data, logs or alerts from being transferred to the Network User Data Folder when connected via modem. By default, DLO will transfer data even when connected by modem. Syntax: To disable transfers to the Network User Data Folder when connected via modem: DLOCommandu -DisableNCOM -on To allow file transfer while connected via modem (default): DLOCommandu -DisableNCOM -off
-RenameUser Command
The RenameUser command is used when a user account was renamed in a domain or on a local machine.
1225
Caution This command should only be used when an account is renamed in the specific scenarios described below. It cannot be used to change from one user account to another and does not rename users in the domain. Scenario 1 A domain account has been renamed. This change needs to be reflected in DLO. Syntax: dlocommandu -renameuser -oun domain\olddomainusername -nun domain\newdomainusername dlocommandu -renameuser -oun machinename\localusername -nun newdomainusername Note -oun specifies the old user name and -nun specifies the new user name. Example 1: The domain user name has changed from mydomain\ johndoe to mydomain\ janedoe. The user logs in using the domain account. dlocommandu -renameuser -oun mydomain\ johndoe -nun mydomain\ janedoe Example 2: The domain user name has changed from mydomain\ johndoe to mydomain\ janedoe. The user logs in to a local account named my account on a machine named mymachine. dlocommandu -renameuser -oun mymachine\myaccount -nun janedoe Scenario 2 The desktop user logs into the local machine using a local account and authenticates to DLO using a domain account. The local account is renamed. Syntax: dlocommandu -renameuser -oun machinename\oldusername -nun machinename\newusername To rename an account: 1. Have the Desktop User log off of the account that is to be renamed. This will exit the Desktop Agent. 2. Rename the account.
3. Run the -RenameUser command 4. Have the Desktop User log back on under the new username. The Desktop Agent will automatically start. Note If a user is renamed in a domain and logs on to the desktop computer before the DLO administrator runs the -RenameUser command, a new account is automatically created for the new username. To correct this error, the administrator should first delete the new user in the DLO administration console and then run -RenameUser to rename the account.
-NotifyClients Command
The -NotifyClients command forces the Desktop Agents to refresh the Profile settings immediately, or the next time the Desktop Agent connects if it is offline. Syntax: dlocommandu -notifyclients
-InactiveAccounts Command
The -InactiveAccounts command is used to list and delete accounts that have not been used in a specified number of days. To list inactive accounts: dlocommandu -inactiveaccounts -list -days <#days> This command returns a list of inactive accounts that includes the following information which is used to delete specific accounts:

machine name machine ID domain\username userID
To delete specific inactive accounts: dlocommandu inactiveaccounts -delete U <domain\username> -M <machine name> -days <#days>
1227
dlocommandu inactiveaccounts -delete UI <userID> -MI <machine ID> -days <#days> Where U and -M are used to delete the user and machine by name and UI and -MI are used to delete the user and machine by ID. To delete ALL accounts inactive for a specified number of days: dlocommandu -inactiveaccounts -delete -a <#days>
-CreateRecoveryKeys Command
The -CreateRecoveryKeys command is now obsolete. Recovery keys are now managed automatically by the Desktop Agent. Related Topics: Setting a Recovery Password on page 1135 Data Integrity Scanner on page 1135
1228
Using the Desktop Agent

The Desktop Agent is the component of the Backup Exec Desktop and Laptop Option that protects files on desktop and laptop computers (collectively referred to as desktops) by backing up data to the desktops local drive and to a Storage Location on the network. The DLO administrator initially configures the Desktop Agent. If the DLO administrator has set your Profile so that you can view the complete Desktop Agent and modify settings, then you can restore files, synchronize files between multiple desktops, configure backup selections, set schedules, view history and more. Your Profile determines the level of interaction between you and the Desktop Agent. The administrator may also configure the Desktop Agent to run without a user interface, with a fully functional user interface, or somewhere in between.
Features and Benefits

The Desktop Agent provides the following features:
Data Protection. Selected files on the desktop are automatically copied to User Data Folders on the desktops local drive and on the network. The Desktop Agent can be configured so that no user interaction is required. Files are protected automatically when the desktop is online or offline. Backup Exec protects the data by backing up the Network User Data Folders on the DLO file server. Data Availability. A user can access data from multiple desktops in multiple locations if they are using the same login credentials. Users can also restore previous file revisions even when the desktop is offline if they are saving at least one file revision in the Desktop User Data Folder. Synchronization. A user that accesses multiple computers with the same login credentials can configure folders to be synchronized on each of the computers. When a synchronized file is changed on one computer, the updated file is copied to the Network User Data Folder and also to the Desktop User Data Folder on all other computers that are configured for synchronization.
1229
System Requirements for the Desktop Agent

The following are the minimum system requirements for running this version of the Desktop Agent.
Minimum System Requirements Item Operating System Description Microsoft Windows 2000 Microsoft Windows XP Service Pack 1 (SP1) or later Note The Desktop Agent is not supported on any server operating system, including Windows Server 2003, Windows Storage Server 2003, and Windows 2000 Server. Processor Memory Pentium system Required: 256 MB RAM Recommended: 512 MB (or more for better performance). Internet Browser Internet Explorer 5.01 or later; however, version 5.5 is recommended. 25 MB hard disk space required after Microsoft Windows is installed (typical installation). Network interface card or a virtual network adapter card (recommended if remote activity is to be performed).
Disk Space
Other Hardware
Using the Desktop Agent Console

The Desktop Agent Console is the user interface for the Desktop Agent. Access to the Desktop Agent Console is controlled by the DLO administrator. The DLO administrator may choose from the following: Display the complete interface. Enables desktop users to access all Desktop Agent options. Display only the status. Enables desktop users to view the status of backup jobs, but they cannot change settings for the Desktop Agent or access options other than status. Desktop users can right click the system tray icon to open the status view, or exit the program.
1230
Display only the system tray icon. The desktop user sees only the Desktop Agent icon in the system tray in the lower right corner of the screen. Desktop users can right click on the system tray icon to exit the program. Do not display anything. The Desktop Agent runs in the background. The desktop user cannot view the Desktop Agent.
Desktop Agent Console Menu bar Tasks bar Views menu
Tasks menu
1231
The Desktop Agent Console has the following components:

Desktop Agent Console Features Item Menu bar Description The menu bar appears across the top of the screen. To display a menu, click the menu name. Some menu items are not available until an item is selected from the console screen. The Tasks bar appears on the left side of the Desktop Agent Console. To hide the Tasks bar, from the View menu, select Tasks Bar. Actions are initiated from the tasks bar, and these actions vary with the selected view. The Views menu appears in the Tasks bar and enables you to navigate to the following views: Provides job status, lists pending jobs, and summarizes recent backup activity. Enables you to define what data is protected by the Desktop Agent.
Tasks bar
Views menu
Status
Backup Selections Synchronized Selections
Enables you to configure the Desktop Agent to maintain a users selected files and folders on multiple computers so that the most recent backed up version is always available to the user. Enables the user to restore backed up data and search for backed up files. Displays Desktop Agent error, warning, and informational messages. Enables you to modify settings that determine how the Desktop Agent operates. Actions are initiated from the tasks menu. These actions vary with the selected view.
Restore
History Settings
Tasks menu
Note To ensure that you have the latest status and settings at any time while using the Desktop Agent, from the Tasks menu, click Refresh.
1232
Resetting Dialogs and Account Information

While using DLO, you can suppress dialogs by checking the Dont show me this message again checkbox. These dialogs can be reset so they will once again be displayed. To reset dialogs and account information: 1. From the Tools menu, select Options. 2. If you want to reset any information dialogs suppressed by the Dont show me this message again checkbox, click Reset dialogs. 3. Click Yes when prompted if you want to reset the dialogs. 4. If you want to clear any passwords and account information that the Desktop Agent has stored, click Reset accounts. 5. Click Yes when prompted if you want to clear the accounts. 6. Click OK when finished.
Installing the Desktop Agent

The DLO administrator determines who installs the Desktop Agent. It can be either the administrator or the desktop user. After the Desktop Agent is installed on a desktop, anyone who logs on to that desktop can use the Desktop Agent. The logged on user will only have access to DLO backup files associated with the logged on account. Note You must have administrative rights to the desktop on which you want to install the Desktop Agent. If you need to reboot the desktop during installation, you must use the same administrator login again to ensure that the installation completes successfully. During the installation process you may be prompted to update or install the required version of Microsoft Data Access Components (MDAC). This may require a reboot, after which you will be able to continue with the DLO installation.
1233
To install the Desktop Agent: 1. From the desktop on which you want to install the Desktop Agent, browse to the network server where the installation files for the Desktop Agent are stored. The default location is \\<Backup Exec media server name>\DLOAgent. If you are unsure of the location, contact the administrator. 2. Double-click the file setup.exe. 3. On the Welcome screen, click Next. 4. Read the license agreement, and then click I accept the terms in the license agreement. 5. Click Next. 6. Select either Typical or Custom, and then click Next. Use the Typical option to install all of the Desktop Agent features in the default location C:\Program Files\VERITAS\Backup Exec\NT\DLO. Use the Custom option to change the location on the desktops local drive where the Desktop Agent will be installed, or to select the installation set for a language other than English. The Custom option is recommended for advanced users only. 7. If you selected Typical, go to step 9. If you selected Custom, select from the following:
Click the Installable Languages icon to install the install set in languages other than English. Click Change to change the location on the desktops local drive where the Desktop Agent will be installed. The default location for the Desktop User Data Folder is C:\Documents and Settings\UserName\Local Settings\Application Data\VERITAS\DLO\.dlo\.lm\ Browse to the folder or type the path in the Folder name field and then click OK.
8. Click Next after making your selections. 9. Click Install. 10. Click Finish. The Desktop Agent is installed on the desktop.
1234
Connecting to the media server

The Desktop Agent interfaces with the DLO database and services on the media server during normal operation. When using the Desktop Agent, you must connect to the media server using a domain account. Note If you connect to the media server with one set of credentials, and then attempt to connect to the server using DLO with a different set of credentials, authentication may fail. Reboot the machine to reconnect.
Using local accounts on desktop computers

You can log in to your desktop with a local account. If you do, DLO will prompt you for domain credentials. See Using Alternate Credentials for the Desktop Agent below for more information on logging in with alternate credentials. The following should be considered when using local accounts on desktops that run the Desktop Agent:
You can only use a set of domain credentials with one local account. If you use more than one local account on a desktop or laptop computer, you should either disable DLO for other accounts or have unique domain credentials for each account. See To log on with alternate credentials or to disable accounts: on page 1237 for additional information. Example If you usually log on to the desktop computer as myusername, you should have a domain account to use for DLO with this account. If you also occasionally log on as administrator, DLO can be disabled when you are logged on to this account. Alternately, you can provide a unique set of domain credentials to use for DLO when you are logged on as administrator.
Multiple users of the same desktop computer can all use DLO, but must provide unique credentials for the desktop computer and unique domain credentials for authentication with DLO.
Using Alternate Credentials for the Desktop Agent

The account used by the Desktop Agent is the logon account by default, but could be an alternate account if one has been specified, such as when connecting across domains. If you are logged on with credentials that are not recognized by the Desktop Agent, you can specify alternate credentials for Desktop Agent operation and save the account information for future sessions. If you prefer, you can disable an account for Desktop
1235
Agent operations so that the Desktop Agent will not run when you are logged on with the account currently being used. This dialog allows you to save this account info for future connections. Note If you have a previously established network connection to the media server and it does not match the account the Desktop Agent is using, the Desktop Agent will attempt to reconnect as the Desktop Agent user. If this fails, the following error displays: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. The account used by the Desktop Agent is the logon account by default, but could be an alternate account if one has been specified; for example, to connect across domains. Using alternate credentials to work across domains In a cross-domain configuration where there is no trust relationship, if multiple users are running the same Desktop Agent, each user must provide a unique user name and password in the media server domain. If different users use the same credentials, DLO displays an error message stating that the user is already connected to the media server. Note For information on resetting accounts that have been disabled for Desktop Agent operation, see To reset dialogs and account information: on page 1233.
1236
To log on with alternate credentials or to disable accounts: 1. When you are logged on to the desktop computer with an account that is not recognized by the Desktop Agent, the Alternate Credential dialog box will appear.
Alternate Credential Dialog Box
2. Specify Desktop Agent logging options as outlined below:

Alternate Credentials Item Use this account Username Enter the user name for an account that is authorized for Desktop Agent operation. Enter the password for the account to be used for Desktop Agent operation. Type the domain for the account to be used for Desktop Agent operation. Check if you would like to save this account information for future DLO sessions. Select to prevent the Desktop Agent from running when you are using the account under which you are currently logged on. Description
Password
Domain Save this account information Disable this account
3. Click OK.
Using the Desktop Agent to Back Up Your Data

When data is backed up by the Desktop Agent, it is transferred to the User Data Folder on the desktops local drive. Then, the data is transferred to a Network User Data Folder, which is assigned by the DLO Administrator. Network User Data Folders are typically also backed up by Backup Exec, which provides an additional level of protection. Caution If you attempt to connect to a server using characters in the share name that do not exist on the code page for the local system, the connection will fail. Code pages map character codes to individual characters, and are typically specific to a language or group of languages. For information on backing up and restoring Microsoft Outlook PST files, see Backing up Outlook PST files on page 1247 and Restoring Microsoft Outlook Personal Folder Files on page 1268. Select files that you want to protect from the Backup Selections view. Backup selections are initially assigned by the administrator, but if the DLO administrator has set your Profile so that you can view the complete Desktop Agent and modify settings, then you can choose your backup selections. You can view and modify backup selections using two views: standard and advanced. The standard view lists the contents of your local drives, allowing you to check off files and folders to be backed up. It also uses default backup selection settings to add new selections. The advanced view provides more configuration options for selections. A backup selection consists of:

A folder or list of folders Criteria for the files to be included or excluded from the backup Limits on the number of file revisions to retain Settings for compression, backup file deletion, and encryption
Managing Revisions
Revisions are versions of a file at a specific point in time. When a file is changed and backed up, DLO stores a new revision. DLO stores and maintains a specific number of revisions for all files in a backup selection. Because each backup selection is configured separately, the number of revisions retained can vary for different backup selections. When the number of revisions is exceeded, DLO removes the oldest revision, maintaining only the specified number of revisions in the desktop and Network User Data Folders.
1238
You can limit the number of revisions DLO retains in a given period of time. If you are working on a document and backing it up frequently, all of your revisions could potentially be just a few minutes apart. By specifying that you want to retain only 2 revisions every 24 hours, at least 120 minutes apart, you can retain older revisions for a longer period of time. While some intermediate versions will not be retained, it does support situations in which returning to an older revision is needed. Another consideration in determining the number of revisions to retain is the amount of storage space required to store the data. The amount of space required for backups can be estimated by multiplying the number of revisions retained by the amount of data protected. Example If you are retaining three revisions of each file and have 10 MB to back up, approximately 30 MB of disk space will be required. Although compression can improve the space utilization, it varies significantly with file type and other factors. Related Topics: Modifying Backup Selections in the Standard View on page 1239 Adding Backup Selections in the Advanced View on page 1241 Backing up Outlook PST files on page 1247 Restoring Microsoft Outlook Personal Folder Files on page 1268
File Grooming
The Desktop Agent grooms revisions based on backup selection settings and does this as new revisions are created. The oldest revision is deleted when a new revision is created that exceeds the limit. Maintenance grooming is the grooming off of deleted files. It occurs at most once every 24 hours. Maintenance grooming occurs during the first backup that runs after 24 hours have passed since the last maintenance grooming.
Modifying Backup Selections in the Standard View

The Backup Selections Standard view provides a list of drives, folders, and files that you can select for backup. Note Profile backup selections are those that were specified by the DLO administrator in your Profile. You cannot modify Profile backup selections in the standard view. You can only modify the backup selections that you create on the Desktop Agent. Profile backup selections are displayed in the standard view with gray check
boxes. They can be modified in the advanced view if the administrator has granted you sufficient rights. See Modifying Backup Selections in the Advanced View on page 1245 for additional information. When you create new backup selections in the standard view, the default backup selection settings are used. When you add new subfolders and files to the backup selection using the standard view, these new backup selections will have the same settings as the main folders.
Standard View
To modify backup selections in the Backup Selections Standard view: 1. Under Views in the Tasks Bar, click Backup Selections. 2. Click Standard view. 3. Select the folders and files you want to back up. Expand selections by clicking the plus sign (+) and collapse selections by clicking the minus sign (-). Note To return to the last saved settings at any time, click Undo changes.
1240
4. Click Save changes to save the new settings or Undo changes to return to the last saved settings. After clicking Save, previously backed-up selections that were unchecked are treated like deleted backup selections and will no longer be backed up. The backup files for this selection will be deleted after the number of days specified in the backup selection settings. The source files for the deleted backup selection will not be deleted by the Desktop Agent. Checked folders that were not previously checked are added to the backup selections for this desktop.
Adding Backup Selections in the Advanced View

To add a backup selection in the Backup Selections Advanced view: 1. Under Views in the Tasks Bar, click Backup Selections. 2. Click Advanced view. 3. Click Add.
Backup Selection Dialog Box
1241
4. From the General tab in the Backup Selection dialog box, select the appropriate options as follows:
Backup Selection General Dialog Box Item Name Description Description Type a descriptive name for the backup selection. Type a description of the backup selection. This description may include, for example, the folder selected, or the purpose for creating the backup selection.
Folder to back up Type a folder name Select this option to add a specific folder to the backup selection, and then type the path to the folder, including the folder name. For example, to add a folder named MyData on drive C:, type C:\MyData. Select this option to choose a pre-defined folder from the list provided. Select this option to also back up all subfolders in the specified directory.
Select a pre-defined folder Include subfolders
5. From the Include/Exclude tab, select the appropriate options as follows:

Backup Selection Include/Exclude Dialog Box Item Include all file types Description Select this option to include all file types in this backup selection.
Include and exclude only Select this option to include or exclude only specific files or file the items listed below types.
6. Click Add Include or Add Exclude to add a filter to the Include/Exclude list.
1242

Add Include/Exclude Filter Dialog Box Ite m Add file name extensions Description
Select this option to add common file types to your include or exclude list. To select multiple file types, click one item and press <Ctrl> or <Shift> while clicking the other items. Select this option to add a custom file or file type to your include or exclude list. Select Files to apply this filter to files or Folders to apply this filter to folders. Type the name of the file or the folder, or a wildcard description of the file or folder that you want to include or exclude from backup selections. Type a description of the custom filter.
Add a custom filter
Apply to
Filter
Description
1243
8. From the Revision Control tab, select the appropriate options for the desktop and Network User Data Folders as follows:
Backup Selection Revision Control Dialog Box Item Description
Specify the number of revisions to keep in the desktop and Network User Data Folders Desktop User Data Folder Type the number of revisions to keep in the Desktop User Data Folder for each file in the backup selection. Note When Outlook PST files are backed up incrementally, only one revision is maintained regardless of the number of revisions set in the backup selection. Limit to Check this option to limit the number of revisions retained in a given amount of time, and specify the following:

Versions. Select the number of versions to retain. Within the last x hours. Select the time period during which you want to retain the versions. At least x minutes apart. Select the minimum amount of time that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created that exceeds one of these limits. Network User Data Folder Limit to Select the number of revisions to keep in the Network User Data Folder for each file in the backup selection. Check this option to limit the number of revisions retained in a given amount of time, and specify the following:

Versions. Select the number of versions to retain. Within the last x hours. Select the time period during which you want to retain the versions. At least x minutes apart. Select the minimum amount of time that must elapse between backups in this backup selection.
Note The oldest revision is deleted when a new revision is created that exceeds one of these limits.
1244
9. From the Options tab, select the appropriate options as follows:

Backup Selection Options Item Compress the files stored in the Network Data Folder Description Check this option to compress files in this backup selection for data transfer over the network and for storage in the desktop and Network User Data Folders. This affects files created after this feature is activated. Previously stored files will not be compressed. Encrypt the files for transmission and storage Check this option to encrypt files for transfer and to store files from this backup selection in an encrypted format in the Network User Data Folder. This affects files transmitted and stored after this feature is activated. Previously stored files will not be encrypted. The AES (Advanced Encryption Standard) and a 128 bit key length are used. If enabled, versions are stored unencrypted in the Desktop User Data Folder, and encrypted in the Network User Data Folder. Files transferred over the network are encrypted. When source files are deleted, delete the backed up files from the: Desktop User Data Folder after Indicate the number of days after which DLO will delete all file versions from the Desktop User Data Folder after the source file has been deleted from the desktop. Indicate the number of days after which DLO will delete all file versions from the Network User Data Folder after the source file has been deleted from the desktop.
Network User Data Folder after
10. Click OK to save your changes.
Modifying Backup Selections in the Advanced View

From the advanced view, backup selections created on the Desktop Agent and those created by the DLO administrator in the Profile can be modified if the Profile grants sufficient rights to the Desktop Agent user. 1. Under Views in the Tasks Bar, click Backup Selections. 2. Click Advanced view. 3. Select the backup selection you want to change, and then click Modify.
4. Profile backup selections are those set by the DLO administrator. If the backup selection is a Profile backup selection, and if the user has been granted sufficient rights, it can be modified by selecting Use custom selection in the drop down menu. Once this option is selected, your backup selection will no longer be updated when the administrator updates the Profile backup selection. You can return to the Profile backup selection settings at any time by selecting Use Profile selection in the drop down menu. Once you make this selection, your Profile will be updated if the DLO administrator modifies the Profile backup selection.
Use Custom Selection
5. Modify the backup selection properties as needed. For detailed information on backup selection settings, review the instructions for setting up a backup selection beginning with step 4 on page 1242. 6. Click OK.
1246
Deleting Backup Selections in the Advanced View

When you delete a backup selection, the backup files are deleted by the Backup Exec grooming process after the number of days specified in the backup selection. For additional information, see Backup Selection Options on page 1245. To delete a backup selection: 1. Under Views in the Tasks Bar, click Backup Selections. 2. Click Advanced view. 3. Select the backup selection you want to delete. 4. Click Remove. 5. Click Yes to verify that you want to delete this backup selection, or click No to cancel.
Backing up Outlook PST files

DLO is unable to perform incremental backups of Outlook PST files unless Outlook is your default mail application. To specify Outlook as your default mail application in your internet options: 1. Open Internet Explorer. 2. On the Tools menu, click Internet Options. 3. Select the Programs tab. 4. Select Microsoft Office Outlook in the E-mail list. Note If you do not intend to use Outlook as your default mail application, you can disable the warning message about incremental backups in the Desktop Agent selecting Settings in the Views menu and deselecting enable incremental backups of Outlook PST files in the Options tab. Pending PST Files When an Outlook PST file is included in a DLO backup selection, it will appear in the Desktop Agent pending queue whenever the PST file is closed. Because PSTs are a shared resource, opening and closing of PST files is controlled by a process called MAPI.
Both DLO and Outlook access PSTs via the MAPI process. MAPI opens a PST upon request from the application. MAPI may or may not, depending on the version in use, close a PST in response to the following:
An application such as DLO or Microsoft Outlook detaches from the PST, such as when Outlook is closed DLO startup After 30 minutes of inactivity in the PST
When the PST is closed DLO does one of the following. If the PST is being handled incrementally via MAPI (see section on incremental PSTs) DLO determines if the PST has been backed up in its entirety. If it has already been backed up then the entry is simply removed from the Desktop Agent pending queue because DLO knows the PST is in sync. If the PST is not being handled incrementally, the PST will be backed up in its entirety at this time. Related Topics: Restoring Microsoft Outlook Personal Folder Files on page 1268
1248
Modifying Desktop Agent Settings

If the DLO administrator has set your Profile so that you can view the complete Desktop Agent and modify settings, you can use the Settings view to modify the following:

Backup job schedule options Desktop User Data Folder location Desktop User Data Folder disk space limits Log file disk space limits Logging level Bandwidth usage
The Desktop Agent will continue to use settings specified in the Profile until you specifically elect to use customized schedules or options as described in Changing Backup Job Schedule Options on page 1250 and Setting Customized Options on page 1252. Settings cannot be changed when the Desktop Agent is offline, or when the media server is not available. The Desktop Agent periodically contacts the server to check for setting changes. If you attempt to change settings after the Desktop Agent has attempted to contact the server and is aware that it is not available, you will be told that settings cannot be changed until the server is available. If the server has recently gone down and the Desktop Agent is not aware that it is unavailable, you will be able to select new settings, but will receive an error message when you try to save the new settings. This message will indicate that configuration settings failed to load because the media server is unavailable. Note Changing settings on one Desktop Agent causes settings to be loaded on other Desktop Agents that use the same authentication. This will cancel and restart any running jobs. When the DLO administrator changes Profile settings, the Desktop Agent scans all files selected for backup on each desktop computers assigned to the Profile.
1249
Changing Backup Job Schedule Options

You can change backup job schedule options if the DLO administrator has set your Profile so that you can view the complete Desktop Agent and modify settings. To change schedule options: 1. Under Views in the Tasks Bar, click Settings, and then click the Schedule tab. 2. Select the appropriate options as follows, and then click OK:
Job Schedule Options Item Use Profile schedule Description Select this option to use the scheduling options specified in the Profile. Note If this option is selected, additional settings on the Schedule tab cannot be modified. Use customized schedule Select this option to specify a customized schedule that differs from the Profile schedule. Run jobs: Whenever a file changes Select this option to back up files automatically whenever they change. Note Automatic backup whenever a file changes is available only for NTFS file systems. For FAT file systems, enter a backup interval. According to a schedule Select this option to back up files according to a schedule. The default is to run a backup at 11:00 PM every Monday, Tuesday, Wednesday, Thursday, and Friday. Click Modify... to change this default. Manually Select this option to run a backup only when you initiate it.
1250
Using the Desktop Agent Job Schedule Options (continued) Item Options: Automatically run jobs when logging on Select this option to start the backup jobs when you log on. Note This option is only applicable when backing up according to a schedule or manually. Select this option to start the backup jobs when you log off. Note This option is only applicable when backing up according to a schedule or manually. Description
Automatically run jobs when logging off
Moving the Desktop User Data Folder

You can change the location of the Desktop User Data Folder if the DLO administrator has set your Profile so that you can view and modify the complete Desktop Agent and modify settings.
Note Only the last backup is stored in the DLO database, so it is not possible to report a complete history of failed jobs. Only the last backup result for each desktop computer is available.
To change the location of the Desktop User Data Folder: 1. Under Views in the Tasks Bar, click Settings. 2. Click the Backup Folders tab. 3. Click Move.
1251
Using the Desktop Agent Settings Dialog Box, Backup Folders tab
4. In the Browse for folder dialog box, choose a new location for the Desktop User Data Folder. 5. Click OK twice.
Setting Customized Options

You can change additional options, such as disk space used by the Desktop User Data Folder, if the DLO administrator has set your Profile so that you can view the complete Desktop Agent and modify settings. To set customized options: 1. Under Views in the Tasks Bar, click Settings, and then click the Options tab. 2. Select Use custom options from the drop down menu.
1252

Options Dialog Box Item Use Profile options Description Select this option from the drop down menu to use settings specified in the Profile. Note If this option is selected, additional settings on the Options tab cannot be modified. Use customized options Select this option from the drop down menu to specify settings that differ from the Profile options. Note This option must be selected to enable access to additional settings on the Options tab. Limit disk space usage on my computer to: % Select this option to enter a percentage of the hard disk space that can be used to store backup files. MB Select this option to enter a limit in MB on the maximum amount of disk space to be used by the Desktop Agent to store backup files. Log file maintenance Keep log files for a minimum of (days) Specify the minimum number of days to keep log files. Log files will not be deleted until they are at least as old as specified. Note Log grooming occurs each time a log is created. Log files will not be deleted until the minimum age has been reached and, when the combined size of all log files, which is set below, is also reached. After minimum number Enter the maximum combined size of all log files to be retained of days, delete oldest before the oldest log files are deleted. log files when Note You may have more than the specified number of MB of log combined size exceeds files stored if none of the log files are as old as specified in the keep log files for a minimum of (days) setting. Logging options Log groom messages Log information messages for backup Check to create logs for grooming operations. Check to create logs for all backup operations.
1253
Using the Desktop Agent Options Dialog Box (continued) Item Log warning messages Description Check to create logs for all operations that generate warnings.
Enable incremental Check to enable incremental backups of Microsoft Outlook backups of Outlook PST Personal Folder (PST) files. Incremental backups must be enabled files to allow PST files to be backed up while they are open. If this option is not checked, PST files that are configured in Outlook will be fully backed up each time the PST file is saved, which generally occurs when Outlook is closed. When Outlook PST files are backed up incrementally, only one revision is maintained regardless of the number of revisions set in the backup selection. Note DLO is unable to perform incremental backups of Outlook PST files unless Outlook is your default mail application. When you restore Microsoft Outlook PST files, the restored PST file will differ from the original PST file as explained in Restoring Microsoft Outlook Personal Folder Files on page 1268. Synchronized files cannot be backed up incrementally. For additional information, see Backing up Outlook PST files on page 1247.
Synchronizing Desktop User Data

Your backed up data is stored in the Desktop User Data Folder on the local drive of each desktop running the Desktop Agent, and in the Network User Data Folder. If you have multiple desktops, your Network User Data Folder contains copies of backed up files from each desktop. When a folder is synchronized using the Desktop Agent, only one copy of the folder and its contents is included in the Network User Data Folder. When the file is changed on one desktop, it is stored in the Desktop User Data Folder on that computer, and then uploaded to the Network User Data Folder the next time a DLO job is run. It is then available for download to another synchronized desktop computer the next time that computer runs a job. After a folder is synchronized, the Desktop Agent checks the Network User Data Folder each time the desktop is connected to the network and a job is run. If new file versions are available in any of the synchronized folders, the Desktop Agent downloads the new version to the User Data Folder on the desktop. If you change a file on your current desktop and change the same file on one of your other backed up computers without synchronizing the files, a conflict will occur and you will be prompted to select which file revision to use.
1254
By synchronizing backed-up data, you can work on a file on any of your desktops with the assurance that you are working on the most recent version. The Synchronized Selections view displays folders backed up on your other desktops that are available for synchronization. Select any of these folders that you want to synchronize with the current desktop computer.
Synchronized Selections View
Note If you customize NTFS permissions or folder attributes for compression or encryption, you must reapply these settings after restoration or synchronization.
How Synchronization Works

When a DLO job runs, DLO does the following to back up and synchronize files:

Backs up files that changed on the desktop. Makes synchronized files available to the other computers with which the desktop is synchronized. Downloads synchronized files that were changed on another computer and uploaded since the last DLO job ran. Retains all conflicting versions of files. You can then choose which version to use.
1255
When you back up files, you can set various filters, such as which types of files to include, exclude, compress or encrypt. When you synchronize files between computers, the filters are combined. For example, if one of the synchronized files is compressed and encrypted, all synchronized files will be compressed and encrypted automatically. If the number of files backed up on different computers varies, DLO synchronizes the largest number of files. For example, if you back up three files on computer A and back up five files on computer B, DLO synchronizes five files. You can manage synchronization using the following options:

Standard view: Enables you to create new synchronization sets. Advanced view: Enables you to modify settings for each synchronization set.
Note In order to use the synchronization feature, the clocks on all of the users computers must be synchronized. To synchronize a folder across multiple desktops: 1. Under Views in the Desktop Agent Tasks Bar, click Synchronized Selections. 2. Click Standard view. Desktops available for synchronization appear in the Remote Computers pane. Note A desktop must have the same owner and must be backed up with the Desktop Agent to appear in the Synchronized Selections view. Only backed up folders are available for synchronization. 3. Select the folders that you want to synchronize. 4. When the Choose Local Folder dialog box appears, type or browse to the location where the synchronized files are to be stored. 5. Click OK. 6. Click Save changes to save the selections or Undo changes to return to the last saved settings. To view or change a synchronized folder: 1. Under Views in the Tasks Bar, click Synchronized Selections. 2. Select the Advanced view radio button.
1256
3. Click on the folder to be viewed or modified. 4. Click Modify. The General tab in the Synchronized Folder dialog box identifies the location where synchronized files from this selection will be stored, and also lists other computers synchronizing with the selected folder. 5. Configure the synchronization folder settings as described for backup selection configuration, beginning with step 5 on page 1242. 6. Click OK. To remove a synchronized folder: Note When a synchronized selection is deleted, the backup files are deleted in the same manner as when source files are deleted. They will be groomed away after the number of days specified in the backup selection. 1. Under Views in the Tasks Bar, click Synchronized Selections. 2. Click the Advanced View radio button. 3. Click the synchronization selection to be deleted. 4. Click Remove. 5. When prompted, if you want to delete the backup selection, click Yes to continue or No to cancel.
Resolving Conflicts with Synchronized Files

If a synchronized file is modified on more than one computer without updating the file with the Desktop Agent, a conflict will occur and you will be prompted to determine which file version to keep. For example, a conflict will occur if the same file is modified on both your desktop computer and your laptop and your laptop is disconnected from the network. When your laptop is subsequently connected to the network, the conflict will be detected. To resolve a conflict with a synchronized file: 1. Under Views in the Tasks Bar, click Status. If a conflict is identified, a resolve conflicts button will appear in the Status view.
1257
Using the Desktop Agent Resolve Conflicts
2. Click the Resolve conflicts button to open the Resolve Conflicts wizard. 3. Click Next. 4. Select the file you wish to resolve. 5. Click the Open Folder button. 6. Manage the revisions as desired. For example, to keep an older revision, you can delete the newer revision and rename the conflicting revision back to it's original name. 7. Click Finish.
1258
Viewing the Desktop Agent Status

The Desktop Agent Status view provides a summary of Desktop Agent operations, including:
Desktop Agent Operations Item Status Description Displays the current state of Desktop Agent jobs, displays when backups will run, and summarizes the results of the last backup. This link is located just below the status summary if a backup selection has been made for a FAT drive. It provides scheduling details based on current Desktop Agent settings.
Details
Show/Hide Pending Files Hides or displays pending files. This selection toggles between Hide pending files and Show pending files when you click on the link. Usage Summary Network Usage Displays the total amount of data stored in the Network User Data Folder for this computer. Displays the total amount of data stored in the Desktop User Data Folder on this computer. This link is located just below the status summary and provides detailed information on folder usage for user data. For additional information, see Viewing Usage Details on page 1260.
Local Usage
Details
1259
Using the Desktop Agent Desktop Agent Status View
Starting a Pending Job in the Status View

To run a pending job from the Status view: 1. Under Views in the Tasks Bar, click Status. 2. Under Tasks in the Tasks Bar, click Run job. All pending jobs will be run, such as backup, synchronization or restore jobs.
Viewing Usage Details

The Desktop Agent Status view provides a summary of information on both local and network disk space used to store your data. Additional usage details and a grooming function are available in the Usage Details dialog:
Total disk space currently used on the network and desktop computer to store your backup data. Quotas, or maximum allowed storage space which can be used to store your data on the network and desktop computers. The disk space available on the network and desktop computer for storing your data.
1260

An option to immediately delete old revisions and deleted files. Links to additional information and help.
Note The link to usage details is only available when the Desktop Agent is idle. It will not be shown when a job is running. To view usage details and groom files: 1. Under Views in the Tasks Bar, click Status. 2. Under Usage Summary in the Status pane, click Details to open the Usage Details dialog.
Usage Details
1261
3. Review the usage information and take the appropriate actions as described below:
Usage Details Item User Data Folder Usage Local Summarizes disk space usage on the desktop computer for storing your data. The following information is provided: Using - The total disk space on the desktop computer currently being utilized to store your backup data. Quota - The maximum amount of disk space you can use to store your backup data on the desktop computer. The quota limit is set by the administrator in the Profile, but can be modified from the Desktop Agent Settings view if you have been given rights to modify settings. For additional information, see Modifying Desktop Agent Settings on page 1249. Available - The amount of free disk space available on the desktop computer for storing your data without exceeding a quota. If there is no quota, the Desktop Agent will reserve a small amount of disk space so the drive will not fill completely with backup data. Network Summarizes disk space usage on the network for storing your data. The following information is provided: Using - The total disk space on the network currently being utilized to store your backup data. Quota - The maximum amount of disk space you can use to store your backup data on the network. Available - The amount of free disk space available on the network for storing backup data for the current user without exceeding a quota. Description
1262
Using the Desktop Agent Usage Details (continued) Item Remove deleted files Description Select to immediately and permanently delete all files that are marked as deleted in your Network and Desktop User Data Folders. The periodic maintenance cycle will otherwise delete these files after the amount of time specified in your assigned Profile. Clicking this button will open the Remove Deleted Files dialog. Choose from the following options:
Remove only the deleted files that currently meet the backup selection deleted files criteria. Remove all deleted files.
Check the Remove files from the network user data folder checkbox to additionally groom deleted files from the Network User Data Folder. Additional information Click here to close this dialog and view your backup selections Some backup selections may have different revision and compression settings, which could contribute to the differences between local and network usage statistics. Click this link to view your backup selections. Click here to view last job log Click here to open the Log File Viewer. For additional information on the log file viewer, see Monitoring Job History in the Desktop Agent on page 1269.
1263
Restoring Files Using the Desktop Agent

If the DLO administrator has set your Profile to include restoring files, then you can use the Desktop Agent to restore files to the original or an alternate directory. If a Desktop Agent user has more than one desktop computer running DLO, files can be selected from all available backups on each of the users desktops, but can only be restored to the current desktop computer. For information on backing up and restoring Microsoft Outlook PST files, see Backing up Outlook PST files on page 1247 and Restoring Microsoft Outlook Personal Folder Files on page 1268.
Restore View
Caution If you attempt to connect to a server using characters in the share name that do not exist on the code page for the local system, the connection will fail. Code pages map character codes to individual characters, and are typically specific to a language or group of languages. If you customize NTFS permissions or directory attributes, such as compression or encryption for files or folders, you must reapply these settings after restoration. To restore files that are locked after the computer reboots, you must have local administrator rights.
1264
If you disconnect from the network while the Desktop Agent is running, you may encounter a slow response when browsing the Restore view. From the Tasks menu, select Refresh to fix this problem. To restore data: 1. Under Views in the Tasks Bar, click Restore. 2. In Show, select one of the following revision display options:
Restore File Version Display Options Item All revisions Description All file revisions will be displayed and available as restore selections. Only the latest file revision will be displayed and available as a restore selection. If selected, enter a date and time after which revisions will be displayed and available as restore selections, then click OK.
Latest revision
Revisions modified on or after
3. Select the items you want to restore. In some cases the Restore Search view may contain duplicate entries for the same file. If this occurs, you can select either file to restore and receive the same outcome. Note When you delete a file, the backup files are retained until they are deleted by the file grooming process. If an original file has been deleted, but backup files are still available, the icon for the file in the restore view will have a small red x to indicate the deletion of the original file. See File Grooming on page 1239 for additional information. 4. Click Restore.
1265
Using the Desktop Agent Restore Dialog Box

Restore Dialog Box Options Item Description
Restore to the original Select this option to restore files and folders to their original folders on this computer location. Redirect the restore to an alternate folder on this computer Preserve folder structure Select this option to restore files and folders to an alternate folder on the same computer.
Select to restore the data with its original directory structure. If you clear this option, all data (including the data in subdirectories) is restored to the path you specify.
Options If file already exists Select one of the following:

Do not overwrite Prompt Overwrite
Restore deleted files
Select this option if you want to restore files even though the source file has been deleted.
1266
Searching for Desktop Files to Restore

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

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

When you restore Microsoft Outlook Personal Folder (PST) files, the following differences will exist between the restored PST and the original PST:

The file size will be different. Any rule that points to a folder inside a PST file will no longer work. You must edit the rule to point to the correct folder. Restored PST files will have Inbox, Outbox, and Sent Items folders, even if the original files did not have them. If you use a password for your PST file, you must reset the password after restoring your PST file.
Related Topics: Backing up Outlook PST files on page 1247
1268
Monitoring Job History in the Desktop Agent

When a backup, restore, or synchronization operation takes place, details of that operation are stored in log files. Log files can be viewed, searched and saved as text files. The History View summarizes the following information and provides access to the full logs.
Job History View Information Item Started Ended Status Description The date and time the operation started The date and time the operation ended The status of the job, such as Active, Completed, Canceled or Failed. The total number of files transferred to the Desktop User Data Folder during the listed job. The total number of bytes of data transferred to the Desktop User Data Folder during the listed job. The total number of files transferred to the Network User Data Folder during the listed job. The total number of bytes of data transferred to the Network User Data Folder during the listed job. The number of files that failed to copy and produced errors.
Files Transferred (Local)
Size Transferred (Local)
Files Transferred (Network)
Size Transferred (Network)
Errors
1269
Using the Desktop Agent History View
Viewing Log Files

To view history logs: 1. Under Views in the Tasks Bar, click History. 2. To view backup logs, select the Backup tab, or to view restore logs, select the Restore tab. 3. Select the appropriate History view filter from the Show drop down menu as follows:
History View Filtering Options Item All logs All logs with errors Description All history logs are displayed History logs for all jobs that generated errors are displayed.
1270
Using the Desktop Agent History View Filtering Options (continued) Item Logs filtered by date Description All logs generated after a specified date and time are displayed. Enter the date and time after which logs are to be displayed in the Filter by date dialog box and click OK.
4. Click the job history entry for which you want to view the history log. 5. Click View log to open the log file viewer. 6. If desired, click Save As to save the log file as a text file. 7. Click Close to exit the log file viewer.
Searching for Log Files

The Log File Viewer has a powerful search mechanism to help you locate the log files you want to view. To search for log files: 1. Under Views in the Tasks bar, click History. 2. Click the Search link, which is located under the History pane, to open the Log File Viewer. 3. Enter filtering parameters as described below:
Log File Viewer Filtering Options Item Search for log entries in All log files Current log file Select this option to show all log entries in the log file viewer. Select this option to search only those log entries in the current log file. Description
1271
Using the Desktop Agent Log File Viewer Filtering Options (continued) Item With timestamp Description Check the With Timestamp box to search only those log entries within a specified time period. The options include: Today - Show only log files that were created today. Within the last week - Show all log files created in the last week. Between dates - Show all log files created between the dates entered. With Type Check the With Type checkbox to show only logs of the indicated type. You may select one of the following types:

Backup Restore Move User Maintenance Error Warning
With Filename like
Check the With Filename like checkbox and enter a filename, or file type. Wildcard entries are supported. Example: *gold.doc Note When using wildcards you must use the * wildcard. For example, *.tmp will return all results with the .tmp extension while .tmp will return only files explicitly named .tmp.
Filter All entries All entries except maintenance Failed entries only Warning entries only Maintenance entries only Display all matching log entries regardless of type. Select this option to display all entries other than those for maintenance operations, such as the grooming of deleted files. Select this option to display only entries for failed operations. Select this option to display only entries for warnings. Select this option to show only logs that reflect maintenance operations, such as the grooming of deleted files.
Local data folder entries Select this option to display all log entries for Desktop User Data only Folders.
1272
Using the Desktop Agent Log File Viewer Filtering Options (continued) Item Failed local data folder entries only Network data folder entries only Failed network data folder entries only Debug entries only Description Select this option to display only entries for failed Desktop User Data Folder operations. Select this option to display all log entries for Network User Data Folders. Select this option to only display entries for failed Network User Data Folder operations. Only debug entries are displayed.
4. Click Search. 5. To view detailed information for a log file entry, expand the tree view for the entry by clicking on the + checkbox.
Expanding a log file entry
6. If desired, click Save As to save the log file as a text file. 7. Click Close when finished.
1273
Troubleshooting
Log file grooming

Log grooming occurs each time a log is created. Log files are not deleted until they have reached both the minimum age and maximum combined size of all log files settings. If the administrator has granted you sufficient rights in your Profile, you can modify these settings in the Desktop Agent settings Options tab as described in Setting Customized Options on page 1252.
Troubleshooting
This section addresses problems or questions that may be encountered while running the DLO Administration Console or the Desktop Agent, and provides solutions for these problems. It is divided into the following two sections:

Troubleshooting the DLO Administration Console Troubleshooting the Desktop Agent
Troubleshooting the DLO Administration Console

I modified an Automated User Assignment, but the change isnt reflected for existing Desktop Agent users. Automated User Assignments are only used once to assign a Profile and Storage Location to a new DLO user. An Automated User Assignment can be modified to change the Profile and Storage Location settings, but these changes will only apply to new users. Users that have already been configured will not be affected by subsequent changes in the Automated User Assignment. This also applies to existing users who install the Desktop Agent on another desktop. The new installation will use the existing user settings and will store data in the users existing User Data Folder. Automated User Assignment changes will not affect an existing user, even if the Desktop Agent installation is on a new computer. Settings for an existing desktop user can be changed by modifying the Profile to which the user is assigned, or by reassigning that user to a new Profile or Storage Location. Related Topics: Modifying DLO Desktop Agent User Properties on page 1180 Managing Desktop Agent Users on page 1177 Setting up Automated User Assignments on page 1168
1274
Troubleshooting
Setting up a DLO Profile on page 1146 Moving a Desktop Agent User on page 1182 A desktop user ran the Desktop Agent and received an error indicating Unable to configure the Desktop Agent. No settings found for the current user and no automatic user assignments match. What does this mean? This message means that DLO could not find the user or an Automated User Assignment that matched the user's domain and group. Users are added to DLO in one of two ways: 1. An Automated User Assignment that matches the users domain and group assigns a Profile and Storage Location to the Desktop Agent and adds the user to DLO. Check that you have created Automated User Assignments that match the Domain and Group to which the user running the Desktop Agent belongs. You can also create an Automated User Assignment that will cover all domains and all groups in order to catch any users who might not match a more specific Automated User Assignment. Such a catchall Automated User Assignment would typically be set to the lowest priority. 2. Users are manually added to DLO. This process requires that you assign a Profile and either a Storage Location or User Data Folder to the new user. Be sure that the user has a matching Automated User Assignment, or is added manually before running the Desktop Agent. Related Topics: Setting up Automated User Assignments on page 1168 When do I need a Network User Data Folder, and when do I need a Storage Location? Every Desktop Agent user must have a Network User Data Folder, which is used to store backup data. Storage Locations are locations on the network where Network User Data Folders are automatically created and maintained. They are not required if existing network shares are used to store user data. If you want DLO to automatically create Network User Data Folders, use a Storage Location. When new users are added to a Storage Location, Network User Data Folders are automatically created for them within the Storage Location. Alternately, if you would like to use existing network shares as Network User Data Folders, or if you want to create Network User Data Folders manually, then do not use Storage Locations.
1275
Troubleshooting
Related Topics: Setting Up DLO on page 1145 I'm trying to create a Storage Location on a remote file server, and I am receiving an error indicating the MSDE Database Instance for the Desktop and Laptop Option needs to have access to the remote file server. What do I need to do? In order to create Storage Locations on a remote file server, you must use an account that has administrative rights on the remote file server. To change the account credentials used to create the Storage Location: 1. On the Tools menu, select Manage Service Credentials. 2. Select Change Service Account Information.er 3. Enter account credentials as follows:
Service Account Information Item Description
Change service account Check to change the service account information information User name Domain name Password Confirm password Enter the user name for the account to be used. Enter the domain for this account. Enter the password for this account. Enter the password again to confirm.
Using a Domain Administrator account is recommended. In order to create Storage Locations in another Domain, there must be appropriate trust relationships in effect. I manually added a new user and assigned the user to an existing Storage Location. I don't see a new User Data Folder for the new user in this Storage Location. Isn't it supposed to create one? User Data Folders are created only after the Desktop Agent is both installed on the desktop and run by the new user.
1276
Troubleshooting
How do I prevent a user from backing up data? 1. On the navigation bar, click Setup. In the Settings pane, click Users. 2. Select the user you do not want to be able to perform backups. 3. Under General Tasks in the Tasks pane, select Properties. 4. Clear the Enable user check box. 5. Select OK. The user's status will display as Disabled. In a Backup Selection, I selected to encrypt or compress my user's data. However, data that has already been backed up is not encrypted or compressed. Why is this? DLO does not retroactively apply changes to encryption and compression settings to user data that is already backed up. Any data backed up after these settings have changed will use the new settings. I would like to prevent files of specific types from being backed up. How can I set up DLO to always exclude files like *.mp3 or *.gho? On the Tools menu, select Global Excludes. In this dialog box, you can add specific file types that will be excluded in all Backup Selections for all Profiles. Backups do not seem to be running for all users, or specific files are not being backed up. If backup jobs are not running for a group of users, check the Profile for these users to verify that backups are scheduled. If specific files are not being backed up, review the Backup Selections in the Profile to verify that the files are selected for backup. I just tried to restore a file, but it doesnt appear to have been restored. When restoring existing files to their original location, verify that you have selected Prompt or Overwrite in the Restore dialog box to replace the file. If you select Do not overwrite, the file will not be restored. In a Profile, I configured backup selections to encrypt files. Now I need to recover files for a user. Do I need an encryption key in order to restore this data? As an Administrator running the DLO Administration Console, you can redirect a restore of encrypted user data to an alternate computer or location, and it will be decrypted during the restore.
1277
Troubleshooting
I would like to restore data to a user's computer, but that user is out of the office. Do I have to wait until that user returns to the office before I can start the restore? DLO can queue restore jobs to desktops. If the user is offline now, you can queue a restore job through the Restore view in the DLO Administration console. Another option is to restore the data to an alternate location, such as the administration computer or a network drive. How can I protect open files? DLO does not protect open files. It will attempt to back up files when they are closed or saved. If a file cannot be backed up because it is open (for example, a Word document you are editing) it will remain in the Desktop Agent's pending list. The Desktop Agent will attempt to back up the file at the next backup time. This also means that certain files opened by the operating system will not be backed up, they never close when the operating system is running. The exception to this is protection of open PST files. The Desktop Agent is designed to protect open PST files if they are part of the Profile or user's backup selections. Incremental backups must be enabled for open file backups of PST files. Related Topics: Excluding Files that are Always Open on page 1127 The History view in the DLO Administration Console doesnt show the most recent backup for all users. The DLO Administration Console is automatically updated when a job runs, but not more than once per hour.
Troubleshooting the Desktop Agent

This section addresses potential problems or questions that may be encountered while running the Desktop Agent, and provides solutions for these problems. Do I have to install Backup Exec on every desktop I want to protect? No. You must install the Desktop Agent on every desktop you want to protect. It is not necessary to install Backup Exec. I installed the Desktop and Laptop option, but I do not know how to install the Desktop Agent on users computers. The Desktop Agent can be installed by running the installation program from the share where DLO is installed as described below, or it can be push installed using the Backup Exec installer (see Installing Backup Exec to Remote Computers on page 73).
Troubleshooting
The Desktop Agent installation program is located in a share where you installed DLO. This share will have a name in the following format: \\<Server>\DLOAgent. Using Windows Explorer, browse to this share from the desktop that you want to protect with the Desktop Agent. Run Setup.exe from this share. You must be an administrator on the desktop in order to install the Desktop Agent software. Symantec recommends that DLO administrators run the Configuration Wizard to familiarize themselves with the application. Can I install the Desktop Agent on Windows Servers or media servers? Because the Desktop Agent is designed to protect user data rather than critical server data, it cannot be installed on Windows Servers or media servers. I am receiving the following error while authenticating through the Desktop Agent to the media server: Failed to Initialize database. 0x800A0E7D You attempted to connect to the media server with an account that is not in the same domain, or a trusted domain, as the media server. For DLO to function properly, the media server must be in a Windows Domain. I have a desktop and a laptop computer protected by the Desktop Agent. Why can't I move my laptop to a new Storage Location? When a user has multiple computers running the Desktop Agent, all backup data is stored in the same Network User Data Folder. If you want to move your data to a new Storage Location, you must move the entire Network User Data Folder for all of your computers to that new location. I am trying to synchronize files between my desktop and laptop computers, but I cannot see my other computer in the Synchronization View in the Desktop Agent. In order to synchronize data between two computers, the same user account must be used when running the Desktop Agent on each computer. For example, the user Domain\MyUser must have backed up data on Computer A and Computer B in order for synchronization to take place between these two computers. If you are sure you have backed up data while running the Desktop Agent under the same user account on both of your computers, select Refresh in the Desktop Agent's Synchronization View to make the synchronization selections available. If this is not successful, Exit from the File menu and restart the Desktop Agent application. What files or folders can I synchronize between my computers? Any data backed up by a backup selection are eligible for synchronization. These backup selections may be defined by the DLO Administrator in the Profile or in a Backup Selection created with the Desktop Agent.
1279
Troubleshooting
I would like to share my synchronized data with my co-workers. How can I do this? The Desktop and Laptop Option does not provide functionality for sharing files between users. Synchronization is designed to share files between a single user's computers.
1280
Troubleshooting
DLO Administration Console Error Codes

The following are errors commonly encountered while using the DLO Administration Console. Typical causes and solutions are provided for each listed error.
DLO Administration Console Error Codes Error Code 0xCC000064 Error Message and Description Error Message: Unable to connect to media server. Explanation: DLO is unable to connect to the media server Typical Cause: The media server is unavailable or cannot be reached. Solution: Verify that the media server is installed on the machine you are trying to connect to, and that the database service is running. 0xCC00C846 Error Message: Failed to load Reports. Explanation: There was an error while loading the report files. Typical Cause: Reports may not be installed. Solution: Verify that reports are installed. 0xCC00012C Error Message: Unable to load alerts table Explanation: There was an error while loading the list of alerts. Typical Cause: The database may not be running. Solution: Verify that the database is running.
1281
Troubleshooting DLO Administration Console Error Codes (continued) Error Code 0xCC00038E Error Message and Description Error Message: Access is denied. Explanation: You do not have permissions to access the required resources. Typical Cause: This is reported when trying to enumerate files and folders in the restore view, but the database service does not have permissions to read the files. Solution: Verify that the DLO Administration Console has the Automatically grant DLO administrators access to network user data folders option checked and a valid group is specified. If not, ask Administrator to manually grant read permissions to files and folders. 0xCC0003B6 Error Message: Failed to execute the create group share stored procedure. Explanation: Failed to execute the stored procedure that creates network storage location. Typical Cause: Database is down, or installation is corrupt Solution: Make sure the logon account of the database service and DLO administration service is a domain user account that has admin rights on the machine where you are trying to create a Storage Location. Verify that XPDLOShareu.dll and its dependent DLLs are properly installed in either in <DLO database install>\BINN or <DLO install>directory. Restart the database service and the DLO admin service.
1282
Troubleshooting DLO Administration Console Error Codes (continued) Error Code 0xCC00C404 Error Message and Description Error Message: Workgroups are not supported in this release. A domain is required. Explanation: Workgroups are not supported in this release of DLO. You must be in a domain. Typical Cause: Attempting to operate DLO in a workgroup. Solution: Operate DLO in a domain, not a workgroup.
1283
Troubleshooting
Desktop Agent Error Codes

The following are errors commonly encountered while using the Desktop Agent. Typical causes and solutions are provided for each listed error.
Desktop Agent Errors Error Code 0xC000704C3 Error Message and Description Error Message: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. Explanation: There is still a connection with the server machine that cannot be canceled. Typical Cause: You could have an open connection that was used to install the Desktop Agent, or there could be a connection from a mapped drive. Solution: Manually disconnect, by doing one of the following:

Log off and then log back on. Unmap a drive that is mapped to the server. Right click on My Computer. Choose Manage and then navigate through System Tools > Shared Folders > Sessions and then disconnect.
0xCC000064
Error Message: Unable to connect to media server. Explanation: You may be disconnected from the network or, the media server is unavailable. Typical Cause: This error is shown if you were previously working online and attempted to refresh or change a setting just after the media server went offline. Solution: Verify that your computer is connected to the network and attempt to connect again. If the problem persists, contact your administrator. The server may be temporarily unavailable.
1284
Troubleshooting Desktop Agent Errors (continued) Error Code 0xCC00C422 Error Message and Description Error Message: The user 'domain1/username1' is already using the credentials 'domain2/username2' to log into server. Explanation: DLO requires unique authentication credentials for each computer in order to uniquely identify computer owners. Typical Cause: Multiple users on the same client computer are trying to use the same authentication credentials to the server. Solution: Provide unique authentication credentials for each user on a multi-user computer. 0xE0140007 Error Message: Unable to configure the Desktop Agent. Explanation: No settings or matching Automated User Assignments were found for the current user. Typical Cause: DLO may not have been configured correctly. Solution: Desktop user should contact their administrator to insure they are either pre-configured or have matching Automated User Assignments. For additional information, see Setting Up DLO on page 1145. 0xCC007671L Error Message: Desktop user data folder storage limit has been reached. Explanation: The storage limit that was set by the administrator for the Desktop User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Desktop User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator.
1285
Troubleshooting Desktop Agent Errors (continued) Error Code 0xCC00765DL Error Message and Description Error Message: Network user data folder storage limit has been reached. Explanation: The storage limit that was set by the administrator for the Network User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Network User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator. 0xCC00764AL Error Message: An attempt to copy a file to the desktop user data folder failed due to insufficient disk space. DLO stops copying files to the desktop user data folder when copying an additional file would result in less than x% disk space remaining. Explanation: The storage limit that was set by the administrator for the Desktop User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Desktop User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator.
1286
Troubleshooting Desktop Agent Errors (continued) Error Code 0xCC007636L Error Message and Description Error Message: An attempt to copy a file to the network user data folder failed due to insufficient disk space. Explanation: The storage limit that was set by the administrator for the Network User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Network User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator. 0x8C007666L Error Message: The volume containing the desktop user data folder is approaching its storage limit. There is less than x% of the allotted space remaining. Explanation: The storage limit that was set by the administrator for the Desktop User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Desktop User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator.
1287
Troubleshooting Desktop Agent Errors (continued) Error Code 0x8C007544L Error Message and Description Error Message: Approaching network user data folder storage limit. Explanation: The storage limit that was set by the administrator for the Network User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Network User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator. 0x8C00763EL Error Message: The volume containing the desktop user data folder is running low. There is less than x% disk space remaining. Explanation: The storage limit that was set by the administrator for the Desktop User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Desktop User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator.
1288
Troubleshooting Desktop Agent Errors (continued) Error Code 0x8C00762AL Error Message and Description Error Message: The volume containing the network user data folder is running low. There is less than x% disk space remaining. Explanation: The storage limit that was set by the administrator for the Network User Data Folder has been reached. Typical Cause: You are backing up more data than will fit in the Network User Data Folder. Solution: Reduce the scope of your backups, remove unnecessary data, reduce the number of revisions you are retaining, or talk to your administrator.
1289
Troubleshooting
DLO History Log Errors

The following errors are commonly seen in the DLO History logs. Typical causes and solutions are provided for each listed error.
History Log Errors Error Code 0xE0140002 Error Message and Description Error Message: Object already exists Explanation: Two machines have simultaneously joined a sync set and are attempting to copy the same file to the server. Solution: No action is needed. The files are protected. 0x0140005 Error Message: Access denied Explanation: Insufficient permissions to access a file. Typical Cause: 1. You don't have sufficient permission to read the source file. 2. You don't have sufficient permission to write to the destination folder. Solution: Contact your administrator to change the permissions. 0xE0140006 Error Message: Out of memory Explanation: The system is running low on memory. Typical Cause: 1. Too many applications are open. 2. There is insufficient virtual memory space. The paging file is too small or there is insufficient disk space. Solution: 1. Close one or more applications. 2. Free space on the page-file-volume or increase the paging-file size.
1290
Troubleshooting History Log Errors (continued) Error Code 0xE0140009 Error Message and Description Error Message: Out of disk space Explanation: The destination volume is out of disk space. Solution: Free disk space on the destination volume or increase the quota. 0xE014000D Error Message: Object is locked by another process Explanation: The source file is in use by another process. Typical Cause: A running application is using the file. Solution: Close the application that is using the file. 0xE0140093 Error Message: Network resource unreachable Explanation: The Network User Data Folder cannot be accessed. Typical Cause: The network is disconnected or misconfigured or the file server is offline. Solution: Reconnect to the network, and if the problem persists, contact your administrator. 0xE0140095 Error Message: Bad network path Explanation: The Network User Data Folder is unreachable. Typical Cause: The network is disconnected or misconfigured or the file server is offline. Solution: Reconnect to the network, and if the problem persists, contact your administrator.
1291
Troubleshooting History Log Errors (continued) Error Code 0x80040401 Error Message and Description Error Message: The Outlook PST handler has timed out. Please confirm that Outlook is configured. Explanation: The Outlook PST handler is unable to initialize. Typical Cause: Outlook is installed on the system, but not configured for the logged in user. Solution: Configure Outlook. 0x8007007B Error Message: The filename, directory name, or volume label syntax is incorrect. Explanation: DLO is unable to create the destination file. Typical Cause: 1. The filename contains characters which are not supported on the destination volume. 2. The maximum filename length supported by DLO is 235 characters when using NTFS on Windows XP and prior. 3. The destination volume is unreachable. The volume is corrupt or disconnected from the network. Solution: 1. Simplify the filename. 2. Shorten the filename. 3. Check that the destination volume is available and intact.
1292
Glossary of Terms
Glossary of Terms
Administrator The user that configures DLO using the Backup Exec DLO Administration Console. This user must have administrative rights to operate the console. Authentication The process of validating a users credentials. Automated User Assignments Rules that assign Profiles and Storage Locations to a specified group of desktop users. Settings are applied the first time a user runs the Desktop Agent. Backup Exec Administration Console The administrators interface with Backup Exec. Compression A method of reducing data to expedite transmission time or storage volume. DLO Administration Console The administrators interface with the Desktop and Laptop Option. DLO backup selection The files and folders on a desktop or laptop that are selected for backup by the DLO Administrator or desktop user. DLO database The location where policy settings and status information are stored. DLO file server The computer that hosts DLO Storage Locations. This computer can be the Backup Exec media server or another server. Desktop Agent install share The network share where the Desktop Agent install files are located. This folder is set up on the Backup Exec media server when DLO is installed, and facilitates the installation of the Desktop Agent on desktops.
1293
Glossary of Terms
DLO Storage Location A shared location on the network in which Network User Data Folders and backup files are stored. Desktop Agent The DLO software that runs on desktop and laptop computers. Desktop Agent console The user interface for the Desktop Agent software. Encryption A process used to ensure data security of files and folders on disk and during data transfer. Open file handling The process by which files currently in use can be backed up. Optimization The process of reducing network traffic and file storage through technologies such as compression. Profile DLO settings configured by the administrator and that apply to users or groups of users. Revision A version of a file at a specific point in time. Synchronization The process that maintains the most recent version of selected files and folders belonging to the same user on multiple desktops. Synchronization is available for files and folders that are backed up by DLO. Task An accessible program function that varies with the view selected in the DLO administration console or Desktop Agent console. User The person who operates the desktop or laptop computer on which the Desktop Agent is run.
Glossary of Terms
User data folder The folder in which user backup data is stored. There is a User Data Folder on each desktop that is protected by the Desktop Agent, and one User Data Folder on the network for each Desktop Agent user. User name The user name used for Windows authentication. View The main navigational interface in the DLO Administration Console.
1295
Glossary of Terms
1296
Appendix
Symantec Backup Exec Agent for Oracle Server

The Backup Exec for Windows Servers 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 database 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.
1297
Requirements for Using the Oracle Agent
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.
Requirements for Using the Oracle Agent

The following software must be installed before you can use the Oracle Agent:

Windows 2000, Windows XP, or Windows Server 2003. Backup Exec for Windows Servers 9.x or later. One of the following supported databases: Oracle Database Server Version 8.0.5, 8i, 9i, or 10g, 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. Attempting to back these files up may also cause the Oracle database to become unresponsive.
1298
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 data file 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.
Appendix M, Symantec Backup Exec - Agent for Oracle Server
1299
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 media server backs up the Becf<Sid_Name>.bak file from this directory. When this file is restored from the storage media, it is automatically placed in the Oracle data file directory on the database server. By default, it is \Orant\Database.
Requirements for Configuring the Oracle Agent

Before you install and configure the Oracle Agent, 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 be used 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. If Oracle Database Server version 10g, the Archive Log Location must be configured as a single directory. (Oracle 10g by default creates a Flash Recovery tree of directories. The Backup Exec Oracle Agent only protects a single directory, therefore Oracle Enterprise Manager must be used to create a single directory for storing the Archived Logfiles.)
Related Topics: Creating a New Oracle User Account for the Oracle Agent on page 1301 Verifying ARCHIVELOG Mode and Automatic Archival Settings on page 1302
1300
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 for the Backup Exec Oracle Agent: 1. Using Oracle SQL Plus or another management tool, connect to the Oracle server with an administration account, and at the command line prompt, type: CREATE USER BNAME IDENTIFIED BY BPASSWORD; Where BNAME is the account name and BPASSWORD is the password used by the account. 2. After the user is created, type: GRANT UNLIMITED TABLESPACE TO BNAME; 3. After the tablespace is granted, type: GRANT AQ_ADMINISTRATOR_ROLE TO BNAME; 4. After the administrator role is granted, type: GRANT DBA TO BNAME; 5. After the DBA is granted, type: ALTER USER BNAME DEFAULT ROLE ALL; 6. After the user has been altered, type: ALTER USER BNAME DEFAULT TABLESPACE SYSTEM; 7. Verify that this account was created correctly by using the account to connect to the Oracle server: CONNECT BNAME/BPASSWORD 8. Verify the roles and privileges associated with this account by typing the following SQL query: SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS WHERE GRANTEE='BNAME' UNION SELECT GRANTEE, GRANTED_ROLE FROM DBA_ROLE_PRIVS WHERE GRANTEE='BNAME'; The following privileges should be displayed:
1301

AQ_ADMINISTRATOR_ROLE DBA UNLIMITED TABLESPACE.
9. If these privileges are not displayed, repeat the GRANT commands in step 2 through step 4. to establish the privileges associated with this account. 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: 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 Note If you cannot enable Automatic Archival in the Oracle instance initialization parameter file, you can enable it using the Oracle Servers Enterprise Manager. Log on as SYSDBA, and then right-click the Instance Configuration. Select the Recovery tab, and then select Automatic Archival. 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 three instances of redo logs. 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.
1303
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.
1304
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 data file definitions to make sure they use fully specified paths. Use the following SQL command from the SQLDBA program to check the data file 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. Related Topics: Renaming Data Files From a Single Tablespace on page 1305
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 data file '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.
1305
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 and the job 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 recorded in the application event log and in the job 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.
1306
Installing the Oracle Agent

The Oracle Agent is installed locally as a separate, add-on component of Backup Exec for Windows Servers, and can protect local or remote 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 to the Local Computer on page 71. For instructions on installing the Remote Agent on a remote resource, see Installing Backup Exec Agents to Remote Computers on page 77. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line on page 794. Note The Oracle Agent must be installed on the media server. If Backup Exec is not already installed, see Installing Backup Exec on page 57. 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> 2. Double-click Setup.exe.
Appendix M, Symantec Backup Exec - Agent for Oracle Server 1307
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. Related Topics: Installing the Remote Agent to Remote Windows Computers on page 793
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, point to Programs, and then click Symantec Agent for Oracle Server Configuration Utility.
1308
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. For Backup Exec 9.x and later, to access the Oracle Agent and backup or restore the Oracle resources, you must create a Backup Exec logon account that uses the same password as the one entered here. The logon account user name is ignored. Add this logon account as the resource credential for the Oracle resource. For more information, see Configuring Logon Accounts on page 386 and Changing and Testing Logon Accounts for Resources on page 292. 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.
Configured Media Servers 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.
1309

Oracle SID options 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 1301. 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.
User
Confirm Archived Logfile Location
Control File Backup Location
5. Click OK.
1310
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 Symantec Agent for Oracle Server Configuration Utility. 2. Click the General tab. 3. Click Add. 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.
1311
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.
Related Topics: Backing Up an Entire Online Database on page 1312 Backing Up Individual Online Tablespaces on page 1314 Backing Up a Closed Database on page 1315
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: 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.
1312
5. Expand the Oracle database server that you want to back up. If you have previously password-protected the Oracle Agent, the Logon Account Selection dialog box appears. 6. Select the logon account to use, then click OK. 7. 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. 8. Complete the backup settings as normal. For more information, see Creating a Backup Job on page 261.
1313
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, the Logon Account Selection dialog box appears. 6. Select the logon account to use, then click OK. 7. 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. 8. Click the box preceding the tablespace folders you want to back up. Make sure you also select the {Archived Logfiles} folder.
A check mark appears in the box, indicating that only the specified tablespaces, along with the Archived Logfile data, will be backed up. 9. 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 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.
1315
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.
1316
Restoring an Online Oracle Database

Use the following procedure when the database is operational, but you want to restore the entire database to a prior state for which you have an online backup. Before using this procedure, make sure that:

The Oracle Database Server is operational. Database administration can be performed. All the tablespaces that you want to restore have been defined. The Oracle Agent has been started on the database server.
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.
1317
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

To restore a closed Oracle database: 1. Close the database by typing the following command: shutdown; 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.
1318
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 may generate an error when the database is initialized. 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.
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.
Appendix M, Symantec Backup Exec - Agent for Oracle Server 1319
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.
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 data file 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.
1320
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.
Related Topics: Recovering a Remote Oracle Database Server from a Disaster on page 1322 Recovering a Combination Oracle Database Server/Media Server on page 1323
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. Related Topics: Backing Up Individual Online Tablespaces on page 1314
1321
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. 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. Disaster recovery of the Oracle database server is now complete.
1322
Related Topics: Restoring an Online Oracle Database on page 1317 Restoring Individual Tablespaces on page 1319
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. 2. Re-install Backup Exec. 3. After re-installing Backup Exec, recatalog the media. 4. Run another restore operation. This time, use the Oracle Agent to restore the media containing all of the Oracle tablespace data files. 5. When the restore operation completes, start the Oracle Server Manager. 6. Connect as System, as a SYSDBA. 7. Type Recover. 8. 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. Disaster recovery of the Oracle database server is now complete. Related Topics: Disaster Recovery Prerequisites on page 1321 Restoring Individual Tablespaces on page 1319
1323
Oracle Agent Error Message Chart

The following chart lists possible Oracle Agent error messages and solutions. Errors are reported in the job log, and because the Backup Exec Oracle Agent runs as a system service on the Oracle database server, error messages are also reported in 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. (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 Unable to access Oracle datafile (%1). Oracle data files must be defined using a full path specification! The Oracle Agent was unable to complete the command. Check the Oracle database server code documentation for information about the particular status code.
The Oracle Agent is unable to access the named data file. Verify that the data file was defined using a fully specified path.
1324
Oracle Agent Error Message Chart Oracle Agent Error messages Application Log Error Message (continued) Unable to logon to the Oracle server. Oracle user account name %1 Solution (continued) 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 SID = %1 Verify that the Oracle SQL Net configuration (Tnsnames.ora) has been set up properly for the named SID. In order to backup online tablespaces and archive logs, Oracle database must be in ARCHIVELOG mode. See Verifying ARCHIVELOG Mode and Automatic Archival Settings on page 1302.
The Oracle database %s has not been started in ARCHIVELOG mode. Please check that ARCHIVELOG is enabled for the database and then try again.
1325
1326
Appendix
Symantec Backup Exec Agent for Lotus Domino

The Symantec 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.
Related Topics: Installing the Lotus Domino Agent on the Media Server on page 1329
1327
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. Note Backup Exec does not support two versions of Lotus Domino on the same computer. If the Lotus Domino files you want to back up are on the local media server, the server must have:

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

Windows operating system Backup Exec Remote Agent for Windows Servers An Intel-compatible processor Corresponding Windows Administrative Share for each volume that contains Lotus Domino databases The Lotus Domino data directory on the Lotus Domino server Transaction logging must be enabled to perform differential and incremental backups and to perform point in time recovery. The Lotus Domino logging style must be set to archive if you want to back up the transaction logs.
Following are requirements for backing up Lotus Domino transaction logs:
Related Topics: Viewing and Selecting Lotus Domino Databases on page 1330
1328
Installing the Lotus Domino Agent on the Media Server
Installing the Lotus Domino Agent on the Media Server

The Symantec Backup Exec Agent for Lotus Domino is installed locally as a separate, add-on component of Backup Exec for Windows Servers, and can protect local or remote Lotus Domino databases. 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 to the Local Computer on page 71. For instructions on installing the Remote Agent on a remote resource, see Installing Backup Exec Agents to Remote Computers on page 77. For instructions on moving the Remote Agent to another remote Windows computer, see Installing and Uninstalling the 32-bit Remote Agent to Remote Windows Computers Using the Command Line on page 794. Related Topics: Configuring Default Lotus Domino Options on page 1332 Backing Up Lotus Domino Databases on page 1332 Restoring Lotus Domino Databases on page 1337
Appendix N, Symantec Backup Exec - Agent for Lotus Domino
1329
Viewing and Selecting Lotus Domino Databases
Viewing and Selecting Lotus Domino Databases

After installing the Lotus Domino Agent, you can view and select existing Lotus Domino databases in the selections pane. To view databases created while Backup Exec is running, select Refresh from the View menu or press F5. To back up the newly-created database, select it from the volume level, unless the entire volume is already selected for backup. 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. 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.
1330
Viewing and Selecting Lotus Domino Databases 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. 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. Related Topics: Backing Up Lotus Domino Databases on page 1332 Restoring Lotus Domino Databases on page 1337 Preparing for Disaster Recovery on a Lotus Domino Server on page 1343
1331
Configuring Default Lotus Domino Options
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 1335. 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 1340. 5. Click OK to save the options or select other options from the Properties pane.
Backing Up Lotus Domino Databases

When a Lotus Domino backup job is submitted, Backup Exec uses Lotus Domino APIs to obtain the backup of the database. The transaction logs associated with the Lotus Domino databases are automatically included in the backup and are stored in a separate backup set within the Lotus Domino database backup set. The Lotus Domino Agent supports the backup of the following types of files:

.ntf - Lotus Notes Template Files .nsf - Lotus Notes Database Files .box - Lotus Mailbox Files .dsk - Cache Files
You must back up .nsf, .ntf, and .box files to properly recover Lotus Domino databases. If you want to back up .njf, .ncf, .id, .dic, or notes.ini files, you must select them for backup from the volume in which the Lotus Domino Program directory is located.
1332
Related Topics: Lotus Domino Transaction Logs on page 1333 Backup Options for Lotus Domino Databases on page 1335 Restore Options for Lotus Domino Databases on page 1340
Supported Lotus Domino Database Configurations

You can back up the following types of Lotus Domino database configurations using the Lotus Domino Agent:
Domino Server Databases. Domino Server databases can be Logged or Unlogged. They are located in a folder in the Domino data directory, typically Lotus\Domino\Data, but may also be linked to the Domino data directory using Lotus Linked Databases.
Logged Domino Server Databases. A logged Domino Server database logs transactions for one or more Lotus databases. If transaction logging is enabled on the server, all database transactions go into a single transaction log. Unlogged Domino Server Databases. An unlogged Domino Server database does not have transaction logging enabled, or the transaction logging has been disabled for specific server databases. Unlogged Domino Server databases will be backed up in their entirety when a full, differential, or incremental backup is performed, but the database can only be restored to the point of the latest database backup.
Local Databases. Lotus databases are considered Local when they cannot be found in the Domino data directory, cannot be shared, and cannot be logged. This type of database requires a backup of the database itself when using any of the Lotus Domino 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
Appendix N, Symantec Backup Exec - Agent for Lotus Domino 1333
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.
1334
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 or third party Lotus Domino agents before running the backup. The transaction logs will automatically be included in the backup job. For details on how to create a backup job, and for definitions of all other backup options see Creating a Backup Job on page 261. Caution All Lotus Domino databases and transaction logs that reside on single or multiple volumes must be backed up by the same media server. In addition, you should not back up a Lotus Domino server simultaneously from multiple media servers. To select backup job properties for Lotus Domino databases: 1. On the navigation bar, click Backup. 2. On the Properties pane, under Settings, click Lotus Domino. 3. Select the appropriate options as follows:
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.
1335
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. This option is selected automatically when you select the full backup method. You cannot clear this option when you are using the full backup method. If the option is selected when you perform a differential or incremental backup job, transaction logs that are needed to maintain the differential backups will be reused. However, it should be selected regularly to create space for new transaction logs. 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. Related Topics: Backing Up Data on page 259
Restoring Lotus Domino Databases

The restore of a Lotus Domino database is a two-part process. The first part of the restore copies database files from the media to the server. The second part of the restore is a recovery process that applies data from the transaction logs to the database to bring it up-to-date. During a restore of the Lotus Domino database, the existing database is taken offline and deleted, the database is restored, and changed records contained in the backup job are applied to the database. If the database is unlogged or local, the database is brought back online. If the database is logged and multiple databases are being restored, the database name is added to a list for recovery. During the restore process, Backup Exec assigns a unique name to databases and then before databases are brought online, reassigns the original name. Changing the name during the restore process has no effect on restored databases.
1336
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.
1337
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. 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.
1338
Restoring Lotus Domino Databases Empty data directory for Differential Backup 0002.
The data backed up for Differential Backup 0002 is actually contained in the transaction log backup set. To restore the data, you must select it from the previous Full Backup 0001. The transaction logs from Differential Backup 0002 will be used to bring the database up to date.
Transaction Logs backup set for Differential Backup 0002.
1339
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. 3. Select the appropriate options as follows:
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 Assign new database ID Assign new database ID and replica ID Select this option to restore the original database IDs. Select this option to assign new IDs to the database. Select this option to assign new IDs to the database. A replica ID is used to synchronize two or more databases that are being replicated in the Lotus Domino environment. You can assign a new replica ID during a restore to prevent other databases under replication from overwriting the restored database files.
1340
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. Related Topics: Restoring Data on page 451 Lotus Domino Transaction Logs on page 1333
Redirecting Restore Jobs for Lotus Domino Databases

The Backup Exec logon account must have administrative credentials on the server to which you want to redirect the backup of the Lotus Domino server. Lotus Domino databases can only be redirected to a different directory on the local server from which the database was backed up. If you are restoring a database to a different location, it must reside in or under the Lotus Domino data directory. Point in time restores cannot be redirected. To redirect the restore of a Lotus Domino database: 1. Select the media that contains the data you want to restore. 2. On the navigation bar, click Restore. 3. Select the Lotus Domino databases.
1341
4. After selecting options on the Restore Job Properties dialog box, on the Properties pane, under Destination, click File Redirection. 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. Related Topics: Restoring Data on page 451 Configuring Logon Accounts on page 386
1342
Preparing for Disaster Recovery on a Lotus Domino Server

A Disaster Preparation Plan is necessary for restoring Lotus Domino databases efficiently and effectively in the event of a catastrophic failure. The goal is to minimize the time to recover. Developing a backup strategy for your Windows computers and Lotus Domino databases is the critical part of this plan. When developing a strategy for backing up your Lotus Domino databases, consider the following recommendations:
If you have linked databases, it is best to keep them on one volume. This allows Backup Exec to synchronize the databases before they are backed up. Back up active databases often. This reduces the amount of effort required to update the databases to the point following the most recent backup. Ensure that the notes.ini, cert.id, and server.id files are protected and available if a disaster occurs.
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 605) or with Backup Execs Intelligent Disaster Recovery option (see Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901). 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.
1343
4. Start the Lotus Domino Server. Related Topics: Disaster Recovery of a Lotus Domino Server Using Circular Logging on page 1345 Disaster Preparation of the Windows Computer on page 607 Restoring Data on page 451 Restore Options for Lotus Domino Databases on page 1340
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.
1344
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. 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. Related Topics: Restore Options for Lotus Domino Databases on page 1340 Restoring Data on page 451
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.
1345
4. To have Lotus Domino create the circular log file in the log directory (created in step 2) when the server starts, set the following parameter in the notes.ini file: translog_path=logdir 5. Use the Lotus Domino Agent to restore the databases to the Domino data directory. Related Topics: Restoring Data on page 451 Restore Options for Lotus Domino Databases on page 1340
1346
Appendix
Symantec 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 Microsoft Windows 2000 using the R/3 BACKINT interface to 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.
1347
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
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. Related Topics: Backup Exec R/3 Agent Security on page 1348
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
Related Topics: Changing Windows Security on page 61
1348
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.
Requirements for Backup Exec R/3 Agent

Microsoft Windows 2000, Windows XP, or Windows Server 2003. Oracle Enterprise Server version 7.3.x, 8.1.x, and 9i. 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 Symantec 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. Related Topics: Installing the Backup Exec R/3 Agent on page 1350 Backup Exec R/3 Agent Security on page 1348
Appendix O, Symantec Backup Exec - Agent for R/3 for Oracle Server
1349
Using the R/3 Agent to Back Up the R/3 Database
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 65. To install the Backup Exec R/3 Agent, see Installing Backup Exec Options to the Local Computer on page 71.

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.
1350
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. 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. Appendix O, Symantec Backup Exec - Agent for R/3 for Oracle Server 1351
Using the R/3 Agent to Back Up the R/3 Database Options in the Biparam.ini file (continued) Use this option: Device=<device name> For this operation: 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 name of the device exactly as it appears in Backup Exec for Windows Servers. Media=<media set name> To specify a name of an existing media set. Description=<backup set name> To specify a name for the next backup set description. 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. To specify the backup compression mode. Allowable values are:
Compression = <backup compression mode>
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.
Related Topics: Backing Up the R/3 Database on page 1353 Restoring the R/3 Database on page 1354 Backup Exec Alerts and the BACKINT Interface on page 1349
1352
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.
1353
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
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.
1354
Related Topics: Disaster Recovery Prerequisites on page 1355 Recovering a Remote R/3 Database Server from a Disaster on page 1355 Recovering a Combination R/3 Database Server/Media Server on page 1356
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. Related Topics: Backing Up Data on page 259 Recovering a Remote R/3 Database Server from a Disaster on page 1355 Recovering a Combination R/3 Database Server/Media Server on page 1356
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.
1355
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. Related Topics: Disaster Recovery Prerequisites on page 1355 Recovering a Combination R/3 Database Server/Media Server on page 1356
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.
1356
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. Related Topics: Disaster Recovery Prerequisites on page 1355 Recovering a Remote R/3 Database Server from a Disaster on page 1355
1357
1358
Appendix
Symantec Backup Exec Agent for Microsoft SharePoint Portal Server

The Symantec Backup Exec Agent for Microsoft SharePoint Portal Server (SharePoint Agent) is an optional, add-on component to Backup Exec for Windows Servers. The SharePoint Agent enables network administrators to perform backup and restore operations on SharePoint Portal Server installations that are connected to a network. SharePoint backups can be integrated with network backups without separate administration or dedicated hardware. The SharePoint Agent supports installations of SharePoint Portal Server 2001 and 2003. Related Topics: Using the SharePoint Agent with SharePoint Portal Server 2001 on page 1360 Using the SharePoint Agent with SharePoint Portal Server 2003 on page 1372
Requirements for the SharePoint Agent

The SharePoint Agent has the following requirements:

The SharePoint Agent must be installed on the media server. The Backup Exec Remote Agent for Windows Servers (Remote Agent) must be installed on each remote SharePoint Portal Server that will be protected. In addition, for SharePoint Portal Server 2003, the Remote Agent must be installed on each SQL server in the server farm. The credentials specified by the logon account used for backing up and restoring SharePoint Portal Server data must have local administrative rights on the servers where SharePoint components are installed. Additionally, to back up and restore
1359
Installing the SharePoint Agent
individual documents in workspaces or backward-compatible document libraries, the account must be granted the Coordinator role in SharePoint on all folders to be accessed in the workspace or document library. For more information on granting permissions on folders in the workspace or backward-compatible document libraries, see your SharePoint Portal Server documentation.
The credentials specified by the logon account used for backing up and restoring the Single Sign-on database must be either the account name or a member of the group that is specified in the "Account name" field in the Single Sign-on Settings section of the Manage Settings for Single Sign-on administration page in SharePoint Portal Server. Internet Information Services (IIS) rights can affect database backups and restores. Ensure that the logon account used for backup and restore has rights to access the IIS sites. Integrated Windows Security should be enabled within the IIS rights.
Installing the SharePoint Agent

The SharePoint Agent must be installed on the media server. If Backup Exec is not already installed, see Installing Backup Exec on page 57. To install the SharePoint Agent, see Installing Backup Exec Options to the Local Computer on page 71. To install the Remote Agent, see Installing Backup Exec Agents to Remote Computers on page 77.
Using the SharePoint Agent with SharePoint Portal Server 2001

You can back up and restore the SharePoint Portal Server, an entire SharePoint workspace, or the individual documents that are contained in the SharePoint workspaces. If you choose to back up the individual documents, you can quickly restore them without restoring the entire SharePoint Portal Server. When you are backing up the SharePoint Portal Server, the SharePoint Agent includes the following data in the backup:

Microsoft Web Storage System files Microsoft Search Service (MSSearch) system resources, which include the property store, subscriptions store, full-text index files, and propagated indexes
1360
SharePoint Portal Server configuration information, including Web Storage System configuration information, content source information, server properties, and access accounts The Applications folder, which contains a subfolder for each workspace on the server Shortcuts or content sources that reference the local file system Individual documents that are contained in the workspaces Content source crawls (a content source is a URL that SharePoint Portal Server uses as a starting point to search, or crawl, for content in documents stored outside the workspace) scheduled using Microsoft Windows 2000 Scheduled Tasks Scheduled tasks for processing subscriptions Gatherer logs Lotus Notes configuration information
SharePoint Agent does not back up the following data:
For more information about the various types of data stored on SharePoint Portal Server, see your Microsoft SharePoint Portal Server documentation. Note SharePoint Portal Server is available only for Windows 2000. Related Topics: Requirements for the SharePoint Agent on page 1359 Installing the SharePoint Agent on page 1360 Backing Up SharePoint Portal Server 2001 on page 1362 About Restoring SharePoint Portal Servers and SharePoint Portal Workspaces on page 1364 Redirecting SharePoint Portal Server Restore Jobs on page 1366 Disaster Recovery of a SharePoint Portal Server on page 1370
Appendix P, Symantec Backup Exec - Agent for Microsoft SharePoint Portal Server
1361
Backing Up SharePoint Portal Server 2001

There are no SharePoint-specific options to configure when you back up SharePoint Portal Server 2001. When backing up SharePoint Portal Server 2001, a full backup will be performed, which backs up the entire SharePoint Portal Server database and all relevant data from other dependent data stores. Related Topics: Creating a Manual Backup Job by Configuring Job Properties on page 262
Backing Up the SharePoint Portal Server Database

To back up the SharePoint Portal Server database: 1. On the navigation bar, click Backup. 2. From the Backup Selections pane, under Local Selections, select Microsoft SharePoint Portal Server. If SharePoint Portal Server is installed remotely, expand Remote Selections and then browse to the server where SharePoint Portal Server is installed. 3. Start the backup job or select other backup options from the Properties pane.
Backing Up Folders and Documents from a SharePoint Portal Workspace

You can back up the individual documents that are contained in the SharePoint Portal Workspace, which will enable you to quickly restore individual documents without restoring the entire SharePoint Portal Server database. To back up a folder and document objects from a SharePoint Portal Workspace: 1. On the navigation bar, click Backup. 2. From the Backup Selections pane, under Local Selections, expand Microsoft SharePoint Portal Workspaces. If SharePoint Portal Server is installed remotely, expand Remote Selections. 3. Select the folders and/or documents in the workspace that you want to back up.
1362
Using the SharePoint Agent with SharePoint Portal Server 2001 Backup Job Properties dialog box
4. Start the backup job or select other backup options from the Properties pane.
1363
About Restoring SharePoint Portal Servers and SharePoint Portal Workspaces

You can restore the entire SharePoint Portal Server or the individual documents that are contained in the SharePoint Portal Workspaces if the documents were backed up separately. You can redirect the restore of a SharePoint Portal Server to a different server than the one from which it was backed up. In addition, you can redirect the restore of SharePoint Portal Workspaces to an alternate workspace or file share. There are some limitations on what information can be restored in SharePoint Portal Workspaces. The Microsoft SharePoint Portal Workspaces interface in Backup Exec is intended to provide backup and restore of individual documents stored in the Documents subfolder for each workspace and should not be used as a substitute for SharePoint Portal Server database backup. Many of the other files and folders contained in the workspace are controlled by the SharePoint Portal Server software and may not restore successfully into the workspace even though they are available for backup. In addition, when restoring individual documents, the creation date and modification date properties do not restore. Note SharePoint Portal Server must be installed on the target server before you can restore a SharePoint Portal Server. Related Topics: Creating a Manual Restore Job by Configuring Job Properties on page 458
Restoring a SharePoint Portal Server

Caution When you restore a SharePoint Portal Server database, all SharePoint data on the target server is overwritten. To restore a SharePoint Portal Server: 1. Place the media containing the data you want to restore in the storage device. 2. On the navigation bar, click Restore. 3. Navigate to and select the SharePoint Portal Server database you want to restore. 4. On the Properties pane, set the appropriate options. 5. Start the restore job.
1364
Restoring a SharePoint Portal Workspace

Individual SharePoint documents are always restored to SharePoint workspaces as checked out to the credentials specified by the logon account used for the restore. The documents must be checked in or published by that user before others can use them. If you try to restore over a document that is published or checked in, the restore will fail. If you try to restore over a document that is checked out, the restore will fail if the document is checked out to a user that differs from the logon account credentials used for the restore. Previous versions of individual documents that existed when the documents were backed up are not preserved when they are restored into a workspace, and the document versions are reset. The only way to preserve version history for documents is to restore the entire SharePoint Portal Server database. Documents that exist in the target location may be overwritten by the restore depending on the overwrite properties for the restore job. If an existing document is overwritten, then the version history for that document is lost as well. To restore SharePoint Portal workspace data: 1. On the navigation bar, click Restore. 2. Navigate to and select the SharePoint workspace data you want to restore. 3. On the Properties pane, set the appropriate options. 4. Start the restore job. Related Topics: Backing Up Folders and Documents from a SharePoint Portal Workspace on page 1362 Redirecting SharePoint Portal Server Restore Jobs on page 1366
Restoring Previous Versions of Documents from Workspace Backups

The SHADOW folder, at the root of the workspace, contains previous versions of the documents that exist in the workspace at the time of backup. If you select the SHADOW folder to include in a workspace backup, you can have access to the previous versions of the documents in the workspace. However, you cannot restore the previous versions directly back into the workspace. You must restore them to an alternate location and then manually copy them into the workspace.
1365
To restore previous versions of documents from workspace backups: 1. On the navigation bar, click Restore. 2. Navigate to the backup sets that contain the workspace data from which you want to restore. 3. Under the backup set, expand the SHADOW folder and then navigate to the folder that contains the documents you want to restore. 4. Proceed with the steps in Redirecting Restored Workspace Data to a File Path on page 1369.
Redirecting SharePoint Portal Server Restore Jobs

Before redirecting the restore of a SharePoint Portal Server database, the SharePoint Portal Server software must be installed on the target server. Caution When you restore a SharePoint Portal Server database, all SharePoint data on the target server is overwritten. To redirect a SharePoint Portal Server restore: 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 Microsoft SharePoint Redirection. 5. Under SharePoint Portal Server 2001, select the Redirect SharePoint Portal Server sets check box. 6. In the Restore to server field, enter the name of the SharePoint server to which you are restoring. Use the following format: \\servername.
1366
Using the SharePoint Agent with SharePoint Portal Server 2001 Restore Job Properties -Sharepoint Redirection
7. Use the default logon account as indicated, or click Change to select a different one. 8. On the Properties pane, select other job properties that might be appropriate for your environment. 9. Start the restore job. After the restore completes, it is recommended that you perform a full backup of the restored SharePoint Portal Server databases. Related Topics: Backing Up SharePoint Portal Server 2001 on page 1362 Restoring a SharePoint Portal Server on page 1364
1367
Redirecting Restored Workspace Data to Another Workspace

Before redirecting the restore of SharePoint Portal workspace data, the SharePoint Portal Server software must be installed on the target server. If any of the folders in the original workspace do not exist in the destination workspace, they will be created during the restore. Caution When you restore SharePoint Portal workspace data, any documents that exist in the target location and that have the same name as the documents being restored may be overwritten, depending on the overwrite properties for the restore job. To redirect SharePoint Portal workspace data to another workspace: 1. On the navigation bar, click Restore. 2. Navigate to and select the SharePoint Portal workspace data you want to restore. 3. On the Properties pane, under Destination, click Microsoft SharePoint Redirection. 4. Select the Redirect SharePoint Portal document sets check box, and then select Redirect to workspace. 5. In the Restore to server field, type the name of the SharePoint server to which you are restoring. Use the following format: \\servername. 6. In the Restore to workspace field, type the name of the workspace to which you are restoring. If you have not yet created the workspace, you must do so before starting the restore operation. 7. Use the default logon account as indicated, or click Change to select a different one. 8. On the Properties pane, select other job properties that might be appropriate for your environment. 9. Start the restore job. Related Topics: Backing Up Folders and Documents from a SharePoint Portal Workspace on page 1362 Restoring a SharePoint Portal Workspace on page 1365
1368
Redirecting Restored Workspace Data to a File Path

To redirect SharePoint Portal Workspace data to a file path: 1. On the navigation bar, click Restore. 2. Navigate to and select the SharePoint Portal Server data you want to restore. 3. On the Properties pane, under Destination, click Microsoft SharePoint Redirection. 4. Select the Redirect SharePoint Portal document sets check box, and then select Redirect to path. 5. In the Restore to drive and Restore to path fields, enter the drive letter and path to which you want to direct the restore, or click the ellipsis (...) button to browse to the location. Note You can also enter a UNC path (\\servername\share) in the Restore to drive field. 6. Use the default logon account as indicated, or click Change to select a different one. 7. On the Properties pane, select other job properties that might be appropriate for your environment. 8. Start the restore job. Related Topics: Backing Up Folders and Documents from a SharePoint Portal Workspace on page 1362 Restoring a SharePoint Portal Workspace on page 1365
1369
Disaster Recovery of a SharePoint Portal Server

Because SharePoint Portal Server uses Windows 2000 security for authentication, disaster recovery of a SharePoint Portal Server cannot be separated from the disaster recovery of Windows 2000. If you purchased the Intelligent Disaster Recovery (IDR) option, see Symantec Backup Exec - Intelligent Disaster Recovery Option on page 901 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 954. You must recover the Windows 2000 server first. For more information, see Manual Disaster Recovery of Windows Computers on page 610. After recovery of the Windows 2000 server is complete (after the last reboot), the SharePoint Portal Server software is installed but is not functional. You must remove SharePoint Portal Server and then reinstall it before the SharePoint data can be restored. Always log on to the Windows 2000 server using the Administrator account (or an Administrator equivalent) during disaster recovery. You need:

A copy of Backup Exec for Windows Servers with the SharePoint Agent installed The latest backup of the SharePoint Portal Server you want to recover The SharePoint Portal Server CD Any SharePoint Portal Server service packs that were applied to the original installation
Caution You cannot completely recover a SharePoint Portal Server database using backups of individual workspaces. You must use a backup of the SharePoint Portal Server database to complete the disaster recovery.
1370
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 using the appropriate options for your environment. When the New Workspace Wizard starts, click Cancel. 3. If applicable, install any SharePoint Portal Server service packs that were applied to the original installation.
Best Practices for SharePoint Portal Server 2001

Symantec recommends the following practices for SharePoint Portal Server 2001.
Perform full backups of Microsoft SharePoint Portal Server 2001, in addition to individual workspace backups. Even though workspace backups may be more useful for granular recovery of individual documents on a day-to-day basis, you must have a full backup to complete a disaster recovery. Keep a record of all service packs and hotfixes that are installed on the SharePoint server when you perform backups. SharePoint restores may not complete successfully if the databases were backed up at a different patch level. Ensure that the SHADOW folder is included in your selections when you back up workspace data. This folder contains previous versions of the current documents that exist in the workspace at the time of backup. While these previous versions cannot be restored directly into that workspace, it is possible to restore them to an alternate location, provided that the SHADOW folder is protected.
1371

You can use the SharePoint Agent to back up and restore SharePoint Portal Server 2003 farm components, which include:

Configuration database Portal sites and their associated databases

Content database User Profile database Services database Index databases Team databases
Windows SharePoint Services sites and their associated databases Single Sign-on database Document Library Store (Web Storage System-based) Document Libraries (Web Storage System-based)
Individual documents can be backed up from and restored to Web Storage System-based document libraries, or redirected to file paths.
Selecting SharePoint Portal Server 2003 Resources for Backup

Backup Exec provides a hierarchical tree view of SharePoint Portal Server 2003 resources in two locations in the Selection tree:
Under Local Selections, a node titled Microsoft SharePoint Resources displays for any server that has locally installed SharePoint resources. For single-server SharePoint deployments, all of the SharePoint resources are listed and are selectable for backup. For SharePoint server farm deployments, this node lists only the SharePoint resources that reside locally on this server and that can be selected for backup from this node. On front-end Web servers, this node lists the entire farm topology, but only the resources that reside locally can be selected for backup. Under Remote Selections, a node titled Microsoft SharePoint Server Farms displays a logical view of the topology of each SharePoint server farm on your network. Symantec recommends that you select SharePoint resources for backup from this node. Backup Exec automatically discovers SharePoint farms when you browse to a SharePoint front-end Web server and adds the farms to this node. Additionally, you can add farms manually using the Add Server Farm menu option.
1372
Adding a Server Farm to the Backup Selections List

If a farm that you want to back up does not display under the Microsoft SharePoint Server Farms node on the Backup Job Properties dialog box, you can manually add that farm to the list. To add a SharePoint server farm: 1. On the navigation bar, click Backup. 2. In the Selection tree, expand Remote Selections. 3. Right-click Microsoft SharePoint Server Farms and then click Add Server Farm.
Add Server Farm
4. In the Web server name field, type the name of a Web server that belongs to the farm you want to add.
1373
5. In the Server farm name field, type a name for the farm or use the default name. The name you type here will display under the Microsoft SharePoint Server Farms node. Backup Exec lists the names of discovered Web servers in parentheses after the server farm name in the Selection tree. Note The following characters cannot be used in farm names: ` ~ ^ * ( ) { } \ ; : " , < > / ? 6. Click OK. Backup Exec adds the new server farm to the Microsoft SharePoint Server Farms node under Remote Selections and contacts the specified Web server to retrieve the remainder of the farm topology. When you create jobs to protect the SharePoint resources for the server farm, make backup selections from this server farm node. In addition, back up the default Microsoft SQL databases (master, model, msdb, pubs) for each Microsoft SQL instance that hosts SharePoint databases. Please note that after a server farm is added to Microsoft SharePoint Server Farms, the SharePoint databases hosted on Microsoft SQL instances can no longer be selected for backup directly from the Microsoft SQL Server resource nodes. If you change the SharePoint server farm topology after it has been added to Microsoft SharePoint Server Farms, you must browse the server farm node so that Backup Exec can recognize and save the changes.
Disabling or Enabling Communication Between a Web Server and Backup Exec

Backup Exec communicates with the Web servers that participate in SharePoint server farms to discover the farm topology. This process may take some time if Backup Exec attempts to communicate with a Web server that is unavailable. If you know that a particular Web server in a farm will be unavailable for a period of time, you can disable the communication between the Web server and Backup Exec. To disable or enable communication between a Web server and Backup Exec: 1. On the navigation bar, click Backup. 2. In the Selection tree, under Remote Selections, right-click Microsoft SharePoint Server Farms, and then click Manage Server Farms. 3. Select the farm that contains the Web server you want to disable or enable, and then click Properties.
1374
4. To prevent Backup Exec from communicating with a Web server, clear the check box next to that Web servers name. If the Web server is now available to communicate with Backup Exec, select the check box next to the Web servers name. Note When you disable communication with a Web server, Backup Exec removes the name of that Web server from the server farm name under the Microsoft SharePoint Server Farms node. 5. Click OK, and then click Close.
Changing the Name of a Farm

When Backup Exec adds a farm, it creates a default name for the farm. You can change the default farm name to a name that is meaningful to you. To change the name of a farm: 1. On the navigation bar, click Backup. 2. In the Selection tree, under Remote Selections, right-click Microsoft SharePoint Server Farms, and then click Manage Server Farms. 3. Select the farm whose name you want to change, and then click Properties. 4. Type the new farm name in the Server farm name field. Then name you type here will display under the Microsoft SharePoint Server Farms node. Backup Exec lists the names of discovered Web servers in parentheses after the server farm name in the Selection tree. Note The following characters cannot be used in farm names: ` ~ ^ * ( ) { } \ ; : " , < > / ? 5. Click OK, and then click Close.
1375
Deleting a SharePoint Portal Farm from the Microsoft SharePoint Server Farms Node
If a server farm is no longer in use or is no longer valid, you can remove it from the Microsoft SharePoint Server Farms node. Note If Backup Exec is installed on the same server that is used as a Web server in a farm, you cannot delete that farm. To delete a SharePoint Portal farm from the Microsoft SharePoint Server Farms node: 1. On the navigation bar, click Backup. 2. In the Selection tree, under Remote Selections, right-click Microsoft SharePoint Server Farms, and then click Manage Server Farms. 3. Select the farm you want to delete, and then click Delete.
Backing Up SharePoint Portal Server 2003 Resources

Each portal site will have a minimum of three databases: Content databases, Services databases, and User Profile databases. Symantec recommends that you back up these databases together. To back up SharePoint Portal Server 2003 resources: 1. On the navigation bar, click Backup. 2. Select the SharePoint resources you want to back up. For information about selecting SharePoint resources, see Selecting SharePoint Portal Server 2003 Resources for Backup on page 1372. 3. On the Properties pane, under Settings, select Microsoft SharePoint.
1376

Backup job properties for SharePoint Item Backup method: Description
Full - Back up entire database. Select this to back up the entire database. Differential - Back up database changes only. Select this to back up only the changes made to the database since the last full backup.
Note The differential backup method cannot be used to back up Index databases or Document Libraries. The Full backup method will be used to back up these resources. Perform consistency Select this option to run a full consistency check (including check before backup of indexes) of the Microsoft SQL databases used by Microsoft Microsoft SQL databases SharePoint before backing up the databases. used by Microsoft SharePoint Continue with backup if consistency check fails Select this to continue with the backup operation even if the consistency check fails.
5. Start the backup job or select other backup options from the Properties pane.
Selecting SharePoint Portal Server 2003 Resources for Restore

Backup Exec provides two hierarchical tree views of SharePoint Portal Server 2003 resources in the Selections tree when using the Resource View:
Server Farm node. This node represents a logical view of the topology for the SharePoint resources that have been backed up from the farm. The name that displays for this node matches the name you defined for the server farm in Backup Selections under the Microsoft SharePoint Server Farms node. If you expand the nodes for each SharePoint component that appears in this view, the backup sets for that component are displayed and can be selected for restore. Individual Server nodes. Each server from which SharePoint components were backed up contains a Microsoft SharePoint Resources node. This node will display the SharePoint components that resided locally on the server when they were backed up. If you expand the nodes for each SharePoint component that appears in this view, the backup sets for that component are displayed and can be selected for restore.
1377
Restoring SharePoint Portal Sites, Services Sites, Document Library Stores, Configuration Databases, and Single Sign-on Databases
Follow these steps to restore SharePoint resources the servers from which they were originally backed up. To redirect a restore job to a different server, see Redirecting a Restore Job for SharePoint Portal Server 2003 on page 1381. Each portal site will have a minimum of three databases: Content databases, Services databases, and User Profile databases. Symantec recommends that you restore these databases together. Caution The Configuration database contains all of the configuration information for the entire SharePoint Server farm. Use caution when restoring this database because any changes made to the farm topology after the backup from which you are restoring will be lost. For more information, refer to the Microsoft SharePoint Portal Server 2003 documentation. Note You can restore Document Library Stores, Configuration databases, and Single Sign-on databases back to the original location only. To restore SharePoint Portal Server 2003 resources: 1. On the navigation bar, click Restore. 2. Select the full and differential backup sets that correspond to the SharePoint data you want to restore. Note If you restore the SharePoint resources for a portal site in one job, the Index database is restored last. If you are restoring in separate jobs, you must restore the Index database last. 3. On the Properties pane, under Settings, select Microsoft SharePoint. 4. To bring the databases online, verify that the Bring restored databases online and reconnect previous database links option is selected. When restoring portal sites or Windows SharePoint Services sites, this option also re-establishes the link between the restored databases and their corresponding sites.
1378
Note If you are restoring full or differential backup sets in separate restore jobs, clear this option for all jobs except the last job. You should select the option for the last restore job in the sequence. Also, you may be prompted to insert media that you have already used. 5. Set additional restore options on the Properties pane or start the restore job.
Restoring SharePoint Document Libraries

Individual SharePoint documents are always restored to SharePoint document libraries as checked out to the credentials specified by the logon account used for the restore. The documents must be checked in or published by that user before others can use them. If you try to restore over a document that is published or checked in, the restore will fail. If you try to restore over a document that is checked out, the restore will fail if the document is checked out to a user that differs from the logon account credentials used for the restore. To restore SharePoint Document Libraries: 1. On the navigation bar, click Restore. 2. Select the SharePoint Document Library data you want to restore. 3. Set additional restore options on the Properties pane or start the restore job.
Restoring Previous Versions of Documents from Document Library Backups

The SHADOW folder, at the root of the Document Library, contains previous versions of the documents that exist in the Document Library at the time of backup. If you select the SHADOW folder to include in a Document Library backup, you can have access to the previous versions of the documents. However, you cannot restore the previous versions directly back into the Document Library. You must restore them to an alternate location and then manually copy them into the Document Library.
1379
To restore previous versions of documents from Document Library backups: 1. On the navigation bar, click Restore. 2. Navigate to the SharePoint Document Library that contains the documents you want to restore. 3. Under the backup set, expand the SHADOW folder and then select the documents you want to restore. 4. Proceed to Redirecting Restored Document Library Data to a File Path on page 1383".
1380
Redirecting a Restore Job for SharePoint Portal Server 2003

Follow these steps to redirect a restore job to an existing site on a Web server in a farm. To redirect a restore job to an existing site: 1. On the navigation bar, click Restore. 2. Select the SharePoint resources you want to restore. Note You can restore Document Library Stores, Configuration databases, and Single Sign-on databases back to the original location only. 3. On the Properties pane, under Settings, select Microsoft SharePoint Redirection. 4. Under SharePoint Portal Server 2003, select Redirect SharePoint Portal Server 2003 sets. 5. In the Restore to site field, type the URL of the site to which you want to restore the data. For example, http://portalsite1 or https://portalsite1 Note In order to restore to a site, the site must already exist. 6. In the Using Web server field, type the name of the Web server on which the site resides. Note You must create the target SharePoint Portal Server 2003 portal site or Windows SharePoint Services site on the specified Web server with the same database structure as the source site before running the restore job. 7. To bring the databases online, verify that the Bring restored databases online and reconnect previous database links option is selected. When restoring portal sites or Windows SharePoint Services sites, this option also re-establishes the link between the restored databases and their corresponding sites. Note If you are restoring full or differential backup sets in separate restore jobs, clear this option for all jobs except the last job. You should select the option for the last restore job in the sequence. Also, you may be prompted to insert media that you have already used. 8. Use the default logon account as indicated, or click Change to select a different one. 9. Set additional restore options on the Properties pane, or start the restore job.
Appendix P, Symantec Backup Exec - Agent for Microsoft SharePoint Portal Server 1381
Redirecting Restored Document Library Data to Another Document Library

Before redirecting the restore of SharePoint Portal document library data, the SharePoint Portal Server software must be installed on the target server. If any of the folders in the original document library do not exist in the destination document library, they will be created during the restore. Caution When you restore SharePoint Portal document library data, any documents that exist in the target location and that have the same name as the documents being restored may be overwritten, depending on the overwrite properties for the restore job. To redirect SharePoint Portal document library data to another document library: 1. On the navigation bar, click Restore. 2. Navigate to and select the SharePoint Portal document library data you want to restore. 3. On the Properties pane, under Destination, click Microsoft SharePoint Redirection. 4. Select the Redirect SharePoint Portal document sets check box, and then select Restore to workspace. 5. In the Restore to server field, type the name of the SharePoint server to which you are restoring. Use the following format: \\servername. 6. In the Restore to workspace field, type the name of the document library to which you are restoring. If you have not yet created the document library, you must do so before starting the restore operation. 7. Use the default logon account as indicated, or click Change to select a different one. 8. On the Properties pane, select other job properties that might be appropriate for your environment. 9. Start the restore job.
1382
Redirecting Restored Document Library Data to a File Path

To redirect SharePoint Portal Document Library 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 Microsoft SharePoint Redirection. 5. Select the Redirect SharePoint Portal document sets check box, and then select Redirect to path. 6. In the Restore to drive and Restore to path fields, enter the drive letter and path to which you want to direct the restore, or click the ellipsis (...) button to browse to the location. Note You can also enter a UNC path (\\servername\share) in the Restore to drive field. 7. Use the default logon account as indicated, or click Change to select a different one. 8. On the Properties pane, select other job properties that might be appropriate for your environment. 9. Start the restore job.
1383
Setting Default Options for SharePoint Portal Server 2003

To set backup and restore default options: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Microsoft SharePoint. 3. Complete the appropriate options as follows:
Microsoft SharePoint Default Options Item Backup Backup method:
Description
Full - Back up entire database. Select this to back up the entire database. Differential - Back up database changes only. Select this to back up only the changes made to the database since the last full backup.
Note The differential backup method cannot be used to back up Index databases or Document Libraries. The Full backup method will be used to back up these resources. Perform consistency Select this option to run a full consistency check (including check before backup of indexes) of the Microsoft SQL databases used by Microsoft Microsoft SQL databases SharePoint before backing up the database. used by Microsoft SharePoint Continue with backup if consistency check fails Restore Bring restored databases online and reconnect previous database links Select this option to bring the databases online after a restore job. When restoring portal sites or Windows SharePoint Services sites, this option also re-establishes the link between the restored databases and their corresponding sites. Select this to continue with the backup operation even if the consistency check fails.
1384
Appendix
Symantec Backup Exec Agent for Microsoft Data Protection Manager

The Symantec Backup Exec - Agent for Microsoft Data Protection Manager (DPM Agent) enables network administrators to perform backup and restore operations between Microsoft Data Protection Manager (DPM) and Backup Exec. For example, you can back up DPM data to tape or disk. Data from three Data Protection Manager sources can be backed up:

Databases Protected Servers Shadow Copies
Depending on the kind of DPM data backed up, Backup Exec can restore the data to the DPM server, a file server in the DPM protection group, or an alternate destination to which you have rights. The DPM Agent enables you to use Backup Exec to:
Navigate to or browse for available DPM databases, protected file servers, and shadow copies to back up. Perform backup and restore jobs between a DPM server and Backup Exec. Discover information about the DPM servers and start the DPM writer.
Related Topics: Requirements for the Agent for Microsoft Data Protection Manager on page 1386 Backup Job with DPM Data on page 1386 Restore Job with DPM Data on page 1389 Monitoring Jobs on page 405 Viewing and Filtering Alerts on page 502 Responding to Active Alerts on page 507
1385
Requirements for the Agent for Microsoft Data Protection Manager
Requirements for the Agent for Microsoft Data Protection Manager

When you have installed and configured Microsoft Data Protection Manager, specific requirements must be met before creating backup jobs and restore jobs between DPM and Backup Exec. The Backup Exec server requirement is:
The Backup Exec Agent for Microsoft Data Protection Manager must be installed on the Backup Exec server. The Backup Exec Remote Agent for Windows Servers must be installed on the DPM server. The Backup Exec Remote Agent for Windows Servers should be installed on all file servers in the DPM protection group. Installing the Remote Agent for Windows Servers on DPM file servers is an optional step that enables you to restore from Backup Exec to the DPM file servers.
The DPM server requirement is:
The DPM file server requirement is:
Related Topics: Installing Backup Exec Options to the Local Computer on page 71 Installing Backup Exec Agents to Remote Computers on page 77
Backup Job with DPM Data

Backing up DPM data with Backup Exec involves selecting data sources from the DPM protection group at the same frequency as your other backup jobs, such as nightly, weekly, or monthly. Due to DPM functionality, you can use the Backup Exec copy backup job method when backing up DPM data. Each DPM protection group consists of DPM file servers that store DPM data from client computers and a DPM server that stores data captured from the DPM file servers. Replicas, created by Microsoft Data Protection Manager, are complete copies of the protected data on the DPM file servers at the time the DPM backup began. The expanded DPM tree view includes the following elements.
1386
Backup Job with DPM Data Backup Job Properties Selections screen
DPM Database Backup Job - The DPM Databases node contains information about the entire DPM environment as it pertains to the DPM installation, such as DPM protection groups and schedules. Select this node to protect the DPM environment settings at the same frequency as your other data, such as nightly, weekly, or monthly. Backing up the DPM databases provides you with a copy of the DPM server and installation data, which you can recover in the event of a network failure or disaster. When the DPM Databases node is selected for a backup job, Backup Exec performs a consistency check of the databases before the backup job starts. If the consistency check fails, the backup continues or stops depending on your Backup Exec database settings.
Protected Servers Backup Job - The Protected Servers node displays each DPM file server of the DPM protection group by name. Within each file server node, replica sets of the data sources (shares, volumes, folders, and files) appear as volumes. Backup Exec can back up any file server or data source protected by DPM. For example, if a DPM protection group has three file servers, the three file servers can be selected for backup. Alternatively, you can select only part of the data, such as the replica set of volume C on file server PHDPM2.
1387
Appendix Q, Symantec Backup Exec - Agent for Microsoft Data Protection Manager
Backup Job with DPM Data
To keep critical business data only, selectively choose information from specific replicas. If necessary, you can use the replica set backups to rebuild server data. Along with backups of the databases, the replica sets can be used to restore your DPM environment in the event of a disaster.
Shadow Copy Backup Job - The Shadow Copies node displays a list of the available shadow copies on the DPM server. Shadow copies are created by Volume Shadow Copy Service (VSS) and consist of a static picture of DPM replicas. It is not necessary to back up shadow copies regularly. Most of the data captured from shadow copy to shadow copy is redundant because, typically, the majority of the data on the server does not change between snapshots. Backup Exec displays the DPM shadow copies by the date and time the DPM shadow copy was created. Each initial shadow copy of your DPM file servers should be backed up. From that point forward, you can back up shadow copies as needed. For example, if you intend to take a server offline, it might be helpful to back up the most recent shadow copy before doing so. Caution Back up DPM shadow copies on an ad-hoc basis due to the quantity of redundant data that shadow copies typically contain.
Related Topics: Using Backup Execs Windows Explorer Interface on page 305 Creating a Backup Job on page 261
1388
Restore Job with DPM Data

Restoring DPM data involves selecting information from the Backup Exec media server and restoring it to a DPM server, protected file server, or alternate destination. In the Resource view, Backup Exec displays the DPM Databases and Protected Servers nodes under the Microsoft Data Protection Manager node. DPM shadow copies are listed under each applicable DPM file server node. Note When restoring DPM data, you must have rights to the selected servers.
Restore Job Properties Selections screen in Resource View
DPM Database Restore Job - By default, Backup Exec restores the full database back to the DPM server from which it originated. The DPM Databases node displays the list of DPM database backup sets from which you can restore. Protected Servers Restore Job - By default, DPM replica sets are restored back to the DPM server from which they were backed up. You can use Backup Exec to redirect the data to an alternate destination.
Appendix Q, Symantec Backup Exec - Agent for Microsoft Data Protection Manager
1389
You can restore all or part of the backed up data. For example, if you back up a DPM file server, you can restore the entire server, individual folders, or individual files. Any data not backed up cannot be selected, so the accompanying check box is grayed out.
Shadow Copy Data Restore Job - The DPM file server nodes are listed by name in the Resource view. By default the shadow copy data is restored to the file server from which it originated. Using Backup Exec, you can redirect the data to any file server in the DPM protection group or an alternate destination to which you have rights. In Media view, you can locate the DPM shadow copies by process of elimination. The databases are labeled with a path that includes the phrase DPM Databases. The DPM replica sets are labeled with a path that includes the phrase Protected Servers. The DPM shadow copies are labeled with the DPM file server name and volume, such as PHDPM2\C:. Backup Exec enables you to restore data from within the DPM shadow copy. For example, if you used Backup Exec to back up a DPM shadow copy that was created on Monday at 10:00 A.M., and someone lost a file named financial.doc on Monday at 11:00 A.M., you can restore the file financial.doc from the DPM shadow copy created at 10:00 A.M. to the DPM file server from which the data originated. Before restoring DPM shadow copy data, you can verify the DPM shadow copy date and time by viewing the properties of the files that were originally backed up. Verifying the date and time can be useful if your user knows the approximate time a file was lost.
Related Topics: Restore Operations and the Catalog on page 452 Redirecting a Restore Operation on page 487 Using the Resource View on page 479 Using the Media View on page 479
1390
Appendix
Symantec Backup Exec Remote Agent for NetWare Servers

The Backup Exec Remote Agent for Windows and NetWare Servers (Remote Agent) is installed as a separate, add-on component that must be used for the backup and restore of remote Windows or NetWare resources. This section outlines protecting remote NetWare resources. For information on protecting remote Windows resources, see Symantec Backup Exec - Remote Agent for Windows Servers on page 789. The Remote Agent allows network administrators for Windows servers to perform backup and restore operations on NetWare servers that are connected to their network. The Remote Agent supports NetWare 4.2, NetWare 5.1, NetWare 6.0, and NetWare 6.5. Because the Remote Agent is also a Client Access License (CAL), it enables you to fully protect your NetWare data and to perform accelerated backups of NetWare data. You cannot select data and special files on resources for a remote NetWare server for backup until a Remote Agent has been installed. The Remote Agent is a NetWare Loadable Module (NLM) installed on the NetWare server. The Remote Agent provides faster backups by locally performing tasks that in typical backup technologies require extensive network interaction. For example, instead of waiting for requests and data packets to be sent between the NetWare server and the media server each time a file is selected for backup, the Remote Agent processes backup data into continuous streams that use Novells Storage Management Services (SMS) and that the media server then processes as a single task. The Remote Agent is fully Novell SMS-compliant.
1391
Requirements for Installing the Remote Agent on a NetWare Server
Requirements for Installing the Remote Agent on a NetWare Server

The following are required to install the Remote Agent on a NetWare server:
The BEWS media server must have network access via the TCP/IP protocol to the remote NetWare server. The computer from which the installation program is running must be able to access the NetWare server. You must have administrative privileges on the NetWare server on which the agent is being installed.
Installing the Remote Agent on a NetWare Server

When you install the Remote Agent on the NetWare server, the following occurs:
A directory called BKUPEXEC is created in the SYS: volume, and the latest tested versions of the NLMs needed by Backup Exec to process NetWare-specific requests are copied to the BKUPEXEC/NLMS directory. The BESTART.NCF and BESTOP.NCF files are created and placed in the SYS:SYSTEM directory. These files contain commands to load the appropriate NLMs that allow the NetWare server to be backed up.
Note The Remote Agent is installed remotely from the Windows media server. If you have previously installed the Remote Agent on NetWare servers, run BESTOP from each NetWare console before installing the Remote Agent on those servers again. For instructions on installing the Remote Agent on NetWare Servers, see Installing Backup Exec Agents to Remote Computers on page 77. 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 on page 1402. Related Topics: Installing Backup Exec Agents to Remote Computers on page 77 Adding BESTART to the AUTOEXEC.NCF File on the NetWare Server on page 1393
1392
Installing the Remote Agent on a NetWare Server
Adding NetWare Servers to the NetWare Agents List

In order for Backup Exec to display a NetWare server in the NetWare Agents list, the agent must either advertise its existence or you must manually add the servers running the Remote Agent. Running BESTART at the NetWare server automatically loads Novells SMDR.NLM component, which advertises the availability of the server for backups using both the IPX/SPX/SAP and TCP/IP/SLP protocols. These protocols must be enabled on the network and in Backup Execs Network and Firewall dialog box in order for the servers to be automatically added to the NetWare Agents list. To access the Network and Firewall dialog box, click Tools, then click Options, and then click Network and Firewall. If your network cannot run these protocols, you must manually add the NetWare servers names to Backup Execs server list. For information about manually adding NetWare servers, see Default Settings for the Remote Agent on page 1402.
Adding BESTART to the AUTOEXEC.NCF File on the NetWare Server

After installing the Remote Agent on the NetWare server, you should load the latest Novell patches. You can also add the BESTART command, which loads the Remote Agent whenever the server is booted, to the AUTOEXEC.NCF file. To edit the NetWare servers AUTOEXEC.NCF file: 1. Add the command BESTART as the last line in the AUTOEXEC.NCF file so that the Remote Agent is automatically started each time the NetWare server is booted. 2. After saving the AUTOEXEC.NCF file, reboot the NetWare server in order for the changes to take effect.
Appendix R, Symantec Backup Exec - Remote Agent for NetWare Servers
1393
About Backing Up NetWare Servers
Unloading the Remote Agent

If you added BESTART as the last line in the AUTOEXEC.NCF file on the NetWare server, the Remote Agent is automatically loaded whenever the AUTOEXEC.NCF file is executed on the NetWare server. You can unload it by typing a command. To unload the Remote Agent: 1. At the NetWare servers console prompt:, type: bestop 2. Press ENTER. All NLMs associated with the Agent will be unloaded.

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
1394
About Backing Up NetWare Servers Necessary rights for NFS backup To do this: Archive You need these rights: Read files File scan Modify file attributes Erase files
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
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.
1395
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. 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.
1396
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.
1397
Backing Up NetWare Servers

Note Backup Exec does not support backing up double-byte character sets for NetWare servers that have a double-byte code page loaded. To back up a NetWare server: 1. On the navigation bar, click Backup.
Backup Selections
2. Double-click Remote Selections. 3. Doubleclick NetWare Agents. 4. Double-click the NetWare computer icon for the NetWare server you want to back 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.
5. 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. NetWare File System and NetWare Directory Services (Novell Directory) are listed separately. Each directory that you want to back up must be selected. The following screen shows a NetWare server (BOBG_NW5) that has both the file system and the NetWare Directory Services selected for backup:
Backup Selections for NetWare server
6. If you want to change the Backup default, on the Properties pane, under Settings, click NetWare SMS. 7. 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. 8. Continue creating the job by following the procedures in Creating a Manual Backup Job by Configuring Job Properties on page 262.
1399
About Restoring NetWare Servers

Before restoring your NetWare server, you may want to read about restore operations in general in Restoring Data on page 451. 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.
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 479. 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 487. Note If you restore NetWare data to a Windows volume, trustee data associated with the files is not restored. If the file was compressed by NetWare and was backed up compressed, you will not be able to restore it to a Windows volume. 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.
1400
Data backed up from a Novell server can be restored to a Windows volume; again, NDS objects cannot be redirected.
6. Complete the restore job by following the procedures described in Creating a Manual Restore Job by Configuring Job Properties on page 458. Note If you clear the Preserve tree option on the General Restore Job Properties and the target directory is the volume root, Backup Exec will still use the Preserve tree option and data will still be restored with its original directory intact.
1401
Default Settings for the Remote Agent

By default, Backup Exec detects NetWare servers that are advertising using either the TCP/IP or IPX/SPX protocols. If these protocols are disabled, no NetWare remote agents will be detected and the NetWare Agents node will not display under NetWare Agents in the backup selections tree. You can change the default protocols and ensure that the correct protocol is enabled on the Options - Set Application Defaults dialog box. Note If a protocol is not installed on the system, it will not be available in this dialog. For example, if the IPX/SPX protocol is not installed on the media server, the IPX/SPX protocol checkbox is grayed out and disabled. Also through this dialog box, you can set network defaults for all backup and restore operations performed on the NetWare servers by Backup Exec, including specifying a dynamic port range to be used by the remote agent. You can override some of these defaults each time you create a backup or restore job. To enable the protocol and specify TCP dynamic port ranges on the media server: 1. On the Tools menu, click Options. 2. On the Properties pane, under Job Defaults, click Network and Firewall. 3. Select the protocols you want to use to detect NetWare servers. 4. If you selected TCP/IP as the protocol and want to specify a TCP dynamic port range, click Enable remote agent TCP dynamic port range and enter the port ranges. 5. Click OK. 6. 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.
1402

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. If you add a server name to this list, Backup Exec must be able to resolve the name to a TCP/IP address. If Backup Exec cannot resolve the name to a TCP/IP address, the server name appears in the server list, but Backup Exec is unable to connect to it. Backup Exec will be able to resolve the name if the NetWare server names and IP addresses are in your networks Domain Naming Services (DNS) database. If these names and IP addresses are not in DNS, you must manually add the names and IP addresses to the media servers HOSTS file, which usually is found in the SYSTEM 32\Drivers\ETC directory. 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
4. To manually add a server to the server list:
1403
Saving Configuration Information for the NetWare Server
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. The contents of your AUTOEXEC.NCF file.
1404
Disaster Recovery of NetWare Servers
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.

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

Reinstall NetWare. Reinstall the Remote Agent. Use the information from BEDIAG.FAX to restore your server configuration. Restore your latest backups. Intelligent Disaster Recovery for NetWare is available as a separate add-on option to Backup Exec for NetWare Servers. For more information, see the Symantec Backup Exec for NetWare Servers Administrators Guide.
Tip
1405
1406
Appendix
Accessibility and Backup Exec
Symantec products meet federal accessibility requirements for software as defined in Section 508 of the Rehabilitation Act:
http://www.access-board.gov/508.htm
Keyboard shortcuts are available for all graphical user interface (GUI) operations and menu items. Symantec products are compatible with operating system accessibility settings as well as a variety of assistive technologies. All manuals also are provided as accessible PDF files, and the online help is provided as HTML displayed in a compliant viewer. The following topics detail accessibility features and compliance in Backup Exec:

Keyboard Navigation and Shortcuts in Backup Exec on page 1408 General Keyboard Navigation Within the GUI on page 1408 Keyboard Navigation Within Dialog Boxes on page 1409 Keyboard Shortcuts on page 1410 Support for Accessibility Settings on page 1414
1407
Keyboard Navigation and Shortcuts in Backup Exec

All program functions and menu items are accessible using the keyboard exclusively. Backup Exec uses standard operating system navigation keys and keyboard shortcuts. For its unique functions, Backup Exec uses its own keyboard shortcuts, which are documented Keyboard Shortcuts on page 1410. Items in the task pane that do not have keyboard shortcuts can be accessed by using the operating systems "mouse keys", which allow you to control the mouse through the numerical keyboard. To see a table of the standard Microsoft navigation keys and keyboard shortcuts, select your version of Microsoft Windows from the table at: http://www.microsoft.com/enable/products/keyboardassist.aspx
General Keyboard Navigation Within the GUI

You can navigate and use Backup Exec with only the keyboard. In the GUI, the current active tree or table has a dark blue highlight, and the current active tab, radio button, or checkbox is enclosed within a rectangle formed by dotted lines. These areas are said to have focus and will respond to commands. All Symantec GUIs use the following keyboard navigation standards:
The TAB key moves the focus to the next active area, field, or control, following a preset sequence. SHIFT+TAB moves the focus in the reverse direction through the sequence. CTRL+TAB exits any Console area that you internally navigate with the TAB key. UP and DOWN ARROW keys move focus up and down the items of a list. The ALT key in combination with the underlined mnemonic letter for a field or command button shifts the focus to that field or button. Either ENTER or the SPACEBAR activates your selection. For example, after pressing the TAB key to select Next in a wizard panel, press the SPACEBAR to display the next screen. SHIFT+F10 provides access to context menus.
1408
Keyboard Navigation Within Dialog Boxes

Dialog boxes contain groups of controls necessary to set options or settings for programs. Here are some general rules about dialog box navigation:
The TAB key moves focus between controls within the dialog box along a preset sequence. Controls displaying a mnemonic (an underlined letter) can be selected regardless of focus by typing ALT and the underlined letter. A dark border indicates the default command button. Press ENTER at any time to choose the button with a dark border. ESC chooses the Cancel button if one exists. SPACEBAR chooses a control you select with the TAB key. SPACEBAR changes the state of a checkbox that has focus. Typing a mnemonic (if one is available) will move the focus to the checkbox and change its state. Arrow keys move focus within radio buttons, list boxes, sliders, groups of option controls, or groups of page tabs. Items that cannot be changed are not visited by the TAB key sequence. Options that are unavailable are grayed-out and can neither be selected nor given focus.
While the controls described here are typically found in dialog boxes, they also can occur in other contexts. The same navigation standards will apply.
Tabbed Dialog Boxes

Some dialog boxes use tabbed pages to subcategorize groups of many options. Each tabbed page contains different groups of controls. Use TAB to move the focus between tabbed pages within a dialog box. Typing the mnemonic for a tab also moves the focus to the tabbed page and displays its page of controls. The following table lists keyboard navigation rules within tabbed dialog boxes:
Keyboard Navigation within Tabbed Dialog Boxes Keyboard input CTRL+PAGE DOWN or CTRL+TAB CTRL+ PAGE UP Result Switches to the next tab and displays the page.
Switches to the previous tab and displays the page.
Appendix S, Accessibility and Backup Exec
1409
Keyboard Navigation and Shortcuts in Backup Exec Keyboard Navigation within Tabbed Dialog Boxes (continued) Keyboard input RIGHT ARROR or LEFT ARROW Result When the focus is on a tab selector, chooses the next or previous tab in the current row and displays the page.
List Boxes
List boxes display a column of available choices. There are different kinds of list boxes with additional navigation conventions:
Drop-down list boxes by default show only the selected item. A small button to the right of the control shows a downward-pointing arrow. Select the arrow to display more items from the list box. If there are more choices than can fit in the preset list box area, a slider appears along the side of the list box. Show or hide the list using ALT+DOWN ARROW, ALT+UP ARROW, or F4. The TAB key selects an item. Extended selection list boxes support selecting single items, blocks of items, or combinations of the two. After selecting an item, hold down CTRL+navigation keys to select or clear additional items or blocks of items.
Keyboard Shortcuts
All menu items can be selected by using accelerator or mnemonic keyboard shortcuts. An accelerator is a key combination that provides shortcut access to a GUI function. A mnemonic (sometimes referred to as a hot key) is a single-key equivalent (used in combination with the ALT key) for selecting GUI components such as menu items. The mnemonic hot key letter is underlined in the GUI. Routine functions such as opening, saving, and printing files can be performed using the standard Microsoft keyboard shortcuts. Other menu items are unique to Backup Exec. The following table lists the keyboard shortcuts unique to Backup Exec:
Keyboard Shortcuts Unique to Backup Exec Backup Exec Accelerator ALT Backup Exec Mnemonic F Result
The File menu expands. From the File menu, you can create
new jobs, devices and media, print selected items, view properties, or exit Backup Exec.
1410
Keyboard Navigation and Shortcuts in Backup Exec Keyboard Shortcuts Unique to Backup Exec (continued) Backup Exec Accelerator ALT Backup Exec Mnemonic E Result
The Edit menu expands. From the Edit menu, you can
rename, delete, copy, and select items. In addition, you can work with selection lists and search catalogs.
ALT
The View menu expands. From the View menu, you can change the information that displays on the screen. The options on the View menu change according to which
item is selected on the navigation bar.
ALT
The Network menu expands. Use the Network menu to
work with Backup Exec logon accounts, connect to media servers on the network, or to reconnect to a local media server.
ALT
The Tools menu expands. The Tools menu provides many
important options for working with Backup Exec, including starting and stopping services, using device and media operations, using Wizards, and setting default options.
ALT
The Window menu expands. Use the Window menu to
move to a new window or view.
ALT
The Help menu expands. Use the Help menu to access
Backup Exec documentation and various Symantec web sites.
Select secondary menu items by opening the main menu and using the UP or DOWN ARROW key until the desired item is highlighted. Press the RIGHT ARROW key to open a submenu, and ENTER to select your choice. Keyboard shortcuts are not case-sensitive. Mnemonic keystrokes may be pressed either sequentially or simultaneously. All menu items have mnemonics, but not all menu items have accelerators.
1411
The following table lists the shortcut keys in Backup Exec Utility.:
Keyboard Shortcuts Unique to Backup Exec Utility Backup Exec Accelerator ALT Backup Exec Mnemonic F Result
The File menu expands. From the File menu, you can create
new media servers and media server groups, view properties, or exit Backup Exec Utility.
ALT
The Edit menu expands. From the Edit menu, you can
rename, delete, and select items
ALT
The View menu expands. From the View menu, you can change the information that displays on the screen. The Help menu expands. Use the Help menu to access
ALT
The following table lists the shortcut keys in the Backup Exec Desktop and Laptop Option Administration Console:
Keyboard Shortcuts Unique to Backup Exec Desktop and Laptop Option Administration Console Backup Exec Accelerator ALT Backup Exec Mnemonic F Result
The File menu expands. From the File menu, you can create new Profiles and Storage Locations, and add users. The Edit menu expands. From the Edit menu, you can restore files, search for files to restore, manage alerts, and delete items. The View menu expands. From the View menu, you can change the information that displays on the screen. The Network menu expands. Use the Network menu to
ALT
ALT
ALT
work with administrator accounts, connect to media servers on the network, or to reconnect to a local media server.
1412
Keyboard Navigation and Shortcuts in Backup Exec Keyboard Shortcuts Unique to Backup Exec Desktop and Laptop Option Administration Console Backup Exec Accelerator ALT Backup Exec Mnemonic T Result
The Tools menu expands. Use the Tools menu to set global excludes, access all DLO wizards, and manage service credentials. The Window menu expands. Use the Window menu to
ALT
move to a new window or view.
ALT
The Help menu expands. Use the Help menu to access
The following table lists the shortcut keys in the Backup Exec Desktop and Laptop Option Desktop Agent:
Keyboard Shortcuts Unique to Backup Exec Desktop and Laptop Option Desktop Agent Backup Exec Accelerator ALT Backup Exec Mnemonic F Result
The File menu expands. From the File menu, you can
minimize or exit the Desktop Agent.

ALT V The View menu expands. From the View menu, you can change the information that displays on the screen. The Tasks menu expands. Use the Tasks menu to run a job
ALT
or refresh the view.
ALT
The Tools menu expands. Use the Tools menu to reset
dialog boxes and accounts.
ALT
The Help menu expands. Use the Help menu to access the
online help for the Desktop Agent
1413
Support for Accessibility Settings
Support for Accessibility Settings

Symantec software responds to operating system accessibility settings. Symantec products are compatible with Microsoft's accessibility utilities. In Windows 2000, accessibility options involving keyboard responsiveness, display contrast, alert sounds, and mouse operation can be set through the Control Panel. To set accessibility options: 1. On the Start menu, select Settings, and then select Control Panel. 2. Select Accessibility Options. Note You can also set accessibility options through the Accessibility Wizard. On the Start menu, select Programs, and then select Accessories. Select Accessibility, and then select Accessibility Wizard. Note Though all graphics in Symantec documentation can be read by screen readers, setting your screen reader to ignore graphics may improve performance.
1414
Glossary
ADAMM Advanced Device and Media Management, the Backup Exec 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 computer. Agent A component that allows workstations or other computers, for example, Microsoft SQL Server, to interact with the Backup Exec media server. Alert An event that usually requires some form of user interaction or acknowledgment. Alert category A group used by Backup Exec to contain similar alert. Examples of alert categories include job success, install warning, and database maintenance failure. Alert source A source that can generate an alert. Alert sources include job, media, device, and system. Alert type Determined by the severity of the alert, an alert type has a corresponding colored icon. Alert types include Error, Warnings, Information, and Attention Required. Allocated media Media that belong to a user media set, and that have current append and overwrite protection periods. 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.
1415
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. Audit log A running history of all actions performed in the Backup Exec system. An entry into the log is created each time an action that is configured to display in the audit log occurs. Backup A process where selected files on a computer drive are copied and stored on a reliable form of media. Backup Exec Service Account A user account configured for the Backup Exec 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 storage 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 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 - Using archive bit (reset archive bit). Includes all of the files selected for backup and resets the archive bit to indicate that the files have been backed up. - Using modified time. Includes all of the files selected for backup and allows the use of incrementals and differentials using the modified date and time stamp. - Copy the files. Includes all selected data, and does not affect any media rotation scheme because the archive bit is not reset. - Archive the files (delete files after successful copy). Backs up the selected data, verifies the media, and then deletes the data from the volume. For data to be deleted, rights to delete a file must be granted; otherwise data will be backed up, but not deleted.
1416
Differential - Back up changed files since last full - Using archive bit (does not reset archive bit). Includes all files that have changed (based on the archive bit) since the last full backup, and does not affect any media rotation scheme because the archive bit is not reset. - Using modified time. Includes all files changed since the last full backup, using the files last modified date and time stamp. Make sure that the same script or selection list is used for the differential backup that was used for the full backup. Incremenatal - Back up changed files since last full or incremental - Using archive bit (reset archive bit). Includes only the files that have changed (based on the archive bit) since the last full or incremental backup and resets the archive bit to indicate that the files have been backed up. - Using modified time. Includes all files that have changed since the last full or incremental backup, using the files last modified date and time stamp. Make sure that the same script or selection list is used for the incremental backup that was used for the full backup. Working Set - Back up files - Changed today. Backs up all files that were created or modified today. - 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. Backup set When a backup job is run, the data selected from a single resource, such as a Microsoft Exchange dataset, 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 requires minimal time to get a computer running in the event of a disaster. Baseline The first backup to run that is associated with the synthetic backup. The baseline backup runs one time only, and will always back up all of the files on the selected resources when it runs. This backup creates the baseline backup set that is used by the subsequent incremental backups.
Glossary 1417
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. Central administration server A Backup Exec 10.0 media server with the Central Admin Server Option (CASO) installed. In a CASO environment, the central administration server becomes the centralized focal point of the Backup Exec enterprise. It is the media server where you make decisions on what data and servers are to be protected in your environment. It is also the media server where the building blocks of job creation take place - the creation of policies and the association of selection lists to those policies. Centralized catalogs Backup Exec catalogs that have been moved from a managed media server to a central administration server in order to facilitate centralized restore operations. Centralized catalogs are only available with the Central Admin Storage Option. Centralized restore Only available with the Central Admin Server Option, centralized restore is the process where you can centrally initiate, run and manage restore operations from a centralized location in your Backup Exec CASO environment. 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. Custom error-handling rule An error-handling rule that you can define in Backup Exec for a specific error code in an error category. When a job fails with the error code that is associated with the custom error-handling rule, the retry options and the final job disposition are applied to it. Custom filter A filter that you can define in Backup Exec to display only the information that you specify in the Job Monitor.
1418
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 - Back up changed files since last full 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 One of the available backup methods. Includes all files since the last full backup using the files last modified date and time stamp. Device In Backup Exec, device can refer to a robotic library drive, a stand-alone drive, a backup-to-disk folder, a backup-to-disk device, or a cascaded drive pool. Device pool A grouping of devices for Backup Exec operations. Jobs assigned to the device pool are run on the first available device. Duplicate Backup Data template A template that allows you to use a multi-stage backup strategy for backing up data to disk and then copying it to tape. Error-handling rule Default or custom rules that set retry options and final job disposition for failed or canceled jobs. Retry options let you specify how often to retry a job if it fails and the time to wait between retry attempts. The final job disposition lets you either place the job on hold until you can fix the error, or cancel the job and reschedule it. Event Action that occurs during a Backup Exec operation. For example, the canceling of a job. Failover When a node in a cluster becomes unavailable and cluster resources migrate to an available node.
Glossary
1419
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 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 - Using modified time One of the available backup methods. Includes all of the files selected for backup and allows the use of incrementals and differentials using the modified date and time stamp. Full - Back Up Files - Using archive bit (reset archive bit) One of the available backup methods. Backs up all of the files selected for backup and resets the archive bit to indicate that the files have been backed up. Full - Back Up Files - Copy the files 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. Full - Back Up Files - Archive the files (delete files after successful copy) One of the available backup methods. 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. Hub A connecting device in a network that joins communication lines together.
1420
Imported media Media created by a product other than this installation of Backup Exec. Incremental - Back up changed files since last full or incremental - Using archive bit (reset archive bit) One of the available backup methods. 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 - Back up changed files since last full or 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. Job An operation that has been scheduled for processing by the media server. For example, if you make selections and submit a backup based on those selections, you have created a backup job. Jobs contain source or destination information, settings, and a schedule. Types of jobs include backup, restore, media rotation, resource discovery, report, test run, and utility jobs. Job delegation A feature of the Central Admin Server Option, job delegation is the process in which jobs are distributed using load-balancing technology to available storage devices by a central administration server in a Backup Exec environment. 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. Junction point A physical location on a hard disk that points to data at another location on the hard disk or on another storage device. See Mount Point.
Glossary
1421
Load-balancing A feature of the Central Admin Server Option, load-balancing is a term used to describe the automatic distribution of multiple jobs from a central administration server for processing among the various storage devices across multiple managed media servers in the Backup Exec enterprise. Local device A disk or tape drive connected to a server and only available to the server to which it is attached. Logon account A Backup Exec logon account stores the credentials of a Windows user account. Logon accounts enable Backup Exec to manage user names and passwords, and can be used to browse resources or process jobs. Managed media server A feature of the Central Admin Server Option, a managed media server is a media server that is managed by a central administration server. Managed media servers are responsible for the actual processing of backup and restore jobs in a CASO environment. 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 Microsoft Windows server where Backup Exec is installed and the Backup Exec services are running. Media server pools A feature of the Central Admin Server Option, media server pools enable you to restrict protected server backup jobs to a specific set of managed media servers and their attached storage devices. 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. Media vault A logical representation of the actual physical location of media. Mount point The directory under which a file system is accessible after being mounted. See also: Junction point 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 110).
Glossary
1423
Offhost backup A feature of the Advanced Disk-based Backup Option that enables the backup operation to be processed on a Backup Exec media server instead of on the remote computer, or host computer. Moving the backup from the remote computer to a media server enables better backup performance and frees the remote computer as well. 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. Policy A method for managing backup jobs and strategies. Policies contain templates, which provide settings for jobs. Protected server Any computer on the network that is being backed up by Backup Exec, including Backup Exec media servers. Recyclable media Media that is assigned to a media set but has expired data overwrite protection periods. Remote administrator The Backup Exec user interface (Administration Console) that is run on remote computers. Remote Agent A Backup Exec system service that runs on Microsoft Windows computers or NetWare remote servers and workstations and allows remote backup and restore of those computers and provides increased backup throughput. Resource Data files and databases, such as Windows shares and Microsoft SQL databases, that can be selected for backing up.
1424
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. 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.
Glossary
1425
Snapshot A consistent point-in-time view of a volume that is used as the reference point for the backup operation. After a snapshot is created, the primary data can continue being modified without affecting the backup operation. Synthetic backup A feature of the Advanced Disk-based Backup Option that enables a full backup to be assembled, or synthesized, from a baseline and subsequent incremental backups. The benefits of using a synthetic backup include a reduced backup window since the synthetic backup can be scheduled outside of the time critical backup window and reduced network traffic since the synthetic backup does not need to access the network. System media All media that has been introduced into the Backup Exec system, except those media that have been assigned to a media set. Template A required element of a policy that defines how and when Backup Exec processes a job. Templates specify the device, settings, and schedule options to be used for the job. Each policy must contain at least one template. Template rule A method of setting up relationships between templates in a policy. Unique Message Identifier (UMI) Errors that are reported in the job log each have a unique code, called a Unique Message Identifier (UMI). These codes contain hyperlinks that you can click to go to the Symantec Software Support Services web site and access technical notes and trouble-shooting steps that are related to a specific error. Unique Message Identifier (UMI) error code establishes unique error and message codes across all Symantec products. 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 - Back up files - Changed today One of the available backup methods. Backs up all files that were created or modified today.
1426
Working Set - Back up files - Last accessed in (x) days 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 in the Files accessed in x days field that you want to include data that has been accessed in a specific number of days.
Glossary
1427
1428
Index
Numerics 64-bit Remote Agent for Windows Servers installing using command script, 795 installing using installation program, 793 overview, 791 A accessibility dialog boxes, 1409 keyboard navigation, 1408 keyboard shortcuts, 1410 overview, 1407 settings, 1414 account, user for Oracle Agent, 1301 active alerts defined, 502 responding to, 507 viewing, 502 Active Alerts by Media Server Report, 559 Active Alerts report, 559 Active Directory Application Mode Writer, 347 Active Directory, backing up in Exchange 2000 and 2003, 1071 Active File Exclusion Exchange data, 1080 active jobs canceling, 418 removing hold, 419 viewing, 405 viewing properties, 415 AD/AM Writer, 347 ADAMM, defined, 1415 add users in DLO, CSV file to, 1179 administration console defined, 1415 Desktop Agent Console, 1230 Desktop and Laptop Option (DLO), 1134 overview, 110 role in backup process, 55 administrator accounts creating, 1137 deleting, 1141 modifying, 1140 Advanced Device and Media Management (ADAMM) database overview, 957 device management overview, 123 Devices view, 125 media operations overview, 251 Advanced Disk-based Backup Option baseline, setting, 876 best practices for offhost backup, 891 host computer, defined, 888 offhost backup overview, 888 offhost backup requirements, 889 offhost backup snapshot provider, choosing, 893 offhost backup, List Snapshot Providers option, 894 offhost backup, single volume snap, choosing, 894 synthetic backup policy, example, 882 synthetic backup template rules, 887 synthetic backup template rules, example, 882 synthetic backup template, requirements, 878 synthetic backup, collecting additional information for backups, 879 synthetic backup, creating, 882 transportable snapshots, defined, 888 VSFW FlashSnap option, using with offhost backup, 890 Advanced File Selection options described, 288 selecting files, 288 Advanced Open File Option cache file location, 1007 cache file size, setting, 1009 changing default settings for Symantec VSP, 1006 databases, backing up, 993 encrypted files, backing up, 995 installing using the command line, 997 minimum quiet time, setting, 1010 overview, 51, 991 requirements, 995 Snap Start for VSFW volumes, 1005 snapshot providers, 994 1429
Symantec Volume Snapshot Provider, 1001 uninstalling, 999 uninstalling using the command line, 998 using with Exchange Server Agent, 1074 wizard, 1008 Advanced options for backup, 277 for duplicate job, 316 for synthetic backup, 885 Advanced tab, 149 advertising to media servers, Remote Agent for Windows Servers, 800 agent for Microsoft Data Protection Manager backup job with DPM data, 1386 database backup job, 1387 database restore job, 1389 overview, 1385 protected servers backup job, 1387 protected servers restore job, 1389 requirements, 1386 restore job with DPM data, 1389 shadow copy backup job, 1388 shadow copy restore job, 1390 Agent for Microsoft SharePoint Portal Server about, 1372 about restoring a SharePoint Server or Workspace, 1364 adding a server farm, 1373 backing up SharePoint Portal Server 2003 resources, 1376 disaster recovery, 1370 installing, 1360 overview, 1359 redirecting a restore for SharePoint Portal Server 2003, 1381 redirecting restore jobs, 1366 restoring SharePoint Portal Server 2003 resources, 1378 selecting SharePoint Portal Server 2003 resources for backup, 1372 setting default options, 1384 system requirements, 1359 agent, defined, 1415 agent.cfg commands (Backup Exec 8.x and 1430
9.x Agent for Unix), 653 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, 51 See also Desktop and Laptop Option upgrading on remote computers, 105 alert category, defined, 1415 alert history defined, 502 viewing, 502 Alert History report, 561 alert notification, printers, 528, 530 alert source, defined, 1415 alert type, defined, 1415 alerts alert types, 501 assigning recipients, 533 clearing recipients, 534 configuring, 501 configuring default options, 121 defined, 501, 1415 defined for DLO, 1201 deleting in DLO, 1205 displaying in DLO, 1204 filters, 502 grooming, 1200 managing in DLO, 1205 modifying alert category properties, 534 monitoring in DLO, 1200 notification methods, 514 properties, 505 responding to, 501, 507 setting filter, 504 viewing, 502 viewing job log, 509 views, 502 all media, defined, 227 allocated media defined, 228, 1415 overwriting, 232 AOFO See Advanced Open File Option append options for media, 232 append period defined, 214, 219, 1415 Administrators Guide
setting for media set, 219 append to media option, 269 archive bit, defined, 357, 1416 archive logging Lotus Domino, 1334 recovery of Lotus Domino, 1344 archiving freeing disk space, 309 NTFS and VFAT file systems, 310 using disk grooming, 310 ARCserve media, restoring data from, 477 ASR files, in IDR copy to diskette or CD, 920 defined, 906 ASR See Automated System Recovery audit log viewing, 437 Audit Log report, 563 audit log, defined, 1416 AUTOEXEC.NCF file, Remote Agent for NetWare Servers, 1393 auto-inventory media after import job completes, 206 Automated System Recovery, 610 Automated User Assignment, 1168 creating, 1168 defined, 1122 deleting, 1173 modifying, 1171 priority, changing, 1171 properties, viewing, 1172 automatic exclusion of files during volume level backups, 1028, 1080 availability windows, 301 B back up on log on/off option in DLO, 1152 backing up desktop data, 1238 files and directories by following junction points, 277 media server using one-button backup, 308 Microsoft clusters database files, 683 local disks, 682 shared disks, 682 Windows 2000 and Windows Server 2003, 681 Index
Outlook PST files, 1247 R/3 database, 1353 remote storage, 278 VERITAS clusters database files, 695 local disks, 694 shared disks, 694 Windows 2000 and Windows Server 2003, 693 BACKINT alerts, 1349 implementation, 1347 overview, 1348 backup defined, 1416 overview, 259 Backup Exec accessibility, 1407 dialog boxes, 1409 keyboard shortcuts, 1410 installing command line installation, 81 installation requirements, 65 overview, 65 silent mode installation, 81 uninstalling, 93 upgrading, 104 using Repair option, 91 overview additional options, 51 how it works, 55 new features, 45 system requirements, 59 repairing, 91 starting after installing Library Expansion Option, 1117 upgrading options on remote computers, 105 overview, 104 Backup Exec 8.x and 9.x Agent for Unix, 653 advertise to media server, 655 back up symbolic links, 646, 652, 655 configuring, 653 loading, 656 system requirements, 649 Backup Exec 8.x and 9.x Agent for Unix commands agent.cfg commands, 653 exclude directories/files, 655 1431
identify exported paths, 654 include remote file systems, 654 password-protect published path, 654 password-protect workstation, 654 preserve ctime, 655 publish directory tree, 654 write-protect published path, 654 Backup Exec Assistant, using, 116 Backup Exec Environment Check, 63 Backup Exec for Windows Servers, described, 43 Backup Exec Server in SAN, 957 Backup Exec Service Account, defined, 66 Backup Exec services account, defined, 1416 Backup Exec Services Manager dialog box, 92 stopping and starting, 92 Backup Exec Utility CASO Tasks change catalog storage location, 750 Disable CASO job delegation on media server, 748 enable CASO job delegation on media server, 748 move central administration server, 749 overview, 745 Remove central administration server, 747 set central administration server, 746 Database Tasks, 756 aging the database, 757 change database access, 762 checking the database consistency, 757 compacting the media server database, 758 copy database, 764 dumping a media server database, 758 new Backup Exec database location, 763 rebuilding a media server database indices, 759 recovering a media server database, 760 repairing a media server 1432
database, 759 General Tasks adding new media servers, 722 deleting a media server, 724 deleting a media server group, 725 deleting media servers from the All Media Servers subnode, 724 running Backup Exec Diagnostics, 726 viewing media server properties, 729 Media Server Group Tasks adding a media server, 765 removing a media server, 766 set central administration server for a media server group, 766 SAN SSO Tasks configuring the SAN SSO, 753 moving the primary SAN SSO Server, 755 promotion to a primary SAN SSO Server, 754 removing the primary SAN SSO Server, 752 setting the primary SAN SSO Server, 752 Services Tasks applying copied media server configuration information, 743 changing service accounts, 736 copying media server configurations, 742 editing server configurations, 737 overview, 733 starting services, 734 stopping services, 734 updating configuration information for new media server name, 743 starting the Backup Exec Utility, 718 Backup Exec Web Administration Console accessing help, 712 alerts, 715 how it differs from Backup Exec for Windows Servers, 711 installing, 710 navigating, 712 requirements, 709 setting Internet Explorer properties, 710 Administrators Guide
starting, 710 Tools tab, 714 backup file defined, 176 deleting, 187 recreating a deleted file, 188 renaming, 187 viewing and changing properties, 189 backup folder adding, 177 changing the path, 180 creating for removable media, 179 creating more disk space, 267 defined, 176 deleting, 181 designating location for, 178 overview, 176 pausing and resuming, 182 recreating, 182 renaming, 180 viewing properties, 183 backup folder, defined, 1416 backup job Advanced options, 277 choices for creating, 259 copying to another server, 394 creating manually, 262 creating using the wizard, 262 Data Protection Manager, 1386 Device and Media options, 267 overview, 261 pre/post commands, 281 scheduling, 398 selecting devices and data, 284 Selections options, 265 tasks to do before, 260 Backup Job Properties dialog box Exchange options, 1075 SQL Agent, 1024 Backup Job Success Rate, 564 backup methods defined, 1416 selecting, 272 setting default, 324 using modified time, 358 backup mode, Oracle Agent, 1297 backup network changing for a backup job, 339 configuring, 336 Index
overview, 334 setting up, 336 backup options backing up data in remote storage, 278 contents of mounted local drives, 277 backup selections adding, 1157 Backup Selection dialog box, 1157, 1242 macros in, 1162 backup selections, changing order, 291 Backup Set Details by Resource report, 566 backup set, defined, 1417 Backup Sets by Media Set report, 567 Backup Size by Resource report, 568 backup strategies See also names of individual agents choosing devices to back up, 353 defined, 351, 1417 frequency of backups, 351 increasing throughput with Remote Agent for Windows Servers, 789 length of data retention, 352 multiple devices per job, 353 one job per device, 353 protecting against viruses, 352 Backup to Disk, See Backup-to-Disk, 176 backup types archive, 354 copy, 354 daily, 355 differential, 354 full, 354 incremental, 355 working set, 355 Backup Wizard, launching, 262 backups option, Configure desktop and laptop, 1134 backup-to-disk renaming file, 187 renaming folder, 180 viewing folder properties, 183 bandwidth settings DLO, for users in, 1147 bar code labels and media ID, 234 default, 235 mixed media libraries, 236 overview, 235 robotic library support, 235 1433
bar code rules changing, 237 deleting, 237 setting up, 236 baseline, defined, 1417 baseline, setting for synthetic backup, 876 BE Diagnostics, running from server properties, 147 bediag.fax file, 1404 bediag.nlm utility, saving configuration information, 1404 BEGather, 632 besernum.xml file, importing serial numbers with, 68 BESTART command, to start Remote Agent for NetWare Servers, 1393 BESTOP command, to stop Remote Agent for NetWare Servers, 1394 BEUtility.exe utility Microsoft clusters, using in, 669 BEWAC, See Backup Exec Web Administration Console biparam.ini options, 1351 specifying Backup Exec parameters, 1351 BKUPEXECDLO MSDE database instance, 1210 block size, setting for drives, 156 Boot managers, restoring in IDR, 939 bootable media for IDR CD image, creating, 920 comparing types, 905 floppy diskettes, creating, 917 tape image, creating, 924 types of media, 905 buffer count, setting for drives, 157 buffer size, setting for drives, 156 build and version information, displaying, 629 byte count, incorrect, 624 C cache file location, for AOFO, 1007 cache file size, setting for AOFO, 1009 calendar display filters, 414 view filters, 414 viewing, 413 1434
cascaded drive pools adding drives, 141 creating, 139 defined, 124, 1418 deleting, 142 deleting drives, 142 overview, 139 properties, 143 renaming, 143 requirements for using, 139 using hardware compression in, 139 CASO Backing up with, 857 Backup options default network interface for delegated jobs, 858 Centralized Restore How it works, 862 multiple storage devices, 863 requirements, 862 Changes to Backup Exec, 853 job monitor and job history, 856 media servers view, 853 media servers view columns, 853 Components, 820 central administration server, 820 managed media servers, 821 Configuration Alerts, 845 communication statuses, 840 configuring catalog storage locations, 840 configuring device pools, 840 configuring time thresholds, 840 Notification, 847 recovering failed jobs, 845 setting a central administration server, 837 setting job history options for managed media servers, 844 setting job log options for managed media servers, 844 Configuration overview, 840 Configuration scenarios, 822 Deleting a managed media server, 852 Device and Media Property, 865 Disabling and enabling communications, 849 Error codes, 872 Administrators Guide
Features, 825 centralized alerts, 827 centralized catalog storage, 826 centralized job logs and history details, 827 centralized reports, 826 centralized restore, 827 job delegation, 825 media server pools, 827 getting started, 829 How it works, 821 Icons, 856 Installation, 832 managed media servers, 832 requirements, 828 upgrading a media server to a central administration server, 836 Job History Options Setting, 844 Managed Media Server status messages, 854 Media Server Pools, 866 adding, 867 creating, 867 deleting, 869 removing a managed media server, 870 renaming, 869 using, 866 no communication status, 841 Overview, 819 Pausing and unpausing a managed media server, 848 Pausing storage devices from the central administration server, 873 Recovered jobs, 841 Recovering failed jobs, 871 Remotely connecting to a managed media server, 851 Restoring Data, 860 centralized catalogs, 861 Running managed media server operations from a central administration server, 848 Stalled managed media servers, 841 Stopping and starting Backup Exec services, 850 Uninstalling, 839 Using the Media View, 861 Index
Viewing managed media server properties, 852 catalog defined, 1418 levels, 455 media in drive, 452 removing unused after x days, 455 searching, 483 catalog database, in SAN Shared Storage Option, 971 catalog operation errors DLT tape drive hangs, 622 Catalogs Using Media View, 861 central administration server, defined, 1418 centralized catalogs, defined, 1418 centralized restore, defined, 1418 CHECKCATALOG utility, 1021 CHECKDB utility, 1021 CHECKFILEGROUP utility, 1021 checkpoint restart on Microsoft cluster failover enabling or disabling, 667 overview, 665 circular logging Exchange 2000 and 2003, reviewing in, 1081 Exchange 5.5, reviewing in, 1081 Lotus Domino, 1334 recovery of Lotus Domino server, 1345 cleaning jobs, submitting for robotic libraries, 204 Cleaning tab for drive properties, 161 cleanings number performed, 127 set maximum number of, 127 clone CD image creating, 98 overview, 69, 98 clrest command, 687 Cluster Failover error-handling rule, 440, 444 cluster, defined, 1418 clusters Desktop and Laptop Option, 1210 disaster recovery entire cluster manually, 700 nodes using IDR, 698 1435
using IDR to prepare, 698 installation Backup Exec on a VERITAS cluster server, 691 Microsoft adding or removing a failover node, 668 all drives pool, 664 backing up shared disks, 682 BEUtility, 669 changing the order in which nodes fail over, 668 configurations, 670, 671, 672, 673, 675 creating drive pools, 664 database files, 683 database server, designating new in SAN SSO, 669 disaster recovery, 702, 703, 705 disaster recovery of Backup Exec on a cluster using IDR, 700 failover restart, 658 installation, 660, 662 local disks, 682 Open File Option, and using, 662 overview, 680 Remote Agent, installing, 660 restoring, 684, 685, 686 system state, backing up, 682 uninstalling Backup Exec, 663 virtual servers, backing up, 683 Windows 2000 and Windows Server 2003, 681 restoring specifying a new drive letter for the Microsoft cluster quorum disk, 688 size, 625 troubleshooting, 705 using with Backup Exec, 657 VERITAS backing up, 693, 694, 695 disaster recovery, 697, 704 overview, 692 Remote Agent, installing, 691 restoring Windows 2000 and Windows 2003, 696 system state, backing up, 694 virtual servers, backing up, 695 1436
combination R/3 database server/media server recovery, 1356 command line installation of Backup Exec, 81 command line interface, 1213 -assignSL, 1214 -changeserver, 1217 -createrecoverykeys, 1228 -DisableNCOM, 1225 -emergencyrestore, 1224 -enableuser, 1216 general options, 1213 -inactiveaccounts, 1227 -keytest, 1218 -listprofile, 1218 -listsl, 1219 -listuser, 1220 -logfile, 1221 -notifyclients, 1227 remote server options, 1213 -renameuser, 1225 -setrecoverypwd, 1225 syntax, 1213 -update, 1222 commands See also names of individual commands Communication Statuses CASO, 840 completed jobs, job log overview, 433 compression Desktop Agent backup selections, setting, 1245 DLO backup selections, setting, 1161 enable hardware compression option, 155 in cascaded drive pools, 139 setting backup defaults, 327 configuration settings copying to another server, 396 Configuration Settings report, 569 Configuration tab for drive properties, 155 Configuration tab for robotic library, 169 Configuration Wizard for DLO, 1145 Configure Alerts dialog box, 1204 Configure desktop and laptop backups option, 1134 Configure Devices button, 109 Configure SAN SSO, See Backup Exec Utility, 753 Administrators Guide
configuring, 1308 drives, 154 holidays, 404 media servers to use with Oracle Agent, 1311 Oracle Agent, overview, 1306 robotic library, 165 consistency check options Exchange Server Agent, 1078 SQL Agent, 1019 continuing Exchange backup if consistency check fails, 1078 control file backup, Oracle Agent, 1300 copy jobs, selection lists, and policies, 394 creating more disk space for backup folder, 267 CSV file to add users in DLO, 1179 custom error-handling rule, defined, 1418 custom filter, defined, 1418 custom filters, managing, 407 D daily backups, defined, 355 Daily Network Device Utilization report, 571 Daily Usage by Policy report, 573 damaged media, removing, 233 database files, backing up in a Microsoft cluster, 683 database files, backing up in a VERITAS cluster, 695 database instance, BKUPEXECDLO MSDE, 1210 database log mode, Oracle Agent, 1300 database maintenance configuring, 447 overview, 447 database server defined, 957, 1419 in Microsoft clusters, 669 Date Modified tab, 486 debug logging, enable for remote Windows computers, 802 default options backup and restore for Exchange 2000 and 2003, 1102 IDR, setting, 909 overview, 55 restore, 490 Index
setting, 119 setting for backup jobs, 324 SQL Agent, backup and restore, 1052 default preferred configuration settings for drives, 157 deleting Automated User Assignment, 1173 DLO desktop computer, 1191 drive pools, 136 drives from pools, 136 media, 252 revisions in DLO, 1161 Storage Location in DLO, 1167 user entry from DLO, 1181 vault, 248 Desktop Agent advanced view option, 1241 backing up data, 1238 Backup Selection dialog box, 1242 backup selections compression, setting, 1245 encryption, setting, 1245 modifying, 1239 overview, 1238 compression, setting for backup selection, 1245 console, 1230 Desktop User Data Folder, moving, 1251 encryption, setting for backup selection, 1245 filter options, History view, 1270 glossary, 1293 History view, 1269 include/exclude, 1242 install set default location, 1234 installing, 1133 log files, overview, 1269 log on/log off option, 1251 menu bar, described, 1232 overview, 1229 Reset accounts option, 1233 Reset dialogs option, 1233 Restore dialog box, 1265 restoring files, 1264 Revision Control tab, 1244 revisions, deleting automatically, 1245 schedule, customized, 1250 scheduling backup jobs, 1250 1437
see also Desktop and Laptop Option (DLO) standard view option, 1240 Status view, 1259 storage limits for user data, 1253 synchronization create new sets, 1256 delete synchronized folder, 1257 Synchronized Selections view, 1255 tasks bar, described, 1232 views menu, described, 1232 Desktop Agent Users managing, 1177 desktop and laptop backups option, Configure, 1134 Desktop and Laptop Option clustering, 1210 Desktop and Laptop Option (DLO), 111, 1121 see also Desktop Agent access, disabling/enabling, 1181 adding user, 1178 administration console, 1134 administrators, creating, 1137 alerts categories, defined, 1201 Configure Alerts dialog box, 1204 deleting, 1205 displaying, 1204 managing, 1205 monitoring, 1200 Automated User Assignment creating, 1169 defined, 1122 deleting, 1173 modifying, 1171 priority, changing, 1171 properties, viewing, 1172 backup selection deleting, 1164 modifying, 1163 backup selections adding, 1155 BEUtility.exe utility, using, 1210 compression, setting for backup selection, 1161 Computer History pane, 1193 Configuration Wizard, 1145 configuring, 1145 1438
deleting entry from DLO database, 1191 encryption, setting for backup selection, 1161 filter options, History view, 1194 glossary, 1293 History view, 1192 import multiple users in CSV file, 1179 include/exclude, 1158, 1242 installing, 1130 Job History pane, 1194 Move priority down option, 1171 Move priority up option, 1171 MSDE database instance, maintaining, 1210 overview, 111, 1121 Profile creating, 1146 defined, 1122 edit schedule, 1152 log on/off option, 1152 logging options, 1153 Schedule tab, 1152 properties, changing user, 1180 removing user, 1181 reset dialogs and accounts, 1233 restoring, 1186 revisions defined, 1156 deleting automatically, 1161 setting number to keep in DLO, 1159, 1244 storage limits for user data, 1148 Storage Location defined, 1122 deleting, 1167 moving users, 1182 summary status, 1143 user bandwidth settings, 1147 User Data Folder, 1165 User Properties dialog box, 1180 View history log file option, 1196 viewing users, 1180 device allocation in a shared storage environment, 961 selecting for backup job, 267 Device and Media options for backup job, 267 Device Driver Installation Wizard, 129 Administrators Guide
device management, 123 device operations See also robotic library cataloging media, 452 ejecting media, 203 Enable Hardware Compression Option, 155 erasing media (quick or long), 195 formatting media, 199 inventorying a drive, 193 labeling media, 201 overview of utility jobs, 192 retensioning a tape, 198 using with SAN Shared Storage Option, 964 device pool, defined, 1419 Device Summary Report, 962 Device Summary report, 571 device, defined, 1419 devices configuring, 128 Device Driver Installation Wizard, 129 Hot-swappable Device Wizard, 128 pausing and resuming, 130 renaming, 130 troubleshooting, 976 viewing, 125 viewing with Library Expansion Option, 1119 Devices view, 125 Dfs See Distributed file system DHCP See Dynamic Host Configuration Protocol dialog box Backup Selection, 1157 New Automated User Assignments, 1170 Restore, 1188 dialog box, Move User, 1182 dialog boxes, overview, 113 differential - Back up changed files since last full defined, 1419 differential - Using modified time defined, 1419 differential backups advantages and disadvantages, 356 defined, 354 disable device for Backup Exec, 153, 168, Index
184 disaster preparation Disaster Preparation Plan (DPP), 606 emergency repair disk, 609 Exchange 2000 and 2003, 1108 hardware protection, 606 Lotus Domino Agent, 1343 off-site storage, 606 overview, 605 SQL 2000, 1057 disaster recovery See also names of individual agents clusters Backup Exec on a Microsoft cluster using IDR, 700 entire cluster manually, 700 nodes using IDR, 698 using IDR to prepare, 698 data protected by Backup Exec agents, 610 different types of computers, overview, 610 Exchange 2000 and 2003, 1108 Exchange 5.5, 1111 local Windows 2000 computers (non-authoritative), 611 Lotus Domino Agent, 1343 manual recovery of Windows system, 610 Microsoft clusters Backup Exec, 705 data files, 702 shared disks, 703 Oracle Agent, 1321 overview, 610 Remote Agent for NetWare Servers, 1405 remote Windows 2000 computers (non-authoritative), 615 VERITAS clusters overview, 697 shared disks, 704 disaster recovery alternate data path, in IDR, 911 disaster recovery data path, in IDR, 910 disaster recovery file (*.dr file) in IDR defined, 906 setting locations for, 909 Disaster Recovery Wizard 1439
requirements, 945 running, 945 disk grooming, using for archive job, 310 Disk Management, using in IDR, 948 Distributed file system (Dfs) backing up, 287 restoring, 476 DLO Configure Alerts dialog box in, 1204 User Properties dialog box in, 1180 DLO Administration Console, restoring from, 1186 DLO see also Desktop and Laptop Option (DLO), Desktop Agent DLO, back up on log on/off option in, 1152 DLO, Configuration Wizard for, 1145 DLO, CSV file to add users in, 1179 DLO, glossary for, 1293 DLO, Move priority options in, 1171 DLT tape, drive hangs when cataloging, 622 Domain Controller, using redirected restore to install from media, 488 domains, host and target, defined, 61 DPM Agent backup job with DPM data, 1386 database backup job, 1387 database restore job, 1389 overview, 1385 protected servers backup job, 1387 protected servers restore job, 1389 requirements, 1386 restore job with DPM data, 1389 shadow copy backup job, 1388 shadow copy data restore job, 1390 DPP See also Disaster Preparation Plan Drive Pool Properties dialog box, 138 drive pools See also cascaded drive pools adding drives, 134 creating, 133 creating in a Microsoft cluster, 664 default for SAN Shared Storage Option, 963 defined, 123 deleting, 136 deleting drives, 136 overview, 132 prioritizing drives, 135 properties, 138 1440
renaming, 137 SAN Shared Storage Option, 961 using the default drive pool, 132 viewing properties, 138 drive properties Cleaning tab, 161 Configuration tab, 154 General tab, 152 Media Types tab, 163 SCSI Information tab, 158 Statistics tab, 159 viewing, 151 drivers download latest, 621 drives block size, 156 buffer count, 157 buffer size, 156 configuring, 154 default settings, 157 high water count, 157 SCSI information, 158 specifying media types for, 163 statistics on usage, 159 statistics since cleaning, 161 using exclusively with Backup Exec, 191 duplicate backup data template defined, 1419 duplicate backup sets template overview, 381 duplicate backup sets templates adding to a policy, 382 duplicate job advanced settings, 316 duplicating backup data, 315 Dynamic Host Configuration Protocol (DHCP), 641 E editions of Backup Exec, listed and described, 43 See also names of individual editions eject media after job completes, 269 from a drive, 203 e-mail configuring MAPI notification, 515 configuring SMTP notification, 514 configuring VIM notification, 516 Administrators Guide
emergency repair disk, creating, 609 enabling bar code rules, 169 device for Backup Exec option, 153, 168, 184 hardware compression, 155 Removable Storage (RSM), 170 robotic library initialization on startup, 169 encrypted files, backing up with AOFO, 995 encryption, 1189, 1255, 1277 backup selections, in Desktop Agent, 1245 backup selections, in DLO, 1161 encryption, setting, 1245 Environment Check, running for Backup Exec, 63 erase media operation, quick or long, 195 error codes, Unique Message Identifier, viewing, 432 error-handling rule, defined, 1419 error-handling rules Cluster Failover rule, 440, 444 configuring, 440 custom rules, defined, 439 default rules, defined, 439 overview, 439 Recovered Jobs custom rule, 440 Evaluation version installing for Backup Exec options, 71 Evaluation version, installing Backup Exec, 68 Event Logs report, 575 Event Recipients report, 576 event, defined, 1419 example policies, 365 Exchange 2000 and 2003 agent features, 1065 agent requirements, 1066 disaster recovery, 1108 logon accounts, overview, 1068 protecting Exchange 2003 using VSS, 1074 resource discovery feature, using with, 1066 restoring Exchange 2003 with Recovery Storage Group, 1092 Exchange 2000 and 2003, backing up Active Directory, 1071 Index
backup methods, 1076, 1103 circular logging, reviewing, 1081 Exchange 2003 with VSS, 1074 Guide Me wizard, 1078 Internet Information Service (IIS) metabase, 1070 Key Management Service (KMS), 1070 mailbox backup methods, 1077 public folders, 1082 recommended selections, 1070 single instance backup for message attachments, 1077 Site Replication Services (SRS) database, 1070 storage groups, 1079 system state, 1070 Exchange 2000 and 2003, restoring, 1086 commit after restore completes option, 1088 mailboxes and user accounts, recreating, 1086 mount database after restore option, 1088 no loss restore option, 1087 redirecting storage groups and databases, 1098 requirements, 1089 restore defaults, 1102 Restore Job Properties dialog box, 1086 restoring data to server, 1086 temporary location for log and patch files, 1088 Exchange 2003, restoring redirecting database restores, 1099 Exchange 5.5 logon accounts, overview, 1068 resource discovery feature, using with, 1066 Exchange 5.5, backing up backup methods, 1076 circular logging, reviewing, 1081 Guide Me wizard, 1078 information store and Exchange directory, 1079 Key Management Service (KMS), 1071 mailbox backup methods, 1077 recommended selections, 1071 single instance backup for message attachments, 1077 1441
Exchange 5.5, restoring defaults, 1105 DS/IS consistency adjuster after restore, 1091, 1097 no loss restore option, 1087 redirecting database restores, 1098 requirements, 1089 restore private mailboxes option, 1087 restore public folder option, 1087 Exchange data, strategies for backing up, 1068 Exchange Server Agent backing up Guide Me wizard, 1076 Backup Job Properties dialog box, 1075 best practices, 1072 creating backup job, 1079 excluding files during volume level backups, 1080 installation, 1067 overview, 1065 redirecting data, 1096 requirements, 1066 using snapshot technology, 1074 Exchange Server Agent, restoring change password when recreating mailboxes, 1107 redirecting mailboxes, 1100 Redirection dialog box, 1096 executing a command after backup, 281 after restore, 469 before backup, 281 before restore, 468 export media template, 370 exporting media, 207 F failback, defined, 658 Failed Backup Jobs report, 576 failover defined, 657 Microsoft adding or removing a failover node, 668 changing the order in which nodes fail over, 668 restart, 658 failover, defined, 1419 1442
farms adding, 1373 changing the default farm name, 1375 deleting, 1376 FAT cluster size, 625 partition, 624 father/son media rotation strategy, 249 Fibre Channel Arbitrated Loop (FC-AL) defined, 1420 fibre channel switch, defined, 1420 Fibre Channel Switched Fabric (FC-SW), defined, 1420 fibre channel tape controller, defined, 1420 fibre channel, defined, 1420 fibre to SCSI bridge defined, 1420 file permissions, restoring, 471 file to add users in DLO, CSV, 1179 filegroups backing up SQL, 1031 displaying, 1031 restoring SQL Agent, 1044 restoring nonprimary SQL 2000, 1040 restoring primary SQL 2000, 1040 files, processing open, 279, 330 filters calendar, 414 History view filters, setting in Desktop Agent, 1270 History view filters, setting in DLO, 1194 job monitor, 405 jobs list, 405 filters for alerts, 502 filters, managing custom, 407 finding media in a location or vault, 244 format media, 199 frequently asked questions about using Backup Exec, 117 Full - Back Up Files - Archive the files defined, 1420 Full - Back Up Files - Copy the files defined, 1420 Full - Back Up Files - Using archive bit Administrators Guide
(Reset Archive Bit) defined, 1420 Full - Back Up Files - Using modified time defined, 1420 full backups advantages and disadvantages, 356 defined, 354 G General drive properties, 152 general job defaults, setting, 122 general media properties, viewing, 253 general options duplicate job, 316 restore jobs, 461 synthetic backup, 885 General tab robotic library, 166 General tab, media server properties, 145 global excludes adding, 1175 deleting, 1175 macros, 1176 using macros in, 1176 glossary for DLO, 1293 grandfather media rotation strategy, 250 grooming alerts, 1200 files, 1164 groups, configuring recipients, 530 H hardware compression in cascaded drive pools, 139 creating profile, 608 enable hardware compression option, 155 protection in case of disaster, 606 high water count, setting for drives, 157 holding jobs that back up selection lists, 296 host domain, defined, 61 hub defined, 1420 I IBM computers, recovering with IDR, 941 IDR Configuration Wizard, 906 imported media
defined, 227, 1421 labeled by Backup Exec, 235 overwriting, 232 importing media, 205 importing templates, 372 include/exclude Desktop Agent backup selections, 1242 DLO backup selections, 1158 Incremental - Back up changed files since last full or incremental - Using archive bit, defined, 1421 Incremental - Back up changed files since last full or incremental - Using modified time, defined, 1421 incremental backups advantages and disadvantages, 357 defined, 355 Information Desk, overview, 113 installation parameter file creating, 89 defined, 89 using, 89 installation requirements, Backup Exec, 65 See also names of individual agents and options installing additional Backup Exec options on a Microsoft cluster, 662 Backup Exec, 67 Backup Exec in a Microsoft cluster, 660 Backup Exec in a VERITAS cluster, 691 besernum.xml file, import serial numbers, 68 Desktop Agent, 1133 Desktop and Laptop Option, 1130 Domain Controllers from media, 488 Environment Check, running pre-install, 63 Evaluation version, 68 Evaluation version for Backup Exec options, 71 import serial numbers, 68 Library Expansion Option, 1117 locally additional options, 71 using clone CD image, 99 Microsoft Data Access Components (MDAC), 57 Microsoft SQL Server 2000 Desktop 1443
Index
Engine (MSDE 2000), 57 Open Database Connectivity (ODBC), 57 overview, 57 Remote Administrator, 95 remotely using clone CD image, 99 SharePoint Agent, 1360 storage devices, 57 to an existing Microsoft SQL Server 2000 instance, 58 using installation program on CD, 67 using Repair option, 91 using Terminal Services, 67 Windows Management Instrumentation performance counter, 540 Windows Management Instrumentation SNMP provider, 541 instance, BKUPEXECDLO MSDE database, 1210 Intelligent Disaster Recovery (IDR), 901 alternate data path on a remote computer, 911 ASR files, 906 boot managers, 939 catalog entries, added to *.dr file, 901 clusters recovering Backup Exec on a Microsoft Cluster, 700 recovering nodes, 698 disaster recovery diskettes, updating, 931 disaster recovery file (*.dr file), defined, 906 First Time Startup Configuration Wizard, 906 hard disk partitions, changing, 946 hard drive partition, altering sizes using IDR, 949 IBM computers, 941 installing, 903 Microsoft Exchange Server, recovering, 954 Microsoft SQL Server, recovering, 953 Options - Set Application Defaults dialog box, 909 OS/2 boot manager, restoring, 939 overview, 51 Recovery Wizard, running, 945 requirements, 902 1444
restoring remote media server, 948 Sharepoint Portal Server, recovering, 954 System Commander boot manager, restoring, 939 utility partitions, backing up, 914 virtual devices, using in, 176, 902 Windows Automated System Recovery (ASR) files, 906 Internet Information Services (IIS) metabase, backing up, 1070 inventory job creating, 194 setting job priority, 194 inventorying all drives on startup, 120 all drives when Backup Exec starts, 193 drives, 193 J job delegation, defined, 1421 Job Distribution by Device report, 577 job history defined, 56, 1421 deleting report, 552 History view filters, setting in DLO, 1194 saving report, 552 viewing, 428 viewing in Desktop Agent, 1269 viewing report, 551 job log configuring default options, 435 defined, 1421 status overview, 433 Job Log Options Setting, 844 job monitor DLO jobs, viewing, 1192 filters, 405 views, 405 job priority setting for cleaning jobs, 205 setting for eject job, 203 setting for erase job, 198 setting for export job, 207 setting for format job, 200 setting for import job, 206 setting for inventory job, 194 Administrators Guide
setting for label media job, 202 setting for retension job, 199 job progress indicators, displaying, 121 job status, and setting thresholds for, 445 jobs changing priority for scheduled, 425 configuring default Lotus Domino options, 1332 configuring default schedule, 403 configuring error-handling rules, 440 configuring new recipients, 535 configuring schedule, 398 creating from policies, 378 defined, 1421 deleting jobs created from policies, 380 deleting scheduled, 426 edit recipients, 535 editing schedule, 401 holiday scheduling, 404 Lotus Domino backup properties, 1335 removing hold active jobs, 419 scheduled jobs, 424 run report, 548 running scheduled job, 423 running scheduled test job, 426 scheduled, modifying, 420 scheduled, viewing, 420 scheduling, 398 selecting recipients for notifications, 534 setting general defaults, 122 viewing active, 405 viewing and filtering calendar, 413 jobs list, 405 viewing and scheduling in a SAN, 970 viewing completed, 427 jobs list view filters, 405 viewing, 405 Jobs Summary report, 578 junction point, defined, 1421 K Key Management Service (KMS) database, backing up, 1070, 1071 L labeling media Index
creating default labels, 241 imported media label, 235 in drive, 201 renaming, 238 using bar code labels, 235 laptop backups option, Configure desktop and, 1134 last known good menu, 607 Library Expansion Option overview, 51, 1115 SCSI addresses for hardware, 1115 setting up hardware, 1115 library sharing, configuring server for, 966 License Information tab, media server properties, 150 linked drives See cascaded drive pools load-balancing, defined, 1422 local device, defined, 1422 local media server, breaking connection with, 96 lock open files for backup, 279, 330 lock robotic library panel, 208 log on/off option in DLO, back up on, 1152 logon account, defined, 1422 logon accounts changing default, 392 changing for a resource being backed up, 292 default, defined, 386 deleting, 391 editing, 390 Exchange 2000 and 2003 resources, 1068 Exchange 5.5 resources, 1068 overview, 386 replacing, 391 SQL resources, 1015 system logon account, 387 testing, 292 logon information copying to another server, 396 Lotus Domino Agent APIs, 1332 archive logging, 1334 backup options, 1335 circular logging, 1334 configuring default options, 1332 database backup overview, 1332 database backup requirements, 1328 1445
disaster preparation, 1343 disaster recovery archive logging, 1344 circular logging, 1345 of server, 1343 overview, 52, 1327 redirecting restore, 1341 requirements, 1328 restore overview, 1337 selecting for restore, 1338 selecting restore options, 1340 supported configurations, 1333 viewing databases, 1330 M Machines Backed Up report, 579 Macintosh Agent, system requirements, 643 macros global excludes, 1176 mailboxes backup methods, 1077 best practices, 1082 change password when recreating, 1107 Exchange 2000 and 2003 overview of backing up, 1082 recreating mailboxes and user accounts, 1086 exclude specific folders, 1082 redirecting restores, 1100 restore overview, 1094 majority node in a cluster, 659 managed media server, defined, 1422 Managed Media Servers report, 579 manually update server list, for NetWare, 1403 MAPI e-mail notification method, 515 MAPI, configuring recipients, 520 master database backup, 1019 master database restore SQL Agent, 1036 media adding to the offline location or user-defined media vault, 245 all media, defined, 227 allocated, defined, 228 append backup to, 269 append options, 232 1446
creating default labels, 241 damaged, 233 deleting, 252 deleting vault, 248 displaying media ID, 253 finding in a location or vault, 244 general properties, 253 how Backup Exec searches for overwritable media, 229 imported, defined, 227 moving to a media set or vault, 252 moving to a new location, 247 overwrite for backup, 269 overwrite options, 228 overwriting allocated or imported, 232 properties, 253 recyclable, defined, 228 retired, defined, 227 scratch, defined, 227 setting default options, 239 sharing, 971 statistical properties, 255 system, defined, 227 testing integrity of, 318 using with Removable Storage, 190 with excessive errors, 233 media capacity, testing before backup runs, 323 media catalogs, 957 media categories, 227 media ID, defined, 234, 1422 media label bar code rule changing, 237 deleting, 237 in mixed media libraries, 236 bar codes, 235 defined, 1422 imported, 235 overview, 234 renaming, 238 media location, 243 media location, updating, 245 media name, specifying during backup job, 268 media operations deleting media, 252 moving media, 252 viewing media properties, 253 Administrators Guide
media overwrite protection levels, defined, 226, 1423 media overwrite protection, overview, 213 Media Required for Recovery report, 581 media rotation, 361 media rotation in SAN, 972 media rotation strategies father/son, 249 grandfather, 250 son, 249 media rotation, defined, 1423 media server backing up using one-button backup, 308 connecting, 96 connecting to, 1141 defined, 1423 running diagnostics on, 144 viewing properties, 144 media server pools, defined, 1423 media servers configuring for robotic library sharing, 966 media set creating, 218 default, 217 defined, 228, 1423 deleting, 221 overwrite and append properties, 223 renaming, 222 selecting for backup job, 268 shared storage environments, and, 971 vault rule properties, 225 wizard, running, 221 Media Set report, 582 media types, specifying for drives, 163 media vault defined, 243, 1423 deleting, 248 finding media in a vault, 244 media vault renaming, 244 user-defined creating, 244 defined, 243 Media Vault Contents report, 583 media vault, defined, 1423 Media View, 861 media view, 451 Index
menu bar, overview, 110 menus, described Help, 1413 Window, 1411 messages error, 623 Microsoft Cluster Server, using with Backup Exec, 658 Microsoft clusters clrest command, 687 Microsoft Data Access Components (MDAC), installing, 57 Microsoft Exchange Server See also Exchange Server Agent Microsoft SQL Server 2000 Desktop Engine (MSDE), installing, 57 Microsoft SQL Server See also SQL Server Agent Microsoft Terminal Services, and installing Backup Exec, 67 Microsoft Volume Shadow Copy Service (VSS), and AOFO, 1002 minimum quiet time, setting for AOFO, 1010 Missed Availability report, 584 mixed media library bar code labeling, 236 mount point, defined, 1423 mounted local drives, backing up files and directories, 277 Move Media to Vault report, 585 Move priority options in DLO, 1171 Move User dialog box, 1182 moving media from vault, 248 media to a media set or vault, 252 MSCS, using with Backup Exec, 658 MSDE 2000 components, installed with Backup Exec, 57 MSDE database instance, BKUPEXECDLO, 1210 MSDE database instance, DLO, 1210 multi-stage backup strategy, 381 N Name & Location dialog box, 485 named transaction include in restore, SQL 2000, 1039 restore up to, SQL 2000, 1039, 1043 navigation bar, overview, 111 1447
Net Send, configuring recipients, 526 NetWare SMS options, 1403 network changing a backup network for a job, 339 overview of backup networks, 334 setting up a backup network, 336 network options, restore job, 493 network protocols, IPX/SPX, 337 Network User Data Folder creating, 1177 New Automated User Assignments dialog box, 1170 New Backup-to-Folder dialog box, 178 node, defined, 1423 nodes configurations in a Microsoft cluster, 670 defined, 657 disaster recovery using IDR, 698 Microsoft adding or removing a failover node, 668 changing the order in which nodes fail over, 668 nonlogged operations occurring in SQL 7.0, 1034 notification assigning recipients to alerts, 533 defined, 502 notifications assigning alert categories, 533 clearing recipients, 534 configuring MAPI e-mail, 515 configuring pager, 517 configuring SMTP e-mail, 514 configuring SNMP, 536 configuring VIM e-mail, 516 methods defined, 514 modifying alert category properties, 534 modifying recipient properties, 531 scheduling recipients, 531 selecting recipients for jobs or selection lists, 534 NTFS cluster size, 625 partition, 624 1448
numbering, specify for media label, 241 O offhost backup best practices, 891 host computer, defined, 888 List Snapshot Providers option, 894 overview, 888 requirements, 889 single volume snap, choosing, 894 snapshot provider, choosing, 893 transportable snapshots, defined, 888 VSFW FlashSnap option, using with, 890 offhost backup, defined, 1424 offline media location adding media to, 245 defined, 243, 1422 offline, when devices display as, 153, 168, 184 off-site storage of backups, 606 on/off option in DLO, back up on log, 1152 one-button backup, 308 online media location, 243, 1422 Online Registration Wizard, using, 90 online, putting device back, 153, 168 Open Database Connectivity (ODBC), installing, 57 open files backing up, 279 backing up with AOFO, 992 setting default for backing up, 330 unable to back up, 624 Operations Overview report, 586 optimizing remote backups, 278 option in DLO, back up on log on/off, 1152 option, Configure desktop and laptop backups, 1134 options default for job log, 435 Options - Set Application Defaults General, 122 Preferences, 120 options in DLO, Move priority, 1171 options, additional Backup Exec options described, 51 Oracle Agent, 1308 account, creating user, 1301 adding media servers, 1311 Administrators Guide
archived redo logfiles, 1297 backup mode, described, 1302 backup strategies, 1298 error messages, 1324 fully specified paths, using, 1305 installing, 1307 overview, 52 renaming data files from a single tablespace, 1305 shutting down and restarting the Oracle database, 1303 system requirements, 1298 troubleshooting, 1324 types of data to protect, 1299 Oracle Agent, backing up closed database, 1315 online database, 1312 online tablespaces, 1314 Oracle Agent, configuring archived logfiles directory, 1306 ARCHIVELOG mode, 1302 automatic archival, 1300, 1302 BECF.BAK, 1300 control file backup, 1300 control file backup location, 1310 database control file, 1306 database log mode, 1300, 1302 Database tab, 1311 General tab, 1311 INIT.ORA, 1304 INITORCL.ORA, 1300 instance initialization parameter files, 1304 list of configured media servers, 1309 multiple database instances on a single database server, 1304 Oracle account username, 1310 Oracle Server using the Oracle Agent Configuration Utility, 1306 overview, 1306 removing configured media servers, 1309 requirements, 1300 server manager, 1302 SID, 1304 SID name, 1310 tablespace data, 1299 TCP/IP address, 1311 Oracle Agent, disaster recovery Index
file system backup, 1321 Oracle database server and media server combination, 1323 remote Oracle database server, 1322 requirements, 1321 tablespace data files, 1321 Oracle Agent, restoring closed database, 1318 database control file, 1320 individual tablespaces, 1319 online database, 1317 Oracle information manager, 1319 over existing files, 1316 Oracle server manager, 1320 Outlook PST files backing up, 1247 overview, 901 overview tab, using, 113 overwritable media, how Backup Exec searches for it, 229 overwrite default media label, 241 overwrite media option, specifying for backup job, 269 overwrite protection levels full, 239 none, 240 partial, 239 overwrite protection period defined, 214, 219, 1424 setting for media set, 219 overwrite protection, disabling, 240 P pager configuring recipients, 523 notification method, 517 parameter file, editing in R/3 Agent for Oracle Server, 1351 partial overwrite protection, 239 partition creating for robotic library, 172 defined, 1424 FAT, 624 NTFS, 624 redefining for robotic library, 174 password database, Remote Agent for NetWare Servers, 1394 pausing device, 130 performance, increasing during backups of 1449
remote Windows computers, 790 physical check, SQL 2000, 1027 physical only check, available with SQL 2000 only, 1019 PHYSICAL_ONLY utility, 1021 placing scheduled job on hold if test run fails, 323 point in time log restore option SQL Agent, 1039, 1042 policies copying to another server, 394 policy adding a backup template, 367 adding a duplicate backup sets template, 382 adding an export media template, 370 changing template rules, 377 creating jobs, 378 creating manually, 363 creating synthetic backup using the Policy Wizard, 881 creating using the Policy Wizard, 363 defined, 1424 deleting, 364 deleting a template, 373 deleting jobs created from policies, 380 deleting template rules, 377 duplicate backup sets template overview, 381 editing a template, 372 importing templates, 372 migrating templates, 367 overview, 361 setting template schedules, 369 template rules, 373 using an example policy, 365 using templates, 366 Policy Jobs by Resource report reports Policy Jobs by Resource, 589 Policy Jobs Summary report, 590 Policy Properties report, 591 Policy Protected Resources report, 592 portal support, 207 post-job command setting for backup job, 281 setting for restore job, 467 pre/post command options for jobs, 332 prefix, creating for media label, 241 1450
pre-job command setting for backup job, 281 setting for restore job, 467 preserve tree option for backup job, 273 for restores, 463 primary navigation bar, 712 primary server defined, 957 printer, configuring recipients, 528 priority Automated User Assignment, changing, 1171 changing for scheduled job, 425 setting for drives in pools, 135, 185 setting for restore job, 462 priority for selection lists, 301 priority options in DLO, Move, 1171 Problem Files Report, 593 Problem Files report, 593 Process logical volumes for backup one at a time, supported by Exchange Agent, 1074 Process logical volumes for offhost backup one at a time, supported by Exchange Agent, 1074 product updates, receiving, 101 Profile, 1146 back up on log on/off option, 1152 creating, 1146 defined, 1122 edit schedule, 1152 logging options, 1153 prompt before overwriting allocated or imported media, 240 properties active job, 415 alerts, 505 Lotus Domino, 1335 media general, 253 statistical, 255 report, 553 user, changing in DLO, 1180 protected server, defined, 1424 PST files backing up, 1247 public folders best practices, 1082 Exchange 2000 and 2003 Administrators Guide
backing up, 1082 Exchange 5.5 restore public folder option, 1087 Exchange Server Agent, restoring mailboxes and public folders, overview, 1094 exclude specific folders, 1082 published drives, defined, 635 Q Quick Start Edition of Backup Exec, described, 44 R R/3 Agent for Oracle Server backing up the R/3 database, 1353 BACKINT implementation, 1347 how it works, 1347 installing, 1350 requirements, 1349 security, 1348 R/3 Agent for Oracle Server, restoring disaster recovery requirements, 1355 submitting restore jobs, 1354 R/3 database server, restoring, remote recovery, 1355 RALUS Installation overview, 804 Making backup selections, 810 Manual install and uninstall, 814 Manually installing from a tar file, 814 Manually starting the RALUS daemon, 815 Manually stopping the RALUS daemon, 816 Manually uninstalling, 815 requirements, 803 Setting Linux/Unix properties, 812 Uninstalling, 813 Using, 810 Using the Installer, 805 Using with the Backup Exec 8.x and 9.x Agent for Unix, 816 RALUS.CFG About, 808 Editing, 808 Format components, 808 reassigning how slots appear, 170 Recently Written Media report, 594 recipients Index
assigning alert categories, 533 clearing recipients, 534 configuring, 522 configuring groups, 530 configuring MAPI e-mail, 520 configuring Net Send, 526 configuring new for jobs or selection lists, 535 configuring pager, 523, 528 configuring SMTP, 518 defined, 518 modifying alert category properties, 534 selecting for notifications, 534 Recovered Jobs custom error-handling rule, 440 recovering jobs, threshold for, 445 recovery completion state, SQL restore, 1035 recovery password setting, 1135 recovery requirements in IDR, 939 Recovery Storage Group, 1092 recyclable media, defined, 228, 1424 redirected restore See also names of individual agents using to install Domain Controllers from Media, 488 redirecting Exchange data, 1096 redirecting scheduled job, 137 registering Backup Exec, 90 registry restoring, 465 Remote Administrator defined, 1424 running, 95 system requirements, 95 Remote Agent installing on a Microsoft cluster, 660 installing on a VERITAS cluster server, 691 Remote Agent for NetWare Servers AUTOEXEC.NCF file, 1393 installing, 1392 overview, 52, 1391 system requirements, 1392 Remote Agent for NetWare Servers, backing up BEDIAG.NLM utility, 1404 1451
create BEDIAG.FAX, 1404 decompressed files, 1403 password database, 1394 rights for backup, 1394, 1395 single server backup strategies, 1396 strategies for multiple administrators, 1396 strategies for single administrator, 1396 Remote Agent for NetWare Servers, restoring, 1400 Remote Agent for Windows Servers 64-bit overview, 791 advertising to media servers, 800 described, 52 hardware requirements, 790 installing, 793 installing 64-bit using command script, 795 installing 64-bit using the installation program, 793 Installing using the command line, 794 Remote Agent Monitor, 797 remote backup and restore, 789 serial numbers, 791 stopping, 797 Uninstalling using the command line, 795 Remote Agent Monitor advertising the Remote Agent for Windows Servers, 800 enable debug logging, 802 Event Viewer, opening, 797 refresh interval, 799 Registry Editor, opening, 797 Services, opening, 797 starting on log on, 799 starting on remote Windows computers, 797 viewing status, 799 Remote Agent, defined, 1424 remote storage, back up data, 278 Removable Storage feature, Microsofts monitoring Backup Exec, 191 using with Backup Exec, 189 using with the SAN SSO, 189 Remove Primary SAN SSO Server, 752 renaming cascaded drive pools, 143 1452
drive pools, 137 media labels, 238 robotic library or drive, 130 vault, 244 renaming libraries and drives in shared environment, 964 reports, 1206 active alerts, 559 Active Alerts by Media Server, 559 alert history, 561 audit log, 563 available in Backup Exec, 555 Backup Job Success Rate report, 564 Backup Set Details by Resource, 566 backup sets by media set, 567 Backup Size by Resource, 568 configuration settings, 569 Daily Network Device Utilization, 571 Daily Usage by Policy, 573 deleting in job history, 552 device summary, 571 event logs, 575 Event Recipient, 576 Failed Backup Jobs, 576 Job Distribution by Device, 577 Jobs Summary, 578 list, 1206 Machines Backed Up, 579 Managed Media Servers, 579 Media Required for Recovery, 581 media set, 582 media vault contents, 583 Missed Availability, 584 Move Media to Vault, 585 operations overview, 586 overview, 543 Policy Jobs Summary, 590 Policy Properties, 591 Policy Protected Resources, 592 Problem Files, 593 Recently Written Media, 594 Resource Backup Policy Performance, 595 Resource Risk Assessment, 596 Restore Set Details by Resource, 597 Retrieve Media from Vault, 598 running, 545, 1209 running job, 548 saving, 552 Administrators Guide
Scheduled Server Workload, 600 scheduling report jobs, 553 Scratch Media Availability, 601 setting notification recipients, 553 test run results, 602 viewing, 544, 1206 viewing in job history, 551 viewing properties, 553 requirements Exchange Server Agent, 1066 installation, for Backup Exec, 65 Lotus Domino Agent, 1328 R/3 Agent for Oracle Server, 1349 SAN Shared Storage Option, 959 system, for Backup Exec, 59 TSM option, 771 Reset accounts option, in Desktop Agent, 1233 Reset Cleaning Statistics, 161 Reset dialogs option, in Desktop Agent, 1233 resource credentials, changing for restore job, 481 order, changing, 291 Resource Backup Policy Performance report, 595 resource discovery creating job, 311 defined, 1425 used with Exchange Agent, 1066 Resource Risk Assessment report, 596 resource, defined, 1424 responding to active alerts, 507 Restore dialog box, 1188 Desktop Agent, 1265 restore job Advanced File Selection, 482 advanced options, 464 canceling, 495 copying to another server, 394 creating through dialog boxes, 458 creating with wizard, 457 Data Protection Manager, 1389 file permissions, 471 general options, 461 Lotus Domino options, 1340 over existing files, 462 overview, 457 Index
pre/post commands, 467 preserve tree option, 463 R/3 Agent for Oracle Server, 1354 redirecting, 487 redirecting Lotus Domino, 1341 security, 463 Selections options, 460 setting defaults, 490 specifying network, 493 Restore Job Properties dialog box Exchange 2000 and 2003, 1086 Exchange Redirection page, 1096 SQL Agent, 1035 Restore Set Details by Resource report, 597 restore to named instance, 1051 restore, defined, 1425 restoring ARCserve tapes, 477 byte count does not match, 626 closed Oracle database, 1318 Distributed file system (Dfs), 476 Exchange 2000 and 2003, 1086 files, using Desktop Agent, 1264 files, using DLO Administration Console, 1186 individual Oracle tablespaces, 1319 Lotus Domino Agent, 1338 media view, 451 Microsoft clusters cluster quorum for Windows 2000 and Windows Server 2003, 685 cluster quorum on node running Active Directory, 686 Windows 2000 and Windows Server 2003, 684 online Oracle database, 1317 Oracle database control file, 1320 registry, 465 Remote Agent for NetWare Servers volume restrictions, 1403 resource view, 451 searching for files, 483 selecting data, 479 using the media view, 479 using the resource view, 479 VERITAS clusters Windows 2000 and Windows Server 2003, 696 restoring SQL master database, 1047 1453
resuming a drive, 130 retarget job, 137 retensioning a tape, 198 retired media defined, 227, 1425 moving damaged media, 233 Retrieve Media from Vault report, 598 returning to a previous configuration, 607 revisions defined, 1156 deleting automatically in Desktop Agent, 1245 deleting automatically in DLO, 1161 number to keep, setting in Desktop Agent, 1244 number to keep, setting in DLO, 1159, 1244 Revision Control tab, Desktop Agent, 1244 Revision Control tab, DLO, 1159 robotic library cleaning jobs, 204 configuring, 165 configuring partitions, 172 creating partitions, 172 defined, 1425 displaying storage devices, 1117 example configuration, 1116 exporting media, 207 importing media, 205 lock front panel, 208 portal support, 207 problem with not displaying, 621 redefining partitions, 174 setting up hardware, 1115 unlock front panel, 208 using with Backup Exec, 164 viewing, 1119 viewing properties, 166 robotic library properties Configuration tab, 169 General tab, 166 SCSI Information tab, 170 robotic library sharing between Windows and NetWare servers, 965 prerequisites, 965
S SAN Shared Storage Option (SSO) device allocation, 961 device operations, 964 installing, 960 overview, 52 requirements, 959 schedule, 404 scheduled jobs changing priority, 425 configuring, 398 configuring default options, 403 deleting, 426 editing, 401 modifying, 420 removing hold, 424 running immediately, 423 running test job, 426 viewing, 420 Scheduled Server Workload report, 600 schedules setting for templates, 369 scheduling backup jobs in Desktop Agent, 1250 backup jobs in DLO, 1152 notification recipients, 531 SAN SSO jobs, 970 scheduling report jobs, 553 scratch media creating, 232 defined, 227, 1425 Scratch Media Availability report, 601 SCSI address for devices, 1115 defined, 1425 information about drives, 158 information about robotic library, 170 setting address for robotic library drives, 1115 SCSI bus, configuring for tape devices in a Microsoft cluster, 673 SCSI pass-through mode, setting for drives, 158 search catalogs, 484 secondary navigation bar, 712 security changing for Windows systems, 61 R/3 Agent for Oracle Server, 1348 restoring, 463 Administrators Guide
1454
select into/bulk copy option, SQL 7.0, 1034 selecting devices and data to back up, 284 selection lists configuring new recipients, 535 copying to another server, 394 creating, 293 creating separate for each computer or resource, 303 defined, 293, 1425 deleting, 298 editing, 298 excludes, 299 holding jobs that back them up, 296 merging and replacing, 297 notification, 293 searching, 304 selecting recipients for notifications, 534 setting priority and availability, 301 using for backup job, 296 selections deleting, 298 Desktop Agent, backup, 1238 DLO, backup, 1155 editing, 299 user-defined, adding, 304 user-defined, using TCP/IP addresses, 305 selections list set up notification, 294 Selections options for backup job, 265 serial numbers Backup Exec, adding and removing, 68, 74, 833 Remote Agent for Windows Servers, 791 See also names of individual agents and options server clusters See also clusters server list adding and removing servers, 92 manually update for NetWare, 1403 server properties viewing, 145, 147, 149 viewing advanced properties, 149 viewing License Information tab, 150 viewing media server information, 145 viewing system properties, 147 ServerFree Option Index
installing, 986 overview, 53 service account changing, 92 described, 66 service state, 344 services starting and stopping, 92 starting and stopping on multiple servers, 975 Set Application Defaults, Preferences, 120 Set Primary SAN SSO Server, See also Backup Exec Utility Set Remote Agent Priority, 278 setting Internet Explorer properties for BEWAC, 710 setting notification recipients for reports, 553 Shadow Copy Components File System, 344 shared catalogs, using, 957 shared device, defined, 1425 SharePoint Agent about, 1359 adding a server farm, 1373 backing up folders and documents from a portal workspace, 1362 backing up SharePoint Portal Server 2003 resources, 1376 best practices for SharePoint Portal Server 2001, 1371 changing the default name of a farm, 1375 default backup and restore options, 1384 deleting a farm, 1376 disabling or enabling communication between Web servers and Backup Exec, 1374 disaster recovery, 1370 installing, 1360 overview, 53, 1359 redirecting restore jobs, 1366 redirecting restore jobs for SharePoint Portal Server 2003, 1381 redirecting workspace data to a file path, 1369 redirecting workspace data to another workspace, 1368 requirements, 1359 1455
restoring a SharePoint Portal Server, 1364 restoring a SharePoint Portal Workspace, 1365 restoring SharePoint Portal Server 2003 resources, 1378 restoring SharePoint Portal Servers and Workspaces, 1364 selecting SharePoint Portal Server 2003 resources for backup, 1372 system requirements, 1359 uninstalling and reinstalling the SharePoint Portal Server software, 1371 using with SharePoint Portal Server 2003, 1372 SharePoint Portal Server disaster recovery, 1370 redirecting restore jobs, 1366 SharePoint Services, 346 sharing media, 957, 971 silent mode installation, 65, 81, 1425 simple recovery model, SQL 2000, 1014 single block mode, setting for drives, 157 single instance backup for message attachments, 1077 single instance backup for NTFS, 277 Site Replication Services (SRS) database, backing up, 1070 size, cluster, 625 slot base configuration, 170, 1119 Small Business Server Edition of Backup Exec, described, 44 SMTP configuring e-mail recipients, 518 e-mail notification method, 514 Snap Start, for VSFW volumes, 1005 snapshot technology using with Exchange Server Agent, 1074 snapshot, used in Advanced Open File Option, 991 SNMP configuring notification, 536 configuring system service for Windows 2000, 540 installing WMI provider, 541 object identifier prefix, 536 traps, defined, 536 1456
WMI, 540 software license agreement, 67, 95 son media rotation strategy, 249 Specified Backup Network feature configuring, 336 described, 334 specify a date and time for restoring named transaction, 1039 splash screen, show at startup, 120 SQL 2000 64-bit Remote Agent, 1015 agent features, 1013 disaster recovery preparation, 1057 physical check after backup, 1019 restore to named instance, 1051 simple recovery models, 1014 standby database, 1013 SQL 2000, backing up disaster recovery preparation, 1057 Guide Me wizard, 1028 loading state, 1027 standby mode, 1027 SQL 2000, restoring disaster recovery, 1059 filegroups, 1044 Intelligent Disaster Recovery (IDR) option, 1057 named transaction, 1043 named transaction, include, 1039 named transaction, to a, 1039 primary and nonprimary filegroups, 1040 SQL 7.0 agent features, 1014 SQL 7.0, backing up nonlogged operations occurring, 1034 select into/bulk copy option, 1034 truncate log on checkpoint option, 1033 SQL Agent backing up backup methods, 1025 consistency check after backup, 1027 consistency check recommendations, 1019 databases, 1029 filegroups, 1031 strategies for, 1017 transaction logs, 1033, 1034 Administrators Guide
Windows registry, 1018 Backup Job Properties dialog box, 1024 consistency check, recommendations, 1019 Database Consistency Check (DBCC), recommendations, 1019 default options, 1052 excluding files during volume level backups, 1028 features, 1013 installation, 1015 logon accounts, 1015 overview, 1013 requirements, 1014 restoring automate master database restore, 1036 create standby database, 1035 database files to target instance, 1038 filegroups, 1044 from SQL database backups, 1041 Guide Me wizard, 1039 master database, 1047 point in time log restore option, 1042 recovery completion state, 1035 redirecting restores, 1049 Redirection dialog box, 1050 Restore Job Properties dialog box, 1035 specify date and time for named transaction, 1039 very large databases, 1041 SQL database backups, restoring from, 1041 staging data, 381 stalled job status, threshold for, 445 standby database creating SQL Agent, 1035 SQL 2000, 1013 starting Backup Exec, 108 Desktop and Laptop Option (DLO), 1134 services, 975 static volume, defined, 1426 statistical properties for media, 255 statistics Index
drive usage, 159 drives since cleaning, 161 Status tab for a robotic library, 171 stopping services, 975 storage devices installing, 57 storage limits for user data Desktop Agent, 1253 DLO, 1148 Storage Location, 1165 defined, 1122 deleting, 1167 Symantec Backup Exec for Windows Servers, described, 43 Symantec Volume Snapshot Provider changing defaults, 1008 Symantec Volume Snapshot Provider (VSP), changing defaults, 1006 Symantec Volume Snapshot Provider, and AOFO, 1001 synchronization create new sets, 1256 delete synchronized folder, 1257 overview, 1254 Synchronized Selections view, in Desktop Agent, 1255 synthetic backup advanced settings, 885 baseline, 876 collecting additional information for backups, 879 creating, 882 requirements, 878 template rules, 887 template rules, example, 882 synthetic backup, creating, 880 synthetic backup, defined, 1426 system logon account, 387 system media, defined, 227, 1426 system requirements See also names of individual agents and options Backup Exec, 59 System State backing up on remote Windows computers, 792 restoring, 472 System Summary, overview, 114 System tab, 147 1457
T tablespace data, Oracle Agent, 1299 tapeinst.exe, Device Driver Installation Wizard, 129 tapes See also media DLT tape drive, 622 target domain, defined, 61 task pane, overview, 111 TCP/IP adding for user-defined shares, 305 enabling protocol, 336 required for Backup Exec 8.x and 9.x Agent for Unix, 649 required for RALUS Agent, 804 template defined, 1426 template rule defined, 1426 templates adding a duplicate backup sets template to policies, 382 adding an export media template to a policy, 370 adding backup templates to a policy, 367 backup template file exclusions, 368 changing template rules, 377 deleting from a policy, 373 deleting template rules, 377 duplicate backup sets template overview, 381 editing in a policy, 372 importing into a policy, 372 migrating from previous versions, 367 setting template rules, 373 setting the schedule, 369 using in policies, 366 test run job creating, 320 defined, 320 running for scheduled job, 426 setting defaults, 323 Test Run Results report, 602 testing logon accounts, 292 transaction logs Lotus Domino DBIID, 1333 overview, Lotus Domino, 1333 recycling, Lotus Domino, 1336 1458
viewing Lotus Domino, 1330 transaction logs, backing up SQL Agent, 1033 troubleshooting clusters, 705 Oracle Agent, 1324 TSM option, 786 truncate log on checkpoint option, SQL 7.0, 1033 TSM Option Backup Exec as TSM client, 772 commands management classes created by bex.mac macro, 784 MC_PI management class created by bex.mac macro, 784 MC_VT management class created by bex.mac macro, 784 objects, default size, 784 objects, defined, 784 password for backupexec node, default, 785 policy domain VERITAS, default, 784 policy set bex_backup, default, 784 registering nodes, 785 time to retain only backup version, setting, 785 VERITAS policy domain, default, 784 components Backup Exec default node name, 785 Backup Exec default node registration, 785 backupexec_pi storage pool associated with bexpi.dsm file, 784 backupexec_pi storage pool, defined, 773 backuppool, 773, 784 bex.mac macro, command details, 784 bex.mac macro, defaults created by, 784 bex.mac macro, defined, 775, 783 bex.mac macro, errors while executing, 778 bex.mac macro, using with shared or individual nodes, 778 Administrators Guide
bex_backup policy set, default, 784 bexpi.dsm file, as used in bex.mac macro, 784 creating backupexec_pi storage pool, 775 creating the bexpi.dsm file, 776 diserror.log error log, 786 dsmfmt utility, defined, 775 dsmfmt utility, using to create a storage volume, 776 dsmrc.h file, 786 MC_PI management class, 773 MC_VT management class in theory of operation, 774 Position Information (PI) data stream, defined, 773 setting backup versions to keep, 785 storage volume, creating with dsmfmt utility, 776 theory of operation, 773 error logs, 786 individual nodes, 778 registering nodes, 779 registry keys, 779 changing default number of slots in robotic library, 781 changing default password, 783 communications timeout, changing default, 780 file space name, changing in Backup Exec, 781 MC_PI management class in Backup Exec, 782 MC_VT management class, changing default name, 782 node name for Backup Exec, 781 objects in Backup Exec, 782 shared nodes, 778 system requirements, 771 troubleshooting, 786 Virtual Tape (VT) data stream, defined, 774 U unattended backup jobs, 139 uninstalling Backup Exec, 93 Backup Exec from a Microsoft cluster, 663 Index
using command line, 88 Windows Management Instrumentation SNMP provider, 541 Unique Message Identifier (UMI) error code, viewing, 432 unlocking robotic library panel, 208 up on log on/off option in DLO, back, 1152 Update vault using wizard, 245 updating DLO, 1131 User Data Folder, defined, 1165 User Properties dialog box, 1180 user-defined media vault, 243, 1423 adding media to, 245 creating, 244 user-defined selections, adding, 304 Users access, disabling/enabling in DLO, 1181 adding in DLO, 1178 Desktop Agent access via Profile, 1229 import in CSV file in DLO, 1179 properties, changing in DLO, 1180 removing from DLO, 1181 viewing in DLO, 1180 users managing, 1177 users in DLO, CSV file to add, 1179 utility jobs, overview, 192 utility partitions backing up, 350 backing up in IDR, 914 restoring, 474 restoring in IDR, 917 selecting data for backup, 286 V vault rules for media sets, 225 vaults, moving media, 245 verify after backup completes, 274 after duplicate backup completes, 316, 885 verify job creating, 318 defined, 318 VERITAS update, 101 version and build information, displaying, 629 view filter, setting, 504 1459
view history, 293 viewing active alerts, 502 active job properties, 415 alert history, 502 alert job log, 509 alert properties, 505 alerts, 502 Automated User Assignment properties, 1172 calendar, 413 completed job, 428 job monitor, 405 jobs, 970 jobs list, 405 Lotus Domino databases, 1330 Lotus Domino transaction logs, 1330 scheduled jobs, 420 users in DLO, 1180 views, alerts, 502 VIM configuring recipients, 522 e-mail notification method, 516 virtual devices, using in IDR, 176, 902 virtual servers, backing up in a Microsoft cluster, 683 virtual servers, backing up in a VERITAS cluster, 695 virus, effect on data storage requirements, 352 volume level backups, automatic exclusion of files, 1028, 1080 volume restrictions, Remote Agent for NetWare Servers, 1403 VSS perform consistency check before Exchange backup, 1078 using to protect Exchange data, 1074 W Window menu, 1411 Windows 98/Me Agent installing, 637 password-protecting published folders, 640 publishing drives and directories, 639 set directories as read-only, 640 system requirements, 636 Windows 98/Me Agent, configuring 1460
allow registry restore, 639 current status, 639 disable and enable network backup, 638 overview, 637 publish directories, 639 set up network protocol, 641 set workstation password, 638 using DHCP, 641 Windows Automated System Recovery (ASR) files, in IDR, defined, 906 Windows Change Journal option to use for backup job, 273 using to determine backed up status, 359 Windows Explorer, backups creating, 305 enabling, 120 overview, 305 submitting, 306 Windows Management Instrumentation (WMI), adding WMI capability, 540 Windows registry, backing up with SQL Agent, 1018 Windows remote computers backing up with Backup Exec Remote Agent, 792 System State, backing up on remote computers, 792 Windows Server 2003 backing up, 344 disaster recovery, 610 protecting upgraded resources, 347 Windows XP, disaster recovery, 610 Wizard for DLO, Configuration, 1145 wizards accessing using the Assistant, 116 defined, 1426 WMI installing performance counter provider, 540 installing SNMP provider, 541 performance counters, 540 uninstalling SNMP provider, 541 working set back up files changed today, defined, 1426 working set back up files last accessed in (x) days, defined, 1427 working set backups, defined, 355

279401

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

279401

Uploaded by

Copyright:

Available Formats

Symantec Backup ExecTM 10d for Windows Servers

N180788 September 2005

Apache Software Foundation

Nebiru Software Inc. (dba DomAPI)

Carnegie Mellon University and The Regents of the University of California

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Administrators Guide - Table of Contents

Using Backup Exec Documentation

Steps Text that you type

Text that you replace

Items on the interface

Introducing Backup Exec

Symantec Backup ExecTM for Windows Servers

Small Business Server

QuickStart Edition (OEM release only)

Related Topics: Backup Exec Options on page 51

Whats New in Backup Exec

Whats New in Backup Exec

EFI system partition backup and restore

Availability windows for selection lists

Set thresholds for recovering stalled jobs

Chapter 1, Introducing Backup Exec

Custom error-handling rules

Unique Message Identifier error codes

Whats New in Backup Exec Agents and Options

Whats New in Backup Exec Agents and Options

Chapter 1, Introducing Backup Exec

Intelligent Disaster Recovery

SAN SSO SharePoint Agent

Remote Agent for Windows and NetWare Servers

Chapter 1, Introducing Backup Exec

Microsoft Operations Manager Support

Backup Exec Options

Backup Exec Options

Chapter 1, Introducing Backup Exec

Backup Exec Options

Symantec Backup Exec Remote Agent for Windows or NetWare Servers

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

Backup Exec installation on the media server includes:

350 MB (Typical installation) 550 MB (Includes all options)

Chapter 2, Installing Backup Exec

System Requirements Minimum System Requirements (continued) Other Hardware

Changing Windows Security

Changing Windows Security