Veritas NetBackup™ for Microsoft Exchange Server Administrator's Guide
- Introducing NetBackup for Exchange
- Installing NetBackup for Exchange
- Snapshot Client configuration and licensing requirements for Exchange snapshot backups
- Configuring Exchange client host properties
- Configuring the account for NetBackup for Exchange operations
- Configuring the Exchange hosts
- Configuring Exchange Granular Recovery
- About Exchange backups and Granular Recovery Technology (GRT)
- About installing and configuring Network File System (NFS) for Exchange Granular Recovery
- About configuring Services for Network File System (NFS)
- Configuring Exchange backup policies (non-VMware)
- About configuring a backup policy for Exchange Server
- Adding schedules to a NetBackup for Exchange policy
- Adding backup selections to an Exchange policy
- About configuring snapshot backups of Exchange Server
- About configuring Instant Recovery backups of Exchange Server
- Configuring an Exchange snapshot policy with Instant Recovery
- Performing backups of Exchange Server, mailboxes, and public folders
- Performing restores of Exchange Server, mailboxes, and public folders
- About restoring Exchange snapshot backups
- About restoring individual Exchange mailbox and public folder items
- About redirecting a restore of Exchange mailbox or public folder objects to a different path
- Protecting Exchange Server data with VMware backups
- About protecting an application database with VMware backups
- About configuring a VMware backup that protects Exchange Server
- About configuring a VMware backup that protects Exchange Server, using Replication Director
- Troubleshooting backups and restores of Exchange Server
- About NetBackup for Exchange debug logging
- Viewing Event Viewer logs on an off-host Exchange server
- About NetBackup status reports
- Troubleshooting Exchange restore operations
- Troubleshooting DAG backups and restores
About restoring Exchange database data
Review the following information before you perform restores of Exchange Server:
The NetBackup for Exchange Agent supports a restore to the same Microsoft service pack (SP) or cumulative update (CU) on which the backup was originally created. Microsoft sometimes introduces database schema changes in SPs or CUs. If you restore to a different SP or CU level, the database server may not operate correctly.
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 database(s) may fail to mount.
You must dismount databases before you restore them.
To restore full and incremental backups, you can restore backups in one of the following ways:
Restore all the backups in a single operation.
The backup images must be of the same type. For example, you must restore full snapshot and a full VMware backups in separate restore jobs. You can, however, restore a full VMware backup and a differential snapshot in a single restore job.
When you restore all the backups in a single operation, NetBackup performs a commit after the last incremental is restored.
Restore the full backups and incremental backups individually.
When you restore the backups individually, deselect
for the full backup and all but the last incremental backup set. Select the following options when you restore the last incremental backup set: and .
If a restore job fails, check the temporary location (including subdirectories) to make sure log files from a previous restore job are deleted.
NetBackup copies logs to the Exchange working directory. After the database is restored, Exchange applies the log files from the temporary location to the database, and then it applies the current log files. After the recovery is complete, Exchange deletes the log files from the temporary location.
A restore of Exchange Server files always overwrites existing files. (For example, if
Pub.edb
already exists on the target server, it is replaced with the copy from the backup.)Review the information for existing transaction logs.
More Information