EDB files not being found during exchange restore

[ftbug]

Hi, during an exchange restore via application items on an sbs 2011 (exchange 2010), when we go to choose the .edb file to mount to restore the users mailbox from, we do not see the .edb file within the backups, and instead, can only see a tmp .edb file

the original .edb file is on the local machine and is still working and accessible, but does not show in the backups

is there a different process to find the edb file to mount during the restore?

[foggy]

Hi Freddie, do you mean you've opened FLR session and browse the backup file for the Exchange database, but cannot see it? Have you tried to use Microsoft Exchange Item Level Restore wizard for the corresponding VM backup right from Veeam B&R console? In this case, database files are automatically obtained from the backup and added to Veeam Explorer for Exchange.

[ftbug]

Hi Foggy,

i have been able to locate the edb file now, however, once entered, it says that the specified folder does not contain valid logs.

What log files are required to mount the edb file?

[foggy]

Exchange Server transactional logs. If you're adding EDB file manually, it is always in a dirty state and logs replay is required. If your do not know the correct logs location, you should repair the database using eseutil to bring it into a clean state. After that it could be open in Veeam Explorer for Exchange. This article could help.

[ftbug]

It seems that the edb database is in a dirty shutdown state, so we are getting the error; the specified folder does not contain valid logs.

Does this mean that we will need to repair the database using eseutil?

if we were to raise a case with technical support, would this be something that they could do?

[foggy]

Not sure, but the procedure described in the mentioned blog post is pretty straightforward (basically, just running a single command).

[Delo123]

It seems that the edb database is in a dirty shutdown state, so we are getting the error; the specified folder does not contain valid logs.

Does this mean that we will need to repair the database using eseutil?

if we were to raise a case with technical support, would this be something that they could do?

Do you actually know where the exchange log files are stored? Maybe you're simply looking at the wrong location.

If i remember correcly you can specify log location with /L: like:
ESEUTIL /R E00 /Lt:\exchange\logfiles

This is probably a good site to help you in the process and create some documentation for next time:
http://www.msexchange.org/articles-tuto ... part1.html

[ftbug]

When we've done exchange restores before, we just specify the edb location, which then autofills the logs section.

In this case, the logs are not valid, which is why foggy sent the article in a previous reply above