NetBackup AdminGuide MSExchg Win

VERITAS NetBackup™ 6.
0 for
Microsoft Exchange Server
System Administrator’s Guide

for Windows
N152688
September 2005
Disclaimer
The information contained in this publication is subject to change without notice. VERITAS Software
Corporation makes no warranty of any kind with regard to this manual, including, but not limited to,
the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software
Corporation shall not be liable for errors contained herein or for incidental or consequential damages
in connection with the furnishing, performance, or use of this manual.
VERITAS Legal Notice

Copyright © 1998-2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS
Logo, and NetBackup are trademarks or registered trademarks of VERITAS Software Corporation or
its affiliates in the U.S. and other countries. Other names may be trademarks of their respective
owners.
Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest
Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.
VERITAS Software Corporation
350 Ellis Street
Mountain View, CA 94043
USA
Phone 650-527-8000
Fax 650-527-2908
www.veritas.com
Third-Party Copyrights
For a list of third-party copyrights, see the NetBackup Release Notes appendix.
ii NetBackup for Microsoft Exchange Server System Administrator’s Guide

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Finding NetBackup Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Accessing the VERITAS Technical Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . x
Contacting VERITAS Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Related Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Comment on the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1. Introduction to NetBackup for Exchange Server . . . . . . . . . . . . . . . . . . . . 1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Backup Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Automatic Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Manual Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
User-Directed Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Exchange Server Files That are Backed Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Database Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Database Patch Files (Exchange 5.5 or pre-Exchange 2000, Service Pack 2) . . . . 7
Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Restore Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Limitations with Exchange 2000/2003 Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Server-Directed Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
iii
Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Redirecting a Restore to a Different Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2. Installation Requirements and Registering a License Key . . . . . . . . . . 11
Verifying the Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Operating System and Platform Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
NetBackup Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Database Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Cluster Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Registering the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Chapter 3. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
User Interface Terminology Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuring NetBackup for Individual Mailbox Operations . . . . . . . . . . . . . . . . . . . . . 16
Configuring the NetBackup Client Service Log On Account . . . . . . . . . . . . . . . . . . 16
Creating a Mailbox for the NetBackup Client Service . . . . . . . . . . . . . . . . . . . . . . . . 17
Exchange 5.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Exchange 2000/2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Granting the NetBackup Client Service Account Advanced Permission . . . . . 19
Configuring NetBackup to Use the Mailbox Associated with the NetBackup
Client Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring the Account Used for Exchange Server Restores . . . . . . . . . . . . . . . . . . . . 23
Configuring Backup Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Adding a New Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Description of Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Adding Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Types of Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Schedule Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Adding Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Adding Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
iv NetBackup for Microsoft Exchange Server System Administrator’s Guide

Creating a Backup Selections List By Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Manually Adding Entries to the Backup Selections list . . . . . . . . . . . . . . . . . . . . 33
Example Entries in the Backup Selections List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Performing Backups with Multiple Data Streams . . . . . . . . . . . . . . . . . . . . . . . . . 36
Using Wildcards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Excluding Folders and Files from Mailbox and Public Folder Backups . . . . . . 39
Testing Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 4. Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Specifying the Server, Client, and the Policy Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Prerequisites for Performing Backups and Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Performing User-Directed Backups of Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . 46
Backup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Exchange 5.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Exchange 2000/2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Restoring Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Before Performing Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Existing Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Restore Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Restoring Exchange 5.x Server Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Restoring the Public and Private Databases Separately from a
Backup Exec Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Restoring Exchange 2003 to the Recovery Storage Group . . . . . . . . . . . . . . . . . . . . . 61
Restoring Storage Groups or Storage Group Databases . . . . . . . . . . . . . . . . . . . . . . 62
Restoring the Key Management Service or Site Replication Service . . . . . . . . . . . . 65
Stopping and Starting KMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Individual Mailbox Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Performing a User-Directed Mailbox Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Restoring Individual Mailboxes, Folders, or Messages . . . . . . . . . . . . . . . . . . . . . . . 70
Redirecting Mailbox Objects to a Different Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Performing Single Instance Store Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Contents
v
Backing Up and Restoring the Exchange Public Folders . . . . . . . . . . . . . . . . . . . . . . . . 81
Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Redirecting Restores of Public Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Chapter 5. Using NetBackup for Exchange Server with Advanced Client . . . . . . . 85
NetBackup Advanced Client for Exchange Server Overview . . . . . . . . . . . . . . . . . . . . 86
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
How Does Advanced Client for Exchange Server Work? . . . . . . . . . . . . . . . . . . . . . . . . 88
Choosing a Backup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
What Is Backed Up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Consistency Checks on Database and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Configuring a Snapshot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuration Tips for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Configuring an Advanced Client Policy for NetBackup for Exchange Server . . . . 91
Performing User-Directed Backups of Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . 94
Restoring Snapshot Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Restore Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Performing a Snapshot Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Manually Mounting a Database After a Restore . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Chapter 6. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Troubleshooting NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Debug Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Backup Operation Debug Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Restore Operation Debug Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Changing the Debug Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
vi NetBackup for Microsoft Exchange Server System Administrator’s Guide

Verifying Exchange Online Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Viewing the Status of a NetBackup Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Operational Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Progress Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Setting Up an Alternate Server for Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Disaster Recovery of Exchange 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Disaster Recovery of Exchange 2000/2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Contents vii
viii NetBackup for Microsoft Exchange Server System Administrator’s Guide

Preface
This guide explains how to configure and use NetBackup for Microsoft® Exchange Server
to perform online backups and restores of Exchange Server.
This document is the same as NetBackup_AdminGuide_MSExchg_Win.pdf
distributed with the NetBackup for Exchange Server software.
This guide is intended for system administrators responsible for configuring and
maintaining systems using Exchange Server. This guide assumes that you have:
◆ A basic understanding of system administration.
◆ A working understanding of the NetBackup client and server software and are
familiar with the information covered in the following NetBackup manuals:
◆ NetBackup Backup, Archive, and Restore Getting Started Guide
◆ NetBackup System Administrator’s Guide for Windows, Volume I
◆ NetBackup System Administrator’s Guide for UNIX, Volume I
◆ NetBackup Troubleshooting Guide for UNIX and Windows
◆ A thorough understanding of the following Exchange Server topics:
◆ Database file types and their relationships at recovery time
◆ Data recovery scenarios
ix
Getting Help
Getting Help
You can find answers to questions and get help from the NetBackup documentation and
from the VERITAS technical support web site.
Finding NetBackup Documentation

A list of the entire NetBackup documentation set appears as an appendix in the NetBackup
Release Notes. All NetBackup documents are included in PDF format on the NetBackup
Documentation CD.
For definitions of NetBackup terms, consult the online glossary.
▼ To access the NetBackup online glossary
1. In the NetBackup Administration Console, click Help > Help Topics.
2. Click the Contents tab.
3. Click Glossary of NetBackup Terms.
Use the scroll function to navigate through the glossary.
Accessing the VERITAS Technical Support Web Site

The address for the VERITAS Technical Support Web site is http://support.veritas.com.
The VERITAS Support Web site lets you do any of the following:
◆ Obtain updated information about NetBackup, including system requirements,
supported platforms, and supported peripherals
◆ Contact the VERITAS Technical Support staff and post questions to them
◆ Get the latest patches, upgrades, and utilities
◆ View the NetBackup Frequently Asked Questions (FAQ) page
◆ Search the knowledge base for answers to technical support questions
◆ Receive automatic notice of product updates
◆ Find out about NetBackup training
◆ Read current white papers related to NetBackup
x NetBackup for Microsoft Exchange Server System Administrator’s Guide

Getting Help
From http://support.veritas.com, you can complete various tasks to obtain specific types
of support for NetBackup:
1. Subscribe to the VERITAS Email notification service to be informed of software alerts,

newly published documentation, Beta programs, and other services.
a. From the main http://support.veritas.com page, select a product family and a

product.
b. Under Support Resources, click Email Notifications.

Your customer profile ensures you receive the latest VERITAS technical
information pertaining to your specific interests.
2. Locate the telephone support directory at http://support.veritas.com by clicking the

Phone Support icon. A page appears that contains VERITAS support numbers from
around the world.
Note Telephone support for NetBackup is only available with a valid support
contract. To contact VERITAS for technical support, dial the appropriate phone
number listed on the Technical Support Guide included in the product box and
have your product license information ready for quick navigation to the proper
support group.
3. Contact technical support using e-mail.
a. From the main http://support.veritas.com page, click the E-mail Support icon.
A wizard guides you to do the following:
◆ Select a language of your preference
◆ Select a product and a platform
◆ Provide additional contact and product information, and your message
◆ Associate your message with an existing technical support case
b. After providing the required information, click Send Message.
Preface xi
Related Resources
Contacting VERITAS Licensing

