1. Reading the log files directly would avoid a MAPI or other client
connection, however it is not zero footprint. You still connect to the
server and you still place an IO load on the server as you read the logs.
2. Backup API backups are not zero footprint. In fact accounting for the
IO caused by backups is a large part of sizing an exchange server.
3. Copy on Write snapshots, like those created by the MS Software provider,
are not zero footprint. While a COW snapshot is in place, each overwrite
requires 3 IOs (read old data, write it to the difference area, overwrite
changed data). Put more than a few in place and your server will come to a
screaching halt.
4. Most Archiving tools I've seen use an Event sink. This goes way back to
the Archiving Sink example in the 2000 reskit and later Exchange 2000 SP2.
http://support.microsoft.com/kb/307798/en-us
5. Even the Archiving sink is not zero footprint. It takes IO to read the
messages and send content somewhere, and that IO will impact your server.
Post by WLANHello,
I think u misunderstood it.
I know that transaction logs are propretery info and only server / backup
APIs might know about its format. I am searching that whether any 3rd party
can access those log files.
My goal is to retrieve a message from the transaction logs, and thus, avoid
making a client connection to Exchange to retrieve the message - to enable
us
to support a "zero footprint" interface with Exchange.
Lot of e-mail archiving softwares uses this mechanism for archiving e-mails
into repository
I know that i can read all messages, if I establish a connection to exchange
server. Also Journaling creates message traffic and need a connection to the
database.
Based on the above feedbacks and assumptions, I am doing a feasiblity study
about mail store. I have see mechanisms like Volume Shadow Copy Service
(VSS), Backup API etc. VSS creates a shadow copy of the mail store and we can
restore that copy into a non - exchange repository also.
Post by unknownJust wait a little while guys - quantum tunneling is planned for the next
version of Exchange.
Post by Martin BlackstoneI told you, I'm out of ideas. :)
Post by John FullbrightKeeps saying "without making a connection to the exchange server".
How
did they intend to get the logs?
Anyway, why wouldn't they just journal the mailboxes in question.
Post by Martin BlackstoneLOL.
After thinking about this for 24 hours, I think he means he doesn't want
to touch the store.
After that point I'm pretty much out of ideas.
Post by John FullbrightThe logs reside on the the Exchange server. Unless your application
exploits quantum tunneling, to read them, you will need to connect to
the Exchange Server.
Post by WLANI think you misunderstood it. I want to read mails without making a
connecttion to exchange server.
Post by John FullbrightThe transaction logs are stored on the exchange server. If you
touch
them,
you are connecting to/touching the exchange server.
Post by WLANHello All,
I have seen the documentation of log shipping feature of
exchange
server.
Exchange server creates transaction logs and keeps uncommited
records in
it.
I want to read mail messages without accessing/connecting exchange
server.
So my idea is to read tranaction logs. But right now i don't know
the file
format of that file. I think it is a JET file database /
transaction file.
(1) Is there any mechanism for reading these transaction logs?
(2) Can we read log file using APIs like Backup/restore,ESE / JET
,EXOLEDB
etc
I am trying some reseach on this transaction logs. Any idea is welcome.
Thanks in advance
regards
~WLAN