RE: PF replication, latency and archiving

2009-05-28 Thread Eric Hanna
Kurt, Speaking on the SEA side of things, it sounds like Exchange is housed at each respective location? If so, it might be best to have a SEA server at each location so that you don't have to archive and retrieve over your WAN (which could cause some bandwidth issues once everything is set

Re: PF replication, latency and archiving

2009-05-28 Thread Kurt Buff
We have an Exchange 2003 server at each location. No way we're going to spend more money on more infrastructure, though. One instance of SEA is all we're going to get. However, we are message journaling the foreign offices back to the US office. I'm hoping that helps significantly. Kurt On

Re: PF replication, latency and archiving

2009-05-28 Thread Kurt Buff
Hit send too soon... Also, we've been manually archiving the message journaling mailbox for years, and saving the daily PST files to disk and tape. Kurt On Thu, May 28, 2009 at 12:17, Eric Hanna eri...@sunbelt-software.com wrote: Kurt, Speaking on the SEA side of things, it sounds like

RE: PF replication, latency and archiving

2009-05-28 Thread Sobey, Richard A
PF replication will always take a lesser precedent to normal mail traffic, and you can configure it to happen out of hours, if any such things exists in your company. You might also have the luxury - depending on costs and how much time you have - of setting up an Exchange PF store on a new

Re: PF replication, latency and archiving

2009-05-28 Thread Kurt Buff
That will probably prove useful. I'll make note of that during the conversations we have. On Thu, May 28, 2009 at 13:29, Sobey, Richard A r.so...@imperial.ac.uk wrote: PF replication will always take a lesser precedent to normal mail traffic, and you can configure it to happen out of hours, if