For license information, you can contact us as follows:
◆ Call 1-800-634-4747 and select option 3
◆ Fax questions to 1-650-527-0952
◆ In the Americas, send e-mail to amercustomercare@veritas.com.
In the Asia and Pacific areas, send email to apaccustomercare@veritas.com.
In all other areas, send email to internationallicense@veritas.com.
Related Resources
You may also need the following resources from Microsoft Corporation:
◆ Exchange Server white papers and FAQs (go to
http://www.microsoft.com/exchange and search for “Disaster Recovery”)
◆ Microsoft Exchange Administrator's Guide
◆ Microsoft Exchange Concepts and Planning Guide
◆ Microsoft TechNet
◆ Microsoft BackOffice Resource Kit
◆ http://www.msexchange.org
Accessibility Features
NetBackup contains features that make the user interface easier to use by people who are
visually impaired and by people who have limited dexterity. Accessibility features
include:
◆ Support for assistive technologies such as screen readers and voice input (Windows
servers only)
◆ Support for keyboard (mouseless) navigation using accelerator keys and mnemonic
keys
For more information, see the NetBackup Installation Guide.
xii NetBackup for Microsoft Exchange Server System Administrator’s Guide

Comment on the Documentation

Let us know what you like and dislike about the documentation. Were you able to find the
information you needed quickly? Was the information clearly presented? You can report
errors and omissions or tell us what you would find useful in future versions of our
manuals and online help.
Please include the following information with your comment:
◆ The title and product version of the manual on which you are commenting
◆ The topic (if relevant) on which you are commenting
◆ Your comment
◆ Your name
Email your comment to NBDocs@veritas.com.
Please only use this address to comment on product documentation. See “Getting Help”
in this preface for information on how to contact Technical Support about our software.
We appreciate your feedback.
Preface xiii
xiv NetBackup for Microsoft Exchange Server System Administrator’s Guide

Introduction to NetBackup for Exchange
Server 1
NetBackup for Microsoft Exchange Server extends the capabilities of NetBackup to
include online backups and restores of Exchange databases when Exchange Server has
been installed. This capability is provided as an add-on or extension to the NetBackup for
Windows client software. Because this product is tightly integrated with the Backup,
Archive, and Restore interface for Windows, this document only gives an overview of
NetBackup functionality. In general, backup and restore operations for Exchange files are
identical to other NetBackup file operations, except where noted in this document.
Microsoft Exchange Server will be referred to as Exchange Server or Exchange.
NetBackup for Microsoft Exchange Server will be referred to as NetBackup for Exchange
Server.
1
Features
Features
Online Backup Exchange Server data and transaction logs can be backed up without
taking the Exchange Server offline. This ensures the availability of
Exchange services and data during the Exchange Server backup.
Minimal Back Up Time An administrator has the choice of performing full or incremental
backups (differential incremental backup or cumulative incremental
backup). A full backup may take considerable time, so it may be
performed infrequently. In the interim, updates that have occurred since
the full backup can be quickly and incrementally backed up by backing
up only the transaction logs. In the event of a failure, the full and
incremental backups would be restored.
During recovery, the Exchange Server will update the databases, applying
each of the logged transactions to the database. After the Exchange Server
recovery has completed, the system will have been brought back to the
state as it existed when the last incremental backup was performed.
Exchange Server NetBackup supports all Exchange Server backup methods: full backup,
Backup Methods cumulative incremental backup, differential incremental backup and
copy.
Tight NetBackup Tight integration with NetBackup means two things:

Integration 1. An administrator already familiar with NetBackup procedures and
software can easily configure and use NetBackup to perform
Exchange Server backup and restore operations.
2. Features and strengths of the NetBackup product suite are available to
the Exchange Server backup user. These features include software
data compression and encryption, scheduled and user-directed
operations, multiple data stream backups, in-line tape copy, etc. Many
of these features are described, in detail, in the NetBackup System
Administrator’s Guide, Volume I.
Central Administration Administrators can define, back up, and restore Exchange Servers and
other NetBackup client machines from a central location.
Media Management Exchange Server backups are saved directly to a wide variety of storage
devices supported by the NetBackup master server.
Automated Backups Administrators can set up schedules for automatic, unattended backups
for local or remote clients across the network. These backups can be full or
incremental and are managed entirely by the NetBackup server from a
central location. The administrator can also manually back up clients.
2 NetBackup for Microsoft Exchange Server System Administrator’s Guide

Features
Restore Operations An administrator using the Backup, Archive, and Restore interface can
browse backups and select the ones to be restored.
Redirected Restores In a redirected restore, you restore an object (database, mailbox, folder, or
message) to a new location.
Individual Mailbox Administrators can perform backup and restore operations on individual
Backup and Restore mailboxes and folders. The capabilities of this feature are:
◆ Scheduled backups of individual mailboxes and folders
◆ User-directed backups of individual mailboxes and folders
◆ Restore of individual mailboxes, folders, or messages, which can be
performed using the Backup, Archive, and Restore interface (on the
server or on the client) or the Remote Administration Console for
Windows or UNIX
Exchange 2000/2003 NetBackup can back up and restore storage groups, as well as back up
Backup and Restore and restore databases within the storage group. The capabilities of this
Features feature are:
◆ Scheduled backups of individual storage groups and databases
◆ User-directed backups of individual storage groups and databases
◆ Restore of individual storage groups and databases, which can be
performed using the Backup, Archive, and Restore interface (on the
server or on the client) or the Remote Administration Console for
Windows or UNIX
◆ NetBackup can also perform backups and restores of the Exchange
Key Management Server (KMS) and Exchange Site Replication Service
(SRS) databases.
Backup and Restore of NetBackup can back up and restore the Exchange Public Store. The
the Exchange Public capabilities of this feature are:
Store ◆ Scheduled backups of individual folders
◆ User-directed backups of individual folders
◆ Restore of individual folders or messages, which can be performed
using the Backup, Archive, and Restore interface (on the server or on
the client) or the Remote Administration Console for Windows or
UNIX
Single Instance Storage Users can enable Single Instance Storage for message attachments so only
(SIS) of message one copy of an attachment is written to the backup.
attachments
Chapter 1, Introduction to NetBackup for Exchange Server 3

Features
Advanced Client This separately-priced option allows NetBackup to perform backups and
restores of Exchange 2003 objects using snapshot methodology. For
complete details on this feature, see “Using NetBackup for Exchange
Server with Advanced Client” on page 85.
Local Backup Backups are performed from the same NetBackup client machine which
contains the Exchange server.
Alternate Client Backups are performed from a second or “alternate” client on behalf of
Backup the primary client. Compared to local backups, this approach reduces the
backup I/O burden on the primary client to the greatest extent.
Primary Client For Alternate Client Backups, this is the NetBackup client which contains
the Exchange server.
Alternate Client For Alternate Client Backups, this is the NetBackup client which actually
performs the backup of the data to the NetBackup server.

Backup Operations
Backup Operations
NetBackup provides three methods to perform backups: automatic, manual, and
user-directed. For more information on these backup methods and other
administrator-directed activities, refer to the NetBackup System Administrator’s Guide,
Volume I.
Additional information is also provided here on the limitations of NetBackup for
Exchange Server and the files included in backups.
Limitations
The following limitations exist for NetBackup for Exchange Server.
◆ Only backups of mailboxes or folders or both are allowed. You cannot specify the
backup of an individual message or individual public document.
◆ (Exchange 2000/2003) Incremental and differential backups are only supported at
storage group level. Incremental and differential backups of individual databases
within a storage group are not supported.
◆ Exchange database backups are required for disaster recovery. Mailbox backups allow
for mailbox recovery, but are not adequate for disaster recovery.
Automatic Backups
The NetBackup administrator can schedule full backup and incremental backups
(differential incremental backup or cumulative incremental backup) that occur
automatically and unattended, under the control of the NetBackup server. Automatic
backups will meet most of your backup requirements.
Manual Backups
NetBackup allows the administrator to perform immediate manual backups of files
associated with any policy, client, or schedules. The manual backup option can be useful
for the following situations:
◆ Testing a configuration
◆ When workstations miss their regular backups
◆ Before installing new software (to preserve the old configuration)
◆ Preserving records before a special event such as when companies split or merge

Backup Operations
In some cases, it may be useful to create a policy and schedule that you use only for
manual backups. You can do this by creating a policy with a single schedule that has no
backup window defined (and therefore never executes automatically).
User-Directed Backups
User-directed backups require a User Backup schedule type to be defined in the
MS-Exchange-Server policy. Performing user-directed backups of Exchange databases is
similar to using the Backup, Archive, and Restore interface to back up normal files.
Exchange Server Files That are Backed Up

The following files can be backed up during a backup operation. Except where noted, the
same files are backed up whether frozen image methodology (available with the
Advanced Client feature) is used to back up the files or not.
Database Files
The database files that are backed up differ for Exchange 5.x and for Exchange 2000/2003.
Exchange 5.x
There are three Exchange Server database files, one for the Directory and two for the
Information Store. The following table gives the database names and their default
locations.
Default locations for Exchange 5.x database files
Database File Name Default Directory
Directory Dir.edb ...\exchsrvr\dsadata
Information Store - Public Pub.edb ...\exchsrvr\mdbdata
Information Store - Private Priv.edb ...\exchsrvr\mdbdata

Backup Operations
Exchange 2000/2003
There can be up to 20 database stores, each consisting of 2 database files. The following
table gives the database names and their default locations for the first Exchange
2000/2003 Storage group.
Default locations for Exchange 2000/2003 database files
Database File Name Default Directory
Mailbox Store Priv1.edb ...\exchsrvr\mdbdata
Priv1.stm ...\exchsrvr\mdbdata
Note Subsequent storage groups and databases may have different locations and names
(user-defined).
Database Patch Files (Exchange 5.5 or pre-Exchange 2000, Service

Pack 2)
Database patch files are used to handle transactions being written to the database during a
backup. During the backup operation, data is read from the .edb file. If a transaction
causes an update to a part of the .edb file that has already been backed up, then it is
written to the patch file for that database. Patch files only exist during the backup process.
These patch files are used during the Exchange Server recovery process to update the
restored database file with the transactions that were in progress during the backup. The
following table gives the names of the patch files and their default locations.
Default locations for patch files
Database Patch File File Name Default Directory
Directory Dir.pat ...\exchsrvr\dsadata
Information Store - Public Pub.pat ...\exchsrvr\mdbdata
Information Store - Private Priv.pat ...\exchsrvr\mdbdata
Transaction Logs
For performance and recoverability, the Exchange database uses transaction logs to
accept, track, and maintain data. All transactions are first written to transaction logs and
memory, and then to their respective databases. Transaction logs can be used to recover

Backup Operations
Directory or Information Store databases in the event that a failure has corrupted the
database. The Information Store can have up to five separate databases but transaction
logs are kept in a single set.
Since transactions are first written to the edb log or e0y log file and then later written to
the database, the current actual or effective database is a combination of the uncommitted
transactions in the transaction log file and the actual edb or e0y database file. When the
log file is filled with transaction data, it is renamed and a new edb or e0y log file is
created. When the log file is renamed, the other renamed log files are stored in the same
subdirectory. The renamed log files are named in a sequential numbering order (for
instance: edb00014.log, edb00015.log, etc. or e0y00014.log, e0y00015.log,
etc., using hexadecimal).
The following table gives the names of the Exchange 5.5 transaction logs and their default
locations.
Default locations for Exchange 5.5 transaction logs
Database Transaction Log File Name Default Directory
Directory edbXXXXX.log ..\exchsrvr\dsadata
Information Store edbXXXXX.log ..\exchsrvr\mdbdata
Where XXXXX is a five digit hexadecimal number that is incremented each time an
edb.log file is renamed.
The following table gives the names of the Exchange 2000/2003 transaction logs and their
default locations.
Default locations for Exchange 2000/2003 transaction logs
Database Transaction Log File Name Default Directory
Information Store e0yXXXXX.log ..\exchsrvr\mdbdata
Where y is a number from 0 - 3 representing the storage group, e.g., e00.log, e01.log,
e02.log, e03.log. XXXXX is a five digit hexadecimal number that is incremented each
time an e0y log file is renamed.
For full backups and differential incremental backups, the committed transaction logs are
truncated (deleted) by Exchange after a successful backup.

Restore Operations
Note After every 5MB of transaction log data is written, a new log is created, even though
the transaction data may not be committed to the database. There may be several
transaction logs containing uncommitted data, and therefore they will not be
purged.
Transactions in log files are committed to the respective edb or e0y file when the
service is shut down normally. For example, when the Information Store service
experiences a normal shutdown (service shuts down with no errors), any
transactions that existed in log files and not in the priv.edb and or pub.edb files
are committed to the edb files. Log files should not be manually purged; it is best to
purge logs through the backup process.
The following process takes place during a full backup:

◆ Database files are written to the backup media.
◆ (Exchange 5.5 or pre-Exchange 2000, Service Pack 2) Patch files are created to
accommodate updates to the database during the backup.
◆ Transaction logs are written to the backup media.
◆ (Exchange 5.5 or pre-Exchange 2000, Service Pack 2) Patch files are written to the
backup media.
◆ Committed transaction logs are truncated (deleted) by Exchange. These logs are no
longer required since they have been committed to the database file and they have
been written to the backup media.
Restore Operations
Using a few simple operations, an administrator using the Backup, Archive, and Restore
interface can browse Exchange Server backups and select the ones to be restored.
Limitations with Exchange 2000/2003 Restores

A restore of more than one storage group at a time (per job) will fail.
Server-Directed Restores
An administrator can browse Exchange Server databases and select the ones to be
restored. NetBackup will allow you to select the NetBackup server from which files will
be restored, to view the backup history, and to select items to restore for a specific client or
other clients that were backed up by the selected NetBackup server

Restore Operations
Redirecting a Restore to a Different Client

Databases or folders can be restored to a client other than the one from which they were
backed up. This is possible only if the NetBackup administrator sets up the configuration
to allow it and the NetBackup for Exchange Server agent has been installed on the
alternate client. The administrator using the NetBackup Administration Console on the
master server or using the Remote Administration Console can direct restores to any
NetBackup client (regardless of which client the files came from). Please see the
appropriate NetBackup manuals for the configuration needed for this type of redirected
restore.
Because the Microsoft Exchange Directory database contains machine and security
information, it can only be restored to the original computer or a clone of the original
computer. The Microsoft Exchange Information Store databases may be restored to a
different Exchange Server.
Additional Requirements for MS Exchange 2000

Before redirecting the restore of storage groups or individual databases:
◆ The storage groups and databases must exist on the target server.
◆ The storage groups and databases must have the same names as the original storage
groups or databases.
◆ The target databases must be configured so that they can be overwritten. Using the
Exchange System Manager, 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.
◆ The target server must have the same Organization and Administrative Group name
as the source server.
Redirecting a Restore to a Different Path

A user can restore mailbox objects and Public folder objects to folders that are different
from the folders from which the objects were backed up. Database objects should not be
redirected to different paths.

Installation Requirements and Registering a
License Key 2
This chapter describes how to perform the following tasks:
◆ Verifying the installation prerequisites for NetBackup for Exchange Server. Perform
this task before enabling this agent.
The NetBackup for Exchange Server software is installed when you install
NetBackup, so verify these prerequisites before enabling NetBackup for Exchange
Server.
◆ Registering the license key for NetBackup for Exchange Server.
11
Verifying the Installation Prerequisites

Before enabling NetBackup for Exchange Server, verify that you are installing the agent
on a supported operating system or platform and that requirements are met for the
NetBackup software, the database agent, and, if applicable, the cluster software. These
requirements apply for remote and local installations.
Operating System and Platform Compatibility

Verify that NetBackup for Exchange Server will be installed on an operating system or
platform supported by NetBackup. A compatibility list for database agents is available on
the Technical Support web site.
▼ To verify compatibility
1. Go to the Technical Support web page: http://support.veritas.com.
2. From the Select Product Family list, click NetBackup Products.
3. From the Select Product list in the right pane, click NetBackup Enterprise Server.
4. Under Support Resources, click Compatibility and Reference.
5. In the list of documents, click NetBackup Enterprise Server (tm)/ Server x.x Database
Agent Compatibility (updated date).
For x.x, look for the current release. For date, look for the most recent date.
For information on supported cluster environments for NetBackup for Exchange
Server, see NetBackup (tm) x.x Cluster Compatibility (updated date).
6. Click on the link for the PDF document, which is a downloadable file that enables you
to view the supported database spreadsheet for this release.
7. Read the document and verify that the software in your environment is compatible
with the NetBackup and NetBackup for Exchange Server software.

NetBackup Software
Verify that the following requirements are met for the NetBackup server and client
software:
❏ The NetBackup server software is installed and operational on the NetBackup server.
The NetBackup server platform can be any of those that NetBackup supports. For
installation information, see the NetBackup Installation Guide.
❏ The NetBackup client software is installed on the client where you will be backing up
the databases. This step also installs NetBackup for Exchange Server.
In addition, the install_path\NetBackup directory must exist on the client. On
Windows platforms, the NetBackup for Exchange Server software is installed along
with the server and client software. For installation information, see the NetBackup
Installation Guide.
❏ Make sure that you have configured backup media in a Media Manager or disk
storage unit. The amount of backup media required depends on the devices used, the
sizes of the databases that you are backing up, the amount of data that you are
archiving, the size of your backups, and the frequency of backups or archives. For
information on using Media Manager, see the NetBackup Media Manager System
Administrator’s Guide.
Database Agent
Verify that the follow requirements are met for the database software.
❏ The Exchange vendor software is installed and operational on each client.
Cluster Software
Verify the following requirements if you are enabling the NetBackup for Exchange Server
software on a NetBackup server configured in a NetBackup cluster:
❏ The Exchange vendor software is installed and operational on each node to which
NetBackup can failover.
❏ The NetBackup server software is installed and configured to work in a NetBackup
cluster. Follow the instructions in the NetBackup Installation Guide.
The NetBackup server installation procedure installs the NetBackup for Exchange
Server software along with the server and client software. After all other prerequisites
are met, you only need to register the license key for the agent on each NetBackup
server in order to enable the agent.
Chapter 2, Installation Requirements and Registering a License Key 13

Registering the License Key
Registering the License Key

NetBackup for Exchange Server is installed with the server and client software. To use this
agent, register a valid license key for it on the master or media server. In a NetBackup
cluster, register the key on each node on which the NetBackup server is installed.
▼ To register a license key
1. On the master or media server, open the NetBackup Administration Console.
2. Choose Help > License Keys.
3. Click the New button.
4. Type in the license key and click Add.

For information on adding license keys, see the NetBackup System Administrator’s
Guide, Volume I.

Configuration 3
This chapter provides information on configuring NetBackup to perform backup and
restore operations of Exchange Server.
◆ “Configuring NetBackup for Individual Mailbox Operations”
◆ “Configuring the Account Used for Exchange Server Restores”
◆ “Configuring Backup Policies”
◆ “Testing Configuration Settings”
User Interface Terminology Notes

You can perform many of the configuration steps in this chapter from the NetBackup
Administration Console on the master server. Depending on your master server’s
platform, the console is available in one or two forms. NetBackup supports a Java
interface for both Windows and UNIX master servers. In addition, NetBackup supports a
Windows interface for Windows master servers.
The Java and Windows interfaces are nearly identical, but when there are interface
differences in the configuration procedures, this manual uses the following headings to
identify the interface being described:
From the Windows interface:
From the Java interface:
15
Configuring NetBackup for Individual Mailbox Operations

The following configuration must be performed so that NetBackup can backup and
restore individual mailboxes and folders and items in the Public Folders.
Note If in a cluster, the procedures in the following sections need to be performed on each
Exchange node in the cluster.
Configuring the NetBackup Client Service Log On Account

By default, the NetBackup Client service uses Local System as the account on which to log
on. To perform individual mailbox backups or restores, the service account needs to be
changed to another valid Windows domain account.
Note If in a cluster, these steps need to be performed on each Exchange node in the
cluster.
▼ To verify or modify the Log On account for the NetBackup Client service
1. Open the Windows Services application.
2. Double-click on the NetBackup Client Service entry.
3. Click on the Log On tab.
4. If Local System account is not selected as the Log on account, proceed with step 7.
5. Provide the name of the account you wish to use for backups and restores on this
client.
Note To change this account, you must have administrator group privileges.
6. Stop and start the NetBackup Client Service.
7. Close the Services application.

Creating a Mailbox for the NetBackup Client Service

In order for NetBackup to gain access to the mailboxes and folders to perform backup and
restore operations, the NetBackup Client service account needs to be associated with a
valid Exchange mailbox. It is recommended that you create a uniquely named mailbox for
the NetBackup Client service account.
Note If in a cluster, these steps need to be performed on each Exchange node in the
cluster.
Exchange 5.x
For Exchange 5.x, if a mailbox is not created for the NetBackup Client service, you can use
any existing mailbox on the Exchange Server to which the NetBackup Client service
account is granted log on rights.
▼ To create a mailbox for the NetBackup Client service account
1. Using Exchange Administrator, create a new mailbox with a unique name.

A unique name is one that does not already exist within the Exchange Organization.
This name cannot be contained as a set of characters in an existing name.
For example, if EXCH1 has been entered as the unique mailbox name, and there are
other mailbox names such as EXCH1BACKUP or BACKUPEXCH1, backups or
restores of individual mailboxes, or both, will fail.
If you cannot create a unique mailbox name, you must enter the fully qualified name
when configuring the mailbox for the NetBackup Client service account (see
“Configuring NetBackup to Use the Mailbox Associated with the NetBackup Client
Service Account” on page 21). For example:
/O=Org_Name/OU=Site_Name/CN=Server_Name/CN=EXCH1
or
Create a new mailbox and assign a unique alias to the mailbox. Then, when
configuring the mailbox for the NetBackup Client service account, enter only the alias.
(See “Configuring NetBackup to Use the Mailbox Associated with the NetBackup
Client Service Account” on page 21.)
2. Double-click on the new mailbox and click the General tab.
3. Click Primary Windows NT Account and add the NetBackup Client service account.
Chapter 3, Configuration 17
4. Select either a site container or recipient container that contains the mailboxes you
want to back up.
a. Click the Properties button.
b. On the Permissions tab, add the NetBackup Client service account, select the
Admin Role, and click OK.
Note The minimum rights required for backing up and restoring a mailbox are Modify
User Attributes and Modify Administrator Attributes. By default, the Admin role
includes Add Child, Modify User Attributes, Modify Administrator Attributes, and
Delete and Logon rights. The Admin role can be edited as a Custom role with only
the minimum rights.
If you elect to grant permissions individually to each mailbox rather than to grant
access to all mailboxes at the site or recipient container level, you can assign the
User role, which allows backing up and restoring mailboxes to which permissions
have been given. This role can also be edited to include only the Modify User
Attributes and the Modify Administrator Attributes.
Exchange 2000/2003
▼ To create a mailbox for the NetBackup Client service account
1. Using Active Directory Users and Computers, create a mailbox with a unique name.
A unique name is one that does not already exist within the Exchange Organization.
This name cannot be contained as a set of characters in an existing name.
For example, if EXCH1 has been entered as the unique mailbox name, and there are
other mailbox names such as EXCH1BACKUP or BACKUPEXCH1, backup or restore
of individual mailboxes or both will fail.
2. Make this account a member of Domain Admins group.
3. Using the Exchange Administration Delegation Wizard, select the NetBackup Client
service account and grant the Exchange Administrator access to the account.
a. Start the Exchange System Manager program.
b. Select the appropriate Administrative Group.
c. Right-click on the Administrative Group and select Delegate Control.

4. Click Next.
5. Click Add.
6. In the Delegate Control dialog box, browse for the mailbox created in step 1.
a. From the Role list, select Exchange Full Administrator.
b. Click OK.
c. Click Next.
d. Click Finish.
7. If you have an active/active configuration, continue with the next section, “Granting
the NetBackup Client Service Account Advanced Permission.”
Granting the NetBackup Client Service Account Advanced
Permission
If you have an active/active configuration, the NetBackup Client service must also be
granted “Receive As” and “Send As” advanced permission on each virtual Exchange
Server in the configuration.
▼ To grant the NetBackup Client service account advanced permission
1. Open Exchange System Manager.
2. Select the virtual Exchange Server name.
3. Right-click on the virtual name and select Properties.
4. Click on the Security tab.
5. Select the NetBackup Client service account under the Name pane.

6. Under Permissions, select Receive As and Send As.
7. Click OK.
8. Repeat step 2 through step 7 for each virtual Exchange Server in the cluster.
Configuring NetBackup to Use the Mailbox Associated with

the NetBackup Client Service Account
This configuration can be performed with the NetBackup Administration Console for
Windows or for UNIX or through the Remote Administration Console.
▼ To configure the mailbox for the NetBackup Client service account
1. Open the NetBackup Administration Console or the Remote Administration Console.
2. In the left pane, expand Host Properties.
3. Click Clients.
4. In the right pane, right-click on the client you wish to configure and choose
Properties.
5. Expand Windows client and click Exchange.
6. In the Mailbox for message level backup and restore box, specify the mailbox. The
mailbox may be specified as:
◆ An Exchange mailbox name
◆ A fully-qualified name
◆ /O=Org_Name/OU=Site_Name/CN=Server_Name/CN=Mailbox_Name
◆ A mailbox alias
7. Click OK.

Configuring the Account Used for Exchange Server Restores
Configuring the Account Used for Exchange Server

Restores
VERITAS recommends that the NetBackup client service use the same account that is
running Exchange Services. If you are restoring from Exchange 5.x and are using an
account other than the one used for Exchange, the account must be added to the local
computer’s Administrators group. It is not necessary to add the account to the domain
Administrators or domain Admins groups. Exchange 5.x services need to be shut down in
order to restore Exchange Server and Administrator privilege is necessary to shut down
services in Windows.
Configuring Backup Policies

A NetBackup policy defines the backup criteria for a specific group of one or more clients.
These criteria include:
◆ Storage unit and media to use
◆ Policy attributes
◆ Backup schedules
◆ Clients to be backed up
◆ Items (database objects) to be backed up
To use NetBackup for Exchange Server, you need to define at least one
MS-Exchange-Server policy with the appropriate schedules. A configuration can have a
single policy that includes all clients, or there can be many policies, some of which include
only one client.
Most requirements for MS-Exchange-Server policies are the same as for file system
backups. In addition to the attributes described here, there are other attributes for a policy
to consider. For configuration instructions and information on all the attributes available,
see the NetBackup System Administrator’s Guide, Volume I.
Adding a New Policy

▼ To add a new policy
1. Log on to the master server as administrator (Windows) or root (UNIX).
2. Start the NetBackup Administration Console.
3. If your site has more than one master server, choose the one on which you want to
add the policy.
4. From the Windows interface: In the left pane, right-click Policies and choose New
Policy.
From the Java interface: In the left pane, click Policies. In the All Policies pane,
right-click the master server, and click New.
The Add a New Policy dialog box displays.
5. In the Policy name field, type a unique name for the new policy.

6. Click OK.
A dialog box displays in which you can specify the general attributes for the policy.
7. From the Policy Type box, select the MS-Exchange-Server policy type.
Note The MS-Exchange-Server policy type does not appear in the drop-down list unless
your master server has a license key for NetBackup for Exchange Server.
8. Complete the entries on the Attributes tab. For more information, see “Description of
Attributes” on page 25.
9. Add other policy information.

◆ To add schedules, see “Adding Schedules” on page 26.
◆ To add clients, see “Adding Clients” on page 31.
◆ To add Exchange objects to the Backup Selections list, see “Adding Backup
Selections.”
10. When you have added all the schedules, clients, and Backup Selections you need,
click OK. The new policy is created.
Description of Attributes
With a few exceptions, NetBackup manages a database backup like a file system backup.
The following table shows the policy attributes that are different for Exchange backups.
This information is used when you are adding a new policy.
Other policy attributes vary according to your specific backup strategy and system
configuration. For more information on policy attributes, see the NetBackup System
Description of Policy Attributes
Attribute Description
Policy type Determines the types of clients that can be in the policy and, in some cases,
the types of backups that NetBackup can perform on those clients. To use
NetBackup for Exchange Server, you must define at least one policy of type
MS-Exchange-Server.
Description of Policy Attributes
Attribute Description
Allow multiple data Specifies that, depending on directives in the list of backup selections,
streams NetBackup can divide automatic backups for each client into multiple jobs,
with each job backing up only a part of the list of backup selections. The
jobs are in separate data streams and can occur concurrently. The number
of available storage units, multiplex settings, and the maximum jobs
parameters determine the total number of streams and how many can run
concurrently.
Keyword phrase A textual description of a backup. Useful for browsing backups and
restores.
Advanced Client See the “Using NetBackup for Exchange Server with Advanced Client” on
page 85 for information on configuring policies for snapshot methods.
Adding Schedules
Each policy has its own set of schedules. These schedules control initiation of automatic
backups and also specify when user operations can be initiated.
▼ To add a schedule
1. In the Policy dialog, click the Schedules tab.

To access the Policy dialog, double-click the policy name in the Policies list in the
NetBackup Administration Console.
2. Click New.
A dialog is displayed.
3. Specify a unique name for the schedule.
4. Select the Type of backup.

For information on the types of backups available for this policy, see “Types of
Backups” on page 28.

5. Specify the other properties for the schedule as explained in “Schedule Properties” on
page 29.
6. If this is the last schedule, click OK.

To add more schedules, click Add and repeat step 2 through step 6.
Types of Backups
Description of Types of Backups
Type of Backup Description
Full Backup For server backups, this schedule type will back up the Exchange Server
database and associated transaction logs. All committed transaction logs
will be truncated (deleted) after they are successfully backed up.
For mailbox backups, this schedule type will back up the entire mailbox,
including all the folders and messages in that mailbox.
For the Public Store, this schedule type will backup the entire Public Store,
including all the folders and messages within the Public Store.
Differential- A differential incremental backup will only back up changes since the last
incremental backup full or differential incremental backup. Differential incremental backups can
be performed of databases, the KMS and SRS services, mailboxes and of the
Public Share.
When using this method to back up a database, only transaction logs are
backed up. After the successful backup of the transaction logs, all
committed logs will be truncated (deleted). The truncation of the transaction
logs sets the context for the next backup.
To perform a full restore the data needed is contained in multiple
NetBackup images. One image for the full backup and another image for
each differential incremental that was performed.
User Backup A user backup is not automatically scheduled and is initiated on the target
client machine.
A user-directed backup of a database is identical to a full backup except that
the transaction logs are not truncated. Because of this, user backups are like
taking a snapshot of the databases at a given point in time without
impacting the content of ongoing full and incremental backups.
You may want to consider creating a separate policy for User Backup
schedule types. This will allow you to easily separate user-directed and
scheduled backups when restoring files. If you decide to create separate
policies for User Backup schedule types, the considerations are similar to
those for automatic backups. A Backup Selections list is not needed because
users select the files before starting the operation.

Description of Types of Backups (continued)
Type of Backup Description
Cumulative A cumulative incremental backup backs up all changes since the last full
incremental backup backup or differential incremental backup (however, it is not standard
practice to mix cumulative- and differential incremental backups between
full backups). Cumulative incremental backups can be performed of
databases, the KMS and SRS services, mailboxes and of the Public Share.
When using this method to back up databases, only transaction logs are
backed up and they are not truncated upon completion of the backup. When
restoring databases, transaction logs remain intact since the last full backup.
In an Exchange Server data recovery scenario where it has been determined
that the transaction logs are all intact, you only need to restore the database
from the last full backup and the last cumulative incremental backup.
During recovery, Exchange Server will replay all the logs in the log folder.
This will bring the Exchange Server database back to the current date
instead of to the time of the last full or incremental backup.
Caution Differential incremental and cumulative incremental backup types will fail if
database circular logging is configured for the Exchange Server. By disabling
circular logging, incremental backups may then be performed. See Microsoft’s
Exchange Server Administration Guide for more information on configuring
circular logging.
Note You are allowed to configure incremental schedule types, but incremental backups
will not be performed for individual databases within storage groups. The backup
job will still run according to the configured incremental schedules, but the job will
log warnings for attempted incremental backups of these objects.
Schedule Properties
Some of the schedule properties have a different meaning for database backups than for a
regular file system backup. The following table explains the schedule properties:
Description of Schedule Properties
Property Description
Type of backup Specifies the type of backup that this schedule controls. The selection list
shows only the backup types that apply to the policy you are configuring.
For more information, see “Types of Backups.”
Description of Schedule Properties (continued)
Property Description
Frequency This setting is used only for scheduled backups and not for user-directed
backups. Frequency specifies the period of time that can elapse until the
next backup or archive operation begins on this schedule. For example, if
the frequency is seven days and a successful backup occurs on Wednesday,
the next full backup does not occur until the following Wednesday.
Typically, incremental backups have a shorter frequency than full backups.
Calendar This setting is used only for scheduled backups. It is not used for
user-directed backups. The Calendar option allows you to schedule backup
operations based on specific dates, recurring week days, or recurring days of
the month.
Retention Specifies a retention period for keeping backup copies of files before
deleting them. The retention level also denotes a schedules priority within
the policy, with Level 9 schedules having the highest priority and Level 0 the
lowest. Set the time period to retain at least two full backups of your
database. In this way, if one full backup has been lost, you will have another
full backup to fall back on. For example, if your database is backed up once
every Sunday morning, you should select a retention period of at least 2
weeks.
Other schedule properties vary according to your specific backup strategy and system
configuration. For more information on schedule properties, consult the NetBackup System

Adding Clients
The Clients list contains a list of the clients that will be backed up during an automatic
backup. A NetBackup client must be in at least one policy but can be in more than one.
The following software must be installed on the client:
◆ Exchange Server
◆ NetBackup client or server
▼ To add clients to a policy
1. In the Policy dialog, click the Clients tab.

To access the Policy dialog, double-click the policy name in the Policies list in the
NetBackup Administration Console.
2. Click New.
3. Enter the name of the client you want to add.

If Exchange is installed in a NetBackup cluster, specify the virtual Exchange name as
the client name.
From the Windows interface:
◆ Type the name into the client list and press Enter.
If NetBackup cannot detect the hardware and operating system, a dialog box
displays so you can specify this information.
OR
◆ Click the Browse for Computer button to choose the client from the network.
From the Java interface:
a. The Add Client dialog box displays. In the Client name field, type the name of
the client you are adding.
b. Choose the Hardware and operating system type and click Add.
4. To add another client, repeat step 2 and step 3.
5. If this is the last client, click OK.
Adding Backup Selections

The Backup Selections list defines the Exchange objects (databases, mailboxes, and
mailbox folders) to be backed up and the grouping of Exchange objects for multiple data
streams. For information on excluding items from backups, see “Excluding Folders and
Files from Mailbox and Public Folder Backups” on page 39.
Notes
◆ Database backups should be performed separately from mailbox backups and
Exchange 5.5 and Exchange 2000/2003 backups should be performed separately. For
example, Microsoft Exchange Server:\Information Store\, an Exchange
5.5 directive, and Microsoft Information Store:\First Storage Group\,
an Exchange 2000 directive, should not be added to the same policy. Nor should
Microsoft Exchange Mailboxes:\*, a mailbox directive, and Microsoft
Information Store:\, an Exchange 2000/2003 directive, be added to the same
policy.
◆ For Active/Active configuration of Exchange 2000/2003 in an Microsoft Cluster
Server environment, if more than one instance is running on the same node, scheduled
backups using the Mailbox directive only will backup all mailboxes on all instances
running on that node, regardless of which virtual server name is specified for
backups.
◆ When individual databases in a storage group are backed up, the transaction logs for
the entire storage group are also included in the backup. Transaction logs will not be
truncated (deleted) until a full backup is run on every database in the storage group.
To ensure transaction logs are truncated (deleted) regularly, include all databases for a
storage group in a full backup policy or specify the storage group, and not individual
databases, in the backup policy.
Creating a Backup Selections List By Browsing

On Windows systems, you can browse for Exchange objects and add them to the Backup
Selections list. Alternatively, the objects can be specified manually (see “Manually Adding
Entries to the Backup Selections list” on page 33). For examples, see “Example Entries in
the Backup Selections List” on page 35.
▼ To add an Exchange object to the Backup Selections list by browsing (Windows

Only)
1. In the Policy dialog, click the Backup Selections tab.
2. Click New.

3. Click the Remote Folder button.
The Browse window is displayed.
4. Navigate to and select the Exchange object to back up and click OK.
To back up an Exchange 5.x Server, add both the Microsoft Exchange
Server:\Directory\ and Microsoft Exchange Server:\Information Store\ to the
Backup Selections list.
5. Edit the new entry, if you wish to define groups of objects or use multiple data
streams.
For example, you can create groups of mailboxes, storage groups or databases, or
Public folders to back up, see “Using Wildcards” on page 37. To divide backups into
multiple data streams, see “Performing Backups with Multiple Data Streams” on
page 36.
6. (Exchange 2000 only) If creating a policy to backup Public folders, the Microsoft
Information Store, or Storage Groups or databases, add the ExIFS drive (M: drive, by
default) to the NetBackup client’s Exclude list. This will prevent Exchange 2000
objects from being backed up as file-level files.
7. Click OK.
Manually Adding Entries to the Backup Selections list

Database objects can be manually added to the Backup Selections list, if you do not wish
to use the browse feature. For examples, see “Example Entries in the Backup Selections
List” on page 35.
▼ To manually add entries to the Backup Selections list
1. In the Policy dialog, click the Backup Selections tab.
2. Click New.
UNIX: A dialog box displays.
3. On Windows, click the Directives button.
4. From the Directive set list, select the desired Directive set.
Use the MS_Exchange_2000 directive set for Exchange 2000 or for Exchange 2003.
5. Select the directive.

To back up an Exchange 5.x Server, add both the Microsoft Exchange
Server:\Directory\ and Microsoft Exchange Server:\Information Store\ directives.
Windows:
a. From the Directive list, select the desired Exchange object.
b. Click OK.
UNIX:
a. From the Pathname or directive list, select the desired Exchange object.
b. Click Add.
c. Click OK.
6. Edit the new entry, if you wish to define groups of objects or use multiple data
streams.
For example, you can create groups of mailboxes, storage groups or databases, or
Public folders to back up, see “Using Wildcards” on page 37. To divide backups into
multiple data streams, see “Performing Backups with Multiple Data Streams” on
page 36.
7. (Exchange 2000 only) If creating a policy to backup Public folders, the Microsoft
Information Store, or Storage Groups or databases, add the ExIFS drive (M: drive, by
default) to the NetBackup client’s Exclude list. This will prevent Exchange 2000
objects from being backed up as file-level files.
8. Click OK.

Example Entries in the Backup Selections List

The following table includes example entries for mailboxes, Public folders, Storage
Groups, and Storage Group databases.
Example entries in the Backup Selections list
To back up Example path
An individual Microsoft Exchange Mailboxes:\Mailbox 1\

mailbox
A mailbox folder Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\Inbox
Multiple mailboxes, NEW_STREAM
using two Microsoft Exchange Mailboxes:\[a-m]*
datastreams*
NEW_STREAM
Microsoft Exchange Mailboxes:\[n-z]*
Multiple mailboxes, Microsoft Exchange Mailboxes:\*
using one stream for

each mailbox*
Multiple folders NEW_STREAM
using two Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\[a-m]*
datastreams*
NEW_STREAM
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\[n-z]*
An individual Public Microsoft Exchange Public Folders:\Folder1\
folder
A Public subfolder Microsoft Exchange Public Folders:\Folder1\Subfolder1\
Multiple Public NEW_STREAM
folders, using two Microsoft Exchange Public Folders:\Folder1\
datastreams*
NEW_STREAM
Microsoft Exchange Public Folders:\Folder2\
Multiple Public Microsoft Exchange Public Folders:\*
folders, using one

stream for each
folder*
Example entries in the Backup Selections list (continued)
To back up Example path
An individual Microsoft Information Store:\First Storage Group\

Storage Group
A database within a Microsoft Information Store:\First Storage Group\Mailbox Store\

Storage Group Note When individual databases in a storage group are backed up, the
transaction logs for the entire storage group are also included in the
backup. Transaction logs will not be truncated (deleted) until a full
backup is run on every database in the storage group. To ensure
transaction logs are truncated (deleted) regularly, include all databases
for a storage group in a full backup policy or specify the storage
group, and not individual databases, in the backup policy.
Multiple Storage NEW_STREAM
Groups, using two Microsoft Information Store:\Storage Group[1-3]
datastreams*
NEW_STREAM
Microsoft Information Store:\Storage Group[4-6]
Multiple Storage Microsoft Information Store:\Storage Group*
Groups, using one

stream for each
Storage Group*
*
Allow multiple data streams must be enabled in order for this Backup Selections list to be backed up
successfully.
Performing Backups with Multiple Data Streams

Multiple datastreams divide automatic backups into multiple jobs, with each job backing
up only a part of the Backup Selections list. To use multiple data streams, enable Allow
multiple data streams on the Attributes tab for the policy) and add the NEW_STREAM
directive in the Backup Selections list to indicate where a new backup stream should
begin. Exchange mailboxes or storage groups defined in the Backup Selections list with
wildcard characters will be backed up in multiple streams.
You can choose to have NetBackup automatically determine where to begin new streams,
or you can control where each stream begins by inserting the NEW_STREAM directive at
a certain point or points in the Backup Selections list. For example, if you enable multiple
datastreams and specify the following in the Backup Selections list, NetBackup will create
a new stream for each mailbox.
Microsoft Exchange Mailboxes:\[a-m]*

