Scenario:
One of your Exchange CAS box crashed, and you have no way of getting it back. As many of you know bringing another Exchange server with same name and IP address wont simply work because the information in regards to failed exchange server is still does exist in Active directory and Exchange utilize Domain, Configuration and Schema partitions in the .DIT database.
So we will use fallowing switch to perform installation, if this is a mailbox server please read the article Henrik wrote
You may ask yourself why are we using recovery switch, again we want setup to go to AD and read the information about failed server and make the new server we are bringing *** We use same IP and same server name***
Steps taken:
- Install fresh Server ( in this case Windows 2008 Sp1)
- Give same IP and Same computer name as previous failed Exchange server, Join domain and make sure your account is added into Local administrator and you have proper Exchange administrator rights.
- Reset computer account in AD
- Make sure Server is identical as the failed one, keep same drive letters etc
- Copy Exchange installation binaries onto this server
- Drill to that directory and use fallowing switch
| >Setup.com /M:RecoverServer |
**** if you are receiving fallowing errors, fallow the additional steps before you move on ****
“You must perform disaster recovery using the same version of Exchange as the last installed version. The current installed version is ‘8.1.240.6’ the last installed version was ‘8.2.176.2’
This translated into , simply The failed Exchange Server version number is SP2, you are using Exchange CD with SP1 and trying to run recovery switch.
As you can see setup is going to AD and reading attribute called “SerialNumber" from failed server object so what we will have to do little trick in AD and modify this attribute.
Open ADSIedit or ADExplorer to
- Configuration
- Services
- Administrative Groups
- CN=ServerName
Find the attribute called SerialNumber and modify it.
if you are receiving this “
The current installed version is 8.1.240.6 the last installed version was 8.2.176.2”
- Current Version 8.2 (Build 30176.2) (SP2)
- installed version is 8.1.240.6 ( build 30240.6) (SP1)
Check out the build numbers.
http://support.microsoft.com/kb/158530
Change the version number to , allow the setup to run, without complaining
http://www.msexchange.org/tutorials/Recovering-Exchange-2007-Server-RecoverServer-switch.html
http://technet.microsoft.com/en-us/library/bb123496(EXCHG.80).aspx
Best,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog
19 comments:
That warning is there for a good reason. Don't complain when you restore RTM for an SP2 installation and Exchange won't start.
Thanks for the feedback. Changing AD attribute allows to get around with good reason for another good reason (-: ,
that is all it is said in the article. I was not complaining why the existing “SerialNumber” attribute has version , compare the CD is being used, obviously it will if the CD is being used for /RecoverServer does not have the same version number as the failed server. ( the Attribute value)
Since the Existed Exchange server was not gracefully taken out from out from existing SMTP org and AD still thinks it is there with Its existed version number, If the CD is being used had same version number the problem simply would not exist.
The article allows those who used CD came with SP1 and upgraded SP1 to SP2 down the road and trying to run /RecoverServer with original CD, it is clear to me the version numbers won’t be the same, but imagine you are in that situation and what would be next?
I still think using /RecoverServer switch should take care of this issue transparent and give user warning at the end of successful recovery the server should be bring to same version number as it was before.
Best,
Ocd
Are you facing fatal errors while accessing your Microsoft Exchange Server 2007 database? Is your EDB (Exchange Database) file is inaccessible? The fatal error in server aborts the application and thus makes it unusable. This behavior of MS Exchange Server renders all your valuable data inaccessible and cause critical data loss situations. In order to get your precious data recovered in such situations, you need to repair and restore the damaged EDB file, using an EDB Recovery solutions.
Server Recovery
Hi OZ,
It should be worth noting that this method is for when you have no backup. For many organizations the full system backup/restore will be the simplest choice.
Things like SSL cert are missing.
If this is a HUB server then you have queue db and log files etc that need to be restored from backup.
But you could use this method as a hybrid approach to recovery.
Main Cause of data loss fetal errors in Exchange Server, EDB file is not open so try to Exchange Database Recovery tool for recovery of edb file from exchange database.
Hi,
I am Sean Werner, working as an Exchange Server administrator. Recently, I have faced the server failure problem in my organization due to the hardware failure. After reading various articles, available online, I could not fixed the issue. Then, I used a third party tool and successfully recovered & restored my failed Server completely. If you are also experiencing such problem, you may also try this program:
http://www.serversdatarecovery.com/exchange.html
Hope it will work for you !
Sean
Wow well done. You have given very good technique for Exchange Server Recovery. This all works as a remedy when you get entangled in errors and your database is out of your reach. But when your EDB file is highly damaged then you can try Stellar Phoenix Exchange Server Recovery utility that is compatible with all versions and works in efficient way.
Well, I was able to fix the problem with the help of Microsoft. Make sure you install all the Exchange Server prerequisites for your Windows Server version in order to run recover server. You need service pack 2 or service pack 3, whichever you have installed on your Exchange Server.
1. Download the appropriate service pack that is currently installed on your Exchange server
2. Extract the service pack to an easy to find location
3. Once all files are extracted open the location
4. You'll see setup.com as part of all files extracted. That's the setup.com you'll need to run
5. Now you can run setup.com /m:recoverserver from the extracted service pack location via command prompt
6. Now you are done. If you have a SSL Certificate you'll need to export it off the old server or request a new cert.
Good luck and hope this helps.
Bakersfield, CA
Thanks for sharing a valuable information. For performing such task user needs some technical knowledge and sufficient time. When i
performing the search on Google found Many companies offering Exchange data repair software.
Some company offering Free Demo version also. By the use of these tools you perform this task with few clicks. From there one such tool is here: http://www.undeletepcfiles.com/exchange-edb-recovery-tool.html
I hope this tool would help you visitors.
Microsoft provides some free utilities, named as Eseutil.exe, Exmerge.exe and Export-Mailbox. These tools convert EDB to PST and extract the user mailboxes in .PST file format. However in case of severely corruption, these tools may fails. The best way to handle this situation is using some advanced third party EDB to PST Converter software. You can use free trial version for extracting edb mailboxes. http://www.exchangedisasterrecovery.edbtopst-converter.com/
Use an effective EDB to PST converter software to make Exchange data readable. This application works in all versions of Exchange and easily export data from EDB to PST Outlook. It is an efficient solution to recover Exchange server and transfer all mailbox attachments to PST file with complete data of Exchange. It makes EDB data readable in accurate format of TXT, RTF and HTML etc.
For More Information, Read
http://www.recoverpublicfolderedb.exchangedatabaserecovery.biz/
One of the powerful tools available in the market today is the Exchange database, recovery which can recover almost all the damaged files on the Exchange server. With this tool you can easily convert PST files EDP without any pain and without errors that might occur while using the integrated tool free.For more information and free download click http://exchangedatabase-recovery.blogspot.com
Migrate EDB to PST in order to make corrupt Exchange data usable again and for this you should try an advance Exchange EDB to PST converter software. It works in all Exchange versions and smartly move EDB to PST file with complete Exchange mailbox folders.
Read More
http://www.edbtopstsoftware.exchangeedbtopstconverter.com
The software is compatible with entire versions of Exchange server and MS Outlook. No special technical skills are needed to handle the software. More details see this site:- http://www.recoverydeletedfiles.com/exchange-server-edb-recovery.html
When I have failed to search best solution to recover Exchange Server issues then my close friend suggest that use Enstella for Exchange Server Recovery Software which provide easy to use feature to fix them all Exchange EDB corruption issues and convert into PST/EML/MSG and HTML with internal coding TXT/RTF and HTML. This utility gives the capacity that you can recover and convert either selective or limitless Exchange Mailboxes Data to Outlook including with all attachment and properties items.
Read More Information So Visit Here :- http://www.enstella.com/edb-to-pst-conversion.html
EDB to PST Converter Tool is an effective & reliable tool provides impeccable recovery. This tool recover & repair all damaged .edb files and then transfer them into usable format that is PST. It supports all versions of Windows and restore PST files in your location. It restores all files in original formats such as HTML, Text, RTF, etc. It is preview of all damaged or corrupted EDB files before restoration. Free availability of trial version with the help of you can easily understand the complete procedure of recovery. For more info, visit here- Convert EDB to PST
EDB to PST Converter Tool to recover corrupted EDB file and fix Exchange EDB file error and Convert Exchange EDB to PST. The EDB to PST converter tool made for Exchange email recovery through which Exchange user easily solve all types corruptiom issues in EDB file & re- open exchange mailbox store into Outlook.PST file - See more at: https://softcart.wordpress.com/edb-to-pst-converter/
Post a Comment