Log corruption on the active copy was detected. The local copy of database '%1' shouldn't be used until after disk diagnostics are performed. Recovery was attempted by marking this copy as Failed and attempting to fail over to another available copy. If the failover attempt doesn't succeed, the database will remain dismounted until it's mounted using the -Force option. Before mounting the database, all passive copies that need the corrupted log should be suspended.
Log Bytes Generated per second is the rate at which data is added to the log. This is different from Log Bytes Write per ...
Log Checkpoint Depth as a % of Target is an expression of the current checkpoint depth in terms of a percentage of the checkpoint ...
Log copy and inspection for database '{0}' on machine '{1}' is falling behind and Exchange isn't able to keep up with new ...
Log corruption on the active copy was detected. The local copy of database '%1' shouldn't be used until after disk diagnostics ...
Log corruption on the active copy was detected. The local copy of database '%1' shouldn't be used until after disk diagnostics ...
Log file %1 is damaged, invalid, or inaccessible (error %2) and cannot be used. If the log file cannot be found, the databases ...
Log file %1 is damaged, invalid, or inaccessible (error %2) and cannot be used. If the log file cannot be found, the databases ...
Log file %1 is damaged, invalid, or inaccessible (error %2) and cannot be used. If this log file is required for recovery, ...
Log file %1 is damaged, invalid, or inaccessible (error %2) and cannot be used. If this log file is required for recovery, ...