If instead you specify the following in the Backup Selections list, NetBackup will create
only two streams, one for mailboxes “a-m” and one for mailboxes “n-z”.
NEW_STREAM
Microsoft Exchange Mailboxes:\[a-m]*
NEW_STREAM
For more information on the multiple data streams feature, refer to the NetBackup System
Using Wildcards
Wildcard characters can be used to define groups of mailboxes, storage groups, or Public
folders. This way multiple objects can be backed up without having to specify the objects
individually in the Backup Selections list. This will only be successful if multiple data
streams have been enabled. If this feature has not been enabled, the backup will fail.
The supported wildcard characters for Backup Selections lists in an Exchange policy are
described below.
Supported wildcard characters
Wildcard character Action
Asterisk (*) Use as a substitute for zero or more characters. To specify all objects that
start with an ‘a’ use “a*”.
Question Mark (?) Use as a substitute for a single character in a name. For example, “s?z”
would process all objects that had ‘s’ for a first character, any character for a
second character, and ‘z’ for a third character.
Left & Right Brackets Use to match any one character enclosed in square brackets. A minus (-)
([ … ]) may be used to indicate a range of consecutive characters; for example, [0-9]
is equivalent to [0123456789].
Note The - loses this special meaning if it occurs last in the string.
Note The right square bracket (]) does not terminate such a string when it is
the first character within it; for example, [] a-f] matches either a right
square bracket (]) or one of the ASCII letters a through f inclusive.
Asterisk (*) and Question Mark (?) stand for themselves within such a
string of characters.
The following rules apply when using wildcard characters in the Backup Selections list.
◆ Only one wildcard pattern per Backup Selections list entry is allowed.
Correct
Incorrect
Microsoft Information Store:\Storage*[1-3]
Microsoft Information Store:\Storage*[4-6]
◆ Wildcard patterns will only be honored in the final segment of the path name.
Correct
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\*
Microsoft Exchange Public Folders:\Folder\Subfolder?
Incorrect
Microsoft Exchange Mailboxes:\Mailbox 1\*\Inbox
Microsoft Exchange Public Folders:\Folder?\
◆ Wildcard patterns in Exchange 2000 directives will only be honored in the Storage
Group segment of the path.
Correct
Microsoft Information Store:\ Storage Group?
Incorrect
Microsoft Information Store:\First Storage Group\Database*
◆ If a wildcard pattern is not honored it will be treated literally.

