Hi,
I'm at the end of a big migration from 2003 to 2010. On 2010 we have 3 server: 1 for CAS e 2 MBX ( MBX01 and MBX02 ( this is the latest node installed ) with DAG. The customer heavy use the public folder mail enabled ( 400GB of data ). Until now we have pf replica between 2003 and 2010.
Until now we have pf replica between 2003 and the first Exch2010 server (MBX01).
All the email flows work properly with this configuration.
We added a public folder db on the second Exchange 2010 server (MBX02) to create a replica of the public folder db owned by MBX01.
But when we change the replica for a single public folder, adding the public folder on MBX02, we have delay to see the new email sent internally
to this public folder.
The email received from outside (internet) are delivered in real-time with no delay.
If we check the email delivered with delay, it seems that goes on the second Exchange 2010 server MBX02 and then delivered to the public
folder db stored on MBX01.
I configured the replica at 1 minute, but this is not possible to use in the future when all pf will be migrated.
I think that there is some Microsoft design constraint that is public folder replica is not possible to use as load balancing, so my idea is to point to MBX02 ( or master replica ) as default public server and use MBX01 as backup public folder database.
Obviously, our goal is to dismiss Exchange 2003 asap but this delay is a problem to fix before.
How Can I catch which is the master replica? How solve this?
Thank you
Best Regards Biagio Paruolo Italy