9 replies
by calves
There is two things I do on a regular basis:
I reboot the server every 2 weeks;
I run the Microsft Exchange Optimizer once a month.
Aside of that, keep the mailboxes clean and exchange up-to-date with Organizational changes, such as people thatleft and no long require a mailbox, etc...
Good luck!
by don_pham
by fred_e944
by don_pham
by guy
I would suggest that you get a good backup program the one that comes with exchange is poor BackupExec or Cheyenne ArcServe are better. Also check to see that Restore actually does what you think it will.
On another tack I would study the Monitors and Links as they can actually prevent problems e.g. synchronise time, alert you if messages are stuck.
Finally I would persuade your manager to send you on a course, that way you will get some structured troubleshooting practice.
by don_pham
by mckaytech
Unlike prior versions of Exchange, v5.5 does a good job of compacting the database, recovering space and so on (you'll notice from the Event Log that certain tasks run about every hour) so there is no real need for routine database defragmentation.
However, I consider backup a part of routine maintenance and I would strongly recommend that you disable circular logging to provide maximum disaster recovery protection. The downside is that transaction logs will continue to accumulate until thenext successful backup is run so you must be sure the backups run so the logs are properly truncated. I also recommend periodically doing a test restore to make sure your backups are good.
Finally, monitor your disk space carefully - most of thereally ugly Exchange crashes I've seen have resulted from running out of drive space.
Incidentally, I don't agree with the need for a biweekly reboot although I think the rest of the advice given in that answer is pertinent and useful.
paul
by don_pham
by don_pham
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending