|
Clyde this is a 5.5 thing, and I have about 1040 mailboxes and a public
folder database of only 13 MB we don’t really use public folders. -----Original
Message----- Justin,
how many mail boxes and public folders do you have? An option that hasnt been
mentioned that may be good for you is to use a resource kit utility called
exmerge.exe to pull all user content and public folder content into pst files.
You can then remove and recreate the information store with no worries
(well, theres one that q262892 outlines how to get around) again, check with MS
PSS, expecially if you have an open ticket. This is a good option if you have a
small number of users. Or as
another option, create another information store in your "First Storage
Group\Mailbox Store" and move all your users to that datastore with AD
Users & Computers (worst case is that users loose connectivity to Exchange
and have to restart Outlook and/or reboot). You can then take the bad
information store offline and work on it. Theres some administrative tasks that
dont work with the default information store offline but that shouldnt affect
the users. Be sure and watch out for limited space though. As far
as having ALL of THAT on one box... Id be lying if I said I didnt cringe when I
read that. But... You should be able to stop/start the exchange 2000
services without impacting the other services of that server. I dont know of a
sure fire way to fix the issue without some inconvenience to the endusers.
But its better to inconvenience them now then lose their email later. Ever
see one of those movies where the villagers light the torches and make a dash
for the datacenter, er I mean castle? Clyde
Burns BTW sorry about the 5.5
specific info earlier, didnt realize this was an exchange 2000 thing. Need to
get my head out of the past... -----Original
Message----- The reason I am waiting on this is because this
server is my forest root, my Exchange server, my DNS server to the Internet, my
WINS server and my Intranet Server all in one. If I could find a way to fix the problem quickly while
fixing the server online I would avoid down time of all these services. Next years budget allows me to break apart these
services -----Original
Message----- No
offense Justin, but what are you waiting for? 1018s are bad news and the sooner
you get to work on this and follow PSS's recommendations the better. It will
bite you in the a$$ if you attempt to work around this. -----Original Message----- When you went through it did you have your users
working with out problems. My
users are currently experiencing no problems -----Original
Message----- Having been through this myself I'm only
going to add my condolences. One of our administrators was using her
Deleted Items folder to store all the stuff she wanted to keep. It was a
classic from the CDW commercials...."Fred? Where do you put all the e-mail
I delete?" Unfortunately, our DLT system had never been tested and our
first good backup was a week old. Poor planning on our part. I found myself
spending the night in the NOC doing eseutil commands on a 16Gb database and it
was taking 6 hours for any successful manipulation. (Copy over network to
working drive, perform ese..., recopy back to production drive, test for
completeness, etc, etc) I have a 3 inch binder of MS Knowledgebase Articles
about recovering Exch5.5. It's been well-thumbed and marked in the margins. Good Luck. -----Original Message----- Id go with what MS is recommending. Ive
gone both ways (with regards to Exchange 5.5) in restoring a known good
database and replaying the transaction logs and having to recover a corrupted
database. I would just make sure to copy off all the contents of your
exchsrvr\mdbdata contents somewhere else before trying the restore. Worst case
then is you can get Exchange back to its current state with a copy of your
priv, pub, and log files. Some things to check first though. Go into
the advanced tab under the server properties in the 5.5 admin program. (Org
-> site -> configuration -> server) See if you have circular logging
turned on or off. Ifs its off your ok with restoring the database from tape and
replaying the logs. If its on you may lose data by restoring an older priv and
pub.edb (though it don't sound like it if you have 500+ separate log files) One other thing to check should you decide
to go the 'repair what you have' route. eseutil /mh priv.mdb > output.txt Clyde Burns -----Original Message----- Hello everyone, I know this is off topic but you guys and
girls always give good advice. I have been getting event Ids 116, 118 and
200 a lot in my application log. The chain of events went like this I installed SP3 for W2K MS Support wants me to restore from the
day the HD failed after I rename the Have any of you done what MS is
recommending? Do any of you feel that this Any help is appreciated Justin A. Salandra, MCSE List info : http://www.activedir.org/mail_list.htm ------------------------------------------------------------------------------ |
Title: Message
- RE: [ActiveDir] OT: Exchange -1018 Error Shawn.Hayes
- RE: [ActiveDir] OT: Exchange -1018 Error Roger Seielstad
- RE: [ActiveDir] OT: Exchange -1018 Error Salandra, Justin A.
- RE: [ActiveDir] OT: Exchange -1018 Error Andy David
- RE: [ActiveDir] OT: Exchange -1018 Error Linton Smith (WBTQ)
- RE: [ActiveDir] OT: Exchange -1018 Error Salandra, Justin A.
- RE: [ActiveDir] OT: Exchange -1018 Error Salandra, Justin A.
- RE: [ActiveDir] OT: Exchange -1018 Error Morgan, Joshua
- RE: [ActiveDir] OT: Exchange -1018 Error Burns, Clyde
- RE: [ActiveDir] OT: Exchange -1018 Error Linton Smith (WBTQ)
- Salandra, Justin A.
