EV email Item archiving processes
Hi
I'm not really sure how to ask this question without rambling on too much :o)
But essentially I'm trying to find out the stages and the sequence of those stages that an EV server will take to fully index and archive an email from exchange. My purpose here is to find out what scenario's may arrive should an EV server suffer a failure mid-way through emailing an item and how it would recover that item.
The kind of info I'm after is something along the lines of:
email Item sent to archive message queue (eg A5) - if EV suddenly fails at this point all the queues are flushed and item not archived
else the Item moves from queue into EV temp folder and converted to HTML - if EV fails at this stage item is not archived
else an Entry is made in Vault Store database - if EV fails here a discrepancy will exist between Vault Store database and Vault store partition - EVSR needs to be run to sort this out
next Item enters SIS process and fingerprint database updated - If EV fails after this, then again EVSR needed to sort out
Item written to Vault store and archive of item is complete but not indexed - if EV fails then item shortcut is not updated to pending and EV will attempt to re-archive the same item on next run - searches on this item will not return any results.
Item is indexed - if EV fails during idexing process EV will not update index but item complete the archive process however search actions will return no results.
Does that make sense?
perhaps the answer to my query is as simple as "As the shortcut is not updated until all the archive process and indexing processes have completed and therefore nothing really matters as until the shortcut is updated the item will always be reattempted for archive as it is still an ipm.note message class"
thanks in advance to anyone who can understand what I'm on about :o)
cheers
I think this is what you are looking for.
General Storage Process Flow
Article:HOWTO84800 | Created: 2013-06-13 | Updated: 2013-06-13 | Article URL http://www.symantec.com/docs/HOWTO84800