NetBackup AdminGuide MSExchg Win 6.5.4 320793 PDF

Veritas NetBackup for
Microsoft Exchange Server

Administrators Guide
Release 6.5.4
Veritas NetBackup for Microsoft Exchange Server

Administrator's Guide
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Documentation version 6.5.4
Legal Notice
Copyright 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, and NetBackup are trademarks or registered trademarks of
Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is required
to provide attribution to the third party (Third Party Programs). Some of the Third Party
Programs are available under open source or free software licenses. The License Agreement
accompanying the Software does not alter any rights or obligations you may have under
those open source or free software licenses. Please see the Third Party Legal Notice Appendix
to this Documentation or TPIP ReadMe File accompanying this Symantec product for more
information on the Third Party Programs.
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.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Supports primary role is to respond to specific queries about product features
and functionality. The Technical Support group also creates content for our online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. For example, the Technical Support group works with Product Engineering
and Symantec Security Response to provide alerting services and virus definition
updates.
Symantecs maintenance offerings include the following:
A range of support options that give you the flexibility to select the right
amount of service for any size organization
Telephone and Web-based support that provides rapid response and

up-to-the-minute information
Upgrade assurance that delivers automatic software upgrade protection
Global support that is available 24 hours a day, 7 days a week
Advanced features, including Account Management Services
For information about Symantecs Maintenance Programs, you can visit our Web
site at the following URL:
www.symantec.com/techsupp/
Contacting Technical Support

Customers with a current maintenance agreement may access Technical Support
information at the following URL:
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
Product release level
Hardware information
Available memory, disk space, and NIC information
Operating system
Version and patch level
Network topology
Router, gateway, and IP address information
Problem description:
Error messages and log files
Troubleshooting that was performed before contacting Symantec
Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
Customer service
Customer service information is available at the following URL:
Customer Service is available to assist with the following types of issues:
Questions regarding product licensing or serialization
Product registration updates, such as address or name changes
General product information (features, language availability, local dealers)
Latest information about product updates and upgrades
Information about upgrade assurance and maintenance contracts
Information about the Symantec Buying Programs
Advice about Symantec's technical support options
Nontechnical presales questions
Issues that are related to CD-ROMs or manuals
Maintenance agreement resources

If you want to contact Symantec regarding an existing maintenance agreement,
please contact the maintenance agreement administration team for your region
as follows:
Asia-Pacific and Japan
contractsadmin@symantec.com
Europe, Middle-East, and Africa
semea@symantec.com
North America and Latin America
supportsolutions@symantec.com
Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and
global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat
analysis, and countermeasures to prevent attacks before they occur.
Managed Security Services
These services remove the burden of managing and monitoring security devices
and events, ensuring rapid response to real threats.
Consulting Services
Symantec Consulting Services provide on-site technical expertise from

Symantec and its trusted partners. Symantec Consulting Services offer a variety
of prepackaged and customizable options that include assessment, design,
implementation, monitoring, and management capabilities. Each is focused on
establishing and maintaining the integrity and availability of your IT resources.
Educational Services
Educational Services provide a full array of technical training, security

education, security certification, and awareness communication programs.
To access more information about Enterprise services, please visit our Web site
at the following URL:
www.symantec.com
Select your country or language from the site index.
Contents
Technical Support ............................................................................................... 4

Chapter 1
Introduction to NetBackup for Exchange

Server ............................................................................... 13
About NetBackup for Exchange Server .............................................
About NetBackup for Exchange features ...........................................
About backup operations ...............................................................
About automatic backups ........................................................
About manual backups ............................................................
About user-directed backups ....................................................
About the Exchange Server files that are backed up ......................
About backups and transaction logs ..........................................
About restore operations ...............................................................
About server-directed restores .................................................
About redirecting a restore to a different path .............................
About redirecting a restore to a different client ...........................
Chapter 2
13
13
17
17
17
17
17
19
20
21
21
21
Installing NetBackup for Exchange Server .................... 23

About installing the NetBackup for Exchange agent ...........................
Verifying the operating system and platform compatibility for
NetBackup for Exchange .........................................................
About NetBackup server and client software requirements for
NetBackup for Exchange ...................................................
About the database software requirements for NetBackup for
Exchange ........................................................................
About installation requirements for restores of individual
Exchange Server items using Granular Recovery Technology
(GRT) .............................................................................
About the requirements for installing NetBackup for Exchange
in a NetBackup cluster ......................................................
About configuration and licensing requirements for NetBackup
for Exchange with Snapshot Client ......................................
About requirements for Exchange 2007 off-host backups ..............
Adding the NetBackup for Exchange license key ................................
23
24
24
25
26
26
27
27
28
Contents
Chapter 3
Installing and configuring NFS for Exchange

Granular Recovery ......................................................... 29
About installing and configuring Network File System (NFS) for
Exchange Server Granular Recovery ..........................................
About requirements to perform backups and restores with Granular
Recovery Technology (GRT) .....................................................
About supported media server platforms for the jobs that use Granular
Recovery Technology (GRT) .....................................................
About supported Exchange Server configurations for the backups
that use Granular Recovery Technology (GRT) ............................
About configuring Services for Network File System (NFS) on the
Windows 2008 NetBackup media server and NetBackup
clients ..................................................................................
Enabling Services for Network File System (NFS) on Windows
2008 ..............................................................................
Disabling the Client for NFS on the media server .........................
Disabling the Server for NFS ....................................................
About configuring Services for Network File System (NFS) on the
Windows 2003 R2 SP2 NetBackup media server and NetBackup
clients ..................................................................................
Installing Services for NFS on the Windows 2003 R2 SP2 media
server ............................................................................
Installing Services for NFS on Exchange granular clients with
Windows 2003 R2 SP2 .......................................................
About configuring a UNIX or Linux media server and Windows clients
for backups and restores that use Granular Recovery
Technology ...........................................................................
Configuring a different network port for NBFSD ................................
Chapter 4
30
30
32
32
33
34
37
38
40
41
44
47
47
Configuring NetBackup for Exchange Server ................ 49

About user interface terminology ....................................................
About configuring NetBackup for backups and restores of individual
mailboxes and public folders ....................................................
About the NetBackup service account ........................................
Configuring the log on account for the NetBackup Client
Service ...........................................................................
Configuring NetBackup to use the mailbox that is associated with
the NetBackup Client Service account ..................................
About configuring backups that use Granular Recovery Technology
(GRT) ...................................................................................
About limitations and conditions for restores using Granular
Recovery Technology (GRT) ...............................................
49
50
50
53
54
55
55
Contents
Configuring the granular proxy server .......................................

About client and proxy server privileges for granular
operations ......................................................................
Configuring client privileges for the operations that use Granular
Disabling the cataloging for duplications of Exchange backups
using Granular Recovery Technology (GRT) ..........................
Configuring streaming mailbox backups with Single Instance
Store ....................................................................................
About configuring a backup policy for an Exchange database ...............
About disk storage units supported for restores using Granular
Policy recommendations for Exchange Server .............................
Adding a new policy ................................................................
About policy attributes ............................................................
Adding schedules to a NetBackup for Exchange policy ..................
About the types of Exchange backups ........................................
About schedule properties .......................................................
Adding clients .......................................................................
Adding backup selections to an Exchange policy ..........................
Testing configuration settings ........................................................
Chapter 5
56
57
58
59
60
61
62
62
63
64
65
66
68
68
70
78
Performing backups and restores of Exchange

Server and Exchange mailboxes ................................ 79
Specifying the server and client for a Exchange Server backup
operation ..............................................................................
Specifying the server, client, and the policy type for a Exchange Server
restore operation ...................................................................
Backup options ............................................................................
Performing user-directed backups of Exchange Server ........................
Performing copy backups ..............................................................
Prerequisites for performing Exchange mailbox backups and
restores ................................................................................
About Active/Active configurations .................................................
About special characters in mailbox folders and message
subjects ................................................................................
Performing user-directed backups of mailboxes and public
folders .................................................................................
About restoring Exchange Server ....................................................
Before you perform restores of Exchange Server ..........................
About existing transaction logs ................................................
80
81
81
82
83
84
84
85
85
87
87
88
10
Contents
Restore options for standard restores of Exchange

databases ....................................................................... 88
Restoring storage groups or storage group databases .................... 90
Restoring the Key Management Service or Site Replication
Service ........................................................................... 93
Stopping and starting KMS ...................................................... 94
Restoring an Exchange 2007 or Exchange 2003 streaming (non
VSS) backup to a recovery storage group .............................. 95
Manually mounting a database after a restore ............................. 98
Prerequisites for restoring Exchange individual mailboxes, mailbox
folders, public folders, or messages ........................................... 98
Restore options for Exchange Server mailbox restores ........................ 99
Restoring mailbox or public folder objects ....................................... 100
About redirecting a restore of mailbox objects or public folders to a
different path ...................................................................... 103
About requirements for redirecting the restore of an Exchange
mailbox or public folder object to a different path ................. 104
Examples of redirecting an Exchange mailbox restore ................. 105
Redirecting the restore of a mailbox, mailbox folder, or public
folder ........................................................................... 105
Redirecting a restore of a mailbox message or public folder
document to a different folder .......................................... 106
Redirecting a restore to a different client ........................................ 108
About using the command line to browse or restore granular backup
images ................................................................................ 109
Chapter 6
Using NetBackup for Exchange Server with

Snapshot Client ............................................................ 111
About the NetBackup Snapshot Client for Exchange Server ................
About supported platforms for NetBackup for Exchange with
Snapshot Client ..............................................................
About limitations of using NetBackup Snapshot Client for
Exchange Server ............................................................
How does Snapshot Client for Exchange Server work? .......................
What is backed up? ...............................................................
About consistency checks on database and log files ....................
Configuring an Exchange 2007 replication backup ............................
How to optimize Exchange CCR backups when the cluster is also setup
as a SAN media server ...........................................................
About configuring snapshot backups of Exchange Server ...................
About configuration requirements for snapshot backups of
Exchange Server ............................................................
112
113
113
114
114
115
116
117
118
118
Contents
About configuration requirements for the Exchange Server ......... 119

Configuring a pause in consistency checks ................................ 119
Backing up transaction log files ............................................... 120
Configuring a Snapshot Client policy ....................................... 121
About instant recovery backups of Exchange Server ......................... 124
About instant recovery methods ............................................. 124
Truncating Exchange transaction logs with instant recovery
backups ........................................................................ 125
Limitations for instant recovery operations ............................... 126
Operational notes for instant recovery operations ...................... 127
About configuring instant recovery backups of Exchange Server ......... 127
About configuration requirements for the Exchange Server when
you use instant recovery .................................................. 127
About instant recovery with the Microsoft System Provider ......... 128
Configuring a Snapshot Client policy with instant recovery .......... 128
Configuring off-host backups ........................................................ 135
Performing user-directed snapshot backups of Exchange Server ......... 136
About restoring snapshot images .................................................. 137
Restore options for Snapshot Client restores ............................. 137
Performing a snapshot restore ................................................ 138
Recovering an Exchange 2007 Local Continuous Replication (LCR)
environment ....................................................................... 140
Recovering an Exchange 2007 Clustered Continuous Replication (CCR)
environment ....................................................................... 141
Redirecting an Exchange 2007 VSS backup to a storage group or the
recovery storage group when a storage group has one
database ............................................................................. 142
Redirecting an Exchange 2007 VSS backup to a storage group or the
recovery storage group when a storage group has more than one
database ............................................................................. 144
About redirecting restores of Exchange 2003 VSS backup
images ................................................................................ 148
Redirecting a restore of a snapshot to a different client ..................... 148
Chapter 7
Disaster Recovery of Exchange Server .......................... 149

About configuring an alternate server for restores ........................... 149
Disaster recovery of Exchange Server 2007 ..................................... 149
Disaster recovery of Exchange Server 2000/2003 ............................. 149
Chapter 8
Troubleshooting NetBackup for Exchange ................... 151

About troubleshooting ................................................................ 151
About debug logging ................................................................... 152
11
12
Contents
About backup operation debug logging .....................................

About restore operation debug logging .....................................
Setting the debug level on a Windows client ..............................
Verifying Exchange online backups ...............................................
Viewing Event Viewer logs on an off-host server ..............................
Connecting to the remote server from within Event Viewer ..........
About installing the Exchange System Management Tools on the
remote server ................................................................
About NetBackup status reports ....................................................
About operational reports ......................................................
About progress reports ..........................................................
Viewing the status of a NetBackup operation .............................
About Exchange Server transaction log errors .................................
Troubleshooting LCR or CCR recovery ............................................
Troubleshooting a status 5 error with bprestore ...............................
Dynamic enforcement of path length limit ......................................
Troubleshooting snapshot operations ............................................
About troubleshooting jobs that use Granular Recovery Technology
(GRT) .................................................................................
About concurrent restore of multiple storage groups ........................
152
153
153
154
154
155
155
155
156
156
156
156
157
157
157
157
158
159
Index ................................................................................................................... 161
Chapter
Introduction to NetBackup
for Exchange Server
This chapter includes the following topics:
About NetBackup for Exchange Server
About NetBackup for Exchange features
About backup operations
About restore operations
About NetBackup for Exchange Server

NetBackup for Microsoft Exchange Server extends the capabilities of NetBackup
to include online backups and restores of Exchange databases when Exchange
Server is 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, this topic 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
topic.
Microsoft Exchange Server is referred to as Exchange Server or Exchange.
NetBackup for Microsoft Exchange Server is referred to as NetBackup for Exchange
Server.

Table 1-1 describes the features of the NetBackup for Exchange Server agent.
14
Introduction to NetBackup for Exchange Server

Table 1-1
NetBackup for Exchange Server features
Feature
Description
Online backups
Exchange Server data and transaction logs can be backed up without taking the Exchange
Server offline. Exchange services and data remain available during the Exchange Server
backup.
Minimal backup time
An administrator has the choice of to perform 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, any updates that occurred since
the full backup can be quickly and incrementally backed up through a transaction log
backup. In the event of a failure, the full backups and incremental backups would be restored.
During recovery, the Exchange Server updates the databases and applies each of the logged
transactions to the database. After the Exchange Server recovery completes, the system is
brought back to the state as it existed when the last incremental backup was performed.
Exchange Server
Backup methods
NetBackup supports all Exchange Server backup methods: full backups, cumulative
incremental backups, and differential incremental backups. User backups function as copy
backups.
Tight NetBackup
integration
Tight integration with NetBackup allows for the following:

An administrator already familiar with NetBackup procedures and software can easily
configure and use NetBackup to perform Exchange Server backup and restore operations.
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, backups of multiple data streams, and in-line
tape copy.
For details about these features see the NetBackup Administrators Guide, Volume I.
Central administration Administrators can define, back up, and restore Exchange Servers and other NetBackup
client computers from a central location.
Media management
Exchange Server backups can be saved directly to a wide variety of storage devices that the
NetBackup master server supports.
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 the clients.
Restore operations
An administrator using the Backup, Archive, and Restore interface can browse backups
and select the ones to be restored.

Table 1-1
NetBackup for Exchange Server features (continued)
Feature
Description
Exchange backup and

restore features
NetBackup can back up and restore storage groups and databases within the storage group.
The capabilities of this feature are as follows:
Scheduled backups of individual storage groups and databases
User-directed backups of individual storage groups and databases
Restores of individual storage groups and databases.These restores can be performed

with the Backup, Archive, and Restore interface (on the server or on the client). Or you
can use the Remote Administration Console for Windows or UNIX.
(Exchange 2000) NetBackup can perform backups and restores of the Exchange Key
Management Server (KMS)
(Exchange 2000/2003) Exchange Site Replication Service (SRS) databases.
Individual mailbox
backup and restore
Administrators can perform backup and restore operations on individual mailboxes and
folders.
The capabilities of this feature are as follows:
Scheduled backups of individual mailboxes and folders
User-directed backups of individual mailboxes and folders
Restores of individual mailboxes, folders, or messages. You can perform this type of
restore with the Backup, Archive, and Restore interface (on the server or on the client).
Or you can use the Remote Administration Console for Windows or UNIX.
Backup and restore of NetBackup can back up and restore the Exchange Public Store. The capabilities of this
the Exchange Public
feature are as follows:
Store
Scheduled backups of individual folders
Restores of individual
items using Granular
Recovery Technology
(GRT)
User-directed backups of individual folders
Restores of individual folders or messages. You can perform this type of restore can
with the Backup, Archive, and Restore interface (on the server or on the client). Or you
can use the Remote Administration Console for Windows or UNIX.
When a backup uses GRT, users can restore individual items directly from any full database
backup. This backup can include the Microsoft Information Store, a storage group, or a
database. This feature adds an extra step that identifies the items within the database. This
step lets you recover individual items instead of recovering the whole database or storage
group.
You can restore individual items using GRT from the following types of backups:
Full or User backups
Incremental backups are not yet supported.
Local VSS snapshot database backups
Off-host VSS snapshot backups
VSS replica snapshot backups (LCR or CCR on Exchange 2007 only)
15
16

Table 1-1
NetBackup for Exchange Server features (continued)
Feature
Description
Exchange 2007
enhancements to
consistency checks of
snapshot backups
For snapshot backups, NetBackup uses the Microsoft API to check the consistency of
databases and transaction logs and to provide additional details. This speeds up a VSS
backup, because it allows the backup to proceed in parallel with the consistency check.
Redirected restores of You can restore mailboxes, mailbox folders, public folders, or mailbox messages to a new
mailbox objects
location.
Redirected restores of Exchange 2007 VSS backups can be restored to another storage group on the local server
storage groups
or on a different server. Exchange 2003 VSS backups can be restored to an identical storage
group on a different server.
Redirection to the
Streaming backups of Exchange 2003 and later storage groups can be redirected to the
recovery storage group RSG. Exchange 2007 VSS backups can also be redirected to the RSG.
(RSG)
Single Instance
Storage (SIS) of
mailbox message
attachments
Users can enable Single Instance Storage for message attachments so that NetBackup writes
only one copy of an attachment to the backup.
Compression of
backups
Compression increases backup performance over the network and reduces the size of the
backup image that is stored on the disk or tape. NetBackup does not support compression
of snapshot backups or backups that use GRT.
Encryption
When the Encryption attribute is enabled, the server encrypts the backup for the clients
that are listed in the policy. NetBackup does not support encryption of snapshot backups
or backups that use GRT.
Snapshot Client
This separately-priced option allows NetBackup to perform backups and restores of Exchange
2003 or later objects using snapshot methodology. NetBackup can perform backups using
the primary (or local) client where the Exchange server resides or using an alternate
client. The latter reduces the backup I/O burden on the primary client.
NetBackup supports instant recovery with Exchange 2007 on Windows 2003 or Windows
2008.
Cluster support
The NetBackup for Exchange Server agent supports Microsoft Cluster Server (MSCS)
environment and Veritas Cluster Server (VCS). See the Veritas NetBackup Enterprise Server
6.5 Cluster Compatibility list. This list contains information on the versions of Exchange
Server that are supported with the cluster environments.
LCR/CCR support
The NetBackup for Exchange agent with Snapshot Client supports backups of the Exchange
2007 passive VSS writer.


NetBackup provides the following methods to perform backups:
Automatic
Manual
User-directed
For more information on these backup methods and other administrator-directed

activities, see the NetBackup Administrators Guide, Volume I.
About automatic backups

The NetBackup administrator can schedule the full backups and the incremental
backups that occur automatically and unattended. (Incremental backups can be
differential incremental backups or cumulative incremental backups.) Automatic
backups meet most backup requirements.
You cannot perform an automatic copy backup. To perform a copy backup, run a
user-directed backup.
About manual backups

NetBackup allows the administrator to perform immediate manual backups of
the files that are 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
About user-directed backups

By using the Backup, Archive, and Restore interface, the user can perform backups
of Exchange Server, mailboxes, and public folders. The user can also perform a
user-directed backup to create a copy backup.
About the Exchange Server files that are backed up

Except where noted, NetBackup backs up the same files whether it uses streaming
or VSS backups (with Snapshot Client) or not.
17
18

The following files can be backed up during a backup operation:
Database files
See About backups and Exchange Server database files on page 18.
Database patch files

See About backups and Exchange Server database patch files (Pre-Exchange
2000, Service pack 2) on page 19.
Transaction logs
See About backups and transaction logs on page 19.
About backups and Exchange Server database files

Different database files are backed up for Exchange Server 2007 than for Exchange
2000/2003. Exchange 2007 allows up to 50 database stores. Each database store
contains only one database file. By default, the Exchange 2007 database file is
named database_name.edb.
Table 1-2 lists the database name and its default location for the first Exchange
storage group.
Table 1-2
Default locations for Exchange 2007 database files
Database
File name
Default directory
Mailbox Store
Database.edb
..\Microsoft\Exchange
Server\Mailbox\First Storage Group
Exchange 2000/2003 allows up to 20 database stores. Each database store consists

of two database files.
Table 1-3 lists the database names and their default locations for the first Exchange
storage group.
Table 1-3
Default locations for Exchange 2000/2003 database files
Database
File name
Default directory
Mailbox Store
Priv1.edb
...\exchsrvr\mdbdata
Priv1.stm
Note: Subsequent storage groups and databases can have different locations and
names (user-defined).

About backups and Exchange Server database patch files

(Pre-Exchange 2000, Service pack 2)
Database patch files are used to handle transactions that are 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 is already
backed up, the update 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. They update the restored database file with
the transactions that were in progress during the backup.
Table 1-4 lists the names of the patch files and their default locations.
Table 1-4
Default locations for patch files
Database patch file
File name
Default directory
Directory
Dir.pat
...\exchsrvr\dsadata
Information Store - Public Pub.pat
Information Store - Private Priv.pat
About Exchange LCR/CCR backups (Exchange 2007)

