Backup
Backup |
|
Although the Exchange directory and information store services are independent of each other, they are built on top of Jet databases.
The Exchange services are backed up online with the data divided into two parts: the database, and the transaction logs and patch files. The transaction logs can be backed up independently from the database during an incremental backup. Backup determines which services are running on the specified server.
Note
To restore, the Exchange service needs the database and a sequential list of transaction logs. If circular logging is enabled on Exchange services, it is not possible to perform a no-loss restore. A no-loss restore uses the log files that reside on the system prior to the restore along with the restored log files to bring the system data to a state just before the crash. Thus if circular logging is enabled, then the existing logs must be deleted. After the restore, the system data is at the state it was just after the backup.
If the log file path is not set, a new log is created on the default directory. Otherwise, the existing log files are used.
Exchange services are restored offline. To perform the restoration, Backup stops the associated services. The Win32 Service Manager functions are used to control the services.