Because the server is old and has a high amount of volume. If you are thinking of committing the trans logs from a backup, that doesn't reset the sequence number.
From: Salvador Manzo [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 1:49 PM To: MS-Exchange Admin Issues Subject: Re: Consuming the available log sequence... Better question - why are the logs growing so much? On 1/8/08 13:39, "Barsodi.John" <[EMAIL PROTECTED]> wrote: Anyone come across this error before? ESE - " Information Store (3888) Storage Group 2: Log sequence numbers for this instance have almost been completely consumed. The current log generation is 940000 (0x000E57E0) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 108559 (0x0001A80F) 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. To reset the log sequence, you have to follow MSKB: http://support.microsoft.com/kb/830408 I was just curious if anyone has performed this process before and if there were any gotchas? Thanks, - John Barsodi ----- Salvador Manzo [ 620 W. 35th St - Los Angeles, CA 90089 e. [EMAIL PROTECTED] ] Auxiliary Services IT, Datacenter University of Southern California 818-612-5112 An avidity to punish is always dangerous to liberty. It leads men to stretch, to misinterpret, and to misapply even the best of laws. He that would make his own liberty secure must guard even his enemy from oppression; for if he violates this duty he establishes a precedent that will reach to himself. Thomas Paine, "Dissertation on First Principles of Government" ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
