Mount Exchange 2013 DB with no logs

Erik Whiteway
Erik Whiteway used Ask the Experts™
on
I had to back / restore my exchange 2013 for some hardware changes.  It was a clean shutdown so I didn't backup the huge log directory.

Now when I power up, I can't get the DB to mount - keeps looking for the logs.  I'm trying with the command:

Mount-Database -Identity ExchangeServer1.Contoso.com\MyDatabase

But when I change to my server name and my database name - I get and error that I did not enter the correct Identity.

How do I find out exactly what to put in here?  (then I can add the force command to start the DB?)
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Erik WhitewayConsultant

Author

Commented:
I droped the server name and the command will run - but still will not mount without the logs files - how do I get it to forget them and just start?
How did you perform the backup. When you say it was a "clean shutdown". Do you mean you dismounted the database then took a file level backup?

-JJ
Most Valuable Expert 2014

Commented:
The logs are part of the database.
You should have done an Exchange aware backup which would have flushed the logs.
As it is, you now have a broken database.

You will have to run a repair on the database using eseutil. Once the database has been repaired you should be able to mount it. However a repaired database should not stay in production, so once it is mounted I would create a new database, move all mailboxes to the new database and then drop the original.

Simon.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Erik WhitewayConsultant

Author

Commented:
It was a Hyper-V copy - but I had the logs on a separate drive - I didn't copy that drive.  So it's not so much a backup as the log drive was just lost.

eseutil confirms the DB is in a clean shutdown.

What do I need to do to just generate new log files?
You are going to have to run Eseutil /P <path to EDB> to repair the database. As Simon stated, you will then need to create a new database and move all your mailboxes.

-JJ
Erik WhitewayConsultant

Author

Commented:
That seems odd that you can't just create new log files - the DB is 100%.  I remember creating new logs on the old version of exchange.

I'll run the util - but it will also take a long time.
You can't "create logs" on Exchange. Never been possible. The database needs the logs to mount. If you don't have the logs, you need to run a repair.

-JJ
Erik WhitewayConsultant

Author

Commented:
I ran eseutil /p and if finished with non errors and I still can't mount.

still get can't enumerate log files error
When you restored your server, did you recreate the log drive and path? If not, you need to do that, otherwise, Exchange will be looking for the log files in a path that doesn't exist.

-JJ
Consultant
Commented:
I had a typo in the path I manually created to remake the log files.

Once I had the path created properly  - simple 'mount-database -force' worked.
Erik WhitewayConsultant

Author

Commented:
file path issue  - not need to scan DB

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial