Discussion Locked

Working with Exchange 2000

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I manage a network for +/- 25 employees. We use Win 2000 server and Exchange 2000. I have 2 servers - one is the PDC and the other runs Exchange and stores user data. I use BackupExec v8.5 for my nightly backups, which have been failing for a few months now. I have an outsourced company to provide support, but I'm not pleased with the response I get from them. Here's my dilemma: With the backups continuing to fail, the drive that Exchange is on is starting to run out of space because of log files not getting committed and flushed. I've been able to run a backup on Exchange alone successfully, but only once. Now I get a message saying that the database is corrupt and access is denied. I've run CHKDSK on the drive with nothing found. Exchange appears to be running without a problem. I've been to Microsoft's site, and their info isn't all that helpful. Of course, the first fix to a corrupt database is to restore it. Great. I'd do that if I had a good backup. My outsourced support suggests upgrading to BackupExec 9.1, but I'm not convinced that that will solve the problem.

Anyone have any thoughts/suggestions/wisdom to share with an overwhelmed mini-techie?

3 replies

by jhansen

In exchange there is only one folder that needs to be backed up.

do a search on your server for
The .edb file contains all the folders, tables and indexes for messaging data and MAPI messages and attachments.
The .stm file (new to Exchange 2000) contains Internet content in its native format.
The .log files (transaction logs) maintains a record of every message stored in a storage group and provides fault tolerance in the event that a database must be restored. Exchange 2000 log files are always 5MB in size (5,252,880 bytes) and if not, then they are damaged. Each storage group also reserves to log files, Res1.log and Res2.log that are placeholders for extra disk place that can be used if the service runs out of space

it should be somewhere under e:\program files\exchsrver\

You will need to back this folder up to tape. if you ever do a restore or rebuild of the exchange database, this is the files you will need.

Also, don't forget to stop the msexchangestorage service before copying and restarting the server when you get done. also, this is not the exact name of the service, but its an exchange service dealing with storage that needs to be stopped and restarted.

Jake
--------------
For an easy way to backup you computers visit http://www.zray.net Resellers Needed!

by wtdriscoll

First off, you can use the NTBACKUP to perform a complete back up of the Exchange Store. Have it save to a harddrive on another server or drive that is not full. When this is done, the log files will erase.

Next open the Exchange manager and dismount the Private Store. Open a CMD window and run ESEUTIL on the priv.edb If you key in ESEUTIL /? you will get options and there is a REPAIR option. YOu need to run this to check on the errors that you are getting. THERE IS A WEALTH of information on DEFRAG EXCHANGE STORE DATABASE

After you run the repair, you will need to run the DEFRAG option of ESEUTIL. WHen this is done, the remount the store.

I use Veritas 9.1. Overall I have not been too impressed with the Exchange backup.

If you have not fixed this yet, let me know

taylor

by ncaramanico

I have been experiencing backup failures with BackupExec 9.1 as well (so much for your outsourced support's solution, auslyunnj). Some nights, the same job runs without a hitch in three hours, some times it runs for over 9 hours. It doesn't make sense. It's almost like my Quantum dlt tape drive is timing out. I also noticed this during a restore. I used the restore wizard with a tape and it just hung up; however, if I restored by right clicking on the tape in devices, it ran. I've run the latest hardware updates. Is it Exchange, Norton Antivirus or the tape drive? Help!!

This discussion is closed to new replies.