NewswireToday - /newswire/ -
London, United Kingdom, 2007/09/20 - E-mail servers are an integral part of businesses today. A critical services database that changes very often, such as messaging and collaboration data needs to have back up devices - UniRecovery.co.uk.
As of now Microsoft Exchange Server is the most popular solution for handling e-mail and other forms of interactive communication through the company’s networks. E-mail servers are an integral part of businesses today. A critical services database that changes very often, such as messaging and collaboration data needs to have back up devices. But, these devices can also fail. When structural damage or media failure have occurred standard repair utilities, such as Eseutil within the mail applications can cause further damage. An Exchange Server failure can cause myriad problems, such inability to receive and send e-mail. Databases can be lost, creating mayhem. Most of the times, you will have to call for Data recovery professionals to recover and restore corrupt Priv.edb files, .edb files and .pst files.
Microsoft Exchange contains one primary database for all mailboxes – Priv.edb, which contains mailboxes as well as email messages. Microsoft’s Exchange Server 2000 has added an extra file called Priv.stm that is also in use for e-mail. Many log files are linked with the Priv.edb file. These files keep a log of all sent and received emails after the last back-up. When a backup is done, the log files copy their information to Priv.edb, and the log files are then emptied. Recovering e-mail from these files when they are damaged can be performed by data recovery software, which can read directly into .edb & .stm files.
Exchange Server holds the .edb files and .stm files, while Outlook holds the .pst files for e-mail. At times, some email message may just vanish or files may become corrupt due to a number of unknown reasons. Exchange server data may be lost and data gets ensnared in the Exchange Server EDB file database files. Email extraction is the process of extracting .edb files from the database and recovering them in the form of .pst files. In other words in e-mail data recovery is the process of extracting the Exchange Server EDB File Database files from your server, converting them to .pst Outlook files, that are sent back into Outlook to repair and retrieve your Exchange server.
According the Microsoft’s white paper published, you need to have a server identical to the one that has failed – to be able to copy from a back up. But, when the latest software available in the market is utilized, this is not required. Exchange Server data recovery can be facilitated by software that can change your .edb files to .pst files which can retrieve and replace data in your repaired or replacement server. These software processes recover ruined mail databases, such as .edb and .stm files, recovers data, and stores the data retrieved to a general Personal Storage File or .pst file format that is readable by Outlook or such attuned mail clients.
The database is in a dirty shutdown state or an inconsistent state when the Exchange mail store has not been shut down properly. Using utilities like Eseutil.exe does not solve this problem. The solution is to get back the .edb and .stm files to a neat shutdown state without resorting to back up restoration or running the repair utility. Your .log files and .chk files should be moved out and your database mounted back. Run the Isinteg (the database repair utility) when the database is back in a clean shutdown state to check corruption.
There are some basic “Do’s” and “Don’ts” when you have a MS Exchange Server Problem. Always back up your priv.edb and pub.edb files. Eseutil.exe is useful for fixing errors in the Exchange database, but it overwrites data. This can affect further data recovery attempts. So do not run the Eseutil program when you have MS Exchange Server problems. Re-installing MS Exchange can also overwrite data, making data recovery difficult – so desist from doing so.
Another important factor to be kept in mind is to make a copy of your .edb, .stm, and .log files before opening a tech support case with Microsoft, sending your database to any Data recovery agent, or attempting any kind of further repairs. It is always in your better interest to seek help from specialized data recovery engineers to recover your lost data.