Greetings, I'm recently getting Event ID 514 in my aplication log on my exchange 2003 server which states: Log sequence numbers for this instance have almost been completely consumed. The current log generation is 932000 (0x000E38A0) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 116559 (0x0001C74F) 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. The part of this that I (and my boss) find alarming is the "Backups will be invalidated" bit. We run full backups nightly, after I run the Troubleshooting Assistant (the prescribed fix) does this mean that any previous backups I have of the four databases in the the affected storage group are now useless? Could someone here clarify? Thanks in advance p

Have you clarified that the Full Backups you are performing are purging your transaction logs?MVP Exchange Server

What that means is that if you have to do a restore, all subsequent log files won't be able to play into the database. So, be sure to take a backup before and after performing the procedure. Refer to this post for more information. http://support.microsoft.com/default.aspx?scid=kb;EN-US;830408 Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Useless in the sense that you wont be able to replay logs from the previous backups against the new store since it has a new signature. Like Ed says, get a full backup after you do this and you will be fine.

Hi, Event ID 514 is indicating that Log sequence numbers for this instance have almost been completely consumed. You need to renumbering the sequence number of the log file. please perform below steps: 1. Dismount the database {which sending event ID 514} 2. Ensure database clean shutdown for use Eseutil/mh. 3. Go to the drive where you have hold log {check through database properties, log file path} select folder and move folder to some other drive where you have sufficient disk space. 4. mount database. 5. check the drive, new folder is automatic create with all .chk & logs. 6. run full backup. Dinesh

On Sun, 3 Oct 2010 07:02:28 +0000, Dinesh111 wrote: >Event ID 514 is indicating that Log sequence numbers for this instance have almost been completely consumed. You need to renumbering the sequence number of the log file. please perform below steps: > >1. Dismount the database {which sending event ID 514} Not just that database, but ALL databases in the storage group. Remember, log files are a storage group resource, they aren't associated with just one database. >2. Ensure database clean shutdown for use Eseutil/mh. > >3. Go to the drive where you have hold log {check through database properties, log file path} select folder and move folder to some other drive where you have sufficient disk space. Don't forget to include the *.chk file, which may not be in the same directory. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP