Exchange 2007 Storage Group Logfiles and System Files

We lost the disk that holds our Storage Group Logfiles and System Files yesterday and naturally the Exchange DB dismounted. Luckily for me once I reseated the disk I was able to move the files off and onto another spare disk. We do a full backup using Backup Exec v11 and there are logs being backed up as well as the DBs. The exchange DB and logfiles/system files are on separate disks.

The question is, if this data is lost what would be the recovery process for the logfiles/system files?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If exchange database dismounted, then mails to your primary MX will fail.
If you have a backup MX - mails will go there.

While exchange is dismounted no logs will be generated.

So if you recovered the logs from the bad disk -- the only emails you lost in the intervening period - were sent to the backup MX configured for your domain.

If there is no backup MX - the mails will bounce back after the TTL period and generate a NDR
enter your domain name

see primary and backup mx details there.

if you moved your log files to another drive (from D to E) to save them
you can update the location in AD of your storage group files

Move-StorageGroupPath -LogFolderPath -SystemFolderPath -ConfigurationOnly

You should verify that your database is not in a dirty shutdown state
eseutil /mh <path to database>\priv.edb
if it is not, moving these folder paths should allow you to mount the database

Digbert91Author Commented:
Everything is fine with the DB as I was able to move the files once the disk was reseated. The question is, if I didn't have access to the log and system files how I would I remount the DB without them?
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

You would have to first determine the current state of the database by using the eseutil /mh. If the database is in a clean shutdown state, you could mount the database without the logs and it would start new log generation (it would give you an alert to this). The only data you would lose of course is anything within the log files that were not committed and lost.
if the database is in a dirty shutdown state, you would need to restore the database from backup. your data loss would be everything after the backup.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You have to check the DB status using eseutil /mh if the database is in dirty shutdown then you may require logs. I you dont have logs then you have to to repair the database followed by defrag and isinteg.
The question is, if I didn't have access to the log and system files how I would I remount the DB without them?
>> If EDB had uncommitted logs, then you'd need all those logs to mount the database.
If you cannot find those logs - then db wont mount

how to check last committed log
eseutil /mh "c:\.....\priv1.edb"

Logs are committed after a full backup, and after that the logs are flushed.

Workaround to missing logs and cant mount database.
If you are missing some log-files,
you can try to do a eseutil /cc "c:\.....\priv1.edb", that will check consistency of your log files and do a log-replay.

After that you'd need to do a hard repair
eseutil /p "c:\.....\priv1.edb"
and offline defrag
eseuti /d "c:\.....\priv1.edb"

and then isinteg to root out errors
isinteg -s server -fix -tests alltests

When you are doing hard-repair using eseutil /p > all uncommitted log files will be lost. Database will be set to the point where you lost the log-files, so that you can mount the stores. If you have some log files / transactions after that, they will be lost.
Everyone's going eseutil /mh way :)

eseutil is the *only* tool available to Exch Admins to do fix the database. :(
2010 is good in the introduction of the DAG which can help in scenarios like this, but for small companies it is cost prohibitive. microsoft needs to have something for the sbs and small networks.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.