Background client replication not creating a session on Domino?

HCL Domino Domino Forum
1

Here’s the problem - User’s mail file is set to local in the location doc with a replication schedule of 15 minutes to the home server. User isn’t receiving asynchronous ‘new mail’ notifications from the router and therefore isn’t initiating a background request to replicate when new mail arrives on the server. For some reason, the user never shows as being connected to the server and hence the router won’t issue the new mail notification (verified in administrator, Notes Users list). Once they open a db directly on the server, then a session is held by the server and the new mail notifications work properly.

This is only the first of 500 users that will be set up this way. I would like to keep the replication interval at 15 minutes to reduce WAN traffic, but don’t want the users to have to wait 15 if they do receive mail.

Is there any way that the server will recognize background client replication as a true session?

Notes: 6.0.1 on Win2000

Domino: 6.0 on OS/400 V5R2

2

Subject: Background client replication not creating a session on Domino?

Notes / Domino is a client / server solution. Unless the target is a server then it will not have any data pushed to it. The Notes client has been setup correctly and working as expected. The client will only notify when the local mail file has something to yell about. Since the mail file is being referenced locally it is totally relient on the replication schedule to pull data down / alert client.

You could increase the replication scheule but then your bandwidth utilisation will just sky-high - catch 22.

–

Jaime

3

Subject: Not True

When you have addressing set to ‘local and server’ in the location doc, the client will initiate background replication with the server when it receives an asynchronous new mail notification from the server router.

My problem is - why doesn’t the server retain a session for background replicating users? The console shows ‘opened session for…’ then ‘closed session for…’ when replicating. Is there a way for the server hold a session for the replicating (local mail) users without them having to access a db directly from the server?

4

Subject: documented in the 6.0.1 release notes

http://www.lotus.com/ldd/doc/domino_notes/6.0.1/readme.nsf

5

Subject: RE: documented in the 6.0.1 release notes

This feature seems nice, but in my testing, seems a bit unpredictable.

(ND6.0.1, server and client)

Mail file: Local

Mail Addressing: Local and Server

I restart Notes clean. send myself a message. (replication set to 15 minutes).

After exactly 1 minute, my client “sees” a new message on the server, replicates, and shows me a new mail indicator. That worked great.

I delete that message, and send another. A full 3 minutes passes and no indication of new mail. I send another message. I receive an indicator 15 seconds later. I send another message within 15 seconds. I get no indicator.

I send another message 3 minutes later. I get the indicator. I wait 30 seconds and send another message. After 5 minutes, still no indicator. I go ahead and replicate manually to sync up and start fresh, one minute passes.

I send a message, I get an indicator 40 seconds later. I wait 2 minutes, send another message, get an indicator in 8 seconds. I immediately send another message within 15 seconds and get no indicator after 3 minutes. I send another message and get the indicator in 30 seconds, replicating that msg and the previous.

Seems that it works, but there must be some time that passes before it will notify again. One last time, I sent a message, got notification in 40 seconds, then waited over 1 minute and sent another message, and again got notification, in 20 seconds.

So, maybe it just needs a certain amount of time between messages, otherwise you have to wait for the next scheduled replication, OR another message to arrive a couple of minutes later.

Anyone else done some timing tests on this? I’d be curious.

-Greg

6

Subject: RE: documented in the 6.0.1 release notes

Greg, have you ever been able to make this work well?

7

Subject: RE: documented in the 6.0.1 release notes

Haven’t worked with any large numbers of users with this, but in testing scenarios, yes it works fine. Then again, my most recent look at it was with 6.51. Not sure about 6.01.