Exchange 2003 restore question

Posted on 2010-09-17
Last Modified: 2012-05-10
I'm going to be performing an Exchange 2003 database restore over the weekend, and I'm hoping an expert in the practice can help with the corrent procedure. First, the backstory:
We have two Exchange 2003 Enterprise servers, one only hosts mailboxes, and one only hosts Public Folders. We're a project based business, and every email our employees recieve about a project gets dragged into the corresponding public folder. The public folder database is 410 GB in size! We realize this is not a good idea and have already put a new email filing system in place for new projects. However, we need the public folder based solution for another few quarters until we've transitioned everything over.
Last Friday evening, the server that hosts the public folders had its RAID controller fail during the Exchange backup window. We went through a bunch of troubleshooting with Dell, and one thing led to another and we eventually lost the entire RAID array that held the Exchange stores. So Monday was spent bringing up a VM with SAN storage, the Exchange data was restored from the last successful Full backup, and the Incremental backups were then restored.
So everything is good, public folders are back, and we think we're back in business. But I kick off a new Full backup of the restored Exchange server, and at the very end of the database, the backup dies due to a bad page checksum, error 1018, which according to the KBs I've read is quite common. Microsoft's top suggestion is to perform a restore from the last good backup, and replay the log files.
So this brings me to the question. I'm going to do another Full restore, and follow it with the Incremental restore like I did on Monday. I've got that procedure nailed. But what do I do with the log files that have been created since the restore on Monday?
Do I leave them in the C:\Program Files\Exchsrvr\MDBDATA folder, and they will replay automatically? Or do I need to copy them in to the temporary restore folder and manually play them with eseutil /cc?

Thanks for your help!
Question by:InterfaceEngr
  • 4
  • 3
LVL 32

Expert Comment

ID: 33703157
a 1018 error is typically a hardware issue (hard drive)
do you have another drive you could move the exchange data to

Author Comment

ID: 33703211
It's hosted on our iSCSI SAN now, which is the only place with enough space right now to host it. If we get 1018's again after the second restore, we'll look at getting some server hardware for it.

Author Comment

ID: 33703254
Oops, didn't select enough points at first.
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

LVL 32

Expert Comment

ID: 33703372
do you have any additional free space on the iSCSI SAN to allocate

Author Comment

ID: 33703397
Yep, I've got several TBs I could use. I don't think moving it is going to correct the bad page in the database though.
LVL 32

Expert Comment

ID: 33703504
no, but it would be good to move before performing another restore

Accepted Solution

InterfaceEngr earned 0 total points
ID: 33727804
Performed the restore last night. I simply left the existing log files in the mdbdata folder, did a full restore, then an incremental restore, and then kicked off an eseutil /cc (hard recovery) command.

After the hard recovery command played though the restored incremental log files, it checked the mdbdata folder for any log files since the last restore. Since the log files in the mdbdata folder were numbered in the correct sequence, picking up right where the incremental restore left off, the eseutil /cc command played them back as well, which I could verify by watching the Application log in Event Viewer.

So the database has all of the changes since the last full backup, and all I had to do was leave the log files in the mdbdata alone, and use eseutil /cc for hard recovery after the restores completed.

Oh, and if you ever do this, make sure you use the same temp directory for the full and then the incremental Exchange restores. And make a backup copy of the folder with your logfiles (possibly C:\Program Files\Exchsrvr\MDBDATA) with the Exchange services shut down just in case something happens before you start any restores.

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now