jjh2010
asked on
Exchange Database Restore Without Transaction Log Files
Hypothetical:
If I have a copy of the .edb file from a 2003/7/10 email server that has only one mailbox store and I have the system state backup, but I don't have any transaction log files, will I still be able to restore a working copy of the mailbox?
My understanding is that it will be a working mailbox store, but it won't have any of the changes made to the database that are still in transaction log files.
If I have a copy of the .edb file from a 2003/7/10 email server that has only one mailbox store and I have the system state backup, but I don't have any transaction log files, will I still be able to restore a working copy of the mailbox?
My understanding is that it will be a working mailbox store, but it won't have any of the changes made to the database that are still in transaction log files.
Firstly if it is Exchange 2003 then you would need the EDB as well as the STM file. Log files would not be needed if the copy of the database you have is in clean shutdown
Your undersdtanding with regards to the last point quoted below is correct
"My understanding is that it will be a working mailbox store, but it won't have any of the changes made to the database that are still in transaction log files."
You would not need the System State backup if you have the online backup of the database\Store in question
Your undersdtanding with regards to the last point quoted below is correct
"My understanding is that it will be a working mailbox store, but it won't have any of the changes made to the database that are still in transaction log files."
You would not need the System State backup if you have the online backup of the database\Store in question
ASKER
I think it is safe to say this would be an offline backup.
I too guess so but that too depends if its in Clean shutdown state or Dirty .... lets first start the restore and then proceed what information we get :)
- Rancy
- Rancy
Well then as I stated on my first post....database clean\dirty....all depends on that as to which direction you need to move ahead
Whether the database is dirty or not, you should still be able to mount it. The only difference is whether it requires a repair or not. Data loss could occur during a repair, and in the small window between the data being written to the logs and then the database - unless this is a backup of course, but then you will lose everything from the last backup.
However you can recover data from OST files, so data recovery from Exchange should not be considered in isolation.
Simon.
However you can recover data from OST files, so data recovery from Exchange should not be considered in isolation.
Simon.
Sembee2: It always depends from scenario to scenario. One can come across scenarios where even blank database also does not mount and the reason in that case would be permissions issue. If database goes in Dirty shutdown then soft recovery option is available provided the required log files are available and REPAIR is an option that should be the last resort in any Case.
Yeah ..... but its not that easy as if its a Offline backup even as the time for Data to be written to log file and then to Database might be short but E00.log or whatever the Generation Log is always and a;ways locked by the Information store service ..... and if the Offline backup was taken at the time database was mounted its Bound to be Dirty shutdown.
As i said if its Exchange 2007 or 2010 .... .edb will work but if its Exchange 2000 or 2003 you will need ".edb and .stm".
And no data will be available since the Backup date ...... if the server or DB crashed recently and users have the Outlook in cache we can convert the data from OST to PST using Outlook itself.
- Rancy
As i said if its Exchange 2007 or 2010 .... .edb will work but if its Exchange 2000 or 2003 you will need ".edb and .stm".
And no data will be available since the Backup date ...... if the server or DB crashed recently and users have the Outlook in cache we can convert the data from OST to PST using Outlook itself.
- Rancy
ASKER
I really appreciate all the concern from members here. The idea about .ost files is a great idea.
Maybe a more specific hypothetical will help.
Server 2008
Exchange 2010
Windows Backup is not a solution I can use because it wants to backup EVERYTHING and there is not enough space to do this.
I awlays have a system state backup that is a week old or less because it is relatively easy to create it with powershell.
I have to leave the office for three days and I don't have another tech around. I have to leave in a hurry.
I find the EDB file and a lot of transaction transaction log files.
I open shadow copies and copy off the EDB to a removable hard drive. I abandon the transaction log files.
I come back after the trip and the server will not turn on.
I replace hardware, including hard drive, get a fresh install of Windows and Exchange, patch it, and I am ready to try to restore email.
Can I put the EDB in a folder and mount it, or is it preferrable to run eseutil on it to check for errors? Will having the transaction logs and the check file in the folder help? Or, is this approach not viable at all?
Maybe a more specific hypothetical will help.
Server 2008
Exchange 2010
Windows Backup is not a solution I can use because it wants to backup EVERYTHING and there is not enough space to do this.
I awlays have a system state backup that is a week old or less because it is relatively easy to create it with powershell.
I have to leave the office for three days and I don't have another tech around. I have to leave in a hurry.
I find the EDB file and a lot of transaction transaction log files.
I open shadow copies and copy off the EDB to a removable hard drive. I abandon the transaction log files.
I come back after the trip and the server will not turn on.
I replace hardware, including hard drive, get a fresh install of Windows and Exchange, patch it, and I am ready to try to restore email.
Can I put the EDB in a folder and mount it, or is it preferrable to run eseutil on it to check for errors? Will having the transaction logs and the check file in the folder help? Or, is this approach not viable at all?
Run a command
eseutil /mh "location of the .ed file" and check if it shows dirty or clean shutdown ?
- Rancy
eseutil /mh "location of the .ed file" and check if it shows dirty or clean shutdown ?
- Rancy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If Exchange 2007 or 2010 you will have just the .edb .... you will be able to work with it only if Exchange DB backup was taken if the Database is in clean shutdown :)
Try to restore and lets than see what happens ?
- Rancy