 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Applications / July 2008Log shipping
Hello 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. I have the following doubts with log shipping: (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 >Hello 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 [quoted text clipped - 11 lines] >regards >~WLAN What is the goal of this project? Why the need to read logs? Hello, I want to archive mails without making footprint of Exchange server. Is it possible to read mails with 'zero" footprint of exchange server? Regards wlan > >Hello All, > > [quoted text clipped - 19 lines] > What is the goal of this project? > Why the need to read logs? The transaction logs are stored on the exchange server. If you touch them, you are connecting to/touching the exchange server. > Hello All, > [quoted text clipped - 18 lines] > regards > ~WLAN I think you misunderstood it. I want to read mails without making a connecttion to exchange server. > The transaction logs are stored on the exchange server. If you touch them, > you are connecting to/touching the exchange server. [quoted text clipped - 21 lines] > > regards > > ~WLAN The 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. >I think you misunderstood it. I want to read mails without making a > connecttion to exchange server. [quoted text clipped - 31 lines] >> > regards >> > ~WLAN LOL. 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. > The logs reside on the the Exchange server. Unless your application > exploits quantum tunneling, to read them, you will need to connect to the [quoted text clipped - 36 lines] >>> > regards >>> > ~WLAN Keeps 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. > LOL. > After thinking about this for 24 hours, I think he means he doesn't want [quoted text clipped - 41 lines] >>>> > regards >>>> > ~WLAN I told you, I'm out of ideas. :) > Keeps saying "without making a connection to the exchange server". How > did they intend to get the logs? [quoted text clipped - 46 lines] >>>>> > regards >>>>> > ~WLAN Just wait a little while guys - quantum tunneling is planned for the next version of Exchange. > I told you, I'm out of ideas. :) > [quoted text clipped - 48 lines] >>>>>> > regards >>>>>> > ~WLAN Hello, 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. > Just wait a little while guys - quantum tunneling is planned for the next > version of Exchange. [quoted text clipped - 51 lines] > >>>>>> > regards > >>>>>> > ~WLAN 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. > Hello, > [quoted text clipped - 90 lines] >> >>>>>> > regards >> >>>>>> > ~WLAN Hello, Thanks for the reply. I have seen your points. Can you tell me the mechanism for reading the log files directly. Now i don't know the format of transaction log file. Is there any mechnism for reading those logs? regards WLAN > 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 [quoted text clipped - 110 lines] > >> >>>>>> > regards > >> >>>>>> > ~WLAN > Thanks for the reply. > [quoted text clipped - 4 lines] > mechnism > for reading those logs? Hi there, You need to give up on the idea of reading the Transaction Logs. Implement Journaling and then read any messages from an alternate Journaling Exchange Server. Oliver >> Thanks for the reply. >> [quoted text clipped - 12 lines] > >Oliver Not to mention that the logs arent "Joe Smith sent a message to Bob" Its more like , "At offset 3bf543......" If you really wanted zero impact, then an archiving appliance that sits in the middle is about the only thing I can think of. If the appliance were a Windows box, you'll still implement an event sink of sorts that copied off the RFC822 message and then manipulated it till your heart's content as it transited the SMTP queue. For items locally delivered to the store still in MAPI format (Exchange 2000/2003), you'd have to route them through the appliance (border server) to force content conversion. #*&$ Still not zero footprint, is it? >>> Thanks for the reply. >>> [quoted text clipped - 17 lines] > Not to mention that the logs arent "Joe Smith sent a message to Bob" > Its more like , "At offset 3bf543......" |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.