NetBackup™ for Microsoft Exchange Server Administrator's Guide
- Introducing NetBackup for Exchange
- Installing NetBackup for Exchange
- Planning the installation of NetBackup for Exchange
- Verifying the operating system and platform compatibility
- NetBackup server requirements for NetBackup for Exchange
- NetBackup client requirements for NetBackup for Exchange
- Exchange server software requirements for NetBackup for Exchange
- Snapshot Client configuration and licensing requirements for Exchange snapshot backups
- Installing the Veritas VSS provider for vSphere
- About the license for NetBackup for Exchange
- Configuring Exchange client host properties
- Configuring Exchange client host properties
- Exchange properties
- About backing up all or only uncommitted Exchange transaction log files with snapshot backups
- Configuring the Exchange granular proxy host
- About truncating Exchange transaction logs with Instant Recovery backups
- Truncating Exchange transaction logs by performing a backup to a storage unit
- About consistency checks options for an Exchange backup
- About the Exchange credentials in the client host properties
- Configuring the account for NetBackup for Exchange operations
- About configuring the account for NetBackup Exchange operations
- About NetBackup and Microsoft Exchange Web Services
- Creating a privileged NetBackup user account for EWS access
- Creating a minimal NetBackup account for Exchange operations
- About configuring the account for NetBackup Exchange operations with the right to Replace a process level token
- Configuring the Exchange hosts
- Configuring Exchange Granular Recovery
- About Exchange backups and Granular Recovery Technology (GRT)
- Configuring an Exchange backup that uses Granular Recovery Technology (GRT) (non-VMware backups)
- About installing and configuring Network File System (NFS) for Exchange Granular Recovery
- About configuring Services for Network File System (NFS)
- Disabling the Server for NFS
- Disabling the Client for NFS on the media server
- Configuring a UNIX media server and Windows clients for backups and restores that use Granular Recovery Technology (GRT)
- Configuring a different network port for NBFSD
- Disk storage units supported with Exchange Granular Recovery Technology (GRT)
- Disabling the cataloging for duplications of Exchange backups that use Granular Recovery Technology (GRT)
- Cataloging an Exchange backup or VMware backup that uses Granular Recovery Technology (GRT)
- Configuring the logon account for the NetBackup Client Service
- Configuring Exchange backup policies (non-VMware)
- About Exchange automatic, user-directed, and manual backups
- About configuring a backup policy for Exchange Server
- Policy recommendations for Exchange Server
- About policy attributes
- Adding schedules to a NetBackup for Exchange policy
- Adding clients to a NetBackup for Exchange policy
- Using physical node names in the clients list
- Adding backup selections to an Exchange policy
- Adding entries to the backup selections list by browsing
- Manually adding entries to the backup selections list
- Performing Exchange backups with multiple data streams
- Using multiple datastreams with Exchange Database Availability Groups (DAG)s
- Using wildcards in an Exchange backup selections list
- About excluding Exchange items from backups
- Configuring exclude lists for Exchange clients
- About Exchange backups and transaction logs
- About configuring snapshot backups of Exchange Server
- About configuring Instant Recovery backups of Exchange Server
- About Exchange Instant Recovery methods
- Policy recommendations for Exchange Instant Recovery
- About Storage Foundations for Windows (SFW) and Exchange Instant Recovery
- About configuration requirements for the Exchange Server when you use Instant Recovery
- About Exchange Instant Recovery with the Microsoft VSS Provider
- Configuring an Exchange snapshot policy with Instant Recovery
- Performing a manual backup
- Performing backups of Exchange Server, mailboxes, and public folders
- Performing restores of Exchange Server, mailboxes, and public folders
- About Exchange server-directed and redirected restores
- About selecting a destination client for an Exchange restore operation
- About restoring Exchange database data
- About existing Exchange Server transaction logs
- About restoring Exchange snapshot backups
- Options for Exchange snapshot restores
- Performing a snapshot restore of a Database Availability Group (DAG)
- Performing a snapshot restore of an Exchange standalone server
- Redirecting a Database Availability Group (DAG) snapshot backup to another database or to the recovery database (RDB)
- Redirecting an Exchange standalone server snapshot backup to another database or to the recovery database (RDB)
- Manually mounting an Exchange database after a restore
- About restoring individual Exchange mailbox and public folder items
- About special characters in Exchange mailbox folders and message subjects
- Prerequisites and operational notes for restoring Exchange individual mailboxes, mailbox folders, public folders, or messages
- Options for restores of Exchange Server mailbox objects or public folder objects
- Restoring Exchange mailbox or public folder objects
- About redirecting a restore of Exchange mailbox or public folder objects to a different path
- About using the command line to browse or restore Exchange granular backup images
- 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
- About restoring Exchange data from a VMware backup
- Enabling protection of passive copies of the Exchange database with VMware backups
- 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
- Exchange Server transaction log truncation errors
- Dynamic enforcement of path length limit for Exchange backups and restores
- Troubleshooting Exchange snapshot operations
- Troubleshooting Exchange jobs that use Granular Recovery Technology (GRT)
- Increased memory usage
- Troubleshooting DAG backups and restores
- Troubleshooting VMware backups
About Exchange 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 committed 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, each of which has its own set of transaction logs.
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 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.
The database transaction log for the Information Store is named EXXYYYYYYYY.log. XX is the database number (in hex). YYYYYYYY is the log file number (in hex). The size of the transaction logs is 1 MB.
After every 1 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.
Transaction logs get committed to their database over time or when the services are brought down. Any transactions that existed in log files and not in the database file are committed to the database.
Do not manually purge log files. Instead, purge logs through the backup process. For backups of a replicated copy (DAG), the log truncation is scheduled. It starts with the active copy when Exchange has the resources to start truncation. It does not happen instantly after a backup as with non-replicated copies.
For information on how transaction logs are truncated, see the following topics: