{"id":308,"date":"2018-07-31T17:43:13","date_gmt":"2018-07-31T17:43:13","guid":{"rendered":"http:\/\/www.blog.mozesoft.com\/?p=308"},"modified":"2021-06-17T10:39:12","modified_gmt":"2021-06-17T10:39:12","slug":"exchange-database-recovery-with-and-without-log-files-is-possible","status":"publish","type":"post","link":"https:\/\/www.mozesoft.com\/blog\/exchange-database-recovery-with-and-without-log-files-is-possible\/","title":{"rendered":"Exchange Database Recovery With and Without Log Files is Possible"},"content":{"rendered":"

Transaction log files plays major role in Exchange server, as transaction log is a file that manages entire records for changes that were made into Exchange database. The information that needs to be inserted to a database of mailbox is firstly written in Exchange server transaction log file, and after that information written in Exchange server database. In case any details are not recorded in log file, could result in issue of operation failure. In these condition users are unable to access their mailbox database from EDB files.<\/p>\n

In this post users can get the solution about how to recover database of Exchange server<\/a> with and without log file.<\/p>\n

How to Recover Exchange Database with Log file <\/strong><\/p>\n

Before stating any process of Exchange mailbox database recovery<\/a> users need to check the state of EDB database using Eseutil\/mh command<\/p>\n

c:\\program files\\exchsrvr\\bin>eseutil \/mh “drive:\\program files\\exchsrvr\\mdbdata\\priv1.edb<\/p>\n

After running above mentioned command if users find the dirty shutdown state of database then recovery of Exchange mailbox database should be first.<\/p>\n

There are two ways to recover Exchange Database<\/p>\n

a)\u00a0Soft Recovery and<\/p>\n

b) Hard Recovery<\/p>\n

Now need to replay transaction log file through the Soft and Hard Recovery process <\/strong><\/p>\n

A)\u00a0\u00a0\u00a0\u00a0 Soft Recovery:<\/strong> The procedure of replaying transaction log files when the database is re- mounted on the server which is suffering unexpected halt. In this situation, Exchange Server automatically executes the soft recovery process through any pending transaction log file by reading checkpoint file. If automated procedure doesn’t get successfully processed, then recovery processed manually using Eseutil commands.<\/p>\n

\"\"<\/p>\n

B)\u00a0\u00a0\u00a0\u00a0 Hard Recovery:<\/strong> This procedure is applicable to replay log files through the online backup. If \u201cLast Backup Set\u201d option is enabled then recovery processed automatically. This hard recovery process is different from soft recovery process because it does not required checkpoint file, it required restore.env file for database recovery.<\/p>\n

Note:<\/strong> In case \u201cLast Backup Set\u201d option is not enabled while restoring, now users need to manually perform this hard recovery process using Eseutil command.<\/p>\n

Now start restoring online backup, once backup is successfully restored then restore.env file will be generated in Temporary folder of the system.<\/p>\n

\"\"<\/p>\n

Hard recovery can be done with this following syntax, which helps to replay log file in restore.env file against Exchange database<\/p>\n

\"\"<\/p>\n

The recovery task will work only on those databases which are restored from the valid backup; it does not support any recovery process for other Exchange server EDB files.<\/p>\n

How to Recover Exchange Database without Log file <\/strong><\/p>\n

The above mentioned procedure helps to recover database if database in dirty shutdown state. For soft or hard recovery propose, it is important that users have log files and it\u2019s in healthy state. In case users don\u2019t have log file it can affect recovery.<\/p>\n