Storage Foundation 8.0 Quick Recovery Solutions Guide for Microsoft Exchange - Windows
- Introducing Quick Recovery for Microsoft Exchange
- Planning a Quick Recovery snapshot solution for Exchange
- System requirements
- Methods of implementing Quick Recovery snapshots
- Recommendations and best practices
- Configuring Exchange for Quick Recovery snapshots
- Implementing Exchange snapshot sets with the configuration wizard
- About the Quick Recovery Configuration Wizard
- Scheduling Exchange snapshot sets
- Scheduling or creating an individual snapshot set for Exchange
- Maintaining or troubleshooting snapshots
- Recovering Exchange mailbox databases
- Recovering after hardware failure
- About recovery after hardware failure
- Scenario I: Database and transaction logs volumes are missing
- Scenario II: Database volumes missing, transaction logs are available
- Refreshing the snapshot set on the current disks
- Moving the production volumes to different disks and refreshing the snapshot set
- Vxsnap utility command line reference for Exchange
About logs
Microsoft Exchange employs "write-ahead" logging to improve performance. As transactions occur, they are appended to a transaction log. Transactions are committed to the database when resources permit. A checkpoint file (E0n.CHK) tracks the location of the last transaction in the log files that has been successfully committed to the database. Transaction logs can be used to roll forward a database to achieve a point-of-failure recovery.
Note:
Do not enable the circular logging option. If circular logging is enabled, you will not be able to roll forward a database to achieve a point-of-failure recovery. Microsoft does not recommend circular logging in production environments. Refer to the Microsoft Exchange Server documentation for further details.