I am involved in setting up a mobile solution…accessing domino via the treo pda. I have setup a domain for this, and created replicas of the mail databases of the users who will be using this feature. In testing my own…what I want to happen is instant replication between the mail databases…this way we I am always looking at a current snapshot of my mail. The domains are cross certified. I can manually replicate the databases successfully. Upon arrival this morning, I realized that they had replicated during the night. But they do not replicate when the primary database receives mail. In the server connection document under configuration->replication via the domino admin client, I have set entry for "route at once if: " to 1 message pending…replication type is Push-Pull, and the schedule s enabled and 24 hrs. It seems that what I want to accomplish would be done via the route at once entry…am I way off here? I am winging it I am def. not an admin…TIA!
Subject: admin question on replication
You have created replicas, so what you need is replication between the replicas of the mail databses. The ‘route at once’ option is used for sending email, but the email has already been received in the original replica. Instead of using the route mail options you should use the replication options on the left of the same form on which you have set the ‘route at once’ option
HTH
Subject: RE: admin question on replication
I figured that…and that helps thanks for clarifying…but on the replication side, there is nothing that indicates forced replication…i.e., when new mail arrives. Maybe the solution is to write an agent which runs when new mail arrives…and use the notesdatabase replicate method? I thought there would be a way to automate this administratively…but that will be a possibility i suppose.
Subject: admin question on replication
I have found a viable option…under the schedule tab there is a repeat interval defaulted to 360 minutes…I set it to 1 minute…and it worked pretty quickly with a test email. So there is a small delay but nothing show stopping. I wish it was real time…this leads to the next question…what impact might this almost constant replication task have on the server performance, if any? It is a small # of users, so it should be minimal if anything I would think.