I read somewhere that the only ways to commit logs onto the DB are full backup of the DB and online maintenance. Is there any other way like script or something like that?

On Sun, 15 Apr 2012 00:39:57 +0000, Jose Rebellon, MCP, MCTS wrote: >I read somewhere that the only ways to commit logs onto the DB are full backup of the DB and online maintenance. Is there any other way like script or something like that? Log files hold both committed and uncommitted transactions. Full backups don't "commit" anything, they just remove the log files that contain only committed transactions. Any log file that contains an uncommtted transaction remains on the disk. Dismounting the database usually commits everything in the log files. What are you trying to accomplish? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

To commit all the log files into database you should dismount the mailbox database. When the database is in mounted state the Database is in dirty shutdown state. Once you dismount the databas all the log gets commited to database and database state becomes clean shutdown. XADM: Using Eseutil to Determine Which Logs Have Been Committed http://support.microsoft.com/kb/182961 Though above article says it applies to Exchange 5.5 n 2000 but its the same command for all the exchange version Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hasnain Shaikh| My blogs: http://messagingserversupport.com

On Sun, 15 Apr 2012 00:39:57 +0000, Jose Rebellon, MCP, MCTS wrote: >I read somewhere that the only ways to commit logs onto the DB are full backup of the DB and online maintenance. Is there any other way like script or something like that? Log files hold both committed and uncommitted transactions. Full backups don't "commit" anything, they just remove the log files that contain only committed transactions. Any log file that contains an uncommtted transaction remains on the disk. Dismounting the database usually commits everything in the log files. What are you trying to accomplish? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP Our DB is now at 55 GB. When I perform full backups, most of the logs disappear and when it starts online maintenance. Where can I find uncommitted logs? Besides full backups and online maintenance, should I also dismount the DB and clear "whitespace"?

Rich, We are using Exchange 2007 Standard Edition, which I read that there is a "soft" threshold of 50GB DB. However, there is a registry key to override this. Have you ever seen a DB dismount due to this threshold? Thanks.

Hi 1. It would seem that the default installation of Exchange Server 2007 Standard Edition does not immediately start off with this "unlimited" size. It actually has a default limit of 50 GB per Database. If you dont modify regedit value, it will cause you problem. This blog is interesting. http://technet.microsoft.com/en-us/library/bb232092(v=exchg.80).aspx 2. If you run full backup, it just remove committed transactions.Terence Yu TechNet Community Support

On Mon, 16 Apr 2012 00:24:09 +0000, Jose Rebellon, MCP, MCTS wrote: >>>On Sun, 15 Apr 2012 00:39:57 +0000, Jose Rebellon, MCP, MCTS wrote: >>>I read somewhere that the only ways to commit logs onto the DB are full backup of the DB and online maintenance. Is there any other way like script or something like that? >>Log files hold both committed and uncommitted transactions. Full backups don't "commit" anything, they just remove the log files that contain only committed transactions. Any log file that contains an uncommtted transaction remains on the disk. Dismounting the database usually commits everything in the log files. >>What are you trying to accomplish? >Our DB is now at 55 GB. When I perform full backups, most of the logs disappear and when it starts online maintenance. The online maintenance doesn't remove log files. Log files are removed by the system attendant service as part of the backup process. >Where can I find uncommitted logs? In the directory you've nominated to hold those log files. But not every log file in the directory contains uncommitted transactions. In fact, most of them don't. If you know what transaction logs contained only committed transactioos, what would you do with that information? >Besides full backups and online maintenance, should I also dismount the DB and clear "whitespace"? Log files are records of the modifications made to the database, they aren't the database. Whitespace is unused space within the database; a log file has no whitespace within it. Dismounting a database won't remove the whitespace from within it. If you're asking about reaching the limit for a databases maximum size you should know that: 1. The size of the file on disk isn't the criterion. 2. The size of the data within the file is the criterion. 3. You can increase the limit on the database size. To see the steps you need to take to raise the size limit, see this KB article: http://technet.microsoft.com/en-us/library/bb232092(v=exchg.80).aspx --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Mon, 16 Apr 2012 00:47:21 +0000, Jose Rebellon, MCP, MCTS wrote: > We are using Exchange 2007 Standard Edition, which I read that there is a "soft" threshold of 50GB DB. However, there is a registry key to override this. Have you ever seen a DB dismount due to this threshold? Thanks. Have I? No, we don't use the "standard" edition for mailbox servers. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Terrence, 1) What kinds of problems will I run into if DB goes beyond 50GB? Can you be more specific. I read that the DB would dismount and I would just need to mount it. 2) I have been running full backup to "remove committed transaction" logs. Should I dismount it too like Hasnain mentioned above?

Hi 1) Database will be dismounted. You should modify database limit and reboot server and mount database again. 2) Please read Richs post. His answer is perfect. If you want to save capacity , dismounted database is useless. Dismounted database just commit uncommitted log to database. If it is not necessary, I wont dismount database. It will affect all the users. Terence Yu TechNet Community Support