NetBackup can back up replicated data by interfacing with the replica (or passive)
Exchange 2007 service. VSS is the only supported backup of this replicated data.
The benefit of such a backup is to reduce I/O impact. NetBackup accesses the
replicated data and leaves the active (or live) Exchange service alone. This is
especially beneficial for a backup of a CCR node because the active node is
completely left out of the backup.
About backups and 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 Information Store databases in the event that a failure corrupted
the database. The Information Store can have multiple separate databases, which
are organized into storage groups. Each storage group can have multiple databases,
which share a common set of transaction logs. The maximum number of databases
and storage groups depends on the Exchange version.
Transactions are first written to the log file and then later written to the database.
The effective database is a combination of the uncommitted transactions in the
transaction log file and the actual database file. When the log file is filled with
19
20

transaction data, it is renamed and a new 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, in hexadecimal.
For Exchange 2007, the database transaction log for the Information Store is
named eXXYYYYYYYY.log. XX is the storage group number (in hex). YYYYYYYY is
the log file number (in hex). The size of the transaction logs is 1 MB.
For Exchange 2000/2003, the database transaction log for the Information Store
is named e0yXXXXX.log. Y is a number from 0 to 3 representing the storage group.
For example, e00.log, e01.log, e02.log. XXXXX is a five-digit hexadecimal number
that is incremented each time an e0y log file is renamed. The size of the transaction
logs is 5 MB.
After every 1 MB or 5 MB of transaction log data is written, a new log is created.
The log is created even though the transaction data may not be committed to the
database. There may be several transaction logs that contain uncommitted data,
therefore they cannot be purged.
Transactions in log files are committed to the respective log file when the service
shuts down normally. For example, consider 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 database file are committed
to the log file.
For full backups and differential incremental backups, the committed transaction
logs are truncated (deleted) by Exchange after a successful backup. Do not manually
purge log files. Instead, purge logs through the backup process.
The following process takes place during a full backup:
Database files are written to the backup media.
(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.
(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 are committed to the database file and they
are written to the backup media.

With the Backup, Archive, and Restore interface, the administrator can browse
for Exchange Server backups and select the ones to restore.

About server-directed restores

An administrator can browse Exchange Server databases and select the ones to
be restored. NetBackup lets you select the NetBackup server from which files are
restored, view the backup history, and select items to restore for a specific client
or other clients that were backed up by the selected NetBackup server.
About redirecting a restore to a different path

A user can restore mailbox objects and Public folder objects to directories that
are different from the directories from which the objects were backed up. Database
objects should not be redirected to different paths. Database objects can be
redirected to an Exchange Recovery Storage Group.
About redirecting a restore to a different client

You can restore the Exchange databases, directories, and mailbox objects to an
Exchange client other than the one from which they were backed up. The
administrator can direct restores to any NetBackup for Exchange client (regardless
of which client performed the backup). To redirect a restore, the administrator
can use the NetBackup Administration Console on the master server or the Remote
Administration Console.
See the NetBackup Administrators Guide for the configuration that is needed for
this type of redirected restore.
21
22

Chapter
Installing NetBackup for

Exchange Server
About installing the NetBackup for Exchange agent
Verifying the operating system and platform compatibility for NetBackup for
Exchange
Adding the NetBackup for Exchange license key
About installing the NetBackup for Exchange agent

Every NetBackup server includes the NetBackup client software by default.
Therefore you can use NetBackup for Exchange on a NetBackup server or client
(if NetBackup for Exchange is supported on that platform). Perform the following
tasks before you use NetBackup for Exchange:
Verify the installation prerequisites.
See Verifying the operating system and platform compatibility for

NetBackup for Exchange on page 24.
See About NetBackup server and client software requirements for

NetBackup for Exchange on page 24.
See About the database software requirements for NetBackup for

Exchange on page 25.
See About installation requirements for restores of individual Exchange

Server items using Granular Recovery Technology (GRT) on page 26.
See About the requirements for installing NetBackup for Exchange in a

NetBackup cluster on page 26.
24
Installing NetBackup for Exchange Server

Verifying the operating system and platform compatibility for NetBackup for Exchange
See About configuration and licensing requirements for NetBackup for

Exchange with Snapshot Client on page 27.
Add the license key for NetBackup for Exchange.

See Adding the NetBackup for Exchange license key on page 28.
Verifying the operating system and platform

compatibility for NetBackup for Exchange
Verify that the NetBackup for Exchange agent is supported on your operating
system or platform.
To verify operating system and compatibility
Go to the Symantec Support Web page:

http://www.symantec.com/business/support/index.jsp
In the Product Finder box, type NetBackup Enterprise Server and click
the > icon.
From the list on the right, click on Compatibility List.
In the list of documents, click on the following link:

Veritas NetBackup (tm) x.x Database Agent Compatibility (Updated
date_updated).
For x.x, look for the current release. For date_updated, look for the most
recent date.
For information on supported cluster environments for NetBackup for

Exchange, see the following document:
Veritas NetBackup (tm) Enterprise Server x.x / Enterprise Server
x.x Cluster Compatibility (Updated date_updated).
For information on support for Snapshot Client, see the following document:
Veritas NetBackup (tm) x.x Snapshot Client (Advanced Client) OS,
Arrays, and Database Agent Compatibility (Updated date_updated)
About NetBackup server and client software requirements for

NetBackup for Exchange
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 that NetBackup supports.
See the NetBackup Installation Guide.
The NetBackup client software is installed on the computer that has the
databases you want to back up. This step also installs the database agent.
The NetBackup client software is installed on the computer that has the
Exchange Server and on any off-host clients. This step also installs the database
agent. In an Exchange Server cluster, install the NetBackup client on each
node in the cluster.
If the client is also a NetBackup server, the client software and database agent
is installed along with the server software.
If you want to take advantage of features included in NetBackup 6.5.4, the

media server and clients must be at the same NetBackup version. If you upgrade
your media server to NetBackup 6.5.4, you must also upgrade your clients to
version 6.5.4.
Make sure that you configure any backup media that the storage unit uses.
The number of media volumes that are required depends on several things:
The devices used
The sizes of the databases that you want to back up
The amount of data that you want to archive
The size of your backups
The frequency of backups or archives
See the NetBackup Administrators Guide, Volume I.
About the database software requirements for NetBackup for Exchange

Verify the following regarding the database software on the NetBackup server or
client:
Exchange server software must be installed and operational.
For Exchange 2007, note the following requirements:
Do not install Microsoft Outlook on the same server on which Exchange is

installed.
If you perform VSS off-host backups, install the Exchange Management

Console on the off-host client. Then you can take advantage of the Exchange
2007 consistency checks with the Microsoft API.
For mailbox-level backups with Exchange 2007, download and install the
Microsoft Exchange Server MAPI Client and Collaboration Data Objects
25
26

package. Version 6.05.8022.0 or higher is required for Windows 2008.

Version 6.05.7888 or higher is required for Windows 2003.
You can find this package at:
http://www.microsoft.com/downloads/
Install the NetBackup Client on the Exchange server, if the Exchange server
is not locally installed on the NetBackup server.
To perform backups and restores of mailboxes and public folders, you must
create a user account for the NetBackup Client Service.
See About configuring NetBackup for backups and restores of individual
mailboxes and public folders on page 50.
A patch is required if you want to cluster Exchange 2007 in a VCS 5.0

environment. See the following TechNote for more information.
http://entsupport.symantec.com/docs/288625.htm
About installation requirements for restores of individual Exchange

Server items using Granular Recovery Technology (GRT)
Additional installation requirements exist if you want to restore individual
Exchange Server items using Granular Recovery Technology (GRT).
See About installing and configuring Network File System (NFS) for Exchange
Server Granular Recovery on page 30.
About the requirements for installing NetBackup for Exchange in a

NetBackup cluster
If you plan to use the database agent software on a NetBackup server configured
in a NetBackup cluster, verify the following requirements:
For information on supported cluster environments, see the following.

See Verifying the operating system and platform compatibility for NetBackup
for Exchange on page 24.
The NetBackup for Exchange agent also supports Clustered Continuous
Replication (CCR) and Single Copy Cluster (SCC). In the NetBackup for Microsoft
Exchange Server Administrator's Guide, any installation or configuration
requirements that are noted for clusters also apply to CCR and to SCC
configurations.
The NetBackup server software is installed and configured to work in a

NetBackup cluster.
See the NetBackup Installation Guide.
See the NetBackup High Availability Guide.

The Exchange server software is installed and operational on each node to

which NetBackup can failover.
On each node where NetBackup server resides, add the license key for the
database agent.
About configuration and licensing requirements for NetBackup for

Exchange with Snapshot Client
To use NetBackup for Exchange with Snapshot Client, you must meet the following
requirements:
NetBackup for Exchange is licensed.
NetBackup Snapshot Client is licensed.
No additional NetBackup software is required. You may need to modify other

hardware and software configurations. Information is available on how to configure
the NetBackup Snapshot Client and on configuration requirements for specific
snapshot methods.
See the NetBackup Snapshot Client Administrators Guide.
If you want to restore individual items (granular recovery), additional installation
requirements and configuration is necessary.
See About installing and configuring Network File System (NFS) for Exchange
Server Granular Recovery on page 30.
About requirements for Exchange 2007 off-host backups

Note the following requirements and operational notes for off-host backups:
VxVM 5.0 or later is required for off-host backups that use SFW.
To successfully perform backups with the VSS Provider for VxVM 5.0, you
must apply the following hotfixes. Apply the hotfixes on the hosts where a
Snapshot Client backup occurs.
Note: These hotfixes are included in SFW/SFW-HA 5.1 and therefore are not
required.
http://entsupport.symantec.com/docs/295112
This hotfix is also included in the SFW/SFW-HA 5.0 MP1 release.
27
28


Every NetBackup server includes the NetBackup client software by default.
Therefore you can use NetBackup for Exchange on a NetBackup server or client
(if NetBackup for Exchange is supported on that platform). To use this agent, add
a valid license key for it on the master or the media server.
For information on how to add license keys, see the NetBackup Administrators
Guide, Volume I.
In a NetBackup cluster, add the key on each node where the NetBackup server is
installed.
To add a NetBackup for Exchange license key in the NetBackup Administration
Console
On the master or the media server, open the NetBackup Administration

Console.
Choose Help > License Keys.
Click the New icon.
Type the license key and click Add.
Chapter
Installing and configuring

NFS for Exchange Granular
Recovery
About installing and configuring Network File System (NFS) for Exchange
Server Granular Recovery
About requirements to perform backups and restores with Granular Recovery

Technology (GRT)
About supported media server platforms for the jobs that use Granular
Recovery Technology (GRT)
About supported Exchange Server configurations for the backups that use
Granular Recovery Technology (GRT)
About configuring Services for Network File System (NFS) on the Windows
2008 NetBackup media server and NetBackup clients
About configuring Services for Network File System (NFS) on the Windows
2003 R2 SP2 NetBackup media server and NetBackup clients
About configuring a UNIX or Linux media server and Windows clients for
backups and restores that use Granular Recovery Technology
Configuring a different network port for NBFSD
30
Installing and configuring NFS for Exchange Granular Recovery

About installing and configuring Network File System (NFS) for Exchange Server Granular Recovery
About installing and configuring Network File System

(NFS) for Exchange Server Granular Recovery
NetBackup Granular Recovery leverages Network File System, or NFS, to read
individual objects from a database backup image. Specifically, the NetBackup
client uses NFS to extract data from the backup image on the NetBackup media
server. The NetBackup client uses Client for NFS to mount and access a mapped
drive that is connected to the NetBackup media server. The NetBackup media
server handles the I/O requests from the client through NBFSD.
NBFSD is the NetBackup File System (NBFS) service that runs on the media server.
NBFSD makes a NetBackup backup image appear as a file system.
Network File System, or NFS, is a widely recognized, open standard for client and
server file access over a network. It allows clients to access files on dissimilar
servers through a shared TCP/IP network. NFS is typically bundled with the host
operating system. NetBackup uses Granular Recovery Technology (GRT) and NFS
to recover the individual objects that reside within a database backup image, such
as:
A user account from an Active Directory database backup
Email messages or folders from an Exchange database backup
A document from a SharePoint database backup
Multiple NetBackup agents that support GRT (for example, Exchange, SharePoint,
and Active Directory) can use the same media server.
About requirements to perform backups and restores

with Granular Recovery Technology (GRT)
Ensure that your environment meets the following requirements:
You have a supported Exchange Server configuration and a supported operating

system for the media server.
See About supported Exchange Server configurations for the backups that
use Granular Recovery Technology (GRT) on page 32.
On all Exchange granular clients, do the following:
Ensure that the computer has an available drive letter on which to mount
the backup image.
Configure the NetBackup Client Service to log on with a domain-privileged

account.

About requirements to perform backups and restores with Granular Recovery Technology (GRT)
See Configuring the log on account for the NetBackup Client Service
on page 53.
On the Exchange Server install the Microsoft Exchange Server MAPI Client
and Collaboration Data Objects package, as follows:
For Exchange 2007 on Windows 2008, install version 6.05.8022.0 or

higher.
For Exchange 2007 on Windows 2003 R2 SP2, install version 6.05.7888

or higher.
These packages are available on the following Microsoft Web site:
http://www.microsoft.com/downloads/
For Windows 2003 R2 SP2, install the hotfix for Client for NFS.
The hotfix is available at the following location:
http://support.microsoft.com/kb/947186
More information is available about which client is the granular client.
See About client and proxy server privileges for granular operations
on page 57.
Enable or configure NFS for your environment.
Windows 2008 media server and clients

See About configuring Services for Network File System (NFS) on the
Windows 2008 NetBackup media server and NetBackup clients on page 33.
Windows 2003 R2 SP2 media server and clients

Windows 2003 R2 SP2 NetBackup media server and NetBackup clients
on page 40.
UNIX/Linux media server and Windows clients

See About configuring a UNIX or Linux media server and Windows clients
for backups and restores that use Granular Recovery Technology
on page 47.
Windows 2008 NetBackup media server and NetBackup clients on page 33.
Windows 2003 R2 SP2 NetBackup media server and NetBackup clients
on page 40.
31
32

About supported media server platforms for the jobs that use Granular Recovery Technology (GRT)
About supported media server platforms for the jobs

that use Granular Recovery Technology (GRT)
Table 3-1 shows the supported platforms for NetBackup media servers that support
granular recovery operations.
Table 3-1
Supported media server platforms for the jobs that use Granular
Recovery Technology
Supported media server platforms

AIX 5L
HP-UX HP 9000 PA-RISC
HP-UX HP Integrity (IA-64)
RedHat Enterprise Linux
Solaris SPARC
SUSE Linux Enterprise Server
Windows 2003 R2 SP2 x86/x64
Windows 2008
About supported Exchange Server configurations for

the backups that use Granular Recovery Technology
(GRT)
Table 3-2 shows the configurations supported for Exchange Server Granular
Recovery.
Note: NetBackup does not support Granular Recovery Technology (GRT) with
Windows Server 2003 R1 or earlier versions.
Table 3-2
Configurations that are supported for Exchange Granular Recovery
Exchange Server
Windows Server
Media server
Exchange Server 2007
Windows Server 2008
See About supported media server platforms for the jobs

on page 32.

About configuring Services for Network File System (NFS) on the Windows 2008 NetBackup media server and NetBackup
clients
Table 3-2
Configurations that are supported for Exchange Granular Recovery

(continued)
Exchange Server
Windows Server
Media server
Exchange Server 2007
Windows Server 2003 R2 or See About supported media server platforms for the jobs
later, 64-bit
on page 32.
Exchange Server 2003 SP1 Windows Server 2003 R2 or See About supported media server platforms for the jobs
later, 32-bit
on page 32.
About configuring Services for Network File System

(NFS) on the Windows 2008 NetBackup media server
and NetBackup clients
To configure NFS in a Windows 2008 environment, perform the following
configuration:
Enable NFS on the following:
The NetBackup media server
The Exchange granular clients

on page 57.
See Enabling Services for Network File System (NFS) on Windows 2008
on page 34.
You can disable the Server for NFS on the following:
The NetBackup media server
The Exchange granular clients

on page 57.
See Disabling the Server for NFS on page 38.
You can disable the Client for NFS on the NetBackup media server.
See Disabling the Client for NFS on the media server on page 37.
If an Exchange granular client resides on the media server, do not disable the
Client for NFS.
33
34

clients
Enabling Services for Network File System (NFS) on Windows 2008

To restore individual items from backups that use Granular Recovery Technology
(GRT), you must enable Services for Network File System. (You do not need to
configure Server Roles for Windows 2003 R2 SP2.)
When this configuration is completed on the media server and the Exchange
granular clients, you can disable any unnecessary NFS services.
More information is available on which clients require this configuration.
See About client and proxy server privileges for granular operations on page 57.
To enable Services for Network File System (NFS) on Windows 2008
Open the Server Manager.
In the left pane, click Roles and, in the right pane, click Add Roles.
In the Add Roles Wizard, on the Before You Begin page, click Next.

clients
On the Select Server Roles page, under Roles, check the File Services check
box.
Click Next.
On the Files Services page, click Next.
On the Select Role Services page, uncheck File Server.
35
36

clients
Check Services for Network File System.
Click Next and complete the wizard.
10 On the media server, configure the portmap service to start automatically at

server restart.
Issue the following from the command prompt:
sc config portmap start= auto
This command should return the status [SC] ChangeServiceConfig SUCCESS.
11 For each host in your configuration, choose from one of the following:
If you have a single host that functions as both the media server and the
Exchange granular client, you can disable the Server for NFS.
For a host that is only the NetBackup media server, you can disable the
Server for NFS and the Client for NFS.

clients
For a host that is only an Exchange granular client, you can disable the
Server for NFS.
See Disabling the Server for NFS on page 38.

See Disabling the Client for NFS on the media server on page 37.
Disabling the Client for NFS on the media server

To disable the Client for NFS on the NetBackup media server
In the left pane, expand Configuration.
Click Services.
In the right pane, right-click on Client for NFS and click Stop.
In the right pane, right-click on Client for NFS and click Properties.
37
38

clients
In the Client for NFS Properties dialog box, for Startup type, click Disabled.
Click OK.
Disabling the Server for NFS

After you enable Services for Network File System (NFS) on the media server and
on the Exchange granular clients, you can disable Server for NFS.
To disable the Server for NFS
In the left pane, expand Configuration.

clients
Click Services.
In the right pane, right-click on Server for NFS and click Stop.
In the right pane, right-click on Server for NFS and click Properties.
39
40

About configuring Services for Network File System (NFS) on the Windows 2003 R2 SP2 NetBackup media server and
NetBackup clients
In the Server for NFS Properties dialog box, for Startup type, click Disabled.
Click OK.
Repeat this procedure for the media server and for each Exchange granular
client.
About configuring Services for Network File System

(NFS) on the Windows 2003 R2 SP2 NetBackup media
server and NetBackup clients
Note: NetBackup does not support Granular Recovery Technology (GRT) with
Windows Server 2003 R1 or earlier versions.
Perform the following configuration:
Install the necessary NFS components on the NetBackup media server.

See Installing Services for NFS on the Windows 2003 R2 SP2 media server
on page 41.

NetBackup clients
Install the necessary NFS components on the Exchange granular clients.

on page 57.
See Installing Services for NFS on Exchange granular clients with Windows
2003 R2 SP2 on page 44.
Table 3-3 describes the NFS components that are necessary for the NetBackup
client and the NetBackup media server.
Table 3-3
NFS components required for Windows 2003 R2 SP2
NFS component
NetBackup client
Client for NFS
Microsoft Services for NFS Administration
RPC External Data Representation
NetBackup
media server
RPC Port Mapper
X
X
Note: If an Exchange granular client resides on the media server, install all the
components on the media server.
Installing Services for NFS on the Windows 2003 R2 SP2 media server
This topic describes how to install Services for NFS on a Windows 2003 R2 SP2
media server.
To install Services for NFS on the Windows 2003 R2 SP2 media server
Click Start > Control Panel > Add or Remove Programs.
Click Add/Remove Windows Components.
41
42

NetBackup clients
Check Other Network File and Print Services and click Details.
Check Microsoft Service for NFS and click Details.

NetBackup clients
Install the components that apply to your configuration.
If the host is only a NetBackup media server, check the following

components:
RPC Port Mapper
If you have a single host that functions as both the media server and the
Exchange granular client, check the following components:
Client for NFS
RPC Port Mapper
Media server
and client
Media
server only
Click OK.
Click OK.
Click Next and complete the Windows Components Wizard.
After the installation is complete, open Services in the Control Panel.
43
44

NetBackup clients
10 Ensure the following:

Host type
Services
required
Services not
required
A single host that has both the media server Client for NFS is
and the Exchange granular client
running.
A host that is only a NetBackup media server
Client for NFS can

be stopped and
disabled.
11 Configure the portmap service to start automatically at server restart.

Issue the following from the command prompt:
sc config portmap start= auto
This command should return the status [SC] ChangeServiceConfig SUCCESS.
Installing Services for NFS on Exchange granular clients with Windows

2003 R2 SP2
This topic describes how to install NFS on the NetBackup clients with Windows
2003 R2 SP2. Only the clients that perform granular operations require NFS. If
an Exchange granular client is also a media server, you must follow a different
procedure.
See Installing Services for NFS on the Windows 2003 R2 SP2 media server
on page 41.
More information is available on which clients require NFS.
To install Services for NFS on the NetBackup clients with Windows 2003 R2 SP2
Click Start > Control Panel > Add or Remove Programs.
Click Add/Remove Windows Components.

NetBackup clients
Check Other Network File and Print Services and click Details.
Check Microsoft Service for NFS and click Details.
45
46

NetBackup clients
Check the following components:
Client for NFS
Click OK.
Click OK.
Click Next and complete the Windows Components Wizard.
After the installation is complete, open Services in the Control Panel.
10 Ensure the following that the Client for NFS service is running.
11 Repeat this procedure for each Exchange client that performs granular
operations.

About configuring a UNIX or Linux media server and Windows clients for backups and restores that use Granular
Recovery Technology
47
About configuring a UNIX or Linux media server and

Windows clients for backups and restores that use
Granular Recovery Technology
To perform backups and restores that use Granular Recovery Technology, perform
the following configuration if you use a UNIX or Linux media server and Windows
clients:
Confirm that your media server is installed on a platform that supports

granular recovery.
See About supported media server platforms for the jobs that use Granular
Recovery Technology (GRT) on page 32.
No other configuration is required for the UNIX or Linux media server.
Enable or install NFS on the Exchange granular clients.

Windows 2008
See Enabling Services for Network File System (NFS) on Windows

2008 on page 34.
Windows 2003 R2 See Installing Services for NFS on Exchange granular clients with
Windows 2003 R2 SP2 on page 44.
You can configure a different network port for NBFSD.

See Configuring a different network port for NBFSD on page 47.

NBFSD runs on port 7394. If another service uses the standard NBFSD port in your
organization, you can configure the service on another port. The following
procedures describe how to configure a NetBackup server to use a network port
other than the default.
To configure a different network port for NBFSD (Windows server)
Log on as administrator on the computer where NetBackup server is installed.
Open Regedit.
Open the following key.:

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
Create a new DWORD value named FSE_PORT.
Right-click on the new value and click Modify.
48

In the Value data box, provide a port number between 1 and 65535.
Click OK.
To configure a different network port for NBFSD (UNIX or Linux server)
Log on as root on the computer where NetBackup server is installed.
Open the bp.conf file.
Add the following entry, where XXXX is an integer and is a port number
between 1 and 65535.
FSE_PORT = XXXX
Chapter
Configuring NetBackup for

Exchange Server
About user interface terminology
About configuring NetBackup for backups and restores of individual mailboxes

and public folders
About configuring backups that use Granular Recovery Technology (GRT)
Configuring streaming mailbox backups with Single Instance Store
About configuring a backup policy for an Exchange database
Testing configuration settings
About user interface terminology

You can perform many of the configuration steps in this topic from the NetBackup
administration console on the master server. The type of console available depends
on your master servers platform. 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. If interface differences
exist in the configuration procedures, the term "Windows interface" or "Java
interface" appears in the procedure to differentiate between the two interfaces.
50
Configuring NetBackup for Exchange Server

About configuring NetBackup for backups and restores of individual mailboxes and public folders
About configuring NetBackup for backups and

restores of individual mailboxes and public folders
You must configure NetBackup so that it can back up and restore individual
mailboxes and mailbox folders, and files within the public folders:
About the NetBackup service account
Configuring the log on account for the NetBackup Client Service
Configuring NetBackup to use the mailbox that is associated with the NetBackup
Client Service account
Note: If in a cluster, perform these steps on each Exchange node in the cluster.
About the NetBackup service account

To perform backup and restore operations, NetBackup must have access to the
mailboxes and folders. To provide this access, the NetBackup Client Service must
be associated with a valid Exchange mailbox. Symantec recommends that you
create a uniquely named mailbox.
Review the following prerequisites before you create an account for the NetBackup
Client Service:
Ensure that the NetBackup service account has domain privileged rights.
Verify that the NetBackup service account mailbox is not hidden.
Note: If in a cluster, perform the steps in the following procedures on each

Exchange node in the cluster.
Configuring the NetBackup service account (Exchange 2007)
Configuring the NetBackup service account (Exchange 2000/2003)
Granting the NetBackup Client Service account advanced permission (Exchange
2007)

Configuring the NetBackup service account (Exchange 2007)

To configure the NetBackup service account (Exchange 2007)
In Active Directory Users and Computers, select the Users directory.
Right-click on the Administrator account, click Copy, and create an account

for NetBackup.
Create a user account that has 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: EXCH1 is entered as the unique mailbox name, and other mailbox
names such as EXCH1BACKUP or BACKUPEXCH1 exist. The backup or restore
of individual mailboxes or both fail.
After you create the account, double-click the account, click the Members Of
tab, and add this account to the Domain Admins group.
Open the Exchange Management Console.
In the Exchange Management Console, click Organization Configuration.
Right-click on Organization Configuration and click Add Exchange

Administrator.
On the Add Exchange Administrator page, click Browse and select the user
to which you want to delegate control.
Click the Exchange Server Administrator role.
Under Select the server(s) to which this role has access, click Add.
10 Select the servers to which you want to delegate control and click OK.
11 Click Add.
12 On the Completion page, verify that the delegation was successful and click
Finish.
13 Configure the NetBackup Client Service log on account.

on page 53.
Configuring the NetBackup service account (Exchange

2000/2003)
This topic describes how to a user account for the NetBackup Client Service for
use with Exchange 2000/2003.
51
52

To configure the NetBackup service account (Exchange 2000/2003)
Use Active Directory Users and Computers to create a user account that has
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: EXCH1 is entered as the unique mailbox name, and other mailbox
names such as EXCH1BACKUP or BACKUPEXCH1 exist. The backup or restore
of individual mailboxes or both fail.
After you create the account, double-click the account, click the Members Of
tab, and add this account to the Domain Admins group.
Open Exchange System Manager.
Right-click the Exchange Organization and click Delegate Control.
Click Next.
On the Users or the Groups screen, click Add.
In the Delegate Control dialog box, provide the following information.

Group or User
Specify the name of the account that was created in step 1.
Role
Select Exchange Full Administrator.
Complete the Delegation wizard.
If you have an Active/Active configuration, you must grant Receive As and

Send As advanced permission to the account created for the NetBackup
Client Service. Perform this action on each virtual Exchange Server in the
configuration.
See Granting the NetBackup Client Service account advanced permission
(Exchange 2007) on page 52.
10 Configure the NetBackup Client Service log on account.

on page 53.
Granting the NetBackup Client Service account advanced

permission (Exchange 2007)
If you have an Active/Active configuration, the account created for 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
Open Exchange System Manager.
Locate the virtual Exchange Server.
Right-click the virtual Exchange Server and click Properties.
Click the Security tab.
Select the user account that you created for the NetBackup Client Service.
See About the NetBackup service account on page 50.
Under Permissions, click Receive As and Send As.
Click OK.
Repeat step 2 through step 7 for each virtual Exchange Server in the cluster.
Configure the NetBackkup Client Service log on account.

on page 53.
Configuring the log on account for the NetBackup Client Service

By default, the NetBackup Client Service uses Local System as the account on
which to log on. A different account is required to perform backups or restores
of individual mailboxes and folders and items in the public folders,. Change the
service account to the Windows domain account that you previously created. To
change this account, you must have administrator group privileges.
Note: In a cluster environment, perform the steps on each database node in the
cluster.
To configure the log on account for the NetBackup Client Service
Open the Windows Services application.
Double-click on the NetBackup Client Service entry.
Click on the Log On tab.
If Local System account is not selected as the Log on as account, proceed

with step 8.
53
54

Provide the name of the user account that you created for the NetBackup
Client Service.
The account must include the domain name, followed by the user account,
domain_name\account. For example, recovery\netbackup.
Type the password.
Stop and start the NetBackup Client Service.
Close the Services control panel application.
Configure NetBackup to use the mailbox that is associated with the NetBackup
Client Service account.
See Configuring NetBackup to use the mailbox that is associated with the
NetBackup Client Service account on page 54.
Configuring NetBackup to use the mailbox that is associated with the

NetBackup Client Service account
This topic describes how to configure NetBackup so that it uses the mailbox that
is associated with the NetBackup Client Service account.
To configure NetBackup to use the mailbox that is associated with the NetBackup
Client Service account
Open the NetBackup Administration Console or the Remote Administration

Console.
In the left pane, expand Host Properties.
Click Clients.
In the right pane, right-click the Exchange client you want to configure and
click Properties.
Expand Windows client and click Exchange.
In the Mailbox for message level backup and restore box, specify the mailbox.
You can specify the mailbox as follows:
An Exchange mailbox name.

Use the mailbox that you configured in following procedure.

55
A fully-qualified name, if you did create a unique mailbox for NetBackup.

For example:
/O=<Org_Name>/OU=<Site_Name>/CN=<Server_Name>/CN=<Mailbox_Name>
A mailbox alias
Click OK.
Create a backup policy for Exchange mailboxes.

See About configuring a backup policy for an Exchange database on page 61.
About configuring backups that use Granular

To configure backups that use Granular Recovery Technology (GRT), review the
following information and configuration steps.
Review the types of backups that are supported.

See About the types of Exchange backups on page 66.
Review the limitations and conditions.

See About limitations and conditions for restores using Granular Recovery
Technology (GRT) on page 55.
If wanted, configure a granular proxy server.

See Configuring the granular proxy server on page 56.
Configure the privileges for clients that perform granular operations.

See Configuring client privileges for the operations that use Granular Recovery
Configure a backup policy.

About limitations and conditions for restores using Granular Recovery

Technology (GRT)
The following limitations and conditions exist for jobs using Granular Recovery
Technology (GRT):
The feature is limited to certain versions of Exchange Server and Windows

Server.
See About supported Exchange Server configurations for the backups that
use Granular Recovery Technology (GRT) on page 32.
56

The master server(s), media server(s), and clients need to have NetBackup
6.5.4.
You must configure NetBackup for browsing and restores of individual

mailboxes and public folders.
This feature only supports full and user-directed backups. NetBackup lets you
create a complete policy for disaster recovery, with all the various types of
schedules. However, an incremental schedule produces a backup image that
can only be used for database recovery.
Backups must be made to a disk storage unit, not to tape, and restores that use
GRT must be made from a disk storage unit. You can manually duplicate the
backup image to disk, but you cannot restore from the tape copy.
Exchange Server provides a feature to retain deleted items for a period of time
after you permanently delete them. Because the deleted items still exist,
NetBackup includes them in the backup image. NetBackup displays these items
when you browse the granular backup image and you can restore these items.
Configuring the granular proxy server

When you browse for or restore individual items using Granular Recovery
Technology (GRT), NetBackup uses the destination client to stage a virtual copy
of the database that you want to restore. However, NetBackup uses the source
client of the backup to stage the database in the following situations: when you
duplicate a GRT-enabled backup image or when you use the bplist command.
Alternatively, you can specify a different Windows system to act as a proxy for
the client. Use a proxy if you do not want to affect the source client or if the source
client is not available.
When you use the bplist command and the bpduplicate command, you can
override the Exchange granular proxy hostsetting with the -granular_proxy
option. More information is available on how to specify the granular host with
these commands.
See About using the command line to browse or restore granular backup images
on page 109.
NetBackup determines the granular host in the following order:
The host that is specified with the -granular_proxy option on the command
line.
The granular proxy host that you specify in the host properties for the source
client.

The source client.
More information is available about requirements for the granular proxy server.
To configure the granular proxy server

Console.
Click Clients.
In the right pane, right-click the client you want to configure and click
Properties.
In the Exchange granular proxy host box, indicate the name of the proxy
server you want to use.
Click OK.
Configure the proxy host to have privileges for granular operations.

on page 57.
About client and proxy server privileges for granular operations

In the following situations the source client for a granular backup is different
than the client that NetBackup uses for granular processing. Additional
requirements exist for these situations.
These situations include the following:
Off-host backups.
When you use a proxy host.

You can specify a proxy host in the NetBackup Administration Console or with
the bplist command.
Note that NetBackup uses the proxy host when you duplicate a backup image.
Backups of a clustered Exchange server.
When you use a private network.
57
58

When you select a destination client other than the source client to browse
the backup image or for restore.
If one of these situations applies to your NetBackup configuration, the following

requirements exist:
The client(s) or the media server must have the same version of Windows as
the client from which the backup is made.
For Windows 2008, the client(s) must have Services for Network File System
enabled (under File Services). For Windows 2003, the client(s) must have NFS
installed.
See About installation requirements for restores of individual Exchange
Server items using Granular Recovery Technology (GRT) on page 26.
The proxy server must also meet the following additional requirements:
Has the same NetBackup version as the Exchange hosts.
Uses the same NetBackup master server.
The client(s) or the media server must have privileges to perform granular
operations.
See Configuring client privileges for the operations that use Granular Recovery
The client name is as follows:
The proxy host name
The off-host client name
The private network host name
The node names in the cluster
The destination client name, if it is different than the source client
Configuring client privileges for the operations that use Granular

This topic describes how to configure client privileges for the operations that use
Granular Recovery Technology (GRT). More information is available on when this
configuration is necessary.
Alternatively, you can perform a server-directed restore. Further instructions are
available on how to allow redirected restores in the Managing client restores
section.
See the NetBackup Administrator's Guide, Volume I.

In the following procedure, peername refers to:
The proxy host name
The off-host client name
The private network host name
The node names in the cluster
The destination client name, if it is different than the source client
To configure client privileges for the operations that use Granular Recovery
Technology
On the master server, create the altnames directory, as follows:
In a non-clustered environment, create the following directory:

install_path\NetBackup\db\altnames
In a clustered environment, create the following directory:

shared_drive_install_path\NetBackup\db\altnames
In the altnames directory, create a peername file.

Peername is the name of the proxy host or off-host client. For clustered
clients, create a peername file for each node in the cluster.
For example, consider that you have a source client named ClientA and you
want to use a proxy host named ProxyClient. On the master server, you create
a file that is called proxyclient.
In the peername file, add the name of the source client.

The source client is the client that originally performed the backup. For
clustered clients, use the virtual Exchange name. For a backup within a private
network, use the private network host name.
For example, in the proxyclient, include the name clienta
Disabling the cataloging for duplications of Exchange backups using

Granular Recovery Technology (GRT)
Duplication of an Exchange backup that uses Granular Recovery Technology
(GRT) from tape to disk takes the same amount of time as a backup of the
Information Store. Granular information is not cataloged during the backup.
Duplication of the same backup from disk to tape takes extra time. NetBackup
requires the extra time to catalog the granular Exchange information. You can
choose not to catalog the granular information so that the duplication is performed
59
60

Configuring streaming mailbox backups with Single Instance Store
more quickly. However, then users are not able to browse for individual items on
the image that was duplicated to tape.
During the duplication process, NetBackup writes log entries periodically to show
progress of the job.
To disable cataloging, refer to the procedure for your platform.
To disable the cataloging of Exchange backups using Granular Recovery Technology
(Windows)
On the NetBackup master server, open Regedit.
Open the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\
Create a new String Value named GRANULAR_DUP_RECURSION.
In the Value data box, type 0.
Click OK.
To disable the cataloging of Exchange backups using Granular Recovery Technology

(UNIX)
In the bp.conf file on the NetBackup master server, add the following line:
GRANULAR_DUP_RECURSION = 0
Configuring streaming mailbox backups with Single

Instance Store
Exchange Server uses the Single Instance Store (SIS) to maintain single-instance
storage of mail messages. This capability in Exchange Server allows the database
to keep one copy of a message sent to multiple users on the same server. To back
up the data that is stored on an SIS volume, enable this feature on the NetBackup
client where Exchange Server is installed.
Note: This feature is only available for streaming mailbox backups, not for any
backups that use Granular Recovery Technology.
Note: Only attachments larger than 100 K are backed up as SIS objects.
Attachments smaller than 100 K are backed up with each individual message.

To configure streaming mailbox backups with Single Instance Store

Console.
Click Clients.
In the right pane, right-click on the client you want to configure and click
Properties.
Click Enable single instance backup for message attachments.
Click OK.
About configuring a backup policy for an Exchange

database
A backup policy for a database defines the backup criteria for a specific group of
one or more clients.
These criteria include the following:
Storage unit and media to use
Policy attributes
Backup schedules
Clients to be backed up
Items (database objects) to be backed up
To back up a database environment, 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 database policies are the same as for file system backups.
In addition to the policy attributes for this database agent, other attributes are
available that you should consider.
To add and configure a policy, see the following procedures:
61
62

See Adding a new policy on page 63.
See Adding schedules to a NetBackup for Exchange policy on page 65.
See Adding clients on page 68.
See Adding backup selections to an Exchange policy on page 70.
About disk storage units supported for restores using Granular

You can only perform restores of individual items using Granular Recovery
Technology (GRT) if the backup resides on a disk storage unit. If you configure
backups to a disk storage unit, no further configuration is required. If you configure
backups to tape, you must copy the backup image to a disk storage unit before
you can restore individual items. Use the bpduplicate command to copy the
image to disk storage.
Table 4-1 lists the disk storage units that support Granular Recovery.
Table 4-1
Supported disk storage units
Disk storage unit
Granular Recovery support
BasicDisk
Yes
AdvancedDisk
Yes
NearStore
No
OpenStorage
No
PureDisk
Yes
SharedDisk
No
SnapVault
No
Policy recommendations for Exchange Server

Refer to the following recommendations when you create policies:
Create a policy that backs up the Information Store, a storage group, or an

individual database. Enable the Enable document restore option so the backup
is performed with Granular Recovery Technology (GRT). This policy supports
full, incremental, and user-directed backups.
From this policy you can restore databases and individual mailbox items. You
cannot restore individual mailbox items from incremental backups that use
GRT. (In Table 4-2, see Policy A.)

(Optional) Create a policy that backs up mailbox objects. This policy uses the
Microsoft Exchange Mailboxes:\ directive. (In Table 4-2, see Policy B.)
(Optional) You can add a user backup schedule to any policy or optionally you
can create a separate policy for User Backups. (In Table 4-2, see Policy C.)
Table 4-2 describes the policies you can create to back up Exchange Server.
Table 4-2
NetBackup policy examples for Exchange Server
Policy and Backup selections

policy type
Other configuration
Auto backup Enable
document
frequency
restore
Policy A
Weekly Full
MSExchangeServer
Microsoft Information
Store:\*
Yes
User Backup
Store:\First Storage
Group\
Group\Database
Policy B
MSExchangeServer
If you want to allow user-directed backups,

create a User Backup schedule. You may want
to include this schedule in a separate policy.
(See Policy D.) User backups act as copy
backups. Transaction logs are not truncated
and the user back does not impact the content
of scheduled full and incremental backups.
To ensure that transaction logs are truncated
(deleted) regularly, include all databases for a
storage group in a full backup policy. Or specify
the storage group (not individual databases) in
the backup policy.
Microsoft Exchange
Mailboxes:\*
Daily
Incremental
Microsoft Exchange
Public Folders:\*
Weekly Full
No
This policy is optional.
(1)
(1) You can disable or enable the

Document-level restore option for a User
Backup.
Group\Mailbox Store\
Policy C
N/A
User Backup
MSExchangeServer
This policy is optional. If you want to separate

scheduled backups from user-directed backups,
include the User Backup schedule in a separate
policy.
Adding a new policy

This topic describes how to add a new backup policy for a database.
63
64

To add a new policy
Log on to the master server as administrator (Windows) or root (UNIX).
Start the NetBackup Administration console.
If your site has more than one master server, choose the one on which you
want to add the policy.
(Windows interface) In the left pane, right-click Policies and choose New
Policy.
(Java interface) In the left pane, click Policies. In the All Policies pane,
right-click the master server, and click New Policy.
In the Add a New Policy dialog box, in the Policy name box, type a unique
name for the new policy.
Click OK.
In the Add a New Policy or Change Policy dialog box, in the Policy type list,
select the MS-Exchange-Server policy type.
The database agent policy type does not appear in the drop-down list unless
your master server has a license key for the database agent.
Complete the entries on the Attributes tab.

See About policy attributes on page 64.
10 Add other policy information as follows:
Add schedules.
Adding schedules to a NetBackup for Exchange policy
Add clients.
Add database objects to the backup selections list.

See Adding backup selections to an Exchange policy on page 70.
11 When you have added all the schedules, clients, and backup selections you
need, click OK.
About policy attributes

With a few exceptions, NetBackup manages a database backup like a file system
backup. Other policy attributes vary according to your specific backup strategy
and system configuration.
For more information on policy attributes, see the NetBackup Administrators
Guide, Volume I.

Table 4-3 shows the policy attributes that are different for Exchange backups.
Table 4-3
Policy attribute descriptions
Attribute
Description
Policy type
Determines the types of clients that can be in the policy. In some

cases the policy type determines the types of backups that
NetBackup can perform on those clients. To use the database
agent, you must define at least one policy of type that is
MS-Exchange-Server.
Allow multiple data

streams
Specifies that NetBackup can divide automatic backups for each

client into multiple jobs. Each job backs 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.
Not all directives in the backup selections list allow for multiple
database streams.
Enable granular
recovery
Allows restores of individual items using Granular Recovery

Technology (GRT). Users can only restore individual items from
a full backup. (You can perform incremental backups using GRT,
but you cannot restore individual items from an incremental
backup.)
You can restore individual items only if the backup image resides
on a disk storage unit. Special configuration is required if you
want to back up images to tape.
See About disk storage units supported for restores using
Granular Recovery Technology (GRT) on page 62.
Exchange Server GRT-enabled backups do not support encryption,
compression, or instant recovery.
Keyword phrase
A textual description of a backup. Useful for browsing backups

and restores.
Snapshot Client
This option enables backups with Snapshot Client.

See About the NetBackup Snapshot Client for Exchange Server
on page 112.
Adding schedules to a NetBackup for Exchange policy

Each policy has its own set of schedules. These schedules control the initiation
of automatic backups and also specify when user operations can be initiated.
65
66

To add a schedule
In the Policy dialog box, click the Schedules tab.

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

Specify the other properties for the schedule.

See About schedule properties on page 68.
Click OK.
About the types of Exchange backups

The following types of backups are available for Exchange policies:
Full backup
For server backups, this schedule type backs up the Exchange Server database
and associated transaction logs. All committed transaction logs are truncated
(deleted) after they are successfully backed up.
For mailbox backups, this schedule type backs up the entire mailbox, including
all the folders and messages in that mailbox.
For the Public Store, this schedule type backs up the entire Public Store,
including all the folders and messages within the Public Store.
Differential incremental backup

A differential incremental backup only backs up changes since the last full or
differential incremental backup. Differential incremental backups can be
performed of databases, the KMS and the SRS services, mailboxes and of the
Public Share.
When you use this method to back up a database, only transaction logs are
backed up. After the successful backup of the transaction logs, all committed
logs are truncated (deleted). The truncation of the transaction logs sets the
context for the next backup.
To perform a full restore the data that is needed is contained in multiple
NetBackup images. One image for the full backup and another image for each
differential incremental that was performed.
This type of schedule does not support restores of individual items using
Granular Recovery Technology.

User backup
A user backup is not automatically scheduled and is initiated on the target
client computer.
A user-directed backup of a database is identical to a full backup except that
the transaction logs are not truncated. User backups are like a snapshot of the
databases at a given point in time, without affecting the content of ongoing
full and incremental backups.
You may want to consider creating a separate policy for User Backup schedule
types. Then you can easily separate user-directed and scheduled backups when
you restore 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 to restore.
Cumulative incremental backup

A cumulative incremental backup backs up all changes since the last full backup
or differential incremental backup. (However, most configurations do not mix
cumulative and differential incremental backups between full backups.) You
can perform cumulative incremental backups of databases, the KMS and the
SRS services, mailboxes, and of the Public Share.
When you use this method to back up databases, only transaction logs are
backed up; they are not truncated upon completion of the backup. When you
restore databases, transaction logs remain intact since the last full backup.
Consider an Exchange Server data recovery scenario where 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 replays all the logs that are in the log folder. The Exchange Server
database is brought back to the current date instead of to the time of the last
full or incremental backup.
This type of schedule does not support restores of individual items using
Granular Recovery Technology.
Note: Differential incremental and cumulative incremental backup types fail if

database circular logging is configured for the Exchange Server. See Microsofts
Exchange Server Administration Guide for more information on how to configure
circular logging.
Note: NetBackup performs incremental backups of storage groups, not individual

databases within storage groups. NetBackup lets you configure incremental
schedules for individual databases. The backup job still runs according to the
configured incremental schedules, but the job logs warnings for attempted
incremental backups of these objects.
67
68

About schedule properties

Some of the schedule properties have a different meaning for database backups
than for a regular file system backup.
Table 4-4 explains the schedule properties.
Table 4-4
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 want to configure.
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, assume that 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 that are based on specific dates, recurring week
days, or recurring days of the month.
Other schedule properties vary according to your specific backup strategy and
system configuration.
For more information on schedule properties, consult the NetBackup
Administrators Guide, Volume I.
Adding clients
The clients list contains a list of the clients that are backed up during an automatic
backup. A NetBackup client must be in at least one policy but can be in more than
one.
For a database policy, clients you want to add must have the following software
installed:
Exchange Server
NetBackup client or server

To add clients to a policy
In the Policy dialog box, click the Clients tab.

To access the Policy dialog box, double-click the policy name in the Policies
list in the NetBackup Administration Console .
Click New.
(Windows interface) Type the name of the client and press Enter.
If NetBackup cannot detect the hardware and the operating system, a dialog
box appears so you can specify this information.
If Exchange is installed in a NetBackup cluster, specify the virtual Exchange
name as the client name.
If you want to perform a restore from a backup using Granular Recovery
Technology (GRT), ensure that the clients meet the requirements for granular
restore.
See Configuring client privileges for the operations that use Granular
(Java interface) Type the name of the client you want to add.
If you want to perform a restore from a backup using Granular Recovery
Technology (GRT), ensure that the clients meet the requirements for granular
restore.
See Configuring client privileges for the operations that use Granular
If Exchange is installed in a NetBackup cluster, specify the virtual Exchange
name as the client name.
The following options are available when you add a client:
Client name
Type the name of the client you want to add.
Hardware and
Choose the applicable hardware and operating system of the
operating system client.
(Java interface) Click Add.
(Java interface) To add another client, repeat steps 2, 4, and 5.
(Windows) To add another client, repeat step 2 and 3.
If this client is the last client, click OK.
69
70

Adding backup selections to an Exchange policy

The Backup Selections list defines the following: the Exchange objects (databases,
mailboxes, and mailbox folders) to back up and the grouping of Exchange objects
for multiple data streams.
You can exclude items from backups.
See About excluding folders and files from mailbox and public folder backups
on page 77.
About notes and limitations when you create a backup

selections list with the Microsoft Exchange Mailboxes:\
directive
Review the following information before you create a backup selections list for
mailbox backups:
To perform backups of mailboxes, additional steps are required beyond policy

configuration.
Do not add Microsoft Exchange Mailboxes:\ (a mailbox directive) and Microsoft

Information Store:\ (a database directive) to the same policy.
When you use the Microsoft Exchange Mailboxes:\ directive, only backups of
mailboxes or folders are allowed.
You cannot specify the backup of an individual message or individual public
document.
Mailbox backups allow for mailbox recovery, but are not adequate for disaster
recovery. Exchange database backups are required for disaster recovery.
The root path of an Exchange Mailbox object (Microsoft Exchange Mailboxes:)

is case sensitive.
About notes and limitations when you create a backup

selections list with the Microsoft Information Store:\ directive
Review the following information before you create a backup selections list for
the Exchange database backups:
If you want to restore mailbox items from a database backup, also refer to the
notes and limitations for mailbox backups.
See About notes and limitations when you create a backup selections list with
the Microsoft Exchange Mailboxes:\ directive on page 70.

NetBackup for Exchange does not support incremental backups of individual

databases within a storage group.
NetBackup lets you configure an incremental backup for a policy that uses
Granular Recovery Technology (GRT). However, you cannot restore individual
items from this backup.
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 are not truncated (deleted) until a full backup is run on every
database in the storage group. To ensure that transaction logs are truncated
(deleted) regularly, include all databases for a storage group in a full backup
policy. Or specify the storage group (not individual databases) in the backup
policy.
Adding entries to a backup selections list by browsing

On Windows systems, you can browse for Exchange objects and add them to the
Backup Selections list. Alternatively, you can specify the objects manually.
See Adding entries to the backup selections list manually on page 72.
See Example backup selections for database backups on page 73.
To add an Exchange object to the backup selections list by browsing (Windows only)
In the Policy dialog box, click the Backup Selections tab.
Click New.
Click the Remote Folder icon.
Navigate to and click the Exchange object to back up and click OK.
Edit the new entry if you want 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. You can also divide backups into multiple data
streams.
See About performing backups with multiple data streams on page 74.
See About wildcards in a backup selections list on page 75.
71
72

(Exchange 2000 only) Add the ExIFS drive (M drive, by default) to the
NetBackup clients Exclude list. Then create a policy to back up the following:
public folders, the Microsoft Information Store, Storage Groups, or databases.
This action prevents Exchange 2000 objects from being backed up as file-level
files.
Click OK.
Adding entries to the backup selections list manually

You can add database objects manually to the Backup Selections list, if you do not
want to use the browse feature. Also see the example entries.
See Example backup selections for database backups on page 73.
To manually add entries to the backup selections list
In the Policy dialog box, click the Backup Selections tab.
Click New.
(Windows) Click the Directives button.
Select the directive set.
Select the directive.
Click OK.
Edit the new entry if you want 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. You can also divide backups into multiple data
streams.
See About performing backups with multiple data streams on page 74.
See About wildcards in a backup selections list on page 75.
(Exchange 2000 only) Add the ExIFS drive (M drive, by default) to the
NetBackup clients Exclude list. Then create a policy to back up the following:
public folders, the Microsoft Information Store, or Storage Groups or
databases. This action prevents Exchange 2000 objects from being backed
up as file-level files.
Click OK.

Example backup selections for database backups

To back up with multiple data streams, you must enable Allow multiple database
streams on the Attributes tab of the policy.
Table 4-5 includes the example entries for storage groups and storage group
databases.
Table 4-5
Example backup selections for database backups
To back up
Example path
An individual storage
group
Microsoft Information Store:\First Storage Group
Multiple storage groups,

with one stream for each
group
Microsoft Information Store:\*
Multiple storage groups, by NEW_STREAM

using two data streams
Microsoft Information Store:\First Storage Group
NEW_STREAM
Microsoft Information Store:\Second Storage Group
A database within a
storage group
Microsoft Information Store:\First Storage Group\SG1_DB1\
Note: When you back up an individual database in a storage group, the transaction
logs for the entire storage group are also included in the backup. Transaction logs are
not truncated (deleted) until a full backup is run on every database in the storage group.
To ensure that transaction logs are truncated (deleted) regularly, include all databases
for a storage group in a full backup policy. Or specify the storage group in the backup
policy, not individual databases.
Multiple databases, with by NEW_STREAM

using two data streams
Microsoft Information Store:\First Storage Group\SG1_DB1
NEW_STREAM
Microsoft Information Store:\First Storage Group\SG1_DB2
Example backup selections for mailbox backups

Table 4-6 includes example entries for mailboxes and public folders.
73
74

Table 4-6
Example backup selections for mailbox backups
To back up
Example path
An individual mailbox
Microsoft Exchange Mailboxes:\Mailbox 1\
A mailbox folder
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\Inbox
Multiple mailboxes, by
using two datastreams
NEW_STREAM
Microsoft Exchange Mailboxes:\[a-m]*
NEW_STREAM
Microsoft Exchange Mailboxes:\[n-z]*
Multiple mailboxes, by
Microsoft Exchange Mailboxes:\*
using one stream for each
mailbox
Multiple folders by using
two datastreams
NEW_STREAM
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\[a-m]*
NEW_STREAM
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\[n-z]*
An individual public folder Microsoft Exchange Public Folders:\Folder1\

A public subfolder
Microsoft Exchange Public Folders:\Folder1\Subfolder1\
Multiple public folders, by NEW_STREAM

using two datastreams
Microsoft Exchange Public Folders:\Folder1\
NEW_STREAM
Microsoft Exchange Public Folders:\Folder2\
Multiple public folders, by Microsoft Exchange Public Folders:\*
using one stream for each
folder
About performing backups with multiple data streams

Multiple datastreams divide automatic backups into multiple jobs; each job backs
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. Then add the
NEW_STREAM directive in the Backup Selections list to indicate where a new
backup stream should begin. The Exchange mailboxes or storage groups that are
defined in the Backup Selections list with wildcard characters are 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 creates a new stream for each mailbox:
If you specify the following in the Backup Selections list, NetBackup creates only
two streams, one for mailboxes a-m and one for mailboxes n-z:
NEW_STREAM
NEW_STREAM
For more information on the multiple data streams feature, see the NetBackup
Administrators Guide, Volume I.
About wildcards in a backup selections list

Wildcard characters can be used to define groups of mailboxes or public folders.
This way multiple objects can be backed up without having to specify the objects
individually in the Backup Selections list. Multiple data streams must also be
enabled. If this feature is not enabled, the backup fails.
Table 4-7 describes the supported wildcard characters for Backup Selections lists
in an Exchange policy.
Table 4-7
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 processes all objects that had s for a first character, any
character for a second character, and z for a third character.
75
76

Table 4-7
Supported wildcard characters (continued)
Wildcard character
Action
Left & right brackets ([ Use to match any one character that is enclosed in square brackets.
... ])
A minus (-) can be used to indicate a range of consecutive
characters; for example, [0-9] is equivalent to [0123456789].
These wildcard characters are not supported for the Microsoft
Information Store:\ directive.
Note: The minus (-) 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 wildcard characters are used in the Backup
Selections list:
Only one wildcard pattern per Backup Selections list entry is allowed.
If a wildcard pattern is not honored it is treated literally.
Wildcard patterns are honored only in the final segment of the path name.
Correct
Microsoft Information Store:\*
Microsoft Information Store:\StorageGroup?
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\*
Microsoft Exchange Public Folders:\Folder\Subfolder?
Incorrect
Microsoft Information Store:\StorageGroup?\Database
Microsoft Exchange Mailboxes:\Mailbox 1\*\Inbox
Microsoft Exchange Public Folders:\Folder?\
For an Exchange Mailbox path: any segment of the path can contain wildcard
characters as long as the wildcard characters are the last characters in the
segment. These segments include mailbox names, folders, or messages within
the Mailbox hierarchy.
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 can contain wildcard
characters as long as the wildcard characters are the last characters in the
segment. These segments include work space names or work space folders.
Correct
Microsoft Exchange Public Folders:\Folder1\Subfolder?
Incorrect
Microsoft Exchange Public Folders:\Folder?\Subfolder1
Microsoft Exchange Public Folders:\*\Subfolder1
About excluding folders and files from mailbox and public

folder backups
This topic describes how to create Exchange mailbox or public folder entries in a
NetBackup exclude list for a streaming backup. An exclude list can be added from
the server or from the client.
For more information on how to create exclude lists by using the NetBackup
Administration Console, see the NetBackup Administrators Guide, Volume I.
Table 4-8 provides examples of Exchange mailbox entries you can add to an exclude
list.
Table 4-8
Example Exchange mailbox entries in an exclude list
This entry ...
excludes ...
Microsoft Exchange Mailboxes:\J*
All mailboxes with a name that starts with J.
Microsoft Exchange Mailboxes:\J?e*
All mailboxes with a name that starts 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.
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 of Information Store\Deleted
Items
The Deleted Items folder for the mailbox Joe Smith.
Microsoft Exchange Mailboxes:\*\Top of

Information Store\Inbox\Virus*
Any messages that begin with Virus in the users Inbox.
Table 4-9 provides examples of public folder entries you can add to an exclude
list.
77
78

Table 4-9
Example public folder entries in an exclude list
This entry ...
excludes ...
Microsoft Exchange Public Folders:\

Marketing
The root public folder called Marketing.

Marketing\*.xls
All .xls documents under the Public Folder called Marketing.

After you configure the master server for NetBackup for Exchange, test the
configuration settings. Perform a manual backup (or backups) with the automatic
backup schedules you created. A description of status codes and other
troubleshooting information is available.
See the NetBackup Troubleshooting Guide.
Note: A manual back creates a real backup. Exchange logs are truncated, if
appropriate.
To test the configuration settings
Log onto the master server as administrator (Windows) or root (UNIX).
Start the NetBackup Administration Console .
In the left pane, click Policies.
Click the policy you want to test.
Select Actions > Manual Backup.

The Schedules pane contains the name of an automatic schedule (or schedules)
configured for the policy that you want to test. The Clients pane contains the
name of the client(s) listed in the policy that you want to test.
Follow the directions in the Manual Backup dialog box.
To check the status of the backup, click Activity Monitor in the NetBackup
Administration Console.
See About troubleshooting on page 151.
Chapter
Performing backups and

restores of Exchange Server
and Exchange mailboxes
Specifying the server and client for a Exchange Server backup operation
Specifying the server, client, and the policy type for a Exchange Server restore
operation
Backup options
Performing user-directed backups of Exchange Server
Performing copy backups
Prerequisites for performing Exchange mailbox backups and restores
About Active/Active configurations
About special characters in mailbox folders and message subjects
Performing user-directed backups of mailboxes and public folders
About restoring Exchange Server
Prerequisites for restoring Exchange individual mailboxes, mailbox folders,

public folders, or messages
Restore options for Exchange Server mailbox restores
Restoring mailbox or public folder objects
80
Performing backups and restores of Exchange Server and Exchange mailboxes

Specifying the server and client for a Exchange Server backup operation
About redirecting a restore of mailbox objects or public folders to a different

path
Redirecting a restore to a different client
About using the command line to browse or restore granular backup images
Specifying the server and client for a Exchange Server

backup operation
When you perform user backups of Exchange Server, you must specify the server
that you want to perform the backups.
In a cluster environment, you must include the name of the virtual Exchange
Server in the client list of the policy. When NetBackup performs the backup of
the client (or Exchange Server) it uses the virtual name of the Exchange Server.
NetBackup requires this configuration for backup operations of Exchange Server
to be successful.
Note: You cannot use the Java client interface to select a virtual client for a backup
operation. To back up a virtual client by using the Java interface, log on with the
virtual client name.
To specify the server and client for a backup operation
Log onto the server as Administrator.
Open the Backup, Archive, and Restore interface.
Select File > Specify NetBackup Machines and Policy Type.
In the Specify NetBackup Machines and Policy Type dialog box, provide the
following information:
Server to use for backups
and restores
Select the server you want to perform the backup.
Source client for restores (or Select the client you want to back up.
virtual client for backups)
To perform a backup of Exchange Server in a clustered
environment, select the virtual Exchange Server name.
If necessary, add the virtual Exchange Server name to
the list and then select it.
Click OK.

Specifying the server, client, and the policy type for a Exchange Server restore operation
Specifying the server, client, and the policy type for

a Exchange Server restore operation
To browse for and restore Exchange backups, specify the following items:
The server that performed the backups
The client that was backed up
The Exchange policy type
You also can choose the destination client to which you want to restore a backup.
(This type of operation is called redirecting a restore to a different client.) To
redirect a restore in this way, you must have administrative privileges or be logged
into the master or the media server.
See Redirecting a restore to a different client on page 108.
In a cluster environment, the name of the virtual Exchange Server must be included
in the client list of the policy. This configuration is required in order for restore
operations of Exchange Server to be successful. It may not be possible to restore
an Exchange database from a NetBackup client-only installation on a cluster. You
may not be able to change the destination client value to match the virtual server
name. In that case, use the NetBackup Backup, Archive, and Restore interface on
a NetBackup server. From the server you can change the destination client value
to the virtual server name.
To specify the server, client, and policy type for a Exchange Server restore operation
Click File > Specify NetBackup Machines and Policy Type.
In the Specify NetBackup Machines and Policy Type dialog box, from the
Server to use for backups and restores list, select the NetBackup server that
performed the backup.
From the Source client for restores list, select the client.
From the Policy type for restores list, choose MS-Exchange-Server.
(Optional) To redirect a restore to a different client, from the Destination

clients for restores list, select the client to which to redirect the restore.
Click OK.
Backup options
Table 5-1 lists the options that are available when you perform a backup.
81
82

Table 5-1
Backup Files dialog box options
Option
Description
NetBackup server
To change the NetBackup server that you want to perform the

backup operation, select another server from the drop-down list.
Items marked to be
backed up
Contains a list of objects to be backed up.
Keyword phrase to
associate with the
backup or archive
Specifies a keyword phrase, up to 128 characters in length, that

NetBackup associates with the image created by this backup
operation. You then can 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.

Users can back up the Information Store, storage groups, and individual databases.
When Enable document restore is enabled in the backup policy, you can later
restore individual mailbox items from the backup.
With Exchange 2000/2003, users can back up the Site Replication Services
database. With Exchange 2000, users can back up the Key Management Services
database.
To perform a user-directed backup
Mount all databases to be backed up.
Click File > Select Files and Folders to Backup.
If you are in a cluster environment, specify the name of the Virtual Exchange
Server as the client.
See Specifying the server and client for a Exchange Server backup operation
on page 80.
In the All Folders pane, click the objects you want to back up.
You can back up the following objects:
Microsoft Information Store
Storage groups

Expand the Microsoft Information Store node and click the storage group
to back up.
Individual databases
Expand the Microsoft Information Store. Then expand the storage group
and click the database to back up.
(Exchange 2000/2003) Site Replication Services database.

Check the SRS node to back up this database.
(Exchange 2000) Key Management Services database.

Check the KMS node to back up this database.
Click Actions > Backup.
Select the backup options you want.

See Backup options on page 81.
Click Start Backup.
To view the progress of the backup, click Yes.

If you do not want to view the progress of the backup, click No.

In NetBackup, a user-directed backup of Exchange acts as a copy backup.
User-directed backups perform a full backup, but do not truncate the logs. You
can change the behavior of a user backup so that it acts as a normal full backup
instead of a copy backup. As with regular full backups, the logs are truncated.
This configuration is only available for streaming backups. Make the following
change on the Exchange clients.
To perform a copy backup
From the Backup, Archive, and Restore interface, perform a user-directed

backup.
To configure user-directed backups to act as full backups
Open Regedit.
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Agents\Exchange
Create a new DWORD value named Convert_USER_to_FULL.
83
84

Prerequisites for performing Exchange mailbox backups and restores
In the Value data box, type 00000001.
Click OK.
Prerequisites for performing Exchange mailbox

backups and restores
Review the following prerequisites before you perform Exchange mailbox backups
and restores:
Special configuration is required before you can perform backups and restores
of individual mailboxes and of individual folders in the public folders.
Note: The administrator must have the same Exchange privileges as the
NetBackup Client Service Account.
Certain Exchange services run on the NetBackup client machine. For mailbox
backups or restores, the services also must run on the Exchange Server that
performs the backups or to which the mailboxes are restored.
The services are as follows:
Microsoft Exchange System Attendant (MSEXCHANGESA)
Microsoft Exchange Information Store (MSEXCHANGEIS)
(Exchange 2000 only) For KMS backups and restores, the Microsoft
Exchange Key Management Service (MSEXCHANGEKMS)
(Exchange 2000 or 2003) For SRS backups and restores, the Microsoft
Exchange Site Replication Service (MSEXCHANGESRS)
Review the additional requirements for mailbox restores.

See Prerequisites for restoring Exchange individual mailboxes, mailbox
folders, public folders, or messages on page 98.
About Active/Active configurations

For an Active/Active configuration, the NetBackup Client Service Account must
also have the advanced privileges Send As and Receive As.
Information about how to assign privileges is available.

About special characters in mailbox folders and message subjects
See Granting the NetBackup Client Service account advanced permission

(Exchange 2007) on page 52.
About special characters in mailbox folders and

message subjects
Table 5-2 describes the special characters in mailbox folders or message subjects
and how they are translated.
Table 5-2
Translation of special characters in mailbox folders and message

subjects
Character
Translation
~0
~1
~2
Performing user-directed backups of mailboxes and

public folders
This topic describes how to perform a user-directed backup of a mailbox or public
folder. To back up individual mailboxes, mailbox folders, or public folders, the
backup policy must include the Microsoft Exchange Mailboxes:\ directive. When
Enable document restore is enabled in a database backup policy, you can restore
individual mailbox items from the backup.
Note: NetBackup displays mailboxes differently for an Active/Active configuration
in a Microsoft Cluster Server environment. If more than one instance is running
on the same node, then NetBackup displays all mailboxes of all instances that run
on that node when you browse for mailboxes, regardless of the specified virtual
server name.
To perform a user-directed backup of a mailbox or a public folder
Open the Backup, Archive, and Restore interface on the Exchange Server.
85
86

Performing user-directed backups of mailboxes and public folders
Select the Exchange policy type (click File > Specify NetBackup Machines
and Policy Type).
If you are in a cluster environment, specify the name of the virtual Exchange
Server as the source client.
on page 80.
Node
In the All Folders pane, expand the node that contains the objects you want
to back up and select those objects, as follows:
Objects to back up
Microsoft Information Microsoft Information

Store
Store
storage group(s)
Other configuration
The backup policy must allow for individual item restores (Enable
document restore).
You cannot select mailboxes, mailbox folders, or public folders.
database(es)
Microsoft Exchange
Mailboxes
mailbox(es)
Microsoft Exchange
Public Folders
public folder(s)
mailbox folder(s)
Select the backup options you want.

See Backup options on page 81.

Click Start Backup.
To view the progress of the backup, click Yes.


NetBackup can restore storage groups, storage group databases, the Key
Management Service (KMS), and the Site Replication Service (SRS). You can also
restore the Exchange 2003 or later to the recovery storage group (RSG).
Before you perform restores of Exchange Server

Review the following information before you perform restores of Exchange Server:
Restore all databases in a storage group at the same time and before the
transaction logs are committed and the databases are mounted.
When an administrator restores 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 are not restored,
the Exchange Server fails to start.
Do not restore Microsoft Exchange Mailboxes:\ or Microsoft Exchange

Public Folders:\and Microsoft Information Store:\ objects at the same
time. Do not restore mailbox or public folder items from a GRT-enabled backup
and a streaming backup at the same time. The restore of the mailbox objects
fails to perform a restore of Exchange server databases because the Exchange
services are down. Or the restore of the Exchange mailbox items can finish
before the restore of the Exchange databases starts. In this case the restore of
the Exchange databases overwrites the restored mailbox objects.
To restore full and incremental backups, you can restore all the backups in a
single operation. Or you can restore the full backups and incremental backups
individually. If you restore all the backups in a single operation, NetBackup
performs a commit after the last incremental is restored. If you restore the
backups individually, select the following options when you restore the last
incremental backup set: Commit after last backup set is restored and Mount
database after restore.
Make sure the temporary location for log and patch files is empty before you
start a restore job. (Patch files apply only to Exchange 2000, pre-Service Pack
2. If a restore job fails, check the temporary location (including subdirectories)
to make sure log and patch files from a previous restore job are deleted.
87
88

Associated log and patch files are kept in the Exchange working directory until
the database is restored. If storage groups are 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. 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. It leaves Exchange 2000 in an unstable state.
Review the information for existing transaction logs.

See About existing transaction logs on page 88.
About existing transaction logs

Depending upon the data recovery scenario you have, you must take existing
transaction logs into consideration.
For example, do one of the following tasks:
Replay all log files

After you restore the files and the service starts up, the database commits the
transactions in the logs you restored. If contiguous logs exist on the server
beyond the log with the highest number you restored, those transactions also
are committed. If there is any gap in the numeric sequence of log names, no
further transactions are committed beyond the gap.
This scenario is useful when the transaction logs are intact but you require
the database to be restored. When you keep existing transaction logs, Exchange
Server can recover to the point of the failure. Otherwise, you must recover to
the time of the last full backup or an incremental backup. (differential
incremental backup or cumulative incremental backup).
Replay only restored log files

Use this option if you only want to restore up to the point of the last backup.
Any transaction logs that are created after the last backup are not involved in
the recovery of the database(s).
Restore options for standard restores of Exchange databases

The Roll-Forward Recovery and Point-in-Time Recovery options correspond
to the Delete existing transaction logs prior to restore option in previous releases.
However, the default option has changed. In previous releases, Delete existing
transaction logs prior to restore was enabled by default, which corresponds to
Point-in-Time Recovery. The new default option is Roll-Forward Recovery.

Different options are available when you perform a mailbox restore or a Snapshot
Client restore.
See Restore options for Exchange Server mailbox restores on page 99.
See Restore options for Snapshot Client restores on page 137.
Table 5-3 lists the options that are available when you perform a standard restore
of Exchange Server.
Table 5-3
Option
Microsoft Exchange tab options
Description
Roll-Forward Recovery Retains the existing transaction logs. The transaction logs that are part of the restore are
(Replay all log files)
replayed, followed by any transaction logs that currently exist.
Point-in-Time
Restores the database and replaces only the transaction logs that existed at the time of
Recovery (Replay only backup. Transaction logs created after the backup are deleted. Transaction logs are deleted
restored log files)
for the Exchange storage group that you restore.
Transaction logs are replayed during the recovery processing only if they are in the backup
image. Current transaction logs are ignored.
89
90

Table 5-3
Option
Description
Exchange 200x
Microsoft Exchange tab options (continued)
Temporary location for log and patch files

Enter a location where the associated log and patch files are to be kept until the database
is restored. The default location is c:\temp. If you choose to restore storage groups, 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 you select Commit after last backup set is restored for the restore, the log and patch
files are applied to the database. 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).
Make sure any previous log and patch files from a previous restore job were deleted.
Dismount database prior to restore

Dismounts the database before the restore begins. If you want to restore any storage
groups that contain databases, select this option to dismount all selected Exchange
databases. This option also sets the This database can be overwritten by a restore flag
on Exchange 2007. By default this option is not enabled.
Note: Use this option with caution. Ensure that you selected the correct database to
restore before you choose to dismount it with this option.
Commit after last backup set is restored
This option should only be set on the last job of a multi-job restore. This option 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 you select Commit after last backup set is restored when an intermediate backup
is applied, you cannot restore further backups. You must restart the restore operation
from the beginning.
Mount database after restore
Mounts the database so that it is available to users. This option is available only if you
select Commit after last backup set is restored.
Redirect to Recovery
Storage Group (RSG)
This option only applies to snapshot backups of Exchange 2007.
Start Restore
Initiates the restore operation.
Restoring storage groups or storage group databases

This topic describes how to restore storage groups or storage group databases.

Note: A restore of Exchange Server files always overwrites any existing files. For
example, if Pub.edb already exists on the target machine, it is replaced with the
copy from the backup.
To restore the storage groups or storage group databases
Dismount all Exchange databases that need to be restored.

Or, when you perform the restore, click the Dismount database prior to
restore option.
Select the type of restore to perform:
To restore from NetBackup backup images, click File > Select Files and
Folders to Restore > from Normal Backup.
To restore from Backup Exec backup images, click File > Select Files and
Folders to Restore > from Backup Exec Backup.
and Policy Type).
See Specifying the server, client, and the policy type for a Exchange Server
restore operation on page 81.
From the NetBackup History pane, select one of the following:
The last full backup
The last full backup and all subsequent differential backups
The last full backup and the last cumulative backup
In the All Folders pane, select the objects you want to restore:
Storage groups.
to restore.
Individual databases.
To restore an individual database within a specific storage group, expand
the Microsoft Information Store, then the storage group, and click the
database.
A full backup of an Exchange database includes the database transaction log

files. When you restore a database, you must also restore the transaction log
files.
91
92

Click Actions > Restore.
Select the restore options you want.

See Restore options for standard restores of Exchange databases on page 88.
To restore the backups individually, click Commit after last backup set is
restored and Mount database after restore when you restore the LAST
incremental backup set.
10 Click Start Restore.

11 If you chose to restore storage groups and you did not click 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

This topic describes how to restore the Key Management Service or the Site
Replication Service.
Note: Before you stop the KMS service, be sure that you have the KMS service
password.
Note: If you restore the backups individually, you must select the following options
when you restore the LAST incremental backup set: Commit after last backup
set is restored and Mount database after restore.
To restore the Key Management Service or Site Replication Service
Stop the KMS or the SRS service.

Stop the KMS service through the Exchange System Manager.
See Stopping and starting KMS on page 94.
Stop the SRS service with the Services applet in the Control Panel.
Delete contents of the kmsdata or the srsdata directory, which is located

under the default Exchange Server installation path.
Start the KMS or the SRS service.
Click File > Select Files and Folders to Restore > from Normal Backup.
and Policy Type).
From the NetBackup History pane, click the image(s) that contain the objects
you want to restore.
Select one of the following:
In the All Folders pane, click the objects you want to restore, as follows:
To restore the Key Management Services database, click the KMS node.
93
94

