Having a nightmare considering your Exchange database damage scenario? For an Exchange administrator, it is never going to be as easy as this. The first thing you can do to manage Exchange server is to maintain it properly and not let the hard-drive of the server play insane which may play a havoc with your Exchange database. Even if you have kept a backup, it is not always possible to roll forward and recover the Exchange database using the transaction logs. May be you can prevent any data loss, but certainly you will never rule out major downtime in rolling it back. Also, ensure that the backup that you have is kept safe and not exposed to environmental hazards, otherwise you are certainly likely to go berserk when you next see it.
If you EDB database has met with any inconsistencies or throwing all different permutations and combinations of errors, this certainly is a sign of corruption of your EDB database. For this sort of corruption, when you Exchange is still functioning and has not given up completely, but loads of errors with slowness, there is an in-built Eseutil Exchange utility tool which can recover any of the salvageable data and fix it back for you. It is almost like a conventional tool which you will find very limiting in fixing the database completely and thoroughly, but it can certainly help you with some. So, as an administrator, I recommend two things: First is secure your EDB database by ensuring to take regular backups and keeping it safe and secure, and secondly, never completely rely on in-built tools such as Eseutil to do the job for you.
How to Repair Exchange Database with Eseutil?
1) First and foremost, you should ensure that your database is really not in the state of getting started. Sometimes, what happens is that the database is pretty fine, but there is something else that is getting in the way of its start up. So you need to figure that our first. Here are some suggestions to help you see for the things to be tried before you conclude that your database should actually be repaired:
2) You need to check the Application Log
3) Then, restart the server once again
4) Now, make a copy of your database files(s) before executing the repair operation on them
5) Now, if however you are still unsure that your database files are damaged find it out from the "Exchange System Manager" through the process of accessing database properties. Database page will list all the paths as well as the names.
6) You also need to ensure that you have sufficient hard disk drive space for doing the repair operation. A general thumb rule says that you must have space equivalent to 20% of your Exchange database size for executing the repair operation.
7) Run the command - Eseutil in /P (repair) mode
8) The command line will help you repair DB1.EDB file located on the C: drive along with its corresponding .STM file that is located on the D: drive and will place the temporary file on E: drive.
9) The process of repairing EDB can take a while - may be hours.
Other Better Faster Option - Exchange Recovery software
A third-party tool that is efficient to repair Exchange database is always a better and faster option as against the lengthy and tiresome Eseutil utility. One such tool that you can bank upon is the EDB Repair software with which you can play your cards safely with A's in every move.
About the Author:
With extreme ease to sort out various issues a wide range of fruitful applications is devised by organization. Exchange Recovery is a solution to cut down problems from corrupt Exchange files so, Exchange EDB File Repair is also possible with this tremendous tool.
How to Repair Exchange Database with Eseutil?
1) First and foremost, you should ensure that your database is really not in the state of getting started. Sometimes, what happens is that the database is pretty fine, but there is something else that is getting in the way of its start up. So you need to figure that our first. Here are some suggestions to help you see for the things to be tried before you conclude that your database should actually be repaired:
2) You need to check the Application Log
3) Then, restart the server once again
4) Now, make a copy of your database files(s) before executing the repair operation on them
5) Now, if however you are still unsure that your database files are damaged find it out from the "Exchange System Manager" through the process of accessing database properties. Database page will list all the paths as well as the names.
6) You also need to ensure that you have sufficient hard disk drive space for doing the repair operation. A general thumb rule says that you must have space equivalent to 20% of your Exchange database size for executing the repair operation.
7) Run the command - Eseutil in /P (repair) mode
8) The command line will help you repair DB1.EDB file located on the C: drive along with its corresponding .STM file that is located on the D: drive and will place the temporary file on E: drive.
9) The process of repairing EDB can take a while - may be hours.
Other Better Faster Option - Exchange Recovery software
A third-party tool that is efficient to repair Exchange database is always a better and faster option as against the lengthy and tiresome Eseutil utility. One such tool that you can bank upon is the EDB Repair software with which you can play your cards safely with A's in every move.
About the Author:
With extreme ease to sort out various issues a wide range of fruitful applications is devised by organization. Exchange Recovery is a solution to cut down problems from corrupt Exchange files so, Exchange EDB File Repair is also possible with this tremendous tool.
No comments:
Post a Comment