Extensible Storage Engine (ESE) soft database failure: The drives storing the database are returning errors on some reads (for example, a -1018 error). |
Possible short outage.
Possible automatic failover. |
Automatic patching of bad page. |
Manual switchover, automatic failover, or online repair. |
Failed |
RAID rebuild, database and database copy repair, restore and run recovery then page patching, or page patching from copy. |
There may be other soft database failure codes.
Doesn't include NTFS file system block failures.
If failover or switchover is performed, host server is updated. |
ESE "semi-soft" database failure: The drives storing the database are returning errors on some writes. |
Short outage during automatic failover. |
Automatic volume/disk rebuilt after possible drive replacement. |
Dismounted if it can't be recovered. |
Failed |
RAID rebuild may solve the problem.
Copy and repair, restore and run recovery, or volume/disk rebuilt after possible replacement. |
An ESE semi-soft write error means some writes are successful.
Doesn't include an NTFS block failure. |
ESE "semi-soft" log failure: The drives storing the log data are returning non-recovered errors on some reads or writes. |
Short outage during automatic failover. |
Automatic volume/disk rebuilt after possible drive replacement. |
Dismounted if it can't be recovered. |
Failed |
RAID rebuild may solve the problem.
Copy and repair, restore and run recovery, or volume/disk rebuilt after possible replacement. |
An ESE semi-soft read/write error means some reads/writes are successful.
If the database fails, automated recovery will occur before log data recovery processing starts. |
ESE software error or resource exhaustion: An error where ESE terminates instance (for example, Event ID 1022, checkpoint depth too deep). |
Short outage during automatic failover. |
None. |
Dismounted if it can't be recovered. |
Failed |
Fix underlying resource issue. |
This failure could be the surfaced error of other cases. |
NTFS block failures: The drives storing the database or logs experiences a read or write error to an NTFS control structure. |
Short outage during automatic failover. |
Volume rebuilt after possible drive replacement. |
Dismounted if it can't be recovered. |
Failed |
RAID rebuild may solve the problem. NTFS utilities may solve the NTFS problems. Exchange recovery may be required. |
This event is more likely to occur when RAID isn't in use. If this event impacts the active log volume, some recent log files will be lost.
Doesn't include errors automatically corrected by NTFS or its underlying software or hardware stack. |
Database or log drive failure: A drive storing the database or logs has failed and is inaccessible. |
Short outage during automatic failover. |
Drive reformatted or replaced, followed by complete volume rebuild. |
Dismounted if it can't be recovered. |
Failed |
Drive replacement followed by possible RAID rebuild.
Drive replacement followed by complete volume rebuild.
Complete volume rebuild. |
Not applicable. |
Database or log volume failure: The volume fails due to NTFS or lower-level volume issues. |
Short outage during automatic failover. |
Drive reformatted or replaced. |
Dismounted if it can't be recovered. |
Failed |
Drive replacement followed by possible RAID rebuild.
Drive replacement followed by complete volume rebuild.
Complete volume rebuild. |
Not applicable. |
Database or log volume out of space: The NTFS file system with the database or log files is out of space. |
Automatic failover if other copy isn't in similar state. |
None. |
Dismounted. |
Failed |
Run full or incremental backups, manually delete logs, let time pass, resume database copy, or repair failed database copy. |
Not applicable. |
Administrator dismounts the wrong database. |
If automatic failover isn't blocked by the administrator, there will be a short outage.
If automatic failover is prevented, there will be an outage until the database is mounted. |
None. |
Dismounted. |
Not applicable |
Administrator corrects the error. |
Not applicable. |
Administrator suspends the wrong database copy. |
Depending on configuration and impacted copy, auto recovery may be prevented. |
None. |
Not applicable. |
Suspended |
Administrator corrects the error. |
Not applicable. |
Administrator dismounts a database for storage, NTFS, or volume maintenance. |
If automatic failover isn't blocked by the administrator, there will be a short outage.
If automatic failover is blocked, there will be an outage until the administrator completes the task. |
None. |
Dismounted. |
Not applicable |
Administrator completes the task. |
Not applicable. |
Administrator suspends a database copy for storage, NTFS, or volume maintenance. |
Depending on configuration and impacted copy, auto recovery may be prevented. |
None. |
Not applicable. |
Suspended |
Administrator completes the actions. |
Not applicable. |
Administrator dismounts a database for offline database maintenance. |
Outage until repaired. |
None. |
Dismounted. |
Suspended |
Administrator completes the actions. |
Active and passive database copies are diverged.
Administrator must suspend copies. |
Storage area network (SAN), disk, or storage controller failure. |
Short outage during automatic failover. |
None. |
Dismounted. |
Any |
Repair hardware. |
A passive database copy will be in the state that existed at the time when the system failed. |
Server hardware maintenance. |
Short outage during automatic failover (unless blocked by an administrator). |
None. |
Dismounted. |
Any |
Complete actions. |
A passive database copy will be in the state that existed at the time when the system was shut down. |
Server software maintenance. |
Short outage during automatic failover (unless blocked by an administrator). |
None. |
Dismounted. |
Any |
Complete actions. |
A passive database copy will be in the state that existed at the time when the system was shut down. |
Microsoft Exchange Information Store service is stopped or paused by an administrator. |
Short outage during automatic failover. |
None. |
Dismounted. |
Any |
Restart the Microsoft Exchange Information Store service. |
Not applicable. |
Microsoft Exchange Information Store service fails; operating system is still running. |
Short outage during automatic failover. |
Service Control Manager restarts the Microsoft Exchange Information Store service. |
Dismounted. |
Any |
Manually or automatically restart the Microsoft Exchange Information Store service. |
A passive database copy will be in the state that existed when the Microsoft Exchange Information Store service failed. |
Partial Microsoft Exchange Information Store service failure; some part of the Exchange store stops functioning, but it's not identified as failed. |
Possible short outage during automatic failover. |
None. |
Mounted and partially functional. |
Any, but may be only partially functional |
Restart server, operating system, or Microsoft Exchange Information Store service. |
Not applicable. |
Server failure: The server fails for one of the following reasons: - Complete power failure
- Unrecovered failure of the processor chip, motherboard, or backplane
- Operating system stop error
- Operating system stops responding
- Complete communication failure
|
Short outage during automatic failover. |
Restart computer. |
Dismounted. |
Any |
Restore power, change operating system settings, change hardware settings, replace hardware, restart operating system, service operating system, service hardware, or repair communication problems. |
Not applicable. |
DAG experiences a quorum failure. |
Outage until repaired. |
None. |
Dismounted. |
Any |
Repair failed quorum, assign new quorum, or restore the network that's causing quorum failure. |
A passive database copy will be in the state that existed at the time when the system failed. |
MAPI network communication failure: The server is no longer available on the MAPI network. |
Short outage during automatic failover; must be lossless. |
None. Communication continues to be attempted. |
Dismounted. |
Any |
Fix communication problem by correcting hardware or software issues. |
Not applicable. |
Replication network communication failure: The server can't receive heartbeats, log copies, or seed through the failed replication network. |
Possible short copying or seeding outage while the workload is switched to other network. |
None. Communication continues to be attempted. |
None. |
Any |
Fix communication problem by correcting hardware or software issues. |
Resiliency impacted by failure. |
Multiple network communication failures: The server can't receive heartbeats, log copies, or seed through multiple networks. |
Short outage during automatic failover; must be lossless. |
None. Communication continues to be attempted. |
Dismounted. |
Any |
Fix communication problem by correcting hardware or software issues. |
At least one network is still functional. |
Partial failure of one or more networks: Networks experience high error rates. |
Failure not detected; no action. |
None. |
Mounted, but possible performance issues. |
Any |
Fix communication problem by correcting hardware or software issues. |
Network experiences higher than normal error rates. |
Undetected operating systems hang: Operating system stops responding but it's not detected by monitoring or clustering. |
None. |
None. |
Any. |
Any |
Restart or terminate the resources that aren't responding. |
Hang isn't detected so no action is taken.
Some functionality may be operational. |
Operating system drive experiences a failure. |
Short outage during automatic failover. |
None. |
Dismounted. |
Any |
Replace drive and rebuild server or rebuild volume by using RAID. |
Not applicable. |
Operating system drive out of space. |
Short outage during automatic failover. |
None. |
Dismounted. |
Any |
Manually free space on the volume. |
Not applicable. |
Drives containing Exchange binaries experience a volume or drive failure. |
Short outage during automatic failover. |
None. |
Dismounted. |
Any |
Replace drive and reinstall application or rebuild volume by using RAID. |
Not applicable. |
Drive containing the Exchange binaries is out of space. |
Short outage during automatic failover. |
None. |
Dismounted. |
Any |
Manually free space on the volume. |
Not applicable. |
Invalid new log detected: The log sequence is disrupted by an existing file. |
Short outage during automatic failover; assume other copies don't have the same problem. |
None. |
Dismounted. |
Failed |
Remove disruptive logs after determining source. |
The disruptive logs shouldn't replicate. |
Continuous replication detects invalid log: Replay detects an inappropriate log during copy or replay. |
Not applicable. |
Discard log. |
Not applicable. |
Failed |
Discard invalid log; move impacting log stream. |
Not applicable. |