asked on
ESE 447 Database corruption
i have had this similar problem in the past. if i remember correctly we ended up using KB 810190 to fix it. i am getting this error message on my first storage group and the priv.edb is about 120gb. i have 2 other storage groups one is executive (14gb) and the other is manager (14gb). the ESE message is happening on the first storage group.
i was curious if i created a new storage group called department A and moved some of the mailboxes from first storage group to the new storage group, would the mailboxes be functional still? after moving them to a new storage or would i start getting the same ESE error on the new storage group?
if you could give me some options other than what is outlined in the KB that would be great.
thank you in advance.
i was curious if i created a new storage group called department A and moved some of the mailboxes from first storage group to the new storage group, would the mailboxes be functional still? after moving them to a new storage or would i start getting the same ESE error on the new storage group?
if you could give me some options other than what is outlined in the KB that would be great.
thank you in advance.
ExchangeEmail SoftwareWindows Server 2003
Last Comment
BBRazz
ASKER
so there is no way i can just move the users without having to run the processes outlined in KB810190. i was hoping to find a way around that. what is the worst thing that can happen if i moved the users without running the eseutil/ function?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
The moving of some mailboxes should remedy the issue, but you will have to run the processes outlined in KB810190 both Prior to and After the move to ensure that the data integrity remains.
Can you move your "Larger" exchange users into the new Storage Group and keep them seperated to reduce Storage Group/DB Sizes?