Log sequence numbers for this instance have almost been completely consumed. The current log generation is %1 which is approaching the maximum log generation of %2, there are %3 log generations left to be used. To begin renumbering from generation 1, the instance must be shutdown cleanly and all log files must be deleted. Backups will be invalidated.
Log Generation Loss Resiliency Depth represents the amount of work, in number of log files, that may be lost while still ...
Log Record Stalls/sec is the number of log records that cannot be added to the log buffers per second because they are full. ...
Log repair failed because temporary log file '{0}' was corrupted after transfer from the active copy on server '{1}'. Error: ...
Log replay for database '{0}' on machine '{1}' is falling behind and Exchange isn't able to keep up with log copy and inspection. ...
Log sequence numbers for this instance have almost been completely consumed. The current log generation is %1 which is approaching ...
Log sequence numbers for this instance have almost been completely consumed. The current log generation is %4 which is approaching ...
Log Threads Waiting is the number of threads waiting for their data to be written to the log in order to complete an update ...
Log truncation failed because not all log files required for recovery were successfully copied. For more information, click ...
Log truncation for database '{0}' could not be coordinated between the active copy on '{1}' and the passive copy on '{2}' ...