All -
Single exchange 2010 SP1 and UR 3v3 server running on a Windows
2008 Enterprise VM (Vmware 4.1)
I come in this morning to a failed Backupexec Full backup job and the drive
consisting of all my logs, tranasaction, smtp, queuedatabase. iis etc is at
about 3.5 GB of free space left. All my
In the past (on 2007 mind you) I’ve used exmon and also Scott Oseychik’s guide
to looking for patterns in logs, it’s a bit hit and miss though, but on a
couple of occasions has located rogue clients
I hate to be the bearer of bad news, but that KB doesn't apply. And I'll
attempt to get it removed.
It applied in the case when you had Exchange 2003 sp1 installed on a
workstation and you had Exchange 2003 sp2 installed on a server (or versus).
7638 is the same version. The .1 vs. .2 doesn't
As far as I know Mailbox Access Auditing is the only thing that would do this.
Absent that, if it's critical you could use a PS script running as a scheduled
task that would periodically check the Inbox for emails that haven't been
moved, and the customer service folder for emails that haven't
You may be able to tell with MFCMapi, but I'm not 100% on that.
To be 100% certain, you'd need to turn on mailbox auditing.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Evan Brastow [mailto:ebras...@automatedemblem.com]
Sent: Wednesday, January
Michael,
Can you elaborate a little further on rolling forward with the log files? Does
that mean restoring the known good DB from a few days ago, then applying todays
log files against it to bring the database up to date?
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Wednesday,
Newer eseutil's can scan older db's so download Ex2010 SP2 and extract from
that.
From: Chris Pohlschneider [mailto:cpohlschnei...@smsprotech.com]
Sent: 11 January 2012 19:26
To: MS-Exchange Admin Issues
Subject: Exchange 2003 SP2 DB Corruption
Hello All,
I have an issue with an Exchange 2003
Exmon (Exchange User Monitor) is my client of choice these days. It can very
rapidly lead you to a culprit (look at the Log bytes column). My recent
experience has been a set of customers who all used a CRM server that was a bit
out of date. It wouldn’t be all of them, but of the four customers
Yes, that's correct.
It's quite simple if there are no problems. However, I recommend you read the
section in the DROG (Exchange Server 2003 Disaster Recovery Operations Guide).
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Chris Pohlschneider