To restore the Site Replication Services database, click the SRS node.
10 Select the restore options you want.


12 After a restore of the KMS is complete, stop and start this service after the
restore completes.
Stopping and starting KMS

This topic describes how to stop and start the KMS by 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
From the Windows Start menu, click Programs > Microsoft Exchange >
System Manager.
In the left pane, open the appropriate Administrator Group and click
Advanced Security.
In the right pane, right-click Key Manager and click All Tasks, then Stop
Service or Start Service.
Restoring an Exchange 2007 or Exchange 2003 streaming (non VSS)

backup to a recovery storage group
NetBackup supports restores to the recovery storage group. You do not need to
redirect the restore. As long as the RSG already exists and is added for the selected
storage group and database(s), the restore automatically is restored to the recovery
storage group.
For further instructions, refer to the following information on recovery storage
groups on Microsofts TechNet site:
Exchange 2007
http://technet.microsoft.com/en-us/library/aa997260.aspx
Exchange 2003
95
96

To restore an Exchange 2007 or Exchange 2003 streaming (non VSS) backup to a

recovery storage group
Create the RSG on the target Exchange Server, if necessary.
(Exchange 2007) Dismount all Exchange databases you want to restore.

restore option.
Confirm that the RSG databases are not mounted.
Policy type for

restores
Select MS-Exchange-Server.
Destination
clients for
restores
If you want to restore to a different server, change the destination

