Well, unfortunately, it's not my call. I agree, completely, about backups,
but I really don't have any way to back up the data... I've got two exchange
servers and nowhere to back 'em up to... I've put in a request to get two
more 400 Gig external drives to use for making backups, but so far haven't
gotten approval.
John
-----Original Message-----
From: Geni [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 19, 2005 12:32 PM
To: Exchange Discussions
Subject: re: Fixing Exchange 5.5 after log file gets "eaten"
I about had a coronary when I saw that you said you're not running nightly
backups. The thought of that is horrifying to me. Having had to several
times completely restore a corrupted d/b (usually due to hardware failures
introducing database corruption before the drive failed entirely), backups
are King in my eyes - a nightly full is the only way to drive. I truly
would not even recommend trying to run Exchange without some provision for a
nightly full backup. Is there a file server with some space on it? You can
run Exchange-aware NT backup, backup to file, and save the .bkf file on
another server elsewhere if you've no better solution - at least it's
SOMETHING.
ESEUTIL /p is one scary option. There are times it's your only option, but
OH MY WORD, it should be your LAST resort short of running into the street
screaming. Come to think of it, running into the street screaming is
sometimes better. ESEUTIL /p will truncate and delete anything it regards
as corrupt within the database. In my case, that was email attachments.
ALL email attachments, for 2500 mailboxes. All gone. Bye-bye. I would
never, ever run ESEUTIL /p again without copying the corrupt information
stores first, and running the utility on the COPY first to judge the
effects. Always, but always, try to restore an uncorrupted database from
backup before running eseutil /p.
Now, as to the log file issue - definitely your antivirus must be set to
leave the log file directories alone. Some people recommend not running ANY
file-level antivirus on Exchange servers at all. I've done okay running
antivirus on mine, provided I do not allow it to run against the log file or
database file directories. Symantec is quite capable of being configured to
exclude those directories.
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
