MS Exchange Log Sequence Number

Has anyone managed to find a way of monitoring the Log Sequence Number on MS Exchange?

For those of you who've not encountered this issue, Exchange keeps a sequence counter of all the transaction log files it's used - note that this number is not used for the log file's name.

Depending upon the version of exchange this value varies but will at some point run out forcing you to intervene manually - see url www.office-outlook.com/.../ or google "Exchange Log Sequence Number reset"

It would be better to schedule this downtime but to date the only place I have found this sequence number is in the exchange server's Application Event Log as an Event ID 514.

Thanks,

Dog

Find more posts tagged with

ms_exchange

Accepted answers

All comments

battery

I too would also like to know if this is possible, we are manually checking the log sequence in the drive's at the moment & it would be very usefull to check this via snmp or similar.

aLTeReGo

Likely the simplest method of being alerted before this becomes a catastrophic event is to use the Windows Event Log Monitor in SAM to key off the 514 event (Sample Below).

Event Type: Warning

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 514

Date: 2/23/2009

Time: 11:19:35 AM

User: N/A

Computer: SRVEXBEL

Description:

Information Store (3956) First Storage Group: Log sequence numbers for this

instance have almost been completely consumed. The current log generation is

946000 (0x000E6F50) which is approaching the maximum log generation of

1048559 (0x000FFFEF), there are 102559 (0x0001909F) 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.