client to the Exchange server that holds the RSG.
If you want to restore to the local server, leave the destination
client the same as the source client.
In the All Folders pane, click the objects you want to restore:
A storage group
to restore.
Individual databases

To restore an individual database within a specific storage group, expand

the Microsoft Information Store, then the storage group, and click the
database.
A full backup of an Exchange database includes the database transaction log
files. When you restore a database, you must also restore the transaction log
files.
10 Click Actions > Restore.
11 Select the other restore options you want.

97
98

Prerequisites for restoring Exchange individual mailboxes, mailbox folders, public folders, or messages
12 (Optional) If wanted, click the General tab and change the destination path
to the RSG name.
The destination path does not need to be changed even though the RSG is a
different name than the original storage group. The ESE engine automatically
redirects the restore to the proper location.
13 To restore the backups individually, click Commit after last backup set is
restored and Mount database after restore when you restore the last
incremental backup set.

15 If you chose to restore storage groups and you did not click Mount database
after restore (after the restore), mount the storage group databases that were
restored.
Manually mounting a database after a restore

If you did not click Commit after last backup set is restored, you need to mount
the database manually after the restore is completed.
To mount a database manually after a restore
Mount all of the databases that were restored in the storage group.
If the mount fails, try a soft recovery (ignore mismatched database

attachments) of the Exchange databases to bring the databases to a consistent
state.
eseutil /r E0n /i
Mount the databases again.
Prerequisites for restoring Exchange individual

