Microsoft Exchange Server allows you to migrate other email systems to Exchange Server. For the migration process to completely successfully, the Site Replication Services (SRS) is required. It is a service that is responsible for exchanging the directory information between Microsoft Exchange Server and Active Directory. In some situations, the migration process may not complete successfully due to corruption to the Srs.edb file and it may damage your Exchange Server Database (EDB) file. In such situations, you are required to opt for EDB Recovery solutions to get your precious and vital data back.
The Remote Procedure Calls (RPCs) are used by the SRS for replicating the directory data among different SRS servers and Microsoft Exchange Server. The RPC uses transaction logging JET database and Srs.edb that is located at exchsrvrsrsdata folder.
Corruption to Srs.edb data is very troublesome, especially for the database administrators' point of view. The Site Replication Service may not work properly in such cases and thus can make your whole EDB corrupt and inaccessible.
The corruption could take place due to a number of reasons such as if you use an anti-virus scanning to srsdata folder, the corruption may occur. This it is always recommended to create backup of your database. Backup is helpful in restoring the database in case of any disaster.
In some cases, while backing up the SRS using NTBackup tool in Microsoft Windows, the process may not complete successfully. In such situations, the backup may appear perfect or you might get some error messages but when you attempt to carry out EDB Repair using backup, the following error message may take place:
"Unable to open file.
(FILE=C:Program FilesExchsrvrsrsdatasrs.edb, EC=SHARING VIOLATION) and
FILE=C:Program FilesExchsrvrsrsdatatemp.edb, EC=SHARING VIOLATION"
In this case of database corruption, you should not try to repair the database using Eseutil tool. You can use this tool only for checking the database consistency as repairing the database in this case may not recognize the database corruption and may delete the damaged file. The best solution to sort out this issue is to go for EDB Recovery software.
These are powerful and advanced third party tools, specifically designed to methodically scan the corrupt EDB file and restore all of its objects. The
edb recovery software come equipped with simple and interactive user interface and thus do not require sound and prior technical skills.
Stellar Phoenix Mailbox Exchange
edb recovery is a robust and comprehensive EDB recover tool to handle most of the EDB corruption issues. It works well with Microsoft Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.
Resource:
I am Daven Atler and like to write articles related to software like
EDB recovery software and MS exchange EDB recover tools . I have more than 5 years of experience in the IT field.
For more information, visit:
http://www.edb-recovery.com