Hi all, my turn to be asking questions I suppose :)
My customer has an Exchange 2003 sp2 running on Windows 2003 ENT sp2.
The database is rapidly growing in size, and due to the nature of the company I can’t restrict the users from storing all their messages in the Exchange DB, can’t archive the messages, make them use local PSTs for the large stuff… basically everything has to stay online.
My question is, is there a way to deal with this situation, except for starting to backup the server as much as possible? (it is already being replicated to a backup site using NeverFail R2, and daily ntbackups are being run – switching to backupexec soon)
the main issue is, that on every little glitch now, the entire information store goes down, and eseutil and isinteg can do nothing to repair it, and I have to restore from backup.
________ TOYOTA MZ ENGINE SPECIFICATIONS