mailboxes, mailbox folders, public folders, or
messages
Review the following information before you restore individual mailboxes, mailbox
folders, public folders, or messages:
Special configuration is required before you can perform backups and restores
of individual mailboxes and of individual folders in the public folders.

Review the prerequisites for performing mailbox backups and restores.

See Prerequisites for performing Exchange mailbox backups and restores
on page 84.
When you restore mailbox or public folder messages, the option Overwrite
existing message(s) overwrites the contents and properties of the original
messages. Messages are overwritten regardless of their location. (For example,
if the messages were moved to the Deleted Items folder.) If the original
message no longer exists, a new message is generated with the same contents
and properties. A new message is also generated if a new destination location
is entered.
If the option Do not restore the message(s) is selected, NetBackup skips the
restore of any message that still exists, regardless of the current location.
Note that if the original message(s) no longer exists, a restore of the message(s)
generates a new copy every time it is restored.
The destination mailbox must exist to successfully restore a mailbox.
When a mailbox is restored, all folders and messages that are 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 that are contained in
the folder are restored. You also can choose to restore specific subfolders or
specific messages or both from the folder backup image.

Table 5-4 lists the options that are available when you perform restores of
Exchange Server mailboxes.
Table 5-4
Option
Options for mailbox restores

Description
Exchange Mailbox If the destination mailbox message(s) already exist, choose from the
following:
Overwrite existing message(s)
Restores the copies of the mailbox messages that already exist.
Do not restore the message(s)
Does not restore mailbox messages if they already exist.
These options are ignored for a redirected restore.

Start Restore
99
100


Symantec recommends that you select one backup image at a time for individual
item restore. While this recommendation is not a restriction, you may at times
restore more copies of messages than you intend.
Note: Browse time for a backup that uses Granular Recovery Technology may take
longer than for a non-granular backup image. The media server gathers granular
information at this time and wait times may vary. Depending on the load on the
media server, you may need to increase the Client read timeout value. This option
is located in the Client host properties in the Timeouts tab.
To restore a mailbox or public folder object to a different location, you follow a
different procedure.
See See About redirecting a restore of mailbox objects or public folders to a
different path on page 103.
Note: Do not restore Microsoft Exchange Mailboxes:\ or Microsoft Exchange
Public Folders:\and Microsoft Information Store:\ objects at the same
time. Do not restore mailbox or public folder items from a GRT-enabled backup
and a streaming or mailbox-level backup at the same time. The restore of the
mailbox or public folder objects fails to perform a restore of Exchange server
databases because the Exchange services are down. Or, the restore of the Exchange
mailbox or public folder items finishes before the restore of the Exchange databases
starts. Then the restore of the Exchange databases wipes out the restored mailbox
or public folder objects.
To restore mailbox or public folder objects
Select the type of restore to perform, as follows:

and Policy Type).
After you specify the policy type, NetBackup displays Exchange Server backup
images.

You cannot restore individual items from an incremental backups that
uses Granular Recovery Technology (GRT).

You cannot restore individual items from an incremental backup that uses
Granular Recovery Technology (GRT).
Expand one of the following:
Microsoft Information Store > Storage Group > Mailbox Store
Microsoft Information Store > Storage Group > Public Store
Microsoft Exchange Mailboxes
Microsoft Exchange Public Folders
In the All Folders pane, select objects you want to restore from the following:
Mailboxes
Mailbox folders
Mailbox messages
Public folders
Documents in a public folder
The following figure shows backup using Granular Recovery Technology.
101
102

The following figure shows a streaming mailbox or mailbox-level backup.
All objects appear as folders and messages. You can identify some
non-message objects by the subject line. For example, if you create a Calendar
event named Appointment1, that name appears 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). They may not be easily identified.

About redirecting a restore of mailbox objects or public folders to a different path
On the Microsoft Exchange tab, choose whether or not to restore existing

mailbox messages.
You can restore individual items to alternate mailboxes, mailbox folders, or

public folders.
See About redirecting a restore of mailbox objects or public folders to a
different path on page 103.
About redirecting a restore of mailbox objects or

public folders to a different path
NetBackup can restore Exchange mailbox objects or public folders from NetBackup
and Backup Exec images to different locations.
Refer to the following topics for more information and instructions:
See About requirements for redirecting the restore of an Exchange mailbox

or public folder object to a different path on page 104.
See Redirecting the restore of a mailbox, mailbox folder, or public folder

on page 105.
103
104

See Redirecting a restore of a mailbox message or public folder document to

a different folder on page 106.
About requirements for redirecting the restore of an Exchange mailbox

or public folder object to a different path
Review the following requirements for redirecting the restore of an Exchange
mailbox or public folder object to a different path:
In the destination path, the following segment of the path cannot be changed:
Microsoft Information Store:\
Microsoft Exchange Mailboxes:\
If you change this part of the path, NetBackup attempts to restore the objects
as normal (non-Exchange) files.
The destination mailbox or destination folder must have an associated user

account.
When you redirect a restore of public folders, the folder that is indicated in
the destination path does not have to exist.
When you redirect mailbox backups, if you modify the name of the Exchange
folders Top of Information Store, Views, Finder, etc., NetBackup restores
the selected object to that specified folder name. You can see the new folder
when you browse for backups and it is backed up on subsequent backups of
that mailbox. However, you cannot use Outlook to view the folder and any
subfolders and messages in that folder.
Additional requirements exist when you restore mailboxes from a granular

backup. Assume the source path is as follows:
Microsoft Information Store:\My-Store-Group\My-database\John Q. Employee\

Top of Information Store\Inbox\Nancys birthday
Note the following:
My-Store-Group must be a valid storage group on the destination

Exchange server. However, the target mailbox does not have to exist in the
specified storage group.
My-database must exist but is not used at restore time. The mailbox for
John Q. Employee is located on the destination Exchange Server but it is
independent of the database specification.
Before you attempt the restore, the mailbox for John Q. Employee must
exist on the destination server.

Examples of redirecting an Exchange mailbox restore

Mailbox 1 consists of Top of Information Store, Inbox, and Folders 1 and 2, each
containing some mail messages. If you back up Mailbox 1 and restore Mailbox 1
to the existing Mailbox 2, all of Mailbox 1 (including its contents) is restored to
Mailbox 2. Note that Mailbox 1 itself is not created under Mailbox 2.
See Figure 5-1.
Figure 5-1
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.
See Figure 5-2.
Figure 5-2
Redirecting the restore of folder 2 to mailbox 2
Redirecting the restore of a mailbox, mailbox folder, or public folder

This topic describes how to redirect the restore of a mailbox, mailbox folder, or
public folder to a different mailbox or public folder.
To redirect the restore of a mailbox, mailbox folder, or public folder
In the Backup, Archive, and Restore interface, open a Restore window.
and Policy Type).
105
106

you want to restore. Select one of the following:

Incremental restores are not available for any backups that use Granular
Recovery Technology.

Incremental restores are not available for any backups that use (GRT).
In the All folders or right pane, click the mailbox or public folder to restore.
On the Microsoft Exchange tab, select the restore options you want.
On the General tab, click Restore everything to a different location.
In the Destination box, indicate where you want to restore the object.
You must indicate an explicit path (or full path) in the Destinationbox.
When you restore mailboxes, change the mailbox name to another existing
mailbox.
For example, if you want to restore the contents of Mailbox 1 to Mailbox
2, specify one of the following in the Destination box:
Microsoft Exchange Mailboxes:\Mailbox 2\
Microsoft Information Store:\Storage Group\Mailbox Store
[Mailbox]\Mailbox 2\
When you restore public folders, change the public folder name to the
folder to which you want to restore. This folder does not have to exist.
Click Start Restore.
Redirecting a restore of a mailbox message or public folder document

to a different folder
This topic describes how to restore a mailbox message or public folder document
to a different folder.
To restore a mailbox message or public folder document to a different path
In the Backup, Archive, and Restore interface, open a Restore window.
and Policy Type).

From the NetBackup History pane, click the image(s) that contain the folder

Recovery Technology (GRT).

Recovery Technology.
In the Contents of or right pane, click the folders, messages, or documents

to restore.
If you select items in the All Folders pane, you cannot redirect individual
objects.
On the Microsoft Exchange tab, select the restore options you want.
On the General tab, click Restore individual folders and files to different
locations option.
Each row under Restore individual folders and files to different locations
is associated with an individual folder, message, or document.
Double-click a row to modify the restore destination.
In the New Destination box, indicate the mailbox or folder where you want
to restore the object(s).
To redirect a mailbox folder or message, the destination can be any existing
mailbox or mailbox folder. To redirect a public folder or document, the
destination can be a new or existing public folder. You must indicate an
explicit path (or full path).
For example, consider that you want to restore the contents of Inbox in
Mailbox 1 to the folder Other in the same mailbox. Specify one of the
following in the Destination box:
Microsoft Exchange Mailboxes:\Mailbox 1\Top of Information Store\Other
Microsoft Information Store:\Storage Group\Mailbox Store [Mailbox
1]\Mailbox 1\Top of Information Store\Other
107
108

10 Click OK.

You can redirect an Exchange restore to a client other than the client that originally
performed the backup.
Most of the Exchange objects that were backed up can be redirected to a different
client, with the following limitations:
The Microsoft Exchange Directory and SRS databases contain machine and
security information. Therefore, they can only be restored to the original
computer or a clone of the original computer.
The Microsoft Exchange Information Store databases can be restored to a

different Exchange Server.
The following requirements must be met before you redirect 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.

