04-16-2009 04:58 AM
We have a new EV 8.0 implementation running journaling and mailbox archiving.
Journaling is working away quite happily, until we reboot our Exchange server at which point it fails and the backlog begins in the journal mailbox
The Exchange serversreboot is something our datacentre provider does because of a memory overflow issue that caused our email server to crash on numerous occasions. Instead of trying to fix the root cause of the issue, reboots twice a week was their answer.
So my question is, can I configure the JournalTask to retry connecting to exchange over a period of time or does it attempt connection once and the task then falls over? I thought it would be more resiliant to what is a very small outage of 3-4 minute as the exchange server reboots.
Anyone any ideas how I can overcome this issue without resorting to manual procedures? (what I'm currently resorting to)
Cheers
D.Misbehavis
04-16-2009 05:11 AM
04-16-2009 05:12 AM
04-16-2009 09:27 AM