GOexchange® can initiate, monitor, and report Documents that provides summary and detailed information regarding a planned specification An object that represent the actions to take on an Exchange Server. Operators can select from a series of scripts to run against one or all databases, as well as custom processes, notifications backup actions and more. that has completed. the state of an Offline or Online Exchange backup job before and after Exchange maintenance .
When an Exchange server is operational and Information stores are mounted, it is Online and available for transactions. An Online Backup Backup job An object that represent the actions to take on an Exchange Server. Operators can select from a series of scripts to run against one or all databases, as well as custom processes, notifications backup actions and more. performed while the Information Store Message Store provider for Microsoft Exchange Server. There are 2 types of message stores used in Microsoft Exchange Server: public folder store and mailbox information store. is still mounted. This type of backup allows users to work without interruption. Online backups also automatically clear the database logs upon completion. job is performed while the Exchange Server Information Store is still mounted, thereby allowing internal and external clients to continue operations without interruption. This type of backup is available through the use of Exchange Backup Agents provided by third party backup solution provider's.
When the Exchange services are properly stopped all the outstanding transactions are immediately committed to the appropriate Information Store database, Exchange is now Offline a no internal or external clients may submit transactions or access the Exchange system.
An Offline Backup job is performed while the Information Store is not mounted. This backup is basically a file level copy of the Information Store databases and other exchange related files.
With the exception of the MTA Error Correction and Online Exchange Backup scripts the GOexchange® maintenance scripts are Offline processes, i.e. any database selected for maintenance is dismounted and unavailable for access of any kind.
The "Preventative Maintenance" script includes defragmentation of the selected Information Stores. In short the defragmentation process creates an entirely NEW Information store. Therefore, the signature on the Exchange databases are changed making it incompatible with any previous Online Backups of databases as well as any previously created Transaction .LOG files. The benefit of Creating an OFFLINE Backup is that you are taking an absolute snapshot of the Exchange Information Stores and the supporting transactions logs just prior to the maintenance process.
Using an Offline Backup provides an absolute way to restore the Exchange system to its last known state or specific "point in time" including any Transaction .LOG files. Therefore, as a safety net and roll back position we highly recommend that an Offline Backup of specific Exchange directories, files and Windows system registry or system state be made before maintenance is started. For information see; "How to determine which files to backup with an Offline Backup"
Proceed to Backup Actions
See also:
Back to Create and Assign Event Notifications
NOTE: Adjust your normally scheduled Backup jobs to ensure that they do not attempt to backup the Exchange server during GOexchange maintenance. If a normally scheduled backup job attempts to access the Exchange Server during maintenance, the backup job and the GOexchange maintenance job will fail.