(Use the Exchange System Manager and right-click the database you want
to overwrite and click 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 you redirect the KMS, this service must be installed on the destination
client.

To redirect a restore to a different client
Indicate the client to which you want to restore.

Continue with the instructions for restoring Exchange Server, public folders,
or mailboxes.
See Restoring storage groups or storage group databases on page 90.
See Restoring the Key Management Service or Site Replication Service
on page 93.
See Restoring mailbox or public folder objects on page 100.
About using the command line to browse or restore

granular backup images
Note the following information when you use the command line to browse or
restore granular backup images:
When you perform a restore of mailboxes or mailbox folders from a granular

backup, specify the file names as relative to the Microsoft Information Store
and storage group.
Correct:
\Microsoft Information Store\My-Store-Group\My-database\John Q.
Employee\Top of Information Store\Inbox\Nancys birthday
Incorrect:
\Microsoft Exchange Mailboxes\John Q. Employee\Top of Information
Store\Inbox\Nancys birthday
The -granular_proxy option is included with the bpduplicate command and

the bplist command. Use the -granular_proxy option to specify a proxy
host if one of the following situations apply: You do not want to affect the
source client, the source client is not available, or you want to use a different
proxy host than the one specified in the host properties for the source client.
The following example shows how you can specify a proxy host with the bplist
command:
bplist -t 16 -k exchgranpolicy -R -s 06/09/2008 16:00:00

-granular_proxy ProxyServerA "\Microsoft Information Store\StorageGroup1\
DeptA\EmployeeA\Top of Information Store\Inbox\*"
109
110

More information is available on how to configure the proxy server in the

client host properties.
See Configuring the granular proxy server on page 56.
If you specify a proxy host, it must have the same version of Windows as the
client from which the backup is made. The proxy host also must have privileges
to perform granular operations.
on page 57.
Chapter
Using NetBackup for

Exchange Server with
Snapshot Client
About the NetBackup Snapshot Client for Exchange Server
How does Snapshot Client for Exchange Server work?
Configuring an Exchange 2007 replication backup
How to optimize Exchange CCR backups when the cluster is also setup as a
SAN media server
About configuring snapshot backups of Exchange Server
About instant recovery backups of Exchange Server
About configuring instant recovery backups of Exchange Server
Configuring off-host backups
Performing user-directed snapshot backups of Exchange Server
About restoring snapshot images
Recovering an Exchange 2007 Local Continuous Replication (LCR) environment
Recovering an Exchange 2007 Clustered Continuous Replication (CCR)

environment
Redirecting an Exchange 2007 VSS backup to a storage group or the recovery

storage group when a storage group has one database
112
Using NetBackup for Exchange Server with Snapshot Client

Redirecting an Exchange 2007 VSS backup to a storage group or the recovery

storage group when a storage group has more than one database
About redirecting restores of Exchange 2003 VSS backup images
Redirecting a restore of a snapshot to a different client
About the NetBackup Snapshot Client for Exchange

Server
NetBackup for Exchange Server can be combined with the features of NetBackup
Snapshot Client. To use the database agent with Snapshot Client, you must have
a license key for both NetBackup for Exchange Server and NetBackup Snapshot
Client.
NetBackup Snapshot Client, when used with NetBackup for Exchange Server, can
back up and restore Exchange objects by taking snapshots of the component files.
Data is captured at a particular instant. The resulting capture or snapshot can be
backed up without affecting the performance or availability of the database. These
snapshots are backed up to tape or to the storage unit. Or the snapshot image is
retained for instant recovery.
Snapshot Client supports the Microsoft Volume Shadow Copy Service (VSS) of
Windows 2003 or later for creating a snapshot image. The actual VSS provider
that is used is dependent on your hardware environment and software
environment. For a description of VSS providers available for use with NetBackup
for Exchange Server, see the supported platforms matrix on the NetBackup support
site.
The following Snapshot Client features are available for use with NetBackup for
Exchange Server:
Snapshot backup
A snapshot is a disk image of the client's data that is made almost

instantaneously. NetBackup backs up the data from the snapshot
volume, not directly from the clients original volume. Client
operations and user access are allowed to continue without
interruption during the backup.

Instant recovery
NetBackup supports instant recovery backups with Exchange 2007

on Windows 2003 or later. This feature makes backups available
for instant recovery from disk. Instant recovery combines
snapshot technology with the ability to do rapid disk-based
restores. Optionally, the image is retained on disk as well as backed
up to storage.
To perform an instant recovery, one of the following methods is
used:
Files are copied back from the snapped volume to the original
volume
The volume is rolled back
Alternate client
backup
Snapshot Client for Exchange supports off-host backups using an

alternate client. Alternate client backups use a second, or alternate,
client to perform the backup on behalf of the primary client.
Compared to local Snapshot Client backups, this approach reduces
the backup I/O burden on the primary client.
About supported platforms for NetBackup for Exchange with Snapshot

Client
Before you use NetBackup for Exchange with Snapshot Client, confirm that your
platform is supported.
See Verifying the operating system and platform compatibility for NetBackup
for Exchange on page 24.
Note: NetBackup Snapshot Client for Exchange is only supported for Exchange
2003 or later on Windows 2003 or later. A compatibility list for Snapshot Client
and Database Agents is available from the Symantec Support Web site.
Note: If you use Veritas Storage Foundation for Windows (SFW), the minimum
software level is SFW 5.0.
About limitations of using NetBackup Snapshot Client for Exchange

Server
The following limitations exist when NetBackup Snapshot Client is used with
NetBackup for Exchange Server:
113
114

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. (However, you select individual databases 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 off-host backups. Only alternate clients
are supported for off-host backups.
You cannot restore both snapshot backups and standard backups in the same
restore operation. Also, you cannot restore standard incremental backups with
snapshot full backups or snapshot incremental backups with standard full
backups. An incremental backup must be of the same type (standard or
snapshot) as the last full backup.

The following topics describe how NetBackup for Exchange Server works with
the Snapshot Client option:
What is backed up?
About consistency checks on database and log files
What is backed up?

Snapshot Client can back up the Information Store and individual storage groups.
The same files are backed up when frozen image methodology is used as when
non-frozen image backup methods is used.
When NetBackup performs full backups, the database files and the transaction
log files are included in the snapshot. (For Exchange 2003 the database files refer
to the .edb and .stm files. For Exchange 2007 the database files refer to the .edb
file.) User-directed backups are supported when a User schedule is included in a
snapshot policy.
For Exchange 2003 with Service Pack 1 or for Exchange 2007 user-directed backups
do not truncate logs files and differential and cumulative backups are supported.
Table 6-1 describes how backup types affect log truncation in Exchange 2003 with
Service Pack 1 or Exchange 2007.

Table 6-1
The effect of backup types on log truncation in Exchange 2003 with

Service Pack 1 or Exchange 2007
Backup type
Supported
Logs are truncated
Full
Yes
Yes
User
Yes
No
Differential
Yes
Yes
Cumulative
Yes
No
For Exchange 2003 pre-Service Pack 1, both full and user-directed backups truncate
log files. Incremental and differential types backups are not supported.
Table 6-2 describes how backup types affect log truncation in Exchange 2003
pre-Service Pack 1.
Table 6-2
The effect of backup types on log truncation in Exchange 2003

pre-Service Pack 1
Backup type
Supported
Logs are truncated
Full
Yes
Yes
User
Yes
Yes
Differential
No
N/A
Cumulative
No
N/A
About consistency checks on database and log files

For an Exchange VSS backup, Microsoft requires that you run a checksum
consistency check on each database file (.edb, but not .stm) and each transaction
log file. The consistency check runs with the proper options against the files that
exist on the snapshot. For Exchange 2007, the consistency check uses THE
Exchange Store Consistency Check Reference (CHKSGFILES). CHKSGFILES also
allows the user to view problems or information in the application event logs. For
Exchange 2003, the consistency check uses eseutil.exe.
More information is available on the pause option added in Exchange 2003 SP2.
NetBackup does not use this option for Exchange 2007.
See Configuring a pause in consistency checks on page 119.
If any of the files fail the consistency check, the backup fails and the backup image
is discarded. The Exchange VSS Writer is notified of the failure. When this kind
115
116

of backup failure occurs, Exchange does not truncate log files. Failure of the
consistency check may be an indication of either database corruption or a problem
with the snapshot.
For off-host backups, the consistency checks are run on the off-host client rather
than on the primary client. You must install the Exchange Management console
on the off-host client.
See Viewing Event Viewer logs on an off-host server on page 154.

Exchange 2007 includes the mirroring (replicating) of Exchange databases and
logs to a local server with replication enabled (LCR). Or databases and logs can be
replicated to a passive node of a Microsoft cluster with replication enabled (CCR).
The supported backup interface to this replicated data is the new VSS passive
writer. NetBackup allows the user to select which VSS writer is backed up from
the Host Properties for the Client. The client seamlessly backs up and catalogs as
if it were a local VSS backup.
To perform an Exchange 2007 replication backup, you must do the following:
Indicate which VSS writer you want backed up.
Create a snapshot backup policy for the storage groups you want to back up.
See About the NetBackup Snapshot Client for Exchange Server on page 112.
Note: Instant recovery and off-host backups cannot be used with a replication
backup.
To configure an Exchange 2007 replication backup

Console.
Click Clients.
In the right pane, right-click on the Exchange client you want to configure
and click Properties.
Expand Windows Client and click Exchange.

How to optimize Exchange CCR backups when the cluster is also setup as a SAN media server
In the Exchange 2007 replication backup (LCR or CCR) box, click the writer
you want to back up.
Backup the passive copy and if not

available backup the active copy
This option backs up the passive copy of

the VSS writer. If the passive copy is not
available and healthy, NetBackup backs
up the active copy.
This option is the default.
Backup the passive copy
This option backs up the passive copy of

the VSS writer. If the passive copy is not
available and healthy, the backup fails.
Backup the active copy
This option backs up the active copy of

the VSS writer.
Click OK.
For a (CCR) environment, the NetBackup Client Service must be running as

a domain-privileged account on each node. Otherwise NetBackup is not
properly authorized to perform dismounts or restores.
For a CCR configuration, configure the same setting to both nodes in the
cluster.
If you change the attributes for the virtual CCR name, only the active node
is updated.
How to optimize Exchange CCR backups when the

cluster is also setup as a SAN media server
See the following TechNote for more information:
http://seer.entsupport.symantec.com/docs/322986.htm
117
118

About configuring snapshot backups of Exchange

Server
To configure a snapshot policy with instant recovery, you follow a different
procedure.
See Configuring a Snapshot Client policy with instant recovery on page 128.
To perform a Snapshot Client for NetBackup for Exchange backup, complete the
following configuration steps:
Review the general configuration requirements for snapshot operations.

See About configuration requirements for snapshot backups of Exchange
Server on page 118.
Review the configuration requirements for Exchange Server.

See About configuration requirements for the Exchange Server on page 119.
Choose which transaction logs to back up.

See Backing up transaction log files on page 120.
Configure a pause in consistency checks.

For Exchange 2007 replication backups, choose whether to back up the passive
or active copy.
See Configuring an Exchange 2007 replication backup on page 116.
Configure an MS-Exchange-Server policy that has the Snapshot Client

attributes selected.
See Configuring a Snapshot Client policy on page 121.
Configure the snapshot volume that you want to use during the backup process.
Disable circular logging for all Exchange storage groups.
About configuration requirements for snapshot backups of Exchange

Server
Observe the following configuration requirements before you perform backups
with NetBackup for Exchange and Snapshot Client:
The hardware and software for the appropriate snapshot method is installed
and configured correctly.
See the NetBackup Snapshot Client Administrators Guide.
See the Symantec Support Web site for details on the snapshot methods and
platforms that are supported for your agent.

NetBackup Snapshot Client is configured correctly and the license key for this
option is registered.
See the NetBackup Snapshot Client Administrators Guide for details.
To perform alternate client backups, perform any special configuration that

is required.
See the NetBackup Snapshot Client Administrators Guide for information.
Mount databases before you perform a backup.
About configuration requirements for the Exchange Server

Symantec recommends the following when you configure Snapshot Client for
Exchange:
The volume(s) that contains the Exchange databases should be dedicated to

Exchange only. Other types of databases (for example, SQL Server) should not
reside on the volume(s). Only Exchange objects are included in a snapshot
backup.
Transaction logs or Exchange system files should not reside on the same
volume as the Exchange database files (edb and stm).
(Exchange 2003, pre-Service Pack 1) The Information Store must be configured

with only one database per storage group.
(Exchange 2003 SP1 or later, Exchange 2007) Restore all databases in a storage
group at the same time. Also restore the databases before the transaction logs
are committed and the databases are mounted. Transaction logs are committed
at a storage group level, rather than at a database level.
Mount databases before you perform a backup.
For Exchange 2003, the database files are the .edb and .stm files. For Exchange
2007, the database file is the .edb file.
Configuring a pause in consistency checks

Note: This option is only applicable to Exchange 2003 SP2 or later and is not used
for Exchange 2007.
NetBackup runs the checksum integrity verification after a snapshot is complete.
You can adjust the I/O rate of the verification by adjusting the value of the
Snapshot verification I/O throttle option.
The value is used during snapshot validation by the Exchange command ESEUTIL
/pXXX where XXX is the value of Snapshot verification I/O throttle. ESEUTIL
119
120

defines the /p setting as a forced one-second pause after every XXX I/Os to limit
the I/O rate during database verification. See the Microsoft Exchange
documentation regarding the ESEUTIL command for details.
To configure a pause in consistency checks

Console.
Click Clients.
click Properties.
In the Snapshot verification I/O throttle box, specify the number of I/Os to
process for each 1-second pause.
Click OK.
Backing up transaction log files

The Backup option for log files during full backups determines how many log
files are backed up during a full or user-directed type backup. If you select Backup
only uncommitted log files, NetBackup only backs up and catalogs the transaction
log files that were not committed to the Exchange database at the time that the
snapshot was taken. Exchange requires these uncommitted log files during the
recovery of the Exchange database to make the database consistent. If Backup
all log files (including committed log files) is selected, all of the log files that exist
on the snapshot volume are backed up and cataloged.
When you back up only the uncommitted log files, the advantage is that less space
is needed on the storage unit for the transaction logs. When you back up all of
the log files, the advantage is that a consecutive set of log files is maintained. A
previous full backup can use these log files for rolling forward. These options do
not affect the ability to recover the current full or user-directed type backup.
These options affect the ability to roll forward from a previous full or user-directed
type backup.
For example, consider if a full backup is performed, followed by two differential
backups, followed by another full backup. If Backup all log files is specified, all
of the log files exist in backup images. The first full backup, the log files from the

two differential backups, and the log files from the second full backup can be
restored. The existence of all the log files allows for a roll-forward recovery. If
you select Backup only uncommitted log files, a gap exists in the sequence of
transaction logs that are in the backup images. From the full backup, you can
restore only as far as the time that is covered in the two differential backups.
To back up all Exchange log files

Console.
Click Clients.
click Properties.
Select the Backup option for log files during full backups option you want.
Back up only uncommitted log

files
Select this option to back up only the log files that

are uncommitted. This option is the default.
Back up all log files (including

committed log files)
Select this option to back up all log files.
Click OK.
Configuring a Snapshot Client policy

This topic describes how to configure a Snapshot Client policy. Optionally you
can choose to perform an off-host backup.
This topic only covers what is necessary to configure snapshot backups of
Exchange Server. Information on how to configure other policy information is
described in another topic. (This information includes other policy attributes and
how to create schedules, add clients, and add backup selections.)
See Configuring off-host backups on page 135.
See About instant recovery backups of Exchange Server on page 124.
121
122

To configure a Snapshot Client policy
Open the policy you want to configure.
Click the Attributes tab.
Select the policy type.
Select the
appropriate storage
unit or storage unit
group.
Click Allow
multiple data
streams to divide
backups into
multiple jobs.
Click Perform
snapshot backups.
(Optional) Click
Perform off-host
backup. Select the
alternate client from the
list, or type it in.
In the Policy type list, click MS-Exchange-Server.
Select a Policy storage unit/lifecycle policy.
Click Perform snapshot backups.
Optional: You can choose to perform off-host backups.

Optional: To divide backups into multiple jobs, click Allow multiple data
streams.
To configure schedules, click the Schedules tab.

See Adding schedules to a NetBackup for Exchange policy on page 65.

Use the Clients tab to specify clients to be backed up by this policy.

Note: For off-host backups, the client name should be the name of the primary
client.
10 Use the Backup Selections tab to enter the directives or browse for Exchange
objects.
When you configure an Exchange snapshot backup policy, only the Exchange
200x 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:
The following selections back up the Information Store:

To back up specific storage groups only, use the following backup

selections:
Microsoft Information Store:\storage_group_1
If Allow multiple data streams is selected, the databases are backed up

in separate data streams.
You can insert the NEW_STREAM directive in the selection list to group
selections into streams.
NEW_STREAM
NEW_STREAM
Store:\storage_group_1\
11 Click OK to close the dialog box.
123
124


This topic describes how instant recovery works and how to configure your
environment and NetBackup for instant recovery backups and restores.
This topic includes the following information:
About instant recovery methods
Truncating Exchange transaction logs with instant recovery backups
Limitations for instant recovery operations
Operational notes for instant recovery operations
About configuration requirements for the Exchange Server when you use
instant recovery
Policy recommendations for Exchange instant recovery
Configuring a Snapshot Client policy with instant recovery
About instant recovery methods

If the snapshot is preserved with the instant recovery option, NetBackup tries to
restore the database with the fastest way possible. Usually, a rollback of the
snapshot volume(s) that contain the Exchange files is the fastest way. However,
the ability to perform a rollback depends on several things: the configuration of
the Exchange database files, the contents of the volumes, and configuration of
the disk array. If a volume rollback cannot be performed, the files that are required
for restoration are copied from the snapshot volume to the original volume.
NetBackup uses the following methods during an Exchange database restore to
restore the physical files:
Volume rollback
The entire volume is rolled back, or resynchronized, by using the

snapshot. This method overwrites the entire volume with the
snapped volume. This method is generally the fastest method for
instant recovery.
File copy back
Individual files are copied back from the snapped volume to the
current volume. This method is generally the slowest method for
instant recovery.
To determine if a volume can be rolled back, checks are made to insure that the
same list of files exists in the following places:
The file list on the current volume.

The file list on the snapped volume.
The file list that corresponds to the Exchange database that is to be restored.
For a volume rollback to occur, all three of these file lists must match. For instance,
to restore Database1 NetBackup restores the physical .edb file. These files must
exist on the current volume and on the snapped volume. In addition, these files
must be the only files on the volumes. If the database files from multiple databases
exist on the same volume, then all of the databases must be selected for restore.
Then volume rollback can occur. These checks are in place to prevent any files
that are not part of the Exchange restore from being overwritten. The NetBackup
client excludes some known Exchange files when it determines whether a volume
is eligible for rollback or not. These files include Exxresyyyyy.jrs and tmp.edb.
In addition, if a Point-in-time restore is tried, any transaction log files that exist
on the current volume are excluded.
The copy-back restore method is used in the following situations:
If the system provider is used and the snapshot selected for restore is not the
most recent snapshot.
If there are other files on the volume that could be lost.
If all the files on the snapshot are not selected for restore.
If you click Roll-Forward Recovery (in the Restore Marked Files dialog box). A
Roll-Forward recovery needs the log files that were created since the backup.
A rollback cannot be performed since it removes those log files.
If multiple volumes are included in the restore set, each volume is evaluated
separately to determine if it is eligible for rollback. (The restore set is based on
the location of the Exchange database, transaction logs, and system files that are
part of the restore.) For example, perhaps the volume that contains the database
files is eligible for rollback, but the volume that contains log files has extra,
non-Exchange files. At the time of the restore, only the volume that contains the
database files is rolled back. All the log files are copied back from the snapshot
to the current volume.
Truncating Exchange transaction logs with instant recovery backups

By default, transaction logs are not truncated for any type of instant recovery
backup.
To truncate transaction logs, perform one of the following procedures. The
EXCHANGE_TRUNCATELOGS_IR only applies to full instant recovery backups.
125
126

To truncate Exchange transaction logs by performing a backup to a storage unit
Create a new backup policy.
Create a full or a differential schedule type.
In the attributes for the schedule, select Snapshots and copy snapshots to a
storage unit.
Select a storage unit for the policy.
Perform a snapshot backup with this policy.
To truncate Exchange transaction logs for snapshot-only backups
Open Regedit.
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config key
Create a new String Value named EXCHANGE_TRUNCATELOGS_IR.
In the Value data box, type Yes.
Click OK.
When you perform a full snapshot-only backup, the bpfis log now contains
the following text:
onlfi_vfms_logf: INF - Allowing Exchange log truncation on a snapshot-only backup.
To turn off truncation of Exchange transaction logs for snapshot-only backups
Do one of the following:
Delete the EXCHANGE_TRUNCATELOGS_IR value.
Set the Value data to No.
Limitations for instant recovery operations

The following limitations exist for instant recovery operations:
Instant recovery is only supported for Exchange 2007.
NetBackup can only restore an instant recovery backup that is performed with
NetBackup 6.5.2 or later.
Instant recovery does not support off-host backups.

Operational notes for instant recovery operations

When using SFW to make your Exchange IR snapshots, use Veritas Enterprise
Administrator (VEA) rather than VShadow or Vssadmin to view and manage your
snapshots. SFW resnaps a volume after a rollback restore, but the Microsoft
utilities are not aware of the new snapshot. They falsely report that the snapshot
does not exist.
About configuring instant recovery backups of

Exchange Server
To perform an Exchange backup with instant recovery, perform the following
configuration tasks:
Disable circular logging for all Exchange storage groups.
Review the general configuration requirements for snapshot operations.

See About configuration requirements for snapshot backups of Exchange
Server on page 118.
Review the configuration requirements for Exchange Server for instant

recovery operations.
See About configuration requirements for the Exchange Server when you use
instant recovery on page 127.
Choose which transaction logs to back up.

See Backing up transaction log files on page 120.
Configure a pause in consistency checks.

Review the backup policy recommendations for instant recovery backups.

See Policy recommendations for Exchange instant recovery on page 130.
Configure an MS-Exchange-Server policy that has the instant recovery attribute

selected and the Snapshot Client options that you want.
See Configuring a Snapshot Client policy with instant recovery on page 128.
Configure one snapshot volume for each backup image that you need to retain
on disk.
About configuration requirements for the Exchange Server when you

use instant recovery
The following configuration is required for the Exchange Server when you use
instant recovery:
127
128

The volume(s) that contains the Exchange databases should be dedicated to

Exchange only. Other types of databases (for example, SQL Server) should not
reside on the volume(s). Only Exchange objects are included in a snapshot
backup.
To allow volume rollback to occur during a restore, a volume should contain

the database files for only one database.
Transaction logs or Exchange system files should not reside on the same
volume as the Exchange database file (.edb).
Restore all databases in a storage group at the same time. Also restore the
databases before the transaction logs are committed and the databases are
mounted. Transaction logs are committed at a storage group level, rather than
at a database level.
About instant recovery with the Microsoft System Provider

A special requirement exists when you want to use instant recovery (IR) with the
Microsoft System Provider. In this case, Symantec recommends when you create
the policy that you include only the storage groups whose databases are on a
common volume.
If an IR policy backs up databases on multiple volumes and you restore a subset
of those volumes, NetBackup deletes the other snapshots.
If you use instant recovery with the Microsoft System Provider and you select a
set of storage groups that spans multiple volumes, the following occurs:
NetBackup creates a backup set with one snapshot for each volume.
On subsequent backups, if any snapshots are rolled back, all of the snapshots
in that set are deleted. (With SFW or the hardware system provider, the rolled
back snapshots are re-snapped so that the snapshot set remains complete.)
This situation is normal. It typically occurs when you do a roll-forward restore
of a storage group whose database and log folders are on separate volumes.
The database volume normally is rolled back but the log volume is copied back.
This action preserves the logs that were created since the backup. NetBackup
then deletes the log snapshot and removes the IR copy of the backup image
from the catalog. If a storage unit copy of the backup exists, it remains.
Configuring a Snapshot Client policy with instant recovery

This topic describes how to configure a Snapshot Client policy with instant
recovery. Optionally you can choose to perform an off-host backup.

This topic only covers what is necessary to configure instant recovery snapshot
backups of Exchange Server. Information on how to configure other policy
information is described in another topic. (This information includes other policy
attributes and how to create schedules, add clients, and add backup selections.)
See Adding schedules for instant recovery on page 132.
To configure a Snapshot Client policy with instant recovery
Create a new policy.
Click the Attributes tab.
Select the policy type.
Select the
appropriate storage
unit or storage unit
group.
Click Allow
multiple data
streams to divide
backups into
multiple jobs.
Click Perform
snapshot backups.
Click this option to
enable instant recovery.
(Optional) Click
Perform off-host
backup. Select the
alternate client from the
list, or type it in.
In the Policy type drop-down list, click MS-Exchange-Server
129
130

Select a Policy storage unit/lifecycle policy.

If you click Snapshots only for the Instant Recovery option (on the Schedules
tab), the storage unit is not used. NetBackup creates only a disk snapshot.
Click Perform snapshot backups.
Click Retain snapshots for Instant Recovery.

NetBackup retains the snapshot on disk, so that instant recovery can be
performed from the snapshot. A normal backup to storage is also performed
if you do not choose to create a snapshot only.
Click Snapshot Client Options.
In the Snapshot Client Options dialog box, from the Snapshot method list,
click VSS.
Adjust the configuration parameters.

See About instant recovery options on page 132.
10 Optional: You can choose to perform off-host backups.

11 Optional: If you want to divide backups into multiple jobs, click Allow multiple
data streams.
12 Add other policy information as follows:
Add schedules to the policy.

Add clients to the policy.

For off-host backups, the client name should be the name of the primary
client.
See Adding backup selections to an Exchange Server policy with instant

recovery on page 134.
13 After you add all the clients, schedules, and backup selections you need, click
OK.
Policy recommendations for Exchange instant recovery

Create the following policies when you use instant recovery:
Create one of the following policies for disaster recovery:

Create a snapshot policy with the instant recovery enabled and with the
option Snapshots and copy snapshots to a storage unit selected. (In
Table 6-3 , see Policy A-1.)
Create a snapshot policy, without instant recovery enabled. (In Table 6-3,
see Policy A-2.)
Create other schedules that perform snapshot backups to a storage unit.

(In Table 6-3, see Policy B, Schedule 2.)
(Optional) For fast, temporary backups, create a separate policy with a Full
Backup schedule. Enable Retain snapshots for Instant Recovery and the
Instant Recovery option Snapshots only. (In Table 6-3, see Policy B.)
Information is available on how transaction logs are truncated according to the

backup type you select.
See What is backed up? on page 114.
Instant recovery policy examples for Exchange Server
Table 6-3
Policy and
policy type
Auto backup
frequency
Copy to Description and other configuration

Retain
snapshots storage
unit
for
instant
recovery
Policy A-1
Weekly Full
Yes
Yes
MS-Exchange- Daily Incremental

Server
or Differential
This policy provides for Disaster Recovery. Alternatively,

you can create a snapshot policy without instant
recovery. (See Policy A-2.)
Note: Do not include cumulative and differential

schedules in the same policy.
Note: If you choose differential backups, you must

choose Snapshots and copy snapshots to a storage unit.
Policy A-2
Weekly Full
No
N/A
This policy provides for Disaster Recovery. Alternatively,

you can create a snapshot policy with instant recovery.
(See Policy A-1.)
Schedule 1:
Weekly Full
Yes
No
(Optional) This policy and schedule provides fast,

temporary backups because the snapshot is not copied
to the storage unit. In the Snapshot Client Options, set
Maximum Snapshots to a small number.
Schedule 2:
Weekly Full
Yes
Yes
If you want to have a single policy that performs

Snapshot-only backups and provides for disaster
recovery, also create this schedule. (Policy A-1 or Policy
A-2 is not required then.)
MS-ExchangeServer
Policy B
MS-ExchangeServer
131
132

About instant recovery options

Table 6-4 lists the options that are available for instant recovery backups.
Table 6-4
Snapshot Client options
Parameter
Value
Description
Provider Type
0-auto
The VSS Provider is automatically selected based on the providers

available for the snapshot volumes.
1-system
Only the default Microsoft VSS Provider is used.
2-software
Currently, the only software VSS Provider that is supported is SFW. If

this provider is not in control of one of the volumes that is required
for the backup, the backup fails.
3-hardware
The applicable hardware VSS Provider is used for the volumes. If a

hardware provider is not available for one of the volumes that is
required for the backup, the backup fails.
0-unspecified
The setting for this option depends on the configuration of the snapshot
volume.
Snapshot Attribute
1-differential
2-plex
Maximum Snapshots
(Instant Recovery
only)
This option defines the number of snapshots that is retained for instant
recovery. When this threshold is reached, a snapshot is automatically
snapped back before another snapshot backup is performed.
Select a number that is appropriate for the number of volumes that
you have available to become snapshot volumes for your backup. If you
use the Microsoft System Provider, consider the amount of disk space
available for the virtual snapshots that it creates.
Adding schedules for instant recovery

Note the following settings in the Schedules tab when you add a schedule for a
policy with instant recovery.
Table 6-5
Settings for schedules in instant recovery policies
Setting
Options
Description
Type of Backup
full or user
Snaps the volumes that contain the Exchange database, system, and log
files.

Settings for schedules in instant recovery policies (continued)
Table 6-5
Setting
Instant Recovery
Options
Description
differential or
cumulative
incremental
Snaps the volumes that contain the Exchange system and log files.
Differential backups require that the transaction logs are backed up to a
storage unit and kept on the instant recovery snapshot volume. (Select the
Snapshots and copy snapshots to a storage unit option.) This
configuration is required because all of the differential backups after the
last full backup are required to fully restore a database. Since a differential
backup truncates the transaction logs, the only way to guarantee that all
of the log files exist is to back them up to a storage unit.
Snapshots and
Note: The Instant Recovery options in this dialog box are unavailable if
copy snapshots to instant recovery is not selected in the policy attributes.
a storage unit
NetBackup creates a disk snapshot and backs up the clients data to the
storage unit that is specified for the policy.
Transaction logs are truncated when the backup (full or differential) to the
storage unit has completed.
Snapshots only
The image is not backed up to tape or to other storage. NetBackup creates

a disk snapshot only. Note that this disk snapshot is not considered a
replacement for traditional backup.
Transaction logs are not truncated for this schedule option. To truncate
transaction logs, you must perform a backup to a storage unit.
This option is available if you select Retain snapshots for instant recovery
(on the Attributes tab of the policy).
Retention
1 week - infinity
The retention level indicates the maximum time that the instant recovery
snapshot is retained. For full backups, select a retention level that ensures
a full backup is always available for restore. The snapshot can be deleted
prior to that time if the snapshot volume is required for another backup
attempt.
See About instant recovery volume rotation on page 134.
To add schedules for instant recovery
In the Policy dialog box, click the Schedules tab.
Click New.
In the Schedules dialog box, create at least one Full type of schedule.
133
134

From the Instant Recovery group, click Snapshots and copy snapshots to a
storage unit.
This option is required for differential backups. This option is also required
for disaster recovery scenarios where both the primary and the snapshot
volume have been damaged.
To close the dialog box, click OK.
About instant recovery volume rotation

At the start of a backup, the snapshot client is queried to determine how many
instant recovery snapshots currently exist for each volume. This information is
required for the Exchange Storage Groups that are selected for backup. If the
number of snapshots is currently at the configured maximum level of snapshots,
a snapshot is resynched. Then a snapshot is available for the upcoming backup
attempt.
The algorithm to determine which snapshot volume is resynched considers
whether the snapshot was taken as part of a full backup or an incremental backup.
The algorithm tries to maintain as many full backups as possible, even if newer
incremental backups have to be resynched.
Adding backup selections to an Exchange Server policy with

instant recovery
You can include each Exchange storage group in one backup policy. Or you can
choose to include a storage group in more than one policy. In the latter case,
ensure that enough snapshot volumes exist to satisfy the Maximum Snapshots
value for each policy that contains the storage group.
When you configure an Exchange snapshot backup policy, only the Exchange
200x directive set is valid. The only valid directives are Microsoft Information
Store:\ (a storage group can be appended) or NEW_STREAM.
Note: To back up individual databases, you must select all the databases in the
storage group.
The following are examples of valid entries:
The following selection backs up the Information Store:

To back up specific storage groups only, use the following backup selections:


If Allow multiple data streams is selected, the storage groups are backed up
in separate data streams.
You can insert the NEW_STREAM directive in the selection list to group
selections into streams.
NEW_STREAM
NEW_STREAM

You can use an alternate client to reduce the processing load on the client. Use
data mover is not a supported option for NetBackup for Exchange Server.
Additional installation requirements and configuration exist if you use SFW.
See About requirements for Exchange 2007 off-host backups on page 27.
The alternate client must be the client that shares the disk array. This option may
require additional configuration.
See to the NetBackup Snapshot Client Administrators Guide.
To configure an off-host backup
In the Policy dialog box, click the Attributes tab.
Click Perform off-host backup.
Click Use alternate client and enter the name of the alternate client.
On the Clients tab, add the client name of the primary client.
Off-host backups with SFW require that you back up storage groups only on
the same VxVM disk group.
135
136

Performing user-directed snapshot backups of Exchange Server
Performing user-directed snapshot backups of

Exchange Server
To perform a user-directed snapshot backup, a policy must exist on the server
that is configured for snapshot backups. This policy must also have a User
schedule. The user can back up the complete Information Store or a storage group.
Transaction logs are also backed up. However, transaction logs are not truncated
for user-directed backups.
Note: For Exchange 2003 pre-SP1, a user-directed backup also truncates the
transaction logs.
To perform a user-directed snapshot backup of Exchange Server objects
Mount any databases that you want to back up.
Click Actions > Specify Policy and Schedule.
In the Backup Policy and Schedule box, type the name of the Snapshot Client
policy.
If you are in a cluster environment, specify the name of the virtual Exchange
Server.
on page 80.
In the All Folders pane, select the objects you want to back up, as follows:
To back up the entire Microsoft Information Store, click this node.
To back up a storage group, expand the Microsoft Information Store, then

click the storage group to back up.
To back up individual databases, you must select all the databases in the
storage group. If you do not select all the databases, the backup job fails.
In the Backup Files dialog box, click Start Backup.
10 To view the progress of the backup, click Yes.



The following information describes how to restore the backups that are performed
with the Snapshot Client feature.
Note the following when you perform restores:
All databases in a storage group must be dismounted before you begin a restore
operation. You can instruct NetBackup to dismount the databases before the
restore begins.
All of the images you select for the restore must be from Snapshot Client
backups.
You must restore objects to the original location from which they were backed
up (Exchange 2003 SP1 or later, or Exchange 2007). Exchange does not allow
the transaction logs to be rolled forward if you restore them to a different
location.
Restore options for Snapshot Client restores

Table 6-6 describes the options that are available when you restore a Snapshot
Client backup.
Table 6-6
Option
Microsoft Exchange tab options for Snapshot Client restores
Description
Roll-Forward Recovery Retains the existing transaction logs. The transaction logs that are part of the restore
(Replay all log files)
operation are replayed, followed by any transaction logs that currently exist.
Point-in-Time
Restores the storage group(s) and replaces only the transaction logs that existed at the time
Recovery (Replay only of backup. Transaction logs created after the backup are deleted. Transaction logs are only
restored log files)
deleted for the Exchange storage group(s) that is restored.
If multiple backup images are required for the restore and you start the restore jobs
individually, only click Point-in-Time Recovery for the first job. Otherwise, transaction
logs from the previous restore jobs are deleted in subsequent restore jobs.
For example, a restore may require a full backup and one or more incremental backups.
You can select all of the images and perform the restore in one job. Or you can restore each
backup image separately.
137
138

Table 6-6
Option
Description
Exchange 200x
Microsoft Exchange tab options for Snapshot Client restores

(continued)
Temporary location for log and patch files

Not applicable for restores of snapshots.
Dismount database prior to restore
Dismounts the database(s) before the restore begins. This option dismounts all of the
databases in the storage groups that you want to restore, even if a database is not selected
for restore. By default this option is not selected.
For Exchange 2007, this option also sets the "Database can be overwritten by a restore"
flag.
Note: Use this option with caution. Ensure that you selected the correct database to
restore before you choose to dismount it with this option.
Commit after last backup set is restored
This option should only be set on the last job of a multi-job restore. This option enables
the restore operation to play through log files and roll back any uncompleted
transactions. If this option is not selected, the database needs to be mounted manually
after the restore.
If Commit after last backup set is restored is selected when an intermediate backup
is applied, you cannot restore further backups. You must restart the restore operation
from the beginning.
Mount database after restore
Mounts the database so that it is available to users. The user cannot change this setting.
A database must be mounted to commit it. Therefore Mount database after restore is
selected if Commit after last backup set is restored is selected. Otherwise, this option
is disabled.
Redirect to Recovery
Storage Group (RSG)
(Exchange 2007 only) Select this option to restore to the Recovery Storage Group.
Start Restore
Performing a snapshot restore

During a restore of an instant recovery backup, one of the following occurs:
The selected storage group is copied back
The selected databases are copied back from the snapped volume to the original
volume
A restore of Exchange Server files always overwrites existing files. (If Pub.edb
already exists on the target machine, it is replaced with the copy from the backup.)
The database files (.edb and .stm) are always overwritten.

To perform a snapshot restore
Dismount all Exchange databases that you want to restore.

restore option.
If you want to restore an instant recovery backup in a cluster environment,

the same node must be active as when the backup was created.
Click File > Select Files and Folders to Restore > from Normal Backup.
Select this type of restore even if you want to perform volume rollback.
NetBackup automatically selects the fastest available file restore method.
Select the Exchange policy type.

From the NetBackup History pane, click the backup image that contains the
objects you want to restore as follows:
The last full backup or user-directed backup
In the All Folders pane, select the objects you want to restore, as follows:
The Microsoft Information Store.

To restore the entire content of the selected backup image, click the
checkbox next to the machine name or the Microsoft Information Store.
Storage groups.
Expand the Microsoft Information Store node and select the storage
group to restore.
(Exchange 2003 with SP1 or a later, or Exchange 2007) Databases.

Expand the storage group and select the database(s) and log files you wan
to restore.
139
140

Recovering an Exchange 2007 Local Continuous Replication (LCR) environment
Click the Microsoft Exchange tab.
Recovering an Exchange 2007 Local Continuous

Replication (LCR) environment
This topic describes how to recover a storage group with LCR enabled. Most of
the following PowerShell commands are now available in the Exchange
Management Console with Exchange 2007 SP1.
Refer to Managing Local Continuous Replication for more information:
Follow these steps:
Issue the PowerShell command Suspend-StorageGroupCopy for a storage

group before you restore that storage group.
Perform a database restore, as described in the NetBackup for Microsoft

Exchange Administrators Guide.

Recovering an Exchange 2007 Clustered Continuous Replication (CCR) environment
You may need to re-seed the copy before you resume the copy.
Do the following:
Remove the database files, all log files and checkpoint files from the copy
location. (If you use the Exchange Management Console, you will be
prompted to perform this step.)
Issue the PowerShell command Update-StorageGroupCopy.

See How to Seed a Local Continuous Replication Copy for more information:
Issue the PowerShell command Resume-StorageGroupCopy to properly resume

the copy.
Recovering an Exchange 2007 Clustered Continuous

Replication (CCR) environment
This topic describes how to recover a storage group with CCR enabled. Most of
the following PowerShell commands are now available in the Exchange
Management Console with Exchange 2007 SP1.
Note: A restore can only be directed to the active node.
See Managing Cluster Continuous Replication for more information:
Follow these steps:
For Exchange 2007 pre-SP1, The NetBackup Client Service must be run as a
privileged domain account on each node. Otherwise, NetBackup is not properly
authorized to perform dismounts or restores.
Issue the PowerShell command Suspend-StorageGroupCopy for a storage

group before you restore that storage group.
Perform a database restore, as described in the NetBackup for Microsoft

Exchange Administrators Guide.
You may need to re-seed the cluster copy before you resume the copy.
Do the following:
Remove the database files, all log files and checkpoint files from the passive
node. (If you use the Exchange Management Console, you are prompted to
perform this step.)
141
142

Redirecting an Exchange 2007 VSS backup to a storage group or the recovery storage group when a storage group has
one database
From the passive node, issue the PowerShell command

Update-StorageGroupCopy.
See How to Seed a Cluster Continuous Replication Copy for more information:
http://technet.microsoft.com/en-us/library/bb124706.aspx
Issue the PowerShell command Resume-StorageGroupCopy to properly resume

the cluster copy.
Redirecting an Exchange 2007 VSS backup to a

storage group or the recovery storage group when a
storage group has one database
This topic describes how to redirect an Exchange 2007 VSS backup when a storage
group has one database. You can redirect the restore to another storage group or
to the recovery storage group. If a storage group has more than one database, you
must follow a different procedure.
See Redirecting an Exchange 2007 VSS backup to a storage group or the recovery
storage group when a storage group has more than one database on page 144.
NetBackup supports a redirected restore from any type of Exchange 2007 VSS
backup. These types include: local VSS snapshot backups, off-host VSS backups,
and Instant Recovery backups (using the copy-back mechanism).
example, if Pub.edb already exists on the target computer, it is replaced with the
To redirect an Exchange 2007 VSS backup to a storage group or the recovery storage
group
The RSG or storage group must already exist. Do the following:
To restore to the RSG, create the RSG on an Exchange server, if necessary.

Leave the RSG dismounted.
To restore to another storage group, create a storage group that has

databases. Those databases must have the same names as those in the
original storage group.

one database
Policy type for
restores
Destination
clients for
restores
If you want to restore to the RSG or a storage group on a different

server, change the destination client to the Exchange server that
holds the RSG.
If you want to restore the RSG or a storage group to the local
server, leave the destination client the same as the source client.
The last full backup, or
The last full backup and all subsequent differential backups, or
In the All Folders pane, expand the Microsoft Information Store and the
storage group.
Select the storage group you want to restore.
10 To redirect the storage group to another storage group, change the destination
path.
In the Restore Marked Files dialog box, click the General tab.
Unlike restores of streaming backups, the ESE engine does not automatically
redirect a storage group restore to its RSG, if it exists.
143
144

more than one database
11 Click the Microsoft Exchange tab.
12 Check Commit after last backup set is restored.

If you choose to restore backup images separately, you must check Commit
after last backup set is restored only when you restore the last incremental
backup set.
13 If you want to restore to an RSG, check Redirect to Recovery Storage Group

(RSG).
Redirecting an Exchange 2007 VSS backup to a

storage group or the recovery storage group when a
storage group has more than one database
This topic describes how to redirect an Exchange 2007 VSS backup when a storage
group has more than one database. You can redirect the restore to another storage
group or to the recovery storage group. If a storage group has only one database,
you must follow a different procedure.

See Redirecting an Exchange 2007 VSS backup to a storage group or the recovery
storage group when a storage group has one database on page 142.
NetBackup supports a redirected restore from any type of Exchange 2007 VSS
backup. These types include: local VSS snapshot backups, off-host VSS backups,
and Instant Recovery backups (using the copy-back mechanism).
example, if Pub.edb already exists on the target computer, it is replaced with the
To redirect an Exchange 2007 VSS backup to a storage group or the recovery storage
group
The RSG or storage group must already exist. Do the following:
To restore to the RSG, create the RSG on an Exchange server, if necessary.

Leave the RSG dismounted.
To restore to another storage group, create a storage group that has

databases. Those databases must have the same names as those in the
original storage group.
Policy type for
restores
Destination
clients for
restores
If you want to restore to the RSG or a storage group on a different

server, change the destination client to the Exchange server that
holds the RSG.
If you want to restore the RSG or a storage group to the local
server, leave the destination client the same as the source client.
145
146

From the NetBackup History pane, click the full backup image that contains
the database you want to restore.
In the All Folders pane, expand the Microsoft Information Store and the
storage group.
Select the following:
One of the databases you want to restore.
The transaction logs.
path.
Unlike restores of streaming backups, the ESE engine does not automatically
redirect a storage group restore to its RSG, if it exists.
11 In the Restore Marked Files dialog box, click the Microsoft Exchange tab.

12 Check Roll-Forward Recovery.

When you select the first database in a storage group to restore, you can
choose Point-In-Time Recovery.
13 Uncheck Commit after last backup set is restored.

If you want to restore only a full backup, check this option only for the last
database in the storage group that you restore.
If you want to restore full and incremental backups, check this option only
for the last incremental backup set.

(RSG).

16 When the restore completes, in a separate restore operation restore the next
database and the transaction logs. Note the following:
If you have full and incremental backups and this database is the last in
the storage group, continue with step 17.
If you have only full backups and this database is the last in the storage
group to restore, continue with step 23.
17 Select the incremental backup image and the storage group.

18 Click Actions > Restore.
path.
20 In the Restore Marked Files dialog box, click the Microsoft Exchange tab.
21 Check Roll-Forward Recovery.
(RSG).
23 Check Commit after last backup set is restored.

If you want to restore only a full backup, check this option only for the last
database in the storage group that you restore.
If you want to restore full and incremental backups, check this option only
for the last incremental backup set.
147
148

About redirecting restores of Exchange 2003 VSS backup images
About redirecting restores of Exchange 2003 VSS

backup images
The following limitations and requirements exist to redirect restores of Exchange
2003 VSS backups:
You cannot restore an Exchange 2003 VSS backup to an RSG.
In this Exchange release, you cannot redirect to a different storage group on

the local server.
If you want to redirect to a storage group on another server, the storage group
and database must be identical. The path(s) of the storage group also must be
identical to the original storage group.
Redirecting a restore of a snapshot to a different

client
You can redirect a restore of a snapshot backup to a different client as you can
with a standard backup, though additional limitations apply.
The following additional limitations apply when you redirect a restore of a
snapshot backup:
(Exchange 2003) The log prefix (for example, E00.log) for the storage group
on the target server must be the same as the prefix of the original storage
group. You may need to create temporary storage groups so that the target
storage group has the same log prefix as the original.
(Exchange 2003) 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.
Other limitations exist when you redirect a restore to a different client.

To redirect a restore to a different client
Follow the instructions for how to redirect a restore to a different client.

If you did not click Commit after last backup set is restored, manually mount
the database after the restore is complete.
See Manually mounting a database after a restore on page 98.
Chapter
Disaster Recovery of
Exchange Server
About configuring an alternate server for restores
Disaster recovery of Exchange Server 2007
Disaster recovery of Exchange Server 2000/2003
About configuring an alternate server for restores

You can use an alternate server to recover an Exchange database. You then can
extract mailbox or public folder data. Technote 264924 explains how to configure
an alternate server for restore operations:
Disaster recovery of Exchange Server 2007

Exchange 2007 disaster recovery information can be found at:

This topic describes what is necessary to perform a full server recovery of Exchange
2000/2003.
For detailed information about Exchange disaster recovery, refer to the Exchange
2003 Disaster Recovery Operations Guide at:
150
Disaster Recovery of Exchange Server

Other disaster recovery information can be found at:
www.microsoft.com/exchange
The following are required before an Exchange 2000/2003 restoration can be
performed:
If the Exchange server you want to restore is a member server in a domain,

the Active Directory must be running. If Active Directory does not exist, you
must restore it before you restore the Exchange.
If the Exchange server you want to restore is a domain controller, you must
first restore Active Directory on the machine.
To recover Exchange Server 2000/2003
Install the same version of Windows on the new or the repaired server.
Apply any service pack you previously installed.
Restore the IIS Metabase.
Reinstall Exchange 2000/2003 and any service packs that were present. (Use
the /DisasterRecovery if the domain is intact.)
Restore the databases.
If you have KMS or SRS, these must be restored independently of an Exchange

2000/2003 server restore.
If you have KMS, restore the Certificate of Authority. The CA can be restored
from a backup of the system_state of the server.
Chapter
Troubleshooting NetBackup
for Exchange
About troubleshooting
About debug logging
Verifying Exchange online backups
Viewing Event Viewer logs on an off-host server
About NetBackup status reports
About Exchange Server transaction log errors
Troubleshooting LCR or CCR recovery
Troubleshooting a status 5 error with bprestore
Dynamic enforcement of path length limit
Troubleshooting snapshot operations
About troubleshooting jobs that use Granular Recovery Technology (GRT)
About concurrent restore of multiple storage groups
About troubleshooting
The information in this topic includes resources available for troubleshooting
NetBackup for Exchange, including the following.
Debug logs
152
Troubleshooting NetBackup for Exchange

About debug logging
Status reports
About debug logging

The NetBackup master server and client software offers a comprehensive set of
debug logs for troubleshooting problems that can occur during NetBackup
operations. Debug logging is also available for Exchange Server backup and restore
operations.
You can control the amount of information written to debug logs.
See Setting the debug level on a Windows client on page 153.
After you determine the cause of the problem, disable debug logging by removing
the previously created debug logging directories. Details are available on the
contents of these debug logs.
See the NetBackup Troubleshooting Guide.
Additional information about NetBackup client logs and NetBackup master server
logs is available.
See the online help for the Backup, Archive, and Restore interface.
Note: When debug logging is enabled, the files can become large. The same files
are used by normal file backups.
To create all debug logs, run the following batch file:
install_path\NetBackup\logs\mklogdir.bat
About backup operation debug logging

To turn on debug logging for standard backup operations, create the following:
install_path\NetBackup\logs\bpbkar
install_path\NetBackup\logs\beds (Exchange 2007 mailbox backups)
For snapshot backups, create the following:

About debug logging
install_path\NetBackup\logs\beds
install_path\NetBackup\logs\bpbkar
install_path\Netbackup\logs\bpfis
For backups performed by an alternate client, the bpfis log exists on the alternate
client and the primary client; bpbkar only exists on the alternate client.
After you create these directories and perform a backup, debug logging information
is placed in the directory in a file named mmddyy.log.
About restore operation debug logging

To turn on debug logging for restore operations, create the following directory:
install_path\NetBackup\logs\beds (Exchange 2007 mailbox restores, instant
recovery)
install_path\NetBackup\logs\bpbkar (instant recovery only)
install_path\Netbackup\logs\bppfi (instant recovery only)
install_path\NetBackup\logs\nbfsd (restores using Granular Recovery
Technology)
install_path\Netbackup\logs\ncf (restores using Granular Recovery
Technology)
The new ncf processes nbgre.exe and nblbc.exe control the browsing and restore
of a granular backup image. The logs for these processes appear on the destination
client or proxy client.
install_path\Netbackup\logs\tar (All restore, excluding those that use Granular
Recovery Technology)
To troubleshoot restores from Snapshot Client backup (local and transportable),
create the following directories:
install_path\Netbackup\logs\bpfis
For alternate client backups, bpfis logs exist on both the primary and the alternate
clients.
After creating these directories and performing a restore, debug logging
information is placed in the directory in a file named mmddyy.log.
Setting the debug level on a Windows client

To control the amount of information that is written to the debug logs, change
the General, Verbose, and Database debug levels on the client(s). Typically, the
153
154

default value of 0 is sufficient. However, technical support may ask you to set the
value higher to analyze a problem.
The debug logs are located in install_path\NetBackup\logs.
To set the debug level on a Windows client
From the Windows Start menu, choose Programs > Veritas NetBackup >
Backup, Archive, and Restore.
Select File > NetBackup Client Properties.
Click the Troubleshooting tab.
Set the General debug level.

Set this level as high as 2.
Set the Verbose debug level.

Set the Database debug level.

Click OK to save your changes.

To verify that the Exchange Server online backup contains a usable copy of the
database, perform the following steps.
To verify Exchange online backups
Perform an online backup.
Set up a test server and restore the backup.
Stop the Exchange services.
Restart the Exchange services.

If the services start, the database is usable and contains no errors.

During the verification of an off-host backup, Exchange Server logs messages on
the off-host server. These logs are helpful if you need to troubleshoot the
verification stage of the backup. If Exchange Server is not installed on the remote
server, you cannot view the details of these logs.
You can view the logs on the remote server in one of the following ways:

Connecting to the remote server from within Event Viewer
About installing the Exchange System Management Tools on the remote server
Connecting to the remote server from within Event Viewer

You can view the logs on the remote server by opening Event Viewer on a server
that has Exchange Server installed. Then connect to the remote computer (the
server that performed the off-host backup).
To connect to the remote server from within Event Viewer
Log in to a server that has Exchange Server installed.
Open the Event Viewer.
Click Actions > Connect to another computer.
In the Select Computer dialog box, click Another computer.
Type the name of the remote server or click Browse to select the server.
Click OK.
In the left-hand pane, click Application to view the Exchange logs related to
the off-host backup.
About installing the Exchange System Management Tools on the remote

server
To install the Exchange System Management Tools, refer to the following articles:
On the Microsoft Support Web site, refer to article 834121:

http://support.microsoft.com
On the Microsoft TechNet Web site, refer to the Administration Guide for
Exchange Server 2003:
http://technet.microsoft.com

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.
The following reports are available:
About operational reports
About progress reports
155
156

About operational reports

The administrator has access to operational progress reports through the
NetBackup Administration Console. Reports can 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
can be generated for a specific time frame, client, or master server.
See the NetBackup Administrators Guide, Volume I for details.
About 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.
Viewing the status of a NetBackup operation

This topic describes how to view the status of a NetBackup backup or restore
operation.
To view the status of a NetBackup operation
Choose File > View Status.
Click the task for which you want to check the progress.
Click Refresh.
More information is available on progress reports and the meaning of the
messages.
See the NetBackup Backup, Archive, and Restore Getting Started Guide.

The Exchange server deletes transaction logs after a successful backup (for full
and differential backup types). If the Exchange server encounters any errors
during the deletion process, the NetBackup for Exchange agent logs this
information. Since the actual backup was successful, NetBackup exits with a status
0 (successful backup). Refer to the Microsoft Exchange Server documentation for
information on any errors that are encountered with the transaction logs.


If you do not perform a full backup of the active instance after you restore the
database, Exchange may report an error similar to the following:
Event
Event
Event
Event
Type:
Source:
Category:
ID:
Error
MSExchangeRepl
Service
2059
Troubleshooting a status 5 error with bprestore

If you start an Exchange mailbox restore operation with the bprestore command
and encounter a status 5 error, check that the path is correct. The bplist command
does not properly escape the [ and ] characters.
For example, bplist returns the following path for a mailbox:
/Microsoft Information Store/SG1/Mailbox1/backrest100 [backrest100]/
Instead, edit the path so it appears as follows:

/Microsoft Information Store/SG1/Mailbox1/backrest100 \[backrest100\]/
Dynamic enforcement of path length limit

The NetBackup Administrators Guide for Windows, Volume I details that files
and directories with path lengths greater than 1023 are automatically excluded
from backups. For streaming mailbox backups and for GRT-enabled backups, the
path length limit applies to individual mailbox folders and messages. When a
legacy mailbox backup encounters an item that exceeds the limit, the backup job
reports a final status of 1. This status indicates that some items were not backed
up, and the job details tell you which items were skipped. For granular backups
NetBackup checks the pathname length limit and reports exceptions, during
browsing and restoring of the granular backup image. It logs the pathnames that
exceed the limit to the ncf log, and reports the items that were skipped during
restore to the View Status window.
Troubleshooting snapshot operations

Note the following when you perform snapshot backup or restore operations:
If you attempt to restore a VSS backup from a multiplexed tape and you selected
a single database from a storage group that contains multiple databases, the
157
158

About troubleshooting jobs that use Granular Recovery Technology (GRT)
restore may fail. In this case, restore the entire storage group instead. This
issue will be fixed in a future release.
If you want to restore a storage group from an Exchange 2007 VSS image, the
restore may fail if an Exxrestore.env file exists in the storage group path.
This temporary Exchange file can be left from a previously failed restore.
Remove this file manually before you attempt another restore.
When you launch an Exchange off-host backup from the NetBackup Client
interface, the progress log window does not display the usual progress messages
as when a scheduled backup is executed. The backup operation is not impacted
by this lack of progress logging. If you want detailed progress, use the
NetBackup Administration Console to launch a manual backup operation of
the Exchange policy.
See Testing configuration settings on page 78.
About troubleshooting jobs that use Granular

Note the following when you use NetBackup to perform backup or restore
operations using Granular Recovery Technology:
Disable or uninstall Qlogic San Surfer software. It may conflict with the port
mapper for Client for NFS.
A status 1 error may occur for a GRT-enabled backup if the granular processing
operations failed to complete successfully. The job details under the Activity
Monitor or error log should indicate if this failure is what caused the status 1.
Do the following:
Look at the bpbkar debug log for more information.
A streaming backup still truncates transaction logs if the job ended with a
status 1 because of a granular processing operation failure. In this situation,
the backup image is suitable for database recovery.
NetBackup must be able to contact the proxy client or destination client.

If NetBackup cannot contact this client, then errors appear in the Problems
or All Log Entries reports. The following error messages appear in the
NetBackup error logs:
The granular proxy <clientname> for client <clientname> could not be

contacted. Unexpected results may have occurred. See bprd debug log for more
details.

Could not connect to <clientname> for virtual browse operation, errno=#,

bpcd_status=#
on page 57.

When you use multiple backup streams, for example, one stream for each storage
group, only the last storage group restored from the last restore job is properly
mounted. Recovery of the remaining storage groups is not complete.
Take one of these corrective actions:
If you want to restore from a snapshot backup, simply mount the unmounted
storage groups.
If you want to restore from a legacy (non-snapshot) backup, restore the logs
from the last backup set for each storage group individually.
To avoid these steps, you can also restore the storage groups individually in
separate restore operations.
159
160

Index
A
Allow multiple data streams 65
B
Back up all log files 121
Back up only uncommitted log files 121
backup media required 25
Backup Selections list
adding by browsing 71
example entries for database backups 74
Backup selections list
example entries for database backups 73
backup types 6667
backups
and mounting Exchange databases 82
automatic
described 17
copy 17
files that are included in database backups 17
in a cluster 80
manual 17, 78
of mailboxes 85
services which must be running 84
user-directed
and cluster environments 82
described 17
mailboxes 85
of Exchange objects 82
snapshot 136
beds log 153
bpbkar log 152153
bpfis log 152153
bppfi log 153
browsing for Exchange objects 71
C
CCR 19
circular logging
and incremental backups 67
clients list
for backup policies 68
Cluster environment
and user-directed mailbox operations 86
clusters
performing backups in 80
Commit after last backup set is restored 90, 138
compatibility information 24
compression 65
consistency checks 25
configuring a pause in 119
of snapshot backups 115
copy backups 17, 67, 83
cumulative incremental backups 67
D
database circular logging
and incremental backups 67
database patch files 1920
debug logs 152
for backup operations 152
for restore operations 153
differential incremental backups 6667
directives
for Exchange databases 18
mixing directive sets 70
disaster recovery 130
alternate servers 149
Exchange 2000/2003 149
Exchange 2007 149
E
e0y.log 20
edb.log 20
Enable granular recovery 65
encryption 65
excluding folders and files from mailbox and public
folder backups 77
162
Index
F
features 13
files that are backed up for Exchange database
backups 17
full backups 20, 66
I
incremental backups
objects that are backed up 67
installation
adding a license key 28
prerequisites in a cluster 26
requirements for NetBackup software 24
instant recovery 65
configuring backup schedules for 132
enabling 130
instant recovery, in a cluster 139
instant recovery, policy recommendations 130
J
Java interface 49
K
Key Management Services (KMS)
restores of 93
user-directed backup of 83
L
LCR 19
license keys, adding 28
log files
how applied after a restore 88
where kept until database restored 88
M
Mailbox operations
case-sensitivity 70
character translation 85
mailbox operations
and required privileges 84
configuring NetBackup for backups and restores
of 50, 55
excluding folders and files from backups 77
mailbox restores
redirecting 104
MAPI Client 26
Mount database after restore 90, 138
multiple data streams 74
N
nbfsd log 153
nbfsd port 47
ncf log 153
NetBackup Client Service log on account,
configuring 53
O
off-host backups 135
Outlook and Exchange servers 25
P
patch files
how applied after restore 88
where kept until database restored 88
Point-in-Time Recovery (Replay only restored log
files) 89, 137
policy configuration
adding clients 69
attributes 64
for databases 64
overview 61
schedules 65
specifying objects to back up 70
testing 78
Policy type for restores 81
public folders operations
configuring NetBackup for 50, 55
excluding folders and files from backups 77
R
recovery
and cumulative incremental backups 67
and differential incremental backups 66
recovery storage group (RSG)
restoring a non-VSS backup to 95
redirected restores
of mailbox objects
to different paths 103
to different clients 81, 108
requirements for 108
to different paths 21
redirecting a restore
of a VSS backup, when the storage group has
more than one database 144
Index
redirecting a restore (continued)

of a VSS backup, when the storage group has
one database 142
replication backup, enabling for Exchange 2007 116
reports
client 156
media 156
operational 156
Restores
of a mailbox folder to a different folder 106
of mailbox objects 100
restores
and existing transaction logs 88
Exchange database 91, 97
failure of 87
from GRT-enabled backups, configuring storage
units for 62
Key Management Service (KMS) 93
mailbox objects to different paths 103
mailbox to a different mailbox 105
redirected
to different client 108
requirements for 91, 96
services which must be running 84
Site Replication Service (SRS) 93
snapshot client backups 138
storage group databases 91
storage groups 91
restores using Granular Recovery Technology
supported backup types 15
Retain snapshots for instant recovery 130
Roll-Forward Recovery (Replay all log files) 89, 137
snapshot operations 158

Snapshot verification I/O throttle 119
Source client for restores 81
SWF and instant recovery restores 127
T
tar log 153
temporary location for log and patch files 90, 138
testing policy configuration 78
transaction logs
and cumulative incremental backups 67
and differential incremental backups 66
and instant recovery 125
and troubleshooting 156
Point-in-time recovery 89
point-in-time recovery 137
replaying all 88
replaying those restored 88
roll-forward recovery 89, 137
troubleshooting 158
NetBackup debug logs 152
status of NetBackup operations 155
transaction logs 156
viewing Event Viewer logs on an off-host
server 154
U
user backups 67
V
virtual Exchange Server
specifying 80
S
schedules
adding 65
frequency 68
properties 68
Server to use for backups and restores 81
Services for NFS
Exchange clients that require 44
installing on Windows 2003 R2 SP2 44
Single Instance Store (SIS)
backups of 60
Site Replication Service (SRS)
user-directed backup of 83
Snapshot Client
backup limitations 113
what is backed up 114
W
wildcard characters
rules when using 76
supported 76
used to define groups of objects 75
Windows interface 49
163

NetBackup AdminGuide MSExchg Win 6.5.4 320793 PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetBackup AdminGuide MSExchg Win 6.5.4 320793 PDF

Uploaded by

Copyright:

Available Formats

Veritas NetBackup for

Microsoft Exchange Server

Veritas NetBackup for Microsoft Exchange Server

Telephone and Web-based support that provides rapid response and

Upgrade assurance that delivers automatic software upgrade protection

Global support that is available 24 hours a day, 7 days a week

Advanced features, including Account Management Services

Contacting Technical Support

Product release level

Available memory, disk space, and NIC information

Version and patch level

Router, gateway, and IP address information

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes

Licensing and registration

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and maintenance contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs or manuals

Maintenance agreement resources

Europe, Middle-East, and Africa

North America and Latin America

Additional enterprise services

Symantec Consulting Services provide on-site technical expertise from

Educational Services provide a full array of technical training, security

Technical Support ............................................................................................... 4

Introduction to NetBackup for Exchange

Installing NetBackup for Exchange Server .................... 23

Installing and configuring NFS for Exchange

Configuring NetBackup for Exchange Server ................ 49

Configuring the granular proxy server .......................................

Performing backups and restores of Exchange

Restore options for standard restores of Exchange

Using NetBackup for Exchange Server with

About configuration requirements for the Exchange Server ......... 119

Disaster Recovery of Exchange Server .......................... 149

Troubleshooting NetBackup for Exchange ................... 151

About backup operation debug logging .....................................

Index ................................................................................................................... 161

About NetBackup for Exchange Server

About NetBackup for Exchange features

About backup operations

About restore operations

About NetBackup for Exchange Server

About NetBackup for Exchange features

Introduction to NetBackup for Exchange Server

NetBackup for Exchange Server features

Minimal backup time

An administrator has the choice of to perform full or incremental backups (differential

Tight integration with NetBackup allows for the following:

Introduction to NetBackup for Exchange Server

NetBackup for Exchange Server features (continued)

Exchange backup and

Scheduled backups of individual storage groups and databases

User-directed backups of individual storage groups and databases

Restores of individual storage groups and databases.These restores can be performed