◆ For an Exchange Mailbox path any segment of the path may contain wildcard
characters, including mailbox names, folders, or messages within the Mailbox
hierarchy, as long as the wildcard characters are the last characters in the segment.
Correct
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\[a-m]*
Microsoft Exchange Mailboxes:\Mailbox [1-3]
Incorrect
Microsoft Exchange Mailboxes:\Mailbox [1-3]\Top of Information Store
Microsoft Exchange Mailboxes:\Mailbox 1\Top*\
◆ For Exchange Public folders any segment of the path may contain wildcard
characters, including workspace names or workspace folders, as long as the wildcard
characters are the last characters in the segment.
Correct
Microsoft Exchange Public Folders:\Folder1\Subfolder?
Incorrect
Microsoft Exchange Public Folders:\Folder?\Subfolder1
Microsoft Exchange Public Folders:\*\Subfolder1
Excluding Folders and Files from Mailbox and Public Folder Backups
Specific folders and files can be excluded from backups of mailboxes or backups of the
Public folder by adding these folders and files to an exclude list. This section describes the
syntax that should be used when adding Exchange entries to an exclude list. An exclude
list can be added from the server or from the client.
For more information on how to create exclude lists using the NetBackup Administration
Console, see the NetBackup System Administrator’s Guide, Volume I.
Example Exchange mailbox entries in an exclude list
This entry... would exclude...
Microsoft Exchange Mailboxes:\J* All mailboxes with names starting with J.
Microsoft Exchange Mailboxes:\J?e* All mailboxes with names starting with J and where the third
letter of the mailbox name is e.
Microsoft Exchange Mailboxes:\Joe Smith* Any mailbox with a name that starts with Joe Smith.
Example Exchange mailbox entries in an exclude list
Microsoft Exchange Mailboxes:\Joe Smith ?JoeS? Any mailbox with a name Joe Smith and an alias name of JoeS.
Microsoft Exchange Mailboxes:\Joe Smith*\Top The Deleted Items folder for the mailbox Joe Smith.
of Information Store\Deleted Items
Microsoft Exchange Mailboxes:\*\Top of Any messages beginning with Virus in the user's Inbox.
Information Store\Inbox\Virus*
Example Public folder entries in an exclude list
Microsoft Exchange Public Folders:\Marketing The root Public folder called Marketing.
Microsoft Exchange Public All .xls documents under the Public Folder called
Folders:\Marketing\*.xls Marketing.

Testing Configuration Settings

After configuring the master server for NetBackup for Exchange Server, test the
configuration settings by performing a manual backup (or backups) using the automatic
backup schedules you have created. For a description of status codes and other
troubleshooting information, refer to the NetBackup Troubleshooting Guide.
▼ To test the configuration settings
1. Log onto the master server as administrator (Windows) or root (UNIX).
2. Start the NetBackup Administration Console.
3. In the left pane, click Policies.

From the Windows interface: The policy list appears in the right pane.
From the Java interface: The right pane splits into an All Policies pane and a details
pane.
4. Click the policy you want to test.
5. Choose Actions > Manual Backup.

The Manual Backup dialog box appears.
The Schedules pane contains the name of an automatic schedule (or schedules)
configured for the policy that you are going to test. The Clients pane contains the
name of the client(s) listed in the policy that you are going to test.
6. Follow the directions in the Manual Backup dialog box.
7. Click Activity Monitor on the NetBackup Administration Console.

If the manual backup does not exit with a successful status, see the Troubleshooting
chapter.

Operating Instructions 4
After completing the configuration, you can use the Backup, Archive, and Restore
interface to back up Exchange databases, mailboxes or folders. This chapter contains the
following information:
◆ “Specifying the Server, Client, and the Policy Type”
◆ “Prerequisites for Performing Backups and Restores”
◆ “Performing User-Directed Backups of Exchange Server”
◆ “Restoring Exchange Server”
◆ “Individual Mailbox Operations”
◆ “Performing Single Instance Store Backups”
◆ “Backing Up and Restoring the Exchange Public Folders”
◆ “Redirecting a Restore to a Different Client”
43
Specifying the Server, Client, and the Policy Type
Specifying the Server, Client, and the Policy Type

