IdiotOutside
asked on
ESEUTIL Options - Help Needed.
Having found out there are checksum error's in the priv.stm and found the solution (using ESEUTIL /r or /p) on the database i have come across another issue.
In the documentation it states i need 110% free space for ESEUTIL to work, i have a 90GB mail store and not enough free space to accomodate the 110% extra.
Can i take an offline backup of prov.edb and .stm and move them to another server where there is sufficient space and point eseutil at them to complete the process then once this is complete move them back?
Or because i am using enterprise edition i have the option of creating another mailbox store, if i did this and simply moved all my mailboxes over to the new store would this just move the corruption?
Obviously i need to keep downtime to a minimum.
OS is Windows 2003 SP1 with Exchange 2003 Enterprise.
Thanks!
In the documentation it states i need 110% free space for ESEUTIL to work, i have a 90GB mail store and not enough free space to accomodate the 110% extra.
Can i take an offline backup of prov.edb and .stm and move them to another server where there is sufficient space and point eseutil at them to complete the process then once this is complete move them back?
Or because i am using enterprise edition i have the option of creating another mailbox store, if i did this and simply moved all my mailboxes over to the new store would this just move the corruption?
Obviously i need to keep downtime to a minimum.
OS is Windows 2003 SP1 with Exchange 2003 Enterprise.
Thanks!
You could move the Database file to a larger drive and the run the tool
Hi,
If space is a constraint, use the /T swtich with ESEUTIL to redirect the temp database to another drive on the same server .
http://support.microsoft.com/kb/192185
Thanks
Nitin
If space is a constraint, use the /T swtich with ESEUTIL to redirect the temp database to another drive on the same server .
http://support.microsoft.com/kb/192185
Thanks
Nitin
providing you have space on the same server
Need not be same servetr - it could be a mapped drive also !!!!
Working with many big clients has one common resolution for such issues - if you are blessed with enterprise edition of exchange and ofcourse required HDD space - use the option that is used with maximum time. MOVE MAILBOX - this would ensure that your downtime is least (since you cannot move all mailboxes at one go) - also if the move mailbox option fails for particular set of users - you can safely bet that those ones are corrupted - next option would be to simply take their info out into PST - create new mailbox on new store - import PST / simply hand them over the PST and ask them to work with blank mailbox.
Hence, i would go with the option
"because i am using enterprise edition i have the option of creating another mailbox store, if i did this and simply moved all my mailboxes over to the new store would this just move the corruption?"
Hence, i would go with the option
"because i am using enterprise edition i have the option of creating another mailbox store, if i did this and simply moved all my mailboxes over to the new store would this just move the corruption?"
Good to know that we have great people answering - Well, I am also working for the world's biggest IT Services company in as Subject Matter Expert in Messaging, being mentored as an Architect !!
I would not recommend Moving Mailboxes as a solution as space is a constraint here and physical size of EDB will as such not reduce (magically) by moving mailboxes !
I would not recommend Moving Mailboxes as a solution as space is a constraint here and physical size of EDB will as such not reduce (magically) by moving mailboxes !
No space will be freed up from moving mailboxes - until a defrag
ASKER
Thanks for all the quick replies folks - much appreciated.
I have 40GB free space on the server, its not disk space that is really the problem. the corruption is my main concern. the lack of space is only a problem if i need to do a defragmentation.
So really the question now is.. if i create another store and move mailboxes say one at a time.. would this move the corrupted data to the new store?
Or do i need to run the ESEUTIL with the /r /T command as the safest bet?
Once again thanks for quick reply!
I have 40GB free space on the server, its not disk space that is really the problem. the corruption is my main concern. the lack of space is only a problem if i need to do a defragmentation.
So really the question now is.. if i create another store and move mailboxes say one at a time.. would this move the corrupted data to the new store?
Or do i need to run the ESEUTIL with the /r /T command as the safest bet?
Once again thanks for quick reply!
ASKER
Or are you saying that the origional db size will not shrink when i move the mailboxes to the new store! - hence i will have disk space issues.. :o)
If downtime is an issue, forget about ESEUtil.
Move mailboxes to a new database - depending on the whitespace you have in the current database, it may fit. Alternatively, add harddrives.
Unless you have a 10Gb network, dont try anything over the network
Move mailboxes to a new database - depending on the whitespace you have in the current database, it may fit. Alternatively, add harddrives.
Unless you have a 10Gb network, dont try anything over the network
40GB is your total free space? On all drives?
ASKER
I have the database files on a seperate partition to the log files, it has just under 49GB of free space (since i moved some old exported PST's to another server)
There is no option to add extra disk as server is ageing and has all drive bays full. Am i right in thinking an offline defrag is the only way to shrink the current database (and this is what takes the time).
Is there a way to run the repair on only the stm file ( this is where the corruption is according to the evet log) this file is only 23GB in size so i would have the free space (just) to do this.
Cheers
There is no option to add extra disk as server is ageing and has all drive bays full. Am i right in thinking an offline defrag is the only way to shrink the current database (and this is what takes the time).
Is there a way to run the repair on only the stm file ( this is where the corruption is according to the evet log) this file is only 23GB in size so i would have the free space (just) to do this.
Cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the reply Exchange Geek. I dont think i'll have the disk space on the exchaneg box to be able to create an extra store on it and move the mailboxes into the new store
Another thought i have had is to to hire a DR server with plenty of Disk - install it with exchange in the same exchange organisation - move the current mailboxes from our server to the temp DR server. (meaning we'll have little downtime) then delete the current message store on our server and recreate a new one. Then move the mailboxes back. Once complete remove the the temp DR server from the exchange organisation.
What do you think?
Cheers!
Another thought i have had is to to hire a DR server with plenty of Disk - install it with exchange in the same exchange organisation - move the current mailboxes from our server to the temp DR server. (meaning we'll have little downtime) then delete the current message store on our server and recreate a new one. Then move the mailboxes back. Once complete remove the the temp DR server from the exchange organisation.
What do you think?
Cheers!
Perfect Game plan.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Kieran and Exhcange Geek - i will price up the sata option ( i may be able to call in a favour to hire a DR server) Im sure the FD will want to go for the cheapest option! :)
Once again Many Thanks!
Once again Many Thanks!