• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 411
  • Last Modified:

Exchange 2007 Event ID 447

Hello,
      I have found some errors in our Exchange 2007 server signaling corruption. In the Application logs it shows many Event 447 ESE errors. Everything seems to running fine but I want to make sure we are ok. We have 2 databases and the errors are reporting the corruption on database 2. It appears that this has been going on for several days so I do not want to do a restore from backup unless I absolutely have to. This db is about 100GB in size. Is it feasible to create a third database and move the current mailboxes from database 2 into database 3 one at a time? Would exchange check the integrity of each mailbox as it is moved and do you think this is a viable solution?

This is the error:

MSExchangeIS (4220) Second Storage Group: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 37, PgnoRoot: 86) of database D:\Exchsrvr\SG2\MDB2.edb (7391395 => 7391389, 5394274).


Thank you in advance.
0
daskas27
Asked:
daskas27
  • 2
1 Solution
 
gbarrientosCommented:
Moving mailboxes to a different database will fix any inconsistency as all items are moved one at a time. On the other hand, if an error is found the move will skip the corrupted item. If you want 0 loss, I would set the skip limit to 0. This way the mailbox wont be moved unless all items are good.
0
 
daskas27Author Commented:
I will attempt this solution this evening. Thanks.
0
 
daskas27Author Commented:
I have started migrating the mailboxes and everything seems fine so far. Thank you.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now