Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Check integrity of an individual mailbox
- Thread starter JCGSTL
- Start date
What are you looking for?
Corruption can exist at several different levels. At the top most level you have the 4K pages in the btree+ database. At this level, you're looking for the checksum of each page to determine if it is consistent with the data on the page.
Each page in a btree+ database can contain either data or indexes. The next level to scan is the indexes. Exchange is not like POP. Each message has a specific messageID, and is store only once in the database. You have majour inexes for messages and attachments, as well as indexes for views and such. Each "mailbox" is a collection of indexes representing folders, which contain indexes that point to entries in the message and attachment tables. Damage to an index would potentially impact more than one mailbox.
At the actual mailbox level, you can retrive the index for each folder and the item each pointer refrences for each email, attachment, etc. Finally, you can check the properties of each message to ensure they are consistent.
At the page level, you would use ESEUtil /k to check the consistency of the pages in the databases.
At the index level, you would use isinteg -test alltests to check all the indexes.
At the item level, you would read each item via MAPI; either move the mailbox to another store or exmerge the mailbox to a PST. An error will be logged in the application log for any items with corrupt properties. The text of the event will reference the corrupt item.
Corruption can exist at several different levels. At the top most level you have the 4K pages in the btree+ database. At this level, you're looking for the checksum of each page to determine if it is consistent with the data on the page.
Each page in a btree+ database can contain either data or indexes. The next level to scan is the indexes. Exchange is not like POP. Each message has a specific messageID, and is store only once in the database. You have majour inexes for messages and attachments, as well as indexes for views and such. Each "mailbox" is a collection of indexes representing folders, which contain indexes that point to entries in the message and attachment tables. Damage to an index would potentially impact more than one mailbox.
At the actual mailbox level, you can retrive the index for each folder and the item each pointer refrences for each email, attachment, etc. Finally, you can check the properties of each message to ensure they are consistent.
At the page level, you would use ESEUtil /k to check the consistency of the pages in the databases.
At the index level, you would use isinteg -test alltests to check all the indexes.
At the item level, you would read each item via MAPI; either move the mailbox to another store or exmerge the mailbox to a PST. An error will be logged in the application log for any items with corrupt properties. The text of the event will reference the corrupt item.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question
