|
|
 |
 |
Your Exchange Server has failed. Now what?
GOexchange® Preventive Maintenance can alleviate unfortunate situations like this by ensuring system errors and corruptions are removed before they can cause a major issue; however, it is not a disaster recovery tool. Fortunately, Lucid8 expert technicians can help.
Most of the time corruption and database inconsistencies are caused by one or more of the following scenarios:
Lack of Maintenance - Exchange databases tend to be subject to corruption. Many times, this corruption starts as a minor database glitch. If the databases are not properly maintained then as time goes on the problem escalates. When this happens, you may not even notice a problem until you stop and try to restart the Exchange services, only to find that they won't start. The scary thing about a situation such as this is that it often means that you've been backing up corrupt data for an extended period of time, and your backups
may only contain corrupted data.
Improper shutdown - Exchange must commit all transactions from the log files to the databases in order to be consistent, therefore if a system is improperly shut down by an individual and or a server loses power the databases can become inconsistent and corrupt. Exchange will try to correct these issues upon a restart but sometimes it just can't make the corrections, therefore the databases will simply not start/mount.
Hardware - Server Hardware such as bad memory, failing hard disk and faulty motherboards can play havoc with an Exchange database.
So what do I do now?
|
|
 |
|
|
|