Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 412
  • Last Modified:

Exchange server crashed....before any data transfered....how to proceed?

Got a new server and installed 2008 R2 and Exchange 2010. Server started acting crazy and network ports stopped working. Got motherboard replaced and all was well....for about 4 hours. Server would just power off. Told HP to give me a new sever which will be here tomorrow. I don't trust the Windows install 100% after so many hard power cycles so I wondering how I should handle it.

No data was ever transferred into Exchange. I only set up send/receive connectors and a few other things. Was going to do the heavy lifting after-hours.

Figure I need to either try and uninstall Exchange 2010 from failed server, remove from domain, install new server or scrap everything, install everything from scratch. Or would I do a DR install of Exchange 2010?

Appreciate any input.
0
mvalpreda
Asked:
mvalpreda
  • 9
  • 8
  • 5
1 Solution
 
Exchange_GeekCommented:
If you believe you had a good installation, might as well perform a DR followed by installation of SP2.

DR would bring back Exchange to its previous state and SP2 would fix any abnormalities. If it does find issues - it'll point you out towards it and get it fixed.

This way, you'll know what broke and what needs to be fixed (if at all there are issues).

Regards,
Exchange_Geek
0
 
mvalpredaAuthor Commented:
Exchange was fine. The server had some many hard power events (never a blue screen) I would rather start with a new 2008 R2.

So format it, name the machine the same thing and do an Exchange DR install?
0
 
Exchange_GeekCommented:
Ensure, you'll need to reset the computer account in Ad, and then join it to the domain to perform /recoverserver.

Your plan looks good.

Regards,
Exchange_Geek
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
mvalpredaAuthor Commented:
Sounds like a plan. I'll be doing that tomorrow once the new server gets here. Just wanted to verify doing the /recoverserver even though I didn't put anything on there.

Should I copy the old logs and database stores to an external drive first?
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
You would need to reset the Server account in ADUC and bring the machine back into the domain as without it ... it would create another Machine account with1 in the end.

Also as said you would need to meet the pre-reqs for Exchange installation and then Bring Exchange with Recover server switch for the same SP level it was previously.

If you have any doubts please consult us.

- Rancy
0
 
Exchange_GeekCommented:
Yep

"Should I copy the old logs and database stores to an external drive first?"

That'll be a good idea, however as you said not much of data was in it as it was a fresh install - so did you happen to have some important emails sent / received.

Regards,
Exchange_Geek
0
 
mvalpredaAuthor Commented:
It was going to be an Exchange 2003 to 2010 migration. I was only able to get the server on the network and installed before everything started going downhill. Nothing had been moved over on any level.

I just wasn't sure if the DR install would be looking for the MDB and LOG files or if I should just create new ones.
0
 
Exchange_GeekCommented:
Nopes - if it is a fresh install, you can mount a blank database - so nothing to worry, relax.

If you faces issues, post your feedback and we'll be here to solve it.

Relax :)

Regards,
Exchange_Geek
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Ideally if you have done with /recoverserver it will pick all information and get the Old database information for you .... however you can go for a complete new Database but i dont think how thats going to make a difference if everything is working fine with the old database :)

if your srating fresh than by default it will create a default store and mount that database and as you had nothing migrated so nothing to worrky about.

Agree with Exchange_Geek "If you faces issues, post your feedback and we'll be here to solve it" :)

- Rancy
0
 
mvalpredaAuthor Commented:
Getting ready to install Exchange back on the new machine. If I do /recoverserver switch I can create a new database?

EDIT
I only formatted the C: drive and had already moved the store and logs to the D:. Everything there is untouched.
0
 
Exchange_GeekCommented:
You're right, blank database can be mounted without issues.

Regards,
Exchange_Geek
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
/recoverserver switch will get all the data there was ... you can remove and create new or just create new afterwards as well.

- Rancy
0
 
mvalpredaAuthor Commented:
Everything went well. I am moving mailboxes. Have a few giving me trouble though. These were disabled accounts, I have re-enabled them.

USERNAME
Failed

Error:
MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=124]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x80040111
    Lid: 26937  
    Lid: 21921   StoreEc: 0x80040111
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753  
    Lid: 21817   ROP Failure: 0x80040111
    Lid: 26297  
    Lid: 16585   StoreEc: 0x80040111
    Lid: 32441  
    Lid: 1706    StoreEc: 0x80040111
    Lid: 24761  
    Lid: 20665   StoreEc: 0x80040111
    Lid: 25785  
    Lid: 29881   StoreEc: 0x80040111

Warning:
When an item can't be read from the source database or it can't be written to the destination database, it will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that Exchange not copy such items to the destination mailbox. At move completion, these corrupted items won't be available in the destination mailbox.


Exchange Management Shell command attempted:
'OU' | New-MoveRequest -TargetDatabase 'Mailbox Database 0017395951' -BadItemLimit '10'

Elapsed Time: 00:00:01
0
 
Exchange_GeekCommented:
Great.

Regards,
Exchange_Geek
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
If you have just re-enabled give it few minutes .... or as the error say try to move with some BAD limit count specified :)

- Rancy
0
 
mvalpredaAuthor Commented:
Took some time. Added to the local move request. Now to move nearly 60gb of mail.....for 35 people.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Yipeeee :)

- Rancy
0
 
mvalpredaAuthor Commented:
All went well and all the mailboxes transferred. I removed Exchange 2003 out of the organization and I have a solid backup in place.

I have a quick question.....I did the move request, everything was fine. When I then clear that move request....what happens? What state is the mailbox in when that moved request is still there but completed?
0
 
Exchange_GeekCommented:
Once the move request is completed - there is nothing that Exchange does with this data, personally I move a lot of my clients mailboxes for maintenance, where in I remove those requests once the move is completed.

There are absolutely no reputation to clean up the requests stored in those cmdlets.

Regards,
Exhange_Geek
0
 
mvalpredaAuthor Commented:
I learned the hard way a while back NOT to remove Exchange 2003 before people have launched Outlook since the move.

I didn't know if there was something that happened in Active Directory once that request is cleared. I am moving a bunch of mailboxes right now for another Exchange 2003-2010 project and no one will launch Outlook until Monday morning. If I clear the request on the mailboxes that have moved....there is no adverse effects?
0
 
Exchange_GeekCommented:
Well, you have so much fears - keep the requests in-place, wait for users to report on Monday morning - if all is well, remove some of them, wait to hear them shreak, if you don't hear them shouting "world is about to end on 21st Dec 2012" - you're good - remove all requests :)

I normally remove any object, and await user feedback - for me feedback is very important. No response means good :)

Regards,
Exchange_Geek
0
 
mvalpredaAuthor Commented:
I agree....no news is good news.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 9
  • 8
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now