When performing user backups of Exchange Server, you must specify the server that will
perform the backups. In a cluster environment, NetBackup performs the backup of the
client (or Exchange Server) by using the virtual name of the Exchange Server. (The name
of the virtual Exchange Server must be included in the client list of the policy in order for
backup and restore operations of Exchange Server to be successful.)
In order to browse for and restore Exchange backups, you need to specify the server that
performed the backups, the client that was backed up, and the Exchange policy type. If
you have administrative privileges or are logged into the master or media server, you can
also choose the destination client to which a backup will be restored (this is called
redirecting a restore to a different client). For more information see “Redirecting a Restore
to a Different Client” on page 83.
Note You cannot use the Java client interface to select a virtual client for a backup
operation. To back up a virtual client using the Java interface, log in using the
virtual client name.
▼ To specify the server (and client) for a backup operation
1. Choose File > Specify NetBackup Machines and Policy Type.
The Specify NetBackup Machines and Policy Type dialog is displayed.
2. From the Server to use for backups and restores list, select the desired server.
3. From the Source client for restores list, select the desired client.
The source client is the client you wish to back up.
If performing a backup of Exchange in a clustered environment, verify that the virtual
Exchange Server name is selected. If necessary, add the virtual Exchange Server name
to the list and select it.
4. Click OK.
▼ To specify the server, client, and policy type for a restore operation
1. Choose File > Specify NetBackup Machines and Policy Type.
The Specify NetBackup Machines and Policy Type dialog is displayed.
2. From the Server to use for backups and restores list, select the desired server.

Prerequisites for Performing Backups and Restores
3. From the Source client for restores list, select the desired client.
The source client is the Exchange Server machine name whose backup images you
would like to browse.
4. From the Policy Type list, choose MS-Exchange-Server.
5. If you wish to redirect a restore to a different client, select the client to which to
redirect the restore from the Destination clients for restores list.
6. Click OK.
Prerequisites for Performing Backups and Restores

The following services are running on the NetBackup client machine. For mailbox
backups or restores, the services must be running on the Exchange Server that will
perform the backups or to which mailboxes will be restored.
◆ Microsoft Exchange System Attendant (MSEXCHANGESA)
◆ (Exchange 5.x) Microsoft Exchange Directory (MSEXCHANGEDS)
◆ Microsoft Exchange Information Store (MSEXCHANGEIS)
◆ (Exchange 2000) For KMS backups and restores, the Microsoft Exchange Key
Management Service (MSEXCHANGEKMS)
◆ (Exchange 2000/2003) For SRS backups and restores, the Microsoft Exchange Site
Replication Service (MSEXCHANGESRS)
Chapter 4, Operating Instructions 45

Performing User-Directed Backups of Exchange Server

This section contains instructions for performing a backup, from a client, of Exchange 5.5
and Exchange 2000/2003 server objects. Exchange 5.5 users can back up the Information
Store and the Directory. Exchange 2000/2003 users can back up the Information Store,
Storage groups, individual databases, the Key Management Services database, and the
Site Replication Services database.
Note To ensure consistent and accurate backups, always check database consistency
before backing up a database.
Backup Options
The following options are available when performing a backup.
Specify Backup Options dialog box options
Option Description
Backup to NetBackup To change the NetBackup server that will perform the backup
server operation, select another server from the drop-down list.
Items marked to be Contains a list of objects to be backed up.

backed up
Keyword phrase to Specifies a keyword phrase, up to 128 characters in length, that

associate with the NetBackup will associate with the image created by this backup
backup operation. You can then restore the image by specifying the keyword
phrase in the Search Backups dialog box.
All printable characters are permitted including space (“ ”) and period
(“.”). The default keyword phrase is the null (empty) string
Start Backup Initiates the backup operation.
Cancel To cancel and return to the previous display without accepting changes
to the parameters in this dialog box, click this button.
Help To view online help for this dialog box, click this button.

Exchange 5.x
This section describes how to perform a user-directed backup of Exchange 5.x objects.
▼ To perform a user-directed backup of Exchange 5.x objects
1. Open the Backup, Archive, and Restore interface.
2. Choose File > Select Files and Folders to Backup.
The Backup window is displayed.
3. If you are in a cluster environment, specify the name of the virtual Exchange Server as
the client. See “Specifying the Server, Client, and the Policy Type” on page 44 for
details.
4. In the All Folders pane, expand the Exchange Server object.

5. Select the Information Store or Directory objects to back up.
6. Choose Actions > Start Backup of Marked Files.
The Specify Backup Options dialog box is displayed.
7. Click Start Backup.

A dialog box is displayed informing you that the backup was successfully initiated.
8. If you want to view the progress of the backup, click Yes. If you do not want to view
the progress of the backup, click No.
Exchange 2000/2003
This section describes how to perform a user-directed backup of Exchange 2000/2003
objects.
▼ To perform a user-directed backup of Exchange 2000/2003 objects
1. Mount all databases to be backed up.

4. If you are in a cluster environment, specify the name of the Virtual Exchange Server as
the client. See “Specifying the Server, Client, and the Policy Type” on page 44 for
details.
Browsing Exchange 2000/2003 objects

Browsing Exchange objects in a cluster environment
5. In the All Folders pane, select the objects you wish to back up. The following objects
can be backed up.
◆ Storage groups. Expand the Microsoft Information Store node and select the
storage group to back up.
◆ Individual databases. To back up an individual database within a specific storage
group, expand the Microsoft Information Store, then the storage group, and select
the database to back up.
◆ Key Management Services database. Select the KMS node to back up this
database.

◆ Site Replication Services database. Select the SRS node to back up this database.



Restoring Exchange Server

The following sections describe how to restore Exchange Server objects.
◆ Before Performing Restores
◆ Existing Transaction Logs
◆ Restore Options
◆ Restoring Exchange 5.x Server Objects
◆ Restoring Exchange 2003 to the Recovery Storage Group
◆ Restoring Storage Groups or Storage Group Databases
Before Performing Restores

◆ When restoring individual databases or transaction logs, the administrator should
have a thorough working knowledge of Exchange Server databases, transaction logs,
and utilities. If the correct files have not been restored, the Exchange Server will fail to
start.
◆ Do not restore both Microsoft Exchange Mailbox and Microsoft Exchange Server
objects at the same time. Either the restore of the mailbox objects will fail because the
Exchange services are down to perform a restore of Exchange server databases or, if
the restore of the Exchange mailbox items finish before the restore of the Exchange
databases starts, the mailbox objects restored will be overwritten by the restore of the
Exchange databases.
◆ If you are restoring full and incremental backups, you can choose to select all the
backups, restoring all in a single operation, or you can restore the full and incremental
backup individually. If you restore all the backups in a single operation, NetBackup
will perform a commit after the last incremental is restored. If you choose to restore
the backups individually, you will need to select the Commit after restore completes
and Mount database after restore options when restoring the last incremental backup
set.

◆ Make sure the temporary location for log and patch files (Exchange 5.5 or Exchange
2000, pre-Service Pack 1) 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.
Associated log and patch files are kept in the Exchange working directory
(...\exchsrvr\mdbdata) until the database is restored. If storage groups are being
restored, a subdirectory is created under the working directory for each storage
group.
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).
◆ Do not restore the ExIFS drive (M: drive, by default) on the Exchange 2000 server. This
will leave Exchange 2000 in an unstable state.
Existing Transaction Logs

Depending upon the data recovery scenario you are attempting, you have to take existing
transaction logs into consideration.
Example considerations:
◆ Keeping existing transaction logs, overwriting any transaction logs that exist.
After you restore the files and the service starts up, the database will commit the
transactions in the logs you have restored. If contiguous logs exist on the server
beyond the log with the highest number you have restored, those transactions will
also be committed.
If there is any gap in the numeric sequence of log names, no further transactions will
be committed beyond the gap. This scenario is useful when the transaction logs are
intact but you require the database to be restored. By keeping existing transaction
logs, Exchange Server will be able to recover to the point of the failure instead of the
time of the last full backup or an incremental backup (differential incremental backup
or cumulative incremental backup).
◆ Delete the existing transaction logs.
Certain situations—such as restoring the Information Store to a different server,
restoring to a previous date without recommitting all the logs that are still on the disk,
or performing a full restore—require existing transaction logs to be deleted.

Restore Options
The following options are available for redirecting a restore.
Restore Marked Files tab options
Option Description
Restore Destination Choices
Restore everything to its Restores the selected items to the folder from which they were
original location backed up. This is the default.
Restore everything to a Select this option to restore all the selected items to a different
different location location. See “Redirecting Mailbox Objects to a Different Path.”
Destination Enter the path to restore to. This field is enabled when Restore
everything to a different location is selected.
Browse This button is enabled when Restore everything to a different

location is selected. Click this button to open the Browse for Folder
dialog box. You can then select a destination folder.
This feature only browses the system of the local client. If you wish
to restore to an alternate client, see “Redirecting a Restore to a
Different Client” on page 83
Restore individual folders Select this option to restore individual items to different locations.
and files to different See “Redirecting Mailbox Objects to a Different Path.”
locations
Restore Options These options are not available for NetBackup for MS Exchange
Server.
Start Restore Initiates the restore operation.
Cancel To cancel and return to the previous display without accepting

changes to the parameters in this dialog box, click this button.

Microsoft Exchange tab options
Option Description
Delete Existing Allows the user to retain or delete existing transaction logs. See
Transaction Logs Prior “Existing Transaction Logs” on page 53 for further information.
To Restore Transaction logs will be deleted only for the Exchange database being
restored. For Exchange 5.5, If only restoring the Information Store,
transaction logs for the Information Store would be deleted and the
Directory transaction logs will remain intact.
Exchange 2000
Note The following options only apply to Exchange 2000/2003, KMS, and SRS. These options
do not apply when restoring Exchange 5.x objects, mailboxes, or public folders.
Temporary Enter a location where the associated log and patch files are to be
location for log kept until the database is restored. The default location is c:\temp. If
and patch files storage groups are being restored, a subdirectory in c:\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 during restore, 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 Make sure the temporary location for log and patch files is
empty before you start a restore job. If a restore job fails, check
the temporary location (including subdirectories) to make sure
any previous log and patch files from a previous restore job
were deleted.
Commit after Use this option if your selection contains the last backup set to be
restore completes restored. This enables the restore operation to play through 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 restore further backups. You will
need to restart the restore operation from the beginning.
Mount database Mounts the database so that it is available to users. This option is only
after restore available if Commit after restore completes is selected.

Microsoft Exchange tab options
Option Description
Exchange 5.5
Note The following only apply when restoring Exchange 5.5 images backed up by Backup
Exec.
Restore public Select this to restore only the Information Store’s public database
databases (PUB.EDB). Although this database cannot be backed up separately
from the Information Store’s private database (PRIV.EDB), it can be
restored separately.
Restore private Select this to restore only the Information Store’s private database.
mailboxes Although this database cannot be backed up separately from the
Information Store’s public database (PUB.EDB), it can be restored
separately.
Start Restore Initiates the restore operation.
Cancel To cancel and return to the previous display without accepting

changes to the parameters in this dialog box, click this button.
Restoring Exchange 5.x Server Objects

This section contains instructions for restoring Exchange 5.x Server objects.
Notes on Restoring Exchange 5.x Objects Backed Up With Backup Exec

◆ “Copy” backups in Backup Exec appear as “Full” backups in NetBackup.
“Incremental” backups appear as “Differential” backups. “Differential” backups
appear as “Cumulative Incremental” backups.
◆ The backup date will be appended to the Backup Exec Exchange 5.5 Directory and
Information Store file names.
▼ To restore Exchange 5.x Server objects
1. Log on as Administrator.

3. Select the type of restore to perform.

◆ To restore from NetBackup backup images, choose File > Select Files and Folders
to Restore > from Normal Backup.
◆ To restore from Backup Exec backup images, choose File > Select Files and
Folders to Restore > from Backup Exec Backup.
The Restore window is displayed.
4. Select the Exchange policy type (choose File > Specify NetBackup Machines and
Policy Type).
For more details see “Specifying the Server, Client, and the Policy Type” on page 44.
Once you have selected the policy type, NetBackup displays Exchange Server backup
images.
5. From the NetBackup History pane, select the image(s) containing the objects you wish
to restore.
◆ the last full backup, or
◆ the last full backup and all subsequent differential backups, or
◆ the last full backup and the last cumulative backup
Note If you choose to restore the backups individually, you will need to select the
Commit after restore completes and Mount database after restore options when
restoring the last incremental backup set.
6. In the All Folders pane, select the checkbox next to the machine name or Microsoft
Information Store. This will restore the entire content of the selected backup image.
You can also select individual databases that needs to be restored.
Note A full backup of an Exchange database includes the database patch file and the
database transaction log files. When restoring a database, you must, at a minimum,
also restore the database patch file and the transaction log files.

Selecting Exchange 5.x objects to restore
7. Choose Actions > Start Restore of Marked Files.

The Restore Marked Files dialog box is displayed.
For information on the restore options available, see “Restore Options” on page 54.
Note A restore of Exchange Server files will always overwrite existing files (if pub.edb
already exists on the target machine, it will be replaced with the copy from the
backup).
8. Click Start Restore.
9. After a successful restore, restart the Exchange 5.x services.

If not in an Exchange cluster, you can restart the services by rebooting the system or
manually restarting the services through the Control Panel or a batch file.
In an Exchange cluster, use the Control Panel to start the services from the node
owning the Exchange resources. Then, from the Cluster Administrator, bring the
Exchange resources online.

Restoring the Public and Private Databases Separately from a

Backup Exec Image
As with Backup Exec, the public and private databases in Exchange 5.5 can also be
restored separately when using NetBackup.
▼ To restore public and private databases separately from a Backup Exec image
3. Choose File > Select Files and Folders to Restore > from Backup Exec Backup.
Policy Type).
to restore.
6. In the All Folders pane, expand the Microsoft Exchange Server node.
7. Select the Information Store box.

9. At this point, you can choose to restore the public databases or private mailboxes
separately.
◆ To restore the Information Store’s public database, select Restore public
databases.
◆ To restore the Information Store’s private database, select Restore private
mailboxes.
Restoring Exchange 2003 to the Recovery Storage Group

NetBackup supports restores to the recovery storage group. It is not necessary to redirect
the restore; the restore will automatically be restored to the recovery storage group, if it
exists. In order for a restore to the recovery storage group to be successful, the recovery
storage group must be configured prior to performing the restore operation.

Restoring Storage Groups or Storage Group Databases

▼ To restore the Storage Groups, or Storage Group databases
2. Dismount all Exchange 2000/2003 databases that need to be restored.

Policy Type).
images.
Browsing an Exchange 2000/2003 backup image

