Hi, I'm having a problem with my two Exchange Servers. During the scheduled maintenance period, I can see multiple event 700 and 701. All the events 701 state that the online defragment was successful. The strange thing is that a new defrag operation (for each SG) starts every 30 minutes, even when it says on the event 701 that it should only run once each 24 hours. Another strange thing shows up on the logs. Event 701 states that "Since the database was created, it has been fully defragmented 1757 times over 1757 days. " The thing is: this servers were installed one year ago. No SG or DB where reused. So how can Exchange think that 1757 days have pasted since? What I already tried: - Create a new SG to see if it would be properlly handled. - Stopped all backup software. - Offline Defrag a test database All of this resulted in the same erratic behavior. After one day, Exchange already defraged more that 4 times and thinks that more than 4 days have passed. Does anyone has any idea on what is going on, and how to fix this? Thanks, Ricardo Btw, the event: Event Type: Information Event Source: ESE Event Category: Online Defragmentation Event ID: 700 Date: 10-06-2009 Time: 2:00:00 User: N/A Computer: EPSILON Description: MSExchangeIS (360) System Accounts Store: Online defragmentation is beginning a full pass on database 'K:\DATABASE\Mail Database.edb'. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Information Event Source: ESE Event Category: Online Defragmentation Event ID: 701 Date: 10-06-2009 Time: 2:00:00 User: N/A Computer: EPSILON Description: MSExchangeIS (360) System Accounts Store: Online defragmentation has completed a full pass on database 'K:\DATABASE\Mail Database.edb', freeing 1 pages. This pass started on 10-06-2009 and ran for a total of 0 seconds, requiring 1 invocations over 1 days. Since the database was created, it has been fully defragmented 1757 times over 1757 days. For more information, click http://www.microsoft.com/contentredirect.asp.

Hi,That is normal.See: It is possible that this process does not complete before the time indicated by the Microsoft Exchange Information Store service. In such a case, the ESE engine stores the last table successfully processed. At the next occurrence of Online Defragmentation, ESE selects the next table in the metadata, and will resume processing tables until the maintenance window ends.. If online defragmentation can process all tables before the maintenance window ends, it will restart at the first table listed in the metadata and loop on all tables until the maintenance window ends. The changes made to the database are transacted. Therefore, a large number of delete operations, followed by an online defragmentation cycle, will generate a large number of transaction logs, because records are compressed into the fewest number pages. From http://technet.microsoft.com/en-us/library/aa996226(EXCHG.65).aspxLeif

Thanks. But, are you sure? I still found the following strange: - Exchange states that it has done a full pass on the database. So, if it was full, why repeat the pass 30 minutes after? - Exchange stating that "it has been fully defragmented 1757 times over 1757 days", when only 365 have passed since the server was installed? Offline defrag resets the count, but after one day, Exchange already states that 4 days have passed. - Exchange starts a new "Online Defragmentation" every 30 minutes, and it only runs for 0 seconds. - Exchange tries to defrag a small SG (not even 1 GB in size), that never does not change over the maintanance period, 5-6 times per maintenance period - Exchange states that this opeartions is only required to run 1 time a day ("...requiring 1 invocations over 1 days."). - The link you gaved me says that "This [online defragmentantion] process will run for at least 15 minutes at the end of the maintenance window." I only have one mainenance window defined (the default 1 to 5 am). That doesn't sound normal to me... Do your servers behave the same way? Regards, Ricardo Duarte