Exchange 2010 SP1, there are 4 databases. The default database is getting the Event ID 629 errors. Something to the nature of "While attempting to move to the next or previous node in a B-Tree, the database engine skipped over 851652 non-visible nodes in 2581 pages" I tried widening the maintenance window and nothing changed. At this point I am considering moving all my users from that database to a new database instead of running an offline defrag that will take hours. Anyone have any tips or guidance regarding this annoying issue? I dont know why it is happenning.

How much time did you give the DB to do maintenance Have you ensured that your maintenance window and backup window do not overlap? Moving the users to a new database might solve the problem but your going to have a fairly heavy overhead on the box evacuating all users to a new store, i.e. lots of logs etc so just plan for that in terms of disk space, CPU, IO, and also ensure you adjust your backup schedule to backup the new store etc. Troy Werelius www.Lucid8.com

Hi Aszyman, Any updates on your issue? Yes, according to my research, creating a new database & offline defrag are two workaround to the issue. Please also run EXBPA in the toolbox. Frank Wang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com 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.

What I meant to send Friday (forgot to hit submit...): "I have 6am-6pm excluded (business hours) and 2-3 hr window middle of the night to avoid the backups. I just realized that I didnt have Sat and Sun selected. I am going to give them all day both days and see if that clears anything up." After the weekend, Isee that there are still some 629 errors (4) from Sunday afternoon. I am going to watch them today and if I get any more then I am going to move ahead with my database migration. For some background, I am new to 2010 sort of, but about the time these started happening, was after our logs drive had run out of space and the Exchange Resouce monitor had stopped servicing clients. I expanded the drive, and performed a backup to clean up the logs. Everything seemed fine after that. Well.. except these annoying messages.

Well. I did a get-Mailbox Statistics on that DB in question, then added up the total sizes. Came out to ~17 GB while the actual database is more like 43 GB. Looks like a new DB is gonna be it, there is something up with this one.

Hi Aszyman, The White space is included in the 43GB. For details, please see this blog: WHITE SPACE EXCHANGE 2010, Where did 1221 Go? http://telnet25.wordpress.com/2011/01/30/white-space-exchange-2010-where-did-1221-go/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.

Thanks for the info. I was wondering where those events had gone. I ran that command on the database in question and it came out at 445 MB free. That is out of a 43 GB database and 17 GB of actual mailbox totals. Still seems unusually high to me. I am adding new storage today in order to start moving users. I will post back my progress. Thanks!

Could be the Recoverable Items i.e. Read these Understanding Recoverable Items http://technet.microsoft.com/en-us/library/ee364755.aspx Cleaning Up Recoverable Items http://technet.microsoft.com/en-us/library/ff678798.aspx Troy Werelius www.Lucid8.com

Hi Aszyman, Any updates?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.

I am about half done moving people over to a new database. I am doing a few departments at a time after hours so to avoid any issues during the day. Plus I am watching the log growth pretty closely when I do it. I can tell that I am not getting any 629 errors on the new database. I expect to be finished by Monday.

Update. I am still moving mailboxes. Things are going pretty well. I ran into one snag. I used the Exchange Management Console to move the new database from the default location to a larger data drive. Seemed fine. I then noticed my C: drive space being eaten up at an unusual rate. Found out that the search indexer service does not write the index data to the new location until you restart the service. So I restarted it and it began writing to the new location. Ok Good. So here is the question. Is there any reason I should not be able to delete the old Index data located here: C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Employees\CatalogData.... It is eating over a gig of my OS drive. Anyone know?

Yes check out this article for the proper steps http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspxTroy Werelius www.Lucid8.com

If I am understanding you right, as well as that article, I am good to delete the old catalog data since it was already rebuilt at the new database location. correct?

The article says to delete it before you rebuild but yes if the other one is built and you not having issues I believe you should be able to delete the older one that is now stagnant without issue.Troy Werelius www.Lucid8.com

Alright, here is what I am at. I have all my users migrated. I have all three arbitration mailboxes moved. One last question. What is the deal with the Discovery Search Mailbox? Should I move that just like I would any other user? Anything special about this I should be aware of? One other question not as important, If I run a command to list the mailboxes on the database that I am getting rid of the users still show up. I am pretty sure that it is just the disconnected mailboxes. Any ill effects from deleting a database while they are still showing up in the Disconnected Mailboes? I only ask because I know the move requests do need to be removed before I delete it. My current work around is to set the retention to 1 day on deleted mailboxes. Should all be gone tomorrow. Thanks for all your help. My new database is 27 GB vs the 45+ on the one with the 629 Event ID warrnings. Oh, and as far as the old catalog/index data. I deleted the old index data on C: without any ill effects. Since it started writing from scratch at the new location it was just like I deleted it anyways.

I am too impatient. I just moved the discovery mailbox. Piece of cake.