to restore.
7. In the All Folders pane, select the objects you wish to restore.
storage group to restore. Multiple storage groups should not be selected for
restore. Attempting to restore more than one storage group in a single job, will
cause the restore will fail.
◆ Individual databases. To restore an individual database within a specific storage
group, expand the Microsoft Information Store, then the storage group, and select
the database.
Note A full backup of an Exchange database includes the database transaction log files.
When restoring a database, you must, at a minimum, also restore the transaction log
files.
8. On the Actions > Start Restore of Marked Files.

backup).
10. If you chose to restore storage groups and you did not select Mount database after
restore (after the restore), be sure to mount the storage group databases that were
restored.

Restoring the Key Management Service or Site Replication

Service
▼ To restore the Key Management Service or Site Replication Service
2. Stop the KMS or SRS service.

The KMS service can be stopped using Exchange System Manager; see “Stopping and
Starting KMS” on page 66 for more information. The SRS service can be stopped using
the Services applet in the Control Panel.
Note Before stopping the KMS service, be sure that you have the KMS service password.
3. Delete content of the kmsdata or srsdata directory, located under the default
Exchange Server installation path.
4. Start the KMS or SRS service.
6. Choose File > Select Files and Folders to Restore > from Normal Backup.
Policy Type).
images.
to restore.

◆ To restore the Key Management Services database, select the KMS node.
◆ To restore the Site Replication Services database, select the SRS node.

For information on the restore options available on the Exchange tab, see “Restore
Options” on page 54.
12. If restoring the KMS, stop and start this service.
Stopping and Starting KMS

The following section describes how to stop and start the KMS using the Exchange System
Manager.
Note Before stopping or starting the KMS, be sure that you have the KMS password.

▼ To stop or start the KMS
1. Choose Start > Programs > Microsoft Exchange > System Manager.
2. In the left pane, open the appropriate Administrator Group and click on Advanced
Security.
3. In the right pane, right-click on Key Manager and choose All Tasks, then Stop
Service or Start Service.

Individual Mailbox Operations

This section describes how to perform individual mailbox backup and restore operations.
Notes
◆ The root path of an Exchange Mailbox object (“Microsoft Exchange Mailboxes:”) is
case-sensitive.
◆ Mailbox folders or message subjects containing the characters “~”, “\”, or “/” are
translated as follows:
Character Translation
~ ~0
/ ~1
\ ~2
Performing a User-Directed Mailbox Backup

▼ To perform a user-directed mailbox backup
1. Log onto the server as Administrator.
Note The administrator must have the same Exchange privileges as the NetBackup Client
Service Account. For Exchange 2000/2003, the NetBackup Client Service Account
must also have the advanced privileges “Send As” and “Receive As.” Refer to
“Configuring the NetBackup Client Service Log On Account” on page 16 for more
information about assigning privileges.
2. Open the Backup, Archive, and Restore interface on the Exchange Server.
Policy Type).
If you are in a cluster environment, specify the name of the virtual Exchange Server as
the source client.

5. In the All Folders pane, expand the Microsoft Exchange Mailboxes node.
Browsing Exchange 5.x mailbox objects
Browsing Exchange 2000/2003 mailbox objects

Note For Active/Active configuration of Exchange 2000/2003 in a Microsoft Cluster

Server environment, if more than one instance is running on the same node, the
NetBackup Client GUI will display all mailboxes of all instances running on that
node when browsing for mailboxes, regardless of which virtual server name is
specified.
6. Select the mailbox you wish to back up.

To back up a folder of a specific mailbox, expand the appropriate mailbox and select
the folder that needs to be backed up.
For information on the backup options available, see “Backup Options” on page 46.

A NetBackup message will indicate that the restore was successfully started. Click Yes
if you wish to open the View Status dialog box and view the progress report of the
NetBackup operation.
Restoring Individual Mailboxes, Folders, or Messages

NetBackup can restore individual mailboxes, mailbox folders, or mailbox messages
backed up by NetBackup or Backup Exec.
Notes
◆ When messages in 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 exist in the
destination folder.
For example, if the Inbox folder contained two messages, “Subject A” and “Subject B”,
and the backup image for the Inbox contained the same two messages, after the
restore of backup is completed, the Inbox folder would contain four messages, two for
“Subject A” and two for “Subject B”.
◆ The destination mailbox must exist to successfully restore a mailbox.
◆ When a mailbox is restored, all folders and messages contained in the mailbox are
restored. You can choose to restore specific folders or messages or both from the
mailbox backup image.

◆ When a folder is restored, all subfolders and messages contained in the folder are
restored. You can also choose to restore specific subfolders or messages or both from
the folder backup image.
◆ For Active/Active configuration of Exchange 2000/2003 a in Microsoft Cluster Server
environment, if more than one instance is running on the same node, scheduled
backups using the Mailbox directive only backup all mailboxes on all instances
running on that node, regardless of which virtual server name was specified for
backups.
▼ To restore a mailbox, folder or message

Policy Type).
Once you have specified the policy type, NetBackup displays Exchange Server
backup images.
to restore.

6. In the All Folders pane, select the mailbox, folder, or message to restore.
When selecting objects from the Microsoft Exchange Mailbox tree, all objects are
displayed as folders and 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 identified.
Note Do not restore Microsoft Exchange Mailbox and Microsoft Exchange Server objects
at the same time. Either the restore of the mailbox objects will fail because the
Exchange services are down to perform a restore of Exchange server databases or, if
the restore of the Exchange mailbox items finish before the restore of the Exchange
databases starts, the mailbox objects restored will be wiped out by the restore of the
Exchange databases.

Note The options on the Microsoft Exchange tab do not apply to restores of individual
mailboxes, folders or messages or to restores of Public Folders.

For information on restoring to different locations, see “Redirecting Mailbox Objects
to a Different Path.”
Redirecting Mailbox Objects to a Different Path

NetBackup can restore Exchange mailbox objects from NetBackup and Backup Exec
images to different locations. Following are examples of how mailbox objects are
redirected.
For example, if you back up Mailbox 1, which consists of Top of Information Store, Inbox,
and Folders 1 and 2, each containing some mail messages, and then you restore Mailbox 1
to the existing Mailbox 2, then all of Mailbox 1, including the Top of Information Store,
Inbox, Folders 1 and 2, and messages, are restored to Mailbox 2. Note that Mailbox 1 itself
is not created under Mailbox 2.
Redirecting the restore of Mailbox 1 to Mailbox 2
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.

Redirecting the restore of Folder 2 to Mailbox 2
Requirements
◆ The NetBackup directive Microsoft Exchange Mailboxes:\ of the destination
path cannot be changed. If this is changed, NetBackup will not recognize that this is
an Exchange mailbox or public folder restore and will attempt to restore the objects as
normal files.
◆ If the destination path’s mailbox name is changed from the original, the destination
mailbox or destination folder must already exist and must have an associated user
account.
◆ When redirecting mailbox backups, if the third segment of the destination path is
modified (the Exchange folders “Top of Information Store,” “Views,” “Finder”), the
selected object will be restored to that specified folder name. The new folder can be
seen when browsing for backups and will be backed up on subsequent backups of
that mailbox. However, the folder and any subfolders and messages in that folder
cannot be viewed using Outlook.
▼ To restore a mailbox to a different mailbox
1. In the Backup, Archive, and Restore interface, open a Restore window.
Policy Type).
backup images.
to restore.

4. Select a mailbox to restore.
6. In the Restore Marked Files dialog, select Restore everything to a different location.
7. In the Destination box, change the destination to restore to.

Change the mailbox portion of the Destination field to another existing mailbox to
restore to. For example, if you wish to restore the contents of Mailbox 1 to Mailbox 2,
specify Microsoft Exchange Mailboxes:\Mailbox 2\ in the Destination box.
Note You must indicate an explicit path (or full path) in the Restore everything to a
different location box for this option to be successful.

▼ To restore a mailbox folder to a different location
Policy Type).
backup images.
3. From the NetBackup History pane, select the image(s) containing the folder you wish
to restore.
4. Select a folder to restore.
6. In the Restore Marked Files dialog, select the Restore individual folders and files to
different locations option.
Each row under Restore individual folders and files to different locations is
associated with a selected folder to restore.
7. Double-click on a row to modify the folder destination.
The Enter New Destination dialog is displayed.
8. In the New box, change the destination to restore to.

The destination can be any valid existing Exchange folder path.
9. Click OK.
▼ To restore a mailbox message to a different location
Policy Type).
backup images.

3. From the NetBackup History pane, select the image(s) containing the message you
wish to restore.
4. Select a message to restore.
6. In the Restore Marked Files dialog window, select the Restore individual folders and
files to different locations.
Each row under Restore individual folders and files to different locations is
associated with a selected message to restore.
7. Double-click on a row to modify the message destination.

The Enter New Destination dialog box is displayed.
8. In the New box, change the destination to restore to.

The destination can be any valid existing Exchange folder path.
9. Click OK.

Performing Single Instance Store Backups
Performing Single Instance Store Backups

Exchange Server uses single-instance storage (SIS) to store mail messages. This capability
in Exchange Server allows the database to keep one copy of a message attachment sent to
multiple users on the same server. To perform SIS backups, this feature must be enabled
on the client where Exchange Server is installed.
Note Only attachments larger than 100K are backed up as SIS objects. Attachments
smaller than 100K are backed up with each individual message.
▼ To enable SIS backups
1. Open the NetBackup Administration Console or the Remote Administration Console.
2. In the left pane, expand Host Properties.
3. Click Clients.
4. In the right pane, right-click on the client you wish to configure and choose
Properties.
5. Expand Windows client and click Exchange.

Backing Up and Restoring the Exchange Public Folders
6. Select Enable single instance backup for message attachments.
7. Click OK.

The Public Folders and individual folders within Public Folders can be backed up and
restored like a mailbox. NetBackup needs to be configured for these types of operations
before backups and restores of individual folders in the Public Folders can be performed.
If NetBackup has already been configured for individual mailbox operations, no further
configuration for Public Folders is necessary. If not, refer to “Configuring NetBackup for
Individual Mailbox Operations” on page 16.
Notes
◆ When messages in 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 exist in the
destination folder.
For example, if the Inbox folder contained two messages, “Subject A” and “Subject B”,
and the backup image for the Inbox contained the same two messages, after the
restore of backup is completed, the Inbox folder would contain four messages, two for
“Subject A” and two for “Subject B”.
◆ When a mailbox is restored, all folders and messages contained in the mailbox are
restored. You can choose to restore specific folders or messages or both from the
mailbox backup image.
◆ When a folder is restored, all subfolders and messages contained in the folder are
restored. You can also choose to restore specific subfolders or messages or both from
the folder backup image.

Instructions
▼ To back up or restore Exchange public folders
To perform back ups and restores of Exchange Public folders, follow the instructions in
“Individual Mailbox Operations” on page 68, but select the Microsoft Exchange
Public Folders node or the desired folders within that node.
Selecting items to back up in the Microsoft Exchange Public Folders node.
Selecting items to restore in the Microsoft Exchange Public Folders node.

Redirecting Restores of Public Folders

To redirect restores of public folders, follow the instructions in “Redirecting Mailbox
Objects to a Different Path” on page 73, but select the Microsoft Exchange Public
Folders node or the desired folders within that node.
Note When redirecting a restore of a Public folder, the folder does not have to exist in the
new path.

An Exchange restore can be redirected to a client other than the client that originally
performed the backup. Most Exchange objects that have been backed up can be redirected
to a different client, with the following limitations:
◆ Because the Microsoft Exchange Directory and SRS databases contain machine and
security information, they can only be restored to the original computer or a clone of
the original computer.
◆ The Microsoft Exchange Information Store databases may be restored to a different
Exchange Server.
◆ The following requirements must be met for Exchange 2000/2003 before redirecting
the restore of storage groups or individual databases.
◆ The storage groups and databases must exist on the target server.
◆ The storage groups and databases must have the same names as the original
storage groups or databases.
◆ The target databases must be configured so that they can be overwritten. (Using
the Exchange System Manager, right-click on the database you want to overwrite
and choose Properties. On the Database tab, select This database can be
overwritten by a restore.)
◆ The target server must have the same Organization and Administrative Group
name as the source server.
◆ If redirecting the KMS, this service must be installed on the destination client.

▼ To redirect a restore to a different client
1. Follow the instructions in “Specifying the Server, Client, and the Policy Type” on
page 44to indicate the client you wish to restore to.
2. Continue with the instructions for restoring Exchange Server, Public Folders, or
mailboxes, as described earlier in this chapter.

Using NetBackup for Exchange Server with
Advanced Client 5
NetBackup for Exchange Server Advanced Client combines the features of NetBackup for
Exchange Server with the features of the NetBackup Advanced Client. To use NetBackup
for Exchange Server Advanced Client, you must have both NetBackup for Exchange
Server and NetBackup Advanced Client licensed and installed.
85
NetBackup Advanced Client for Exchange Server Overview

NetBackup Advanced Client, when used in conjunction with NetBackup for Exchange
Server, enables you to back up and restore Exchange objects by taking snapshots of the
component files and then backing up the snapshot version to tape or to the storage unit.
This means capturing the data at a particular instant, without causing significant client
downtime. The resulting capture or snapshot can be backed up without affecting the
performance or availability of the database.
A snapshot is a disk image of the client's data made almost instantaneously. NetBackup
backs up the data from the snapshot volume, not directly from the client’s original
volume. This allows client operations and user access to continue without interruption
during the backup.
Advanced Client supports the Microsoft Volume Shadow Copy Service of Windows 2003
(VSS) for creating a snapshot image. The actual VSS Provider used is dependent on your
hardware and software environment. For a description of VSS providers available for use
with NetBackup for Exchange Server, see the supported platforms matrix on the VERITAS
support site.
Advanced Client for Exchange supports offhost alternate client backups. Alternate client
backups use a second or alternate client to perform the backup on behalf of the primary
client. Compared to local Advanced Client backups, this approach reduces the backup
I/O burden on the primary client.
Supported Platforms
NetBackup Advanced Client for Exchange is only supported for Exchange 2003 on
Windows 2003. A compatibility list for Advanced Client and Database Agents is available
from the VERITAS support web site, as described below.
▼ To access the supported platforms information
1. Go to the VERITAS support web page: www.support.veritas.com.
2. From the Select Product Family list, click NetBackup Products.
3. From the Select Product list in the right pane, click NetBackup Enterprise Server.
4. Under Support Resources, click Compatibility and Reference.
5. In the list of documents, click NetBackup Enterprise Server (tm)/ Server x.x
Advanced Client OS and Database Agent Compatibility (updated date).
For x.x, look for the current release. For date, look for the most recent date.

