In Exchange 2007 / Exchange 2010, the maximum number of log files that can be reached before the log file sequence is exhausted is 7fffffec (2147483628). That’s a lot of log files!
In an attempt to warn administrators of when they are approaching the maximum log file, so a planned outage can be taken to reset the log generation, we implemented an ExBPA rule to inspect current log generation and provide a warning if approaching the maximum log file.
Here is a sample output.
Current transaction log generation for storage group ‘SG22’ on server EVS02 is nearing maximum value. Action must be taken to ensure that the databases do not stop.
Unfortunately the rule incorrectly calculates this value based on Exchange 2003. In Exchange 2003 the maximum log generation is FFFFF (1048575).
At this time this rule can be safely ignored for Exchange 2007 / Exchange 2010 servers. Application log messages can be monitored to ensure you are not approaching maximum log generation.