6. Click on the link for the PDF document, which is a downloadable file that enables you
to view the supported database spreadsheet for this release.
7. Read the document and verify that the software in your environment is compatible
with the NetBackup and NetBackup for Exchange Server software.
Chapter 5, Using NetBackup for Exchange Server with Advanced Client 87

How Does Advanced Client for Exchange Server Work?

This section includes information on how NetBackup for Exchange Server works with the
Advanced Client option.
Choosing a Backup Option

If you want to perform an Advanced Client backup, either automatically through the
master server, or manually from the client, you must configure a NetBackup for Exchange
policy that specifies the appropriate Advanced Client attributes. For details on
configuring policies, see “Configuring an Advanced Client Policy for NetBackup for
Exchange Server” on page 91.
What Is Backed Up?

Advanced Client can back up the Information Store and individual storage groups. The
same files are backed up when using frozen image methodology as when using
non-frozen image backup methods.
When performing Full backups, database files (.edb and .stm files) and transaction log
files are included in the snapshot. User-directed snapshot backups are supported as long
as a User backup type of schedule is included in a policy configured for snapshot backups.
Note For Exchange 2003 pre-Service Pack 1, both full and user-directed backups truncate
log files. Incremental and differential types backups are not supported. For
Exchange 2003 with Service Pack 1, user-directed backups do not truncate logs files
and differential and cumulative backups are supported.
Backup types supported with Advanced Client for Exchange
Exchange 2003 Exchange 2003

pre-Service Pack 1 with Service Pack 1
Supported? Logs Truncated? Supported? Logs Truncated?
Full Yes Yes Yes Yes

Backup Type
User Yes Yes Yes No
Differential No N/A Yes Yes
Cumulative No N/A Yes No

Limitations
The following limitations exist when using NetBackup Advanced Client with NetBackup
for Exchange Server.
◆ Snapshot backups are supported only for the full Information Store or storage groups.
The entire Information Store or a storage group must be selected for backup.
Individual databases cannot be selected for backup (However, individual databases
can be selected for restore).
◆ Snapshot backups are not supported for Exchange mailboxes, the Site Replication
Service (SRS), the Key Management Service (KMS), or public folders.
◆ (Exchange 2003, pre-Service Pack 1) Differential and cumulative backups are not
supported.
◆ Data movers are not supported with offhost backups. Only alternate clients are
supported for offhost backups.
◆ When performing restores, mixing images from Advanced Client and Standard
Exchange backups is not supported.
Consistency Checks on Database and Log Files

For an Exchange VSS backup, Microsoft requires that each database file (.edb, but not
.stm) and each transaction log file required for the restore have a checksum consistency
check run against the files. This consistency check is accomplished by running
eseutil.exe with the proper options against the files which exist on the snapshot. For
alternate client backups, the consistency checks are run on the alternate client rather than
on the primary client.
If any of the files fail the consistency check, the backup will fail, the backup image will be
discarded, and the Exchange VSS Writer will be notified of the failure. When this occurs,
Exchange will not truncate log files.
Failure of the consistency check may be an indication of either database corruption or a
problem with the snapshot. The Exchange administrator should investigate the reason for
the failure by dismounting the Exchange database which caused the failure, and running
eseutil.exe against the database file to determine the cause of the corruption.

Configuring a Snapshot Backup
Before configuring NetBackup for Exchange Server for snapshot backups, review the
configuration requirements and configuration steps in the following two sections.
Instructions for configuring snapshot policies are covered in “Configuring an Advanced
Client Policy for NetBackup for Exchange Server” on page 91.
Configuration Requirements
◆ The hardware and software required for the appropriate snapshot method is installed
and configured correctly. Refer to the NetBackup Advanced Client System Administrator’s
Guide. See the VERITAS Technical Support Web site for details on the snapshot
methods and platforms that are supported for your agent.
◆ NetBackup Advanced Client is installed and configured correctly and the license key
for this option has been registered. Refer to the NetBackup Advanced Client System
Administrator’s Guide for details.
◆ If you wish to perform alternate client backups, perform any special configuration
that is required. See the NetBackup Advanced Client System Administrator’s Guide for
information.
◆ Databases need to be mounted for backup.
Configuration Tips for Exchange

VERITAS recommends the following when configuring Advanced Client for Exchange.
◆ The volume(s) which contains the Exchange databases and log files should be
dedicated to Exchange only. Other types of databases (e.g., SQL) should not reside on
the volume(s). Only Exchange objects will be included in a snapshot backup.
◆ Transaction logs should reside on a different volume than where the Information
Store resides.
◆ (Exchange 2003, pre-Service Pack 1) The Information Store must be configured with
only one database per storage group, since all databases in a storage group must be
restored at the same time prior to the committing the transaction logs and mounting
the databases. Committing transaction logs takes place at a storage group level, rather
than at a database level.

Configuration Steps
In order to perform an Advanced Client for Exchange Server backup, you must perform
the following configuration steps:
❏ Configure an MS-Exchange-Server policy that has the Advanced Client attributes
selected. See “Configuring an Advanced Client Policy for NetBackup for Exchange
Server” on page 91.
❏ Configure the snapshot volumes which will be used during the backup process.
❏ Disable circular logging for all Exchange storage groups.
Configuring an Advanced Client Policy for NetBackup for

Exchange Server
This section only covers what is necessary to configure snapshot backups for a
MS-Exchange-Server policy. For information on other policy attributes, creating
schedules, adding clients, and adding backup selections, see the “Configuration” chapter
earlier in this manual.
▼ To configure an Advanced Client policy
1. Open the policy you wish to configure.
2. Click on the Attributes tab.

3. Select the MS-Exchange-Server policy type.
Select the policy type.
Select the appropriate

storage unit or storage
unit group.
Click Allow
multiple data
streams to divide
backups into
Click Perform snapshot
backups.
(Optional) Click Perform

offhost backup. Select
the alternate client from
the drop-down list, or
type it in.
4. Select a Policy storage unit.
5. Select Perform snapshot backups.
6. Optional: If you wish to use an alternate client to reduce the processing load on the
client, perform the following steps:
a. The alternate client must be the client that shares the disk array. This option may
require additional configuration. Refer to the NetBackup Advanced Client System
Administrator’s Guide.
b. Select Perform offhost backup.

c. Select Use alternate client and enter the name of the alternate client.
Note Use data mover is not a supported option for NetBackup for Exchange Server.
d. Select Advanced Snapshot Options and from the Snapshot method for this
policy list select VSS_Transportable.
7. Optional: If you wish to divide backups into multiple jobs, select Allow multiple data
streams.
8. To configure schedules, click on the Schedules tab.
Note A full or user-directed backup will snap the volumes which contain the Exchange
database, system, and log files. A differential or cumulative incremental backup will
snap the volumes which contain the Exchange system and log files.
9. Use the Clients tab to specify clients to be backed up by this policy.

Refer to the “Configuration” chapter earlier in this manual for details on adding
clients to a policy.
Note For offhost backups, the client name should be the name of the primary client.
10. Use the Backup Selections tab to enter the directives.

When configuring a Exchange snapshot backup policy, only the Exchange 2000
directive set is valid. The only valid directives are Microsoft Information
Store:\ (a storage group can be appended) or NEW_STREAM.
The following are examples of valid entries:
◆ Backup Selections List 1, backs up the Information Store
Microsoft Information Store:\
◆ Backup Selections List 2, backs up only the desired storage groups

Microsoft Information Store:\storage_group_1
11. Click OK to close the dialog.


In order to perform a user-directed snapshot backup, a policy must exist on the server that
is configured for snapshot backups and has a User schedule. The user can back up the
complete Information Store or a storage group. Transaction logs will also be backed up.
Note For Exchange 2003 pre-SP1, a user-directed backup will also truncate the transaction
logs.
▼ To perform a user-directed snapshot backup of Exchange Server objects
1. Mount any databases that will be backed up.
3. To select the Advanced Client policy for this backup operation, choose Actions >
Specify Policy and Schedule. In the Backup Policy box, type the name of the
Advanced Client policy.
5. If you are in a cluster environment, specify the name of the Virtual Exchange Server as
described in “Specifying the Server, Client, and the Policy Type” on page 44.
Browsing Exchange 2003 objects

6. In the All Folders pane, select the objects you wish to back up.
◆ To back up the entire Microsoft Information Store, select this node.
◆ To back up a storage group, expand the Microsoft Information Store, then select
the storage group to back up.
Note Databases cannot be backed up individually. Select only the entire Microsoft
Information Store or individual storage groups. An attempt to backup at the
database level will result in the backup job failing.



Restoring Snapshot Images
This section describes how to restore backups performed with the Advanced Client
feature. Note the following when performing restores:
◆ All databases in a storage group must be dismounted prior to starting a restore.
◆ All of the images selected for restore must be from Advanced Client backups.
The following limitations exist when performing Advanced Client for Exchange restores:
◆ Objects must be restored to the original location from which they were backed up. If
individual databases are restored to a different location (Exchange 2003 SP1),
Exchange will not allow the transaction logs to be rolled forward if the database files
have been moved.
◆ A restore to an Exchange Recovery storage group is not supported.
Restore Options
The following options are available when restoring an Advanced Client backup.
Microsoft Exchange tab options for Advanced Client restores
Option Description
The Delete Existing Allows the user to retain or delete existing transaction logs.
Transaction Logs Prior Transaction logs will be deleted only for the storage group being
To Restore restored.
When restoring a full or user-directed backup, if the user wants to roll
forward all of the transaction log files, including the log files that
exist after the last backup, the user should deselect this option.
Exchange 2003
Temporary Not applicable for restores of snapshots.

location for log
and patch files
Commit after Use this option if your selection contains the last backup set to be
restore completes restored. This enables the restore operation to play through log files
and roll back any uncompleted transactions. If this option is not
selected, the database will need to be mounted manually.
Mount database Mounts the database so that it is available to users. Since committing
after restore after the restore requires that the database be mounted, the database
will be mounted if Commit after restore completes is selected.

Performing a Snapshot Restore

▼ To perform a snapshot restore
2. If restoring storage groups which contain databases, dismount all Exchange
databases.
4. Choose File > Select Files and Folders to Restore > from Normal Backup.
5. Select the Exchange policy type.

images.
6. From the NetBackup History pane, select the image containing the objects you wish to
restore.
◆ (Exchange 2003 without SP1) From a full or user-directed backup, all of the
databases and the log file folder under a storage group must be restored at the
same time. Select the storage group to be restored.
◆ (Exchange 2003 with SP1). From a full or user-directed backup, individual
databases and the log file folder can be selected for restore.

◆ Mixing images from Advanced Client and Standard Exchange backups is not
supported. Select only images which were backed up with Advanced Client.
◆ The Microsoft Information Store. To restore the entire content of the selected
backup image, select the checkbox next to the machine name or Microsoft
Information Store.
storage group to restore.
◆ (Exchange 2003 with SP1) Databases. Expand the storage group and select the
database(s) and log files to be restored.

For information on the restore options available on the Exchange tab, see “Restore
Options” on page 96.
backup). The database files (*.edb and *.stm) will always be overwritten. The log
files will not be overwritten if Delete Existing Transaction Logs Prior To Restore is
not selected.
10. If you chose to restore storage groups and you did not select Commit after restore
completes, be sure to mount the storage group databases that were restored. See the
next section for instructions.
Manually Mounting a Database After a Restore

If you did not choose Commit after restore completes before performing the restore, you
need to manually mount the database after the restore is completed.

▼ To manually mount a database after a restore
1. For the Exchange storage group that was restored, delete the checkpoint file,
E0n.chk, from the System Path folder.
In the absence of a checkpoint file, Exchange Server begins to replay the logs from the
lowest numbered log file that is available in the Transaction Logs folder: the low
anchor log. If the E0n.chk file exists, Exchange Server begins replay at the
checkpoint that is recorded in this file.
2. Mount all of the databases that were restored in the storage group.
3. If the mount fails, attempt a soft recovery (ignoring mismatched database

attachments) of the Exchange databases to bring the databases to a consistent state.
eseutil /r E0n /i
4. Mount the databases again.


A restore of a snapshot backup can be redirected to a different client just as with a
standard backup, though additional limitations apply.
The following additional limitations apply when redirecting a restore of a snapshot
backup. Refer to “Redirecting a Restore to a Different Client” on page 83 for other
limitations of redirecting a restore to a different client.
◆ The log prefix (i.e., E00.log) must be the same for the storage group on the target
server as the original storage group. This may require the user to create temporary
storage groups so that the target storage group has the required log prefix.
◆ The target storage group and databases must have the same path for the Exchange
database, transaction logs, and system files as the original storage group and
databases.
▼ To redirect a restore to a different client
1. Follow the instructions in “Redirecting a Restore to a Different Client” on page 83.
2. If you did not choose Commit after restore completes, manually mount the database
after the restore is completed. See the previous section “Manually Mounting a
Database After a Restore” on page 99.

Troubleshooting 6
This chapter includes details on troubleshooting NetBackup for Exchange Server, locating
instructions for setting up an alternate server for restores, and performing a disaster
recovery of Exchange Server.
103
Troubleshooting NetBackup
The NetBackup master server and client software offers a comprehensive set of debug
logs for troubleshooting problems that may occur during NetBackup operations. Debug
logs are covered in detail in the NetBackup Troubleshooting Guide.
If you are experiencing problems backing up or restoring databases or transaction logs,
and the cause of the problem cannot be determined from standard NetBackup progress
reports, you may enable NetBackup debug logs to aid in determining the cause of the
problem. Debug logging is enabled by creating certain folders under the NetBackup Logs
folder.
Debug Logging
Debug logging is available for both backup and restore operations. You can control the
amount information written to debug logs by following the instructions in “Changing the
Debug Level” on page 105.
For details on the contents of these debug logs, refer to the NetBackup Troubleshooting
Guide. After the cause of the problem has been determined, debug logging can be disabled
by removing the previously created debug logging folders.
Note When debug logging is enabled, the files can become large. The same files are used
by normal file backups.
Backup Operation Debug Logging

To turn on debug logging for standard backup operations, create the following folder.
install_path\NetBackup\logs\bpbkar
For snapshot backups, create the following directories. For backups performed by an
alternate client, the bpfis log exists on the alternate client and the primary client;
bpbkar only exists on the alernate client.
install_path\NetBackup\logs\bpbkar
install_path\netbackup\logs\bpfis
install_path\netbackup\logs\tar
After creating these directories and performing a backup, debug logging information will
be placed in the directory in a file named mmddyy.log.

Restore Operation Debug Logging

To turn on debug logging for restore operations, create the following folder. For all
Exchange restores, tar logs exist on the primary client.
install_path\NetBackup\logs\tar
To troubleshoot restores from Advanced Client backup (local and transportable), create
the following directory. For alternate client backups, bpfis logs exist on both the primary
and alternate clients.
install_path\netbackup\logs\bpfis
After creating these directories and performing a restore, debug logging information will
be placed in the directory in a file named mmddyy.log.
Changing the Debug Level

You can control the amount of information written to the bpbkar, tar, and
bpfis debug logs by changing the General debug level debug level. The higher
the value, the more information is logged. In everyday normal operations, the default
value of 0 is sufficient. However, VERITAS technical support may ask you to set the value
higher when a problem is being analyzed.
▼ To change the Debug Level
1. Choose Start > Programs > VERITAS NetBackup > Backup, Archive, and Restore.
The Backup, Archive, and Restore - NetBackup window appears.
2. Choose File > NetBackup Client Properties.
3. Click the Troubleshooting tab.
By default, the settings are zero.
4. Set the General debug level debug level.
5. Click OK to save your changes.
Chapter 6, Troubleshooting 105

Verifying Exchange Online Backups

To verify that the Exchange Server online backup contains a usable copy of the database,
perform the following steps:
1. Perform an online backup.
2. Set up a test server and restore the backup.
3. Stop the Exchange services.
4. (Exchange 5.5 only) Perform an integrity check of the databases and verify that no
errors are reported when you run the following commands:
a. Eseutil /g /ispriv
b. Eseutil /g /ispub
c. Eseutil /g /ds
5. Restart the Exchange services.
If the services start at this point, the database is usable and contains no errors.
Viewing the Status of a NetBackup Operation

NetBackup provides many standard status reports to verify the completion of backup and
restore operations. In addition, users and the administrator can set up additional reports if
a site requires them.
Operational Reports
The administrator has access to operational progress reports through the NetBackup
Administration Console. Reports may be generated for Status of Backups, Client Backups,
Problems, All Log Entries, Media Lists, Media Contents, Images on Media, Media Logs,
Media Summary, and Media Written. These reports may be generated for a specific time
frame, client, or master server. Refer to NetBackup System Administrator’s Guide, Volume I
for details.

Progress Reports
Progress reports on the client allow easy monitoring of user operations. When reports are
created by the NetBackup client for each user-directed backup or restore operation,
administrators can monitor these operations and detect any problems that may occur.
▼ To view the status of an operation
1. Choose File > View Status.
2. Click on the task for which you want to check the progress.
3. Click Refresh.
The status of the operation is displayed in the lower pane.
When the requested operation was successfully completed message
appears, the NetBackup operation is finished. (See your NetBackup Backup, Archive, and
Restore Getting Started Guide for further information on the progress report and the
meanings of the messages.)
Transaction Logs
Transaction logs are deleted by the Exchange server after a successful backup (for full and
differential backup types). If there are any errors encountered by the Exchange server
during the deletion process, the NetBackup for Exchange agent will log this information.
Since the actual backup was successful, NetBackup will exit with a status 0 (successful
backup). Refer to the Microsoft Exchange Server documentation for information on any
errors encountered with the transaction logs.

Setting Up an Alternate Server for Restores
Setting Up an Alternate Server for Restores

An alternate server can be used to recover an Exchange database in order to extract
mailbox or Public folder data. The following technotes cover how to configure an
alternate server for restore operations.
Exchange 2000/2003
TechNote 264924, http://library.veritas.com/docs/264924
Exchange 5.5
TechNotes 188501, http://support.veritas.com/docs/188501

Disaster Recovery of Exchange 5.5
Disaster Recovery of Exchange 5.5

This section describes what is necessary to perform a full server recovery of Exchange 5.5.
▼ To recover Exchange 5.5
1. Install Exchange Server on the alternate server and create a new site.
Caution Do not attempt to join an existing site. Give the server its original organization
and site name (Org:xxx, Site:xxxxx or xxxxx).
2. Run the Performance Optimizer and select the appropriate locations for the files.
3. Check the working path for the Directory and Information Store. This is set on the
Database Path property page for the server object set for the D: drive.
4. Install Microsoft Outlook Client on the alternate server.
5. Perform a full restore, which will include the Directory, Information Store and the
transaction logs/patch files from the latest tape backup.
6. Start all Exchange services. Start the System Attendant first, then the Directory, IS,
MTA and Event Services.
7. Review the Event Viewer for any errors.
8. Run a DS/IS Consistency Adjustment (from the Server properties, choose Advanced).
9. To verify that your users’ mailboxes have a Windows account associated with them,
follow these steps.
a. In Microsoft Exchange Administrator, select a server, and choose Recipients.
b. Double-click a user’s name.
c. Review the Primary Windows NT Account box to verify that the Windows
account matches the mailbox. Repeat this procedure as needed for each user.

Disaster Recovery of Exchange 2000/2003
▼ To test a user's logon from a client workstation

To test a user’s logon from a Microsoft Outlook Client workstation, perform these steps.
1. Start the Microsoft Outlook Client.
2. Verify that the user’s password is accepted.
3. Confirm that the data has been restored.
Disaster Recovery of Exchange 2000/2003

This section describes what is necessary to perform a full server recovery of Exchange
2000/2003. For detailed information about Exchange 2000/2003 disaster recovery, refer to
the Microsoft Exchange 2000/2003 Database recovery white paper at
http://www.microsoft.com/exchange.
The following are required before an Exchange 2000/2003 restoration can be performed:
◆ If the Exchange 2000/2003 server you are restoring is a member server in a domain,
the Active Directory must be running. If Active Directory does not exist, you must
restore it before restoring Exchange 2000/2003.
◆ If the Exchange 2000/2003 server you are restoring is a domain controller, you must
restore Active Directory on the machine before you can restore Exchange 2000/2003.
▼ To recover Exchange 2000/2003
1. Install Windows 2000/2003 on the new or repaired server.
2. Restore the IIS Metabase.
3. Restore Exchange 2000/2003.
4. Restore the Information Stores.
5. If you have KMS or SRS, these have to be restored independently of an Exchange

2000/2003 server restore.
6. If you have KMS, restore the Certificate of Authority. The CA can be restored from a
backup of the system_state of the server.

Index
A browsing for Exchange objects 32
accessibility features xii
C
Advanced Client
circular logging, and incremental

backup limitations 89
backups 29
what is backed up 88
Clients list 31
alternate client backups 92
clusters, performing backups in 44
automatic backups
Commit after restore completes 55
Exchange 2000/2003 databases 7
compatibility information 12
Exchange 5.x databases 6
configuration
B database debug level 105
Backup Selections list

for individual mailbox and folder
adding by browsing 32
operations 16–22
example entries 35
for public folder operations 16–22
backup types 28–29 Media Manager 13
backups
cumulative incremental backups 29
alternate client 92
D
and mounting Exchange 2000/2003
database circular logging, and incremental

databases 48
backups 29
automatic, described 5
database patch files 7, 9
in a cluster 44
debug logs 104
manual 41
for backup operations 104
manual, described 5
for restore operations 105
of mailboxes 68
Delete existing transaction logs prior to
of Public folders 81
restore 55, 96
services which must be running 45
differential incremental backups 28, 29
Single Instance Store (SIS) 80
directives
snapshot 90
for Exchange 2000/2003 databases 7
user-directed
for Exchange 5.x databases 6
and cluster environments 47, 49
mixing directive sets 32
Exchange Public Folders 81
mailboxes 68
E
of Exchange 2000/2003 objects 48
e0y.log 8
of Exchange 5.x objects 47

edb.log 8
snapshot 94
Exchange Public Share, backing up and
user-directed, described 6
restoring 81
bpbkar log 104

excluding folders and files from mailbox
bpfis log 104, 105

and public folder backups 39
111
F P
files backed up
patch files
Exchange 2000/2003 databases 7

how applied after restore 53
Exchange 5.x databases 6

where kept until database restored 53
full backups 9, 28
permissions
for restores 23
required for mailbox operations 18
incremental backups, objects backed up 29
platform compatibility 12
installation
policy configuration
compatibility information 12
adding clients 31
operating system compatibility 12
adding new 24
platform compatibility 12
attributes 25
prerequisites 12
overview 24
prerequisites in a cluster 13
schedules 26
registering the license key 14
specifying objects to back up 32
requirements for NetBackup software 13
testing 41
J progress reports 107
Java interface 15
client 107
K public folders operations
Key Management Services (KMS)

configuring NetBackup for 16–22
restores of 65
excluding folders and files from
user-directed backup of 50
backups 39
L R
license keys, registering 14
recovery
log files
and cumulative-incremental backups 29
how applied after a restore 53

and differential-incremental backups 28
where kept until database restored 53

recovery storage group 61
logs
redirected restores
debug 104
of mailbox objects, to different paths 73
to different clients 10, 44, 83
M to different clients, requirements for
mailboxes
Exchange 2000/2003 83
configuring NetBackup for backups and

to different paths 10
restores of 16–22
reports
excluding folders and files from

client 107
backups 39
media 106
permissions required for backing up and

operational 106
restoring 18
progress 107
Media Manager Restore private mailboxes 56
configuring backup media 13

Restore public databases 56
Mount database after restore 55

restores
Mount database after restore 96

advanced client backups 97
multiple data streams 36

and existing transaction logs 53
N Backup Exec 56
NetBackup for Microsoft Exchange database

Exchange 2000/2003 database 63
agent features 2
Exchange 5.x 56
failure of 53
O Key Management Service (KMS) 65
operating system compatibility 12
112
NetBackup for Microsoft Exchange Server System Administrator’s Guide
mailbox message to a different
T
message 77
tar log 104, 105
mailbox objects to different paths 73

temporary location for log and patch files 55,
mailbox to a different mailbox 74

96
mailboxes, folders, messages 70

testing policy configuration 41
permissions 23
transaction logs
public folders 81
and cumulative-incremental backups 29
redirected, to different client 10, 83

and differential-incremental backups 28
redirected, to different locations 74

deleting 53
requirements for Exchange 2000/2003 62

deleting prior to a restore 55, 96
services which must be running 45

keeping 53
Site Replication Service (SRS) 65

troubleshooting 104
storage group databases 62
U
storage groups 62
Use alternate client 93
retention period 30
user backups 28
S
V
schedules
virtual Exchange Server, specifying 44
adding 26
frequency 30
W
properties 29
wildcard characters
retention 30
rules when using 38
Single Instance Store (SIS) backups 80

supported 37
Site Replication Service (SRS)

used to define groups of objects 37
restores of 65
Windows interface 15
user-directed backup of 51
Index 113

NetBackup AdminGuide MSExchg Win

Hochgeladen von

Dokumentinformationen

Copyright

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

NetBackup AdminGuide MSExchg Win

Hochgeladen von

Copyright:

VERITAS NetBackup™ 6.

Microsoft Exchange Server

System Administrator’s Guide

VERITAS Legal Notice

ii NetBackup for Microsoft Exchange Server System Administrator’s Guide

Finding NetBackup Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Accessing the VERITAS Technical Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . x

Contacting VERITAS Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii

Related Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii

Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii

Comment on the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1. Introduction to NetBackup for Exchange Server . . . . . . . . . . . . . . . . . . . . 1

Exchange Server Files That are Backed Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Database Patch Files (Exchange 5.5 or pre-Exchange 2000, Service Pack 2) . . . . 7

Limitations with Exchange 2000/2003 Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Redirecting a Restore to a Different Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Installation Requirements and Registering a License Key . . . . . . . . . . 11

Verifying the Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Operating System and Platform Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Registering the License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

User Interface Terminology Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring NetBackup for Individual Mailbox Operations . . . . . . . . . . . . . . . . . . . . . 16

Configuring the NetBackup Client Service Log On Account . . . . . . . . . . . . . . . . . . 16

Creating a Mailbox for the NetBackup Client Service . . . . . . . . . . . . . . . . . . . . . . . . 17

Granting the NetBackup Client Service Account Advanced Permission . . . . . 19

Configuring NetBackup to Use the Mailbox Associated with the NetBackup

Client Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Configuring the Account Used for Exchange Server Restores . . . . . . . . . . . . . . . . . . . . 23

Configuring Backup Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Adding a New Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Adding Backup Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

iv NetBackup for Microsoft Exchange Server System Administrator’s Guide

Manually Adding Entries to the Backup Selections list . . . . . . . . . . . . . . . . . . . . 33

Example Entries in the Backup Selections List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Performing Backups with Multiple Data Streams . . . . . . . . . . . . . . . . . . . . . . . . . 36

Testing Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4. Operating Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Specifying the Server, Client, and the Policy Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Prerequisites for Performing Backups and Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Performing User-Directed Backups of Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . 46

Restoring Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Before Performing Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Existing Transaction Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Restoring Exchange 5.x Server Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Restoring the Public and Private Databases Separately from a

Backup Exec Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Restoring Exchange 2003 to the Recovery Storage Group . . . . . . . . . . . . . . . . . . . . . 61

Restoring Storage Groups or Storage Group Databases . . . . . . . . . . . . . . . . . . . . . . 62

Restoring the Key Management Service or Site Replication Service . . . . . . . . . . . . 65

Stopping and Starting KMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Individual Mailbox Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Performing a User-Directed Mailbox Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Restoring Individual Mailboxes, Folders, or Messages . . . . . . . . . . . . . . . . . . . . . . . 70

Redirecting Mailbox Objects to a Different Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Performing Single Instance Store Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Redirecting Restores of Public Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Redirecting a Restore to a Different Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 5. Using NetBackup for Exchange Server with Advanced Client . . . . . . . 85

NetBackup Advanced Client for Exchange Server Overview . . . . . . . . . . . . . . . . . . . . 86

How Does Advanced Client for Exchange Server Work? . . . . . . . . . . . . . . . . . . . . . . . . 88

Choosing a Backup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

What Is Backed Up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Consistency Checks on Database and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring a Snapshot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configuration Tips for Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Configuring an Advanced Client Policy for NetBackup for Exchange Server . . . . 91

Performing User-Directed Backups of Exchange Server . . . . . . . . . . . . . . . . . . . . . . . . . 94