Or perhaps WAN utilization changed. Do you have stats on that you can refer to?
On Mon, May 10, 2010 at 09:33, Roger Wright <rhw...@gmail.com> wrote: > The BES and BE servers are connected over a WAN link. What confuses > us, though, is this delay just started about 10 days ago. Prior to > that the messages would sometimes hit my BB a second or two before > they'd appear in my Outlook folders. > > I know, I know... "what changed?" That's what I'm trying to > determine... Perhaps a BE server reboot is in order. > > > Die dulci fruere! > > Roger Wright > ___ > > > > > On Mon, May 10, 2010 at 12:22 PM, Brian Hintz <bhi...@gmail.com> wrote: >> Assuming this BES and BE server are separated by a WAN link, you may be >> running into a common problem with the BES product. >> >> RIM usually recommends that the BES is as close to the mailbox as possible. >> The latency between the BES and the mailbox can prevent the UDP messages >> from reaching the BES messaging agent in a timely manner so mail isn't >> picked up and delivered to the handset in real time. >> >> The 20 minute delay is the manual mailbox reconciliation process that the >> BES runs to catch any mail that is missed. >> >> See this link in the RIM KB for an explanation of latency impact - >> http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB14139&sliceId=SAL_Public&dialogID=53728817&stateId=0%200%2027577931 >> >> and this one for debugging steps - >> http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/7979/1181821/278286/745137/Capacity_Planning_and_Performance_Tuning_for_Environments_Using_the_BlackBerry_Enterprise_Solution.pdf?nodeid=973626 >> >> >> >> On Mon, May 10, 2010 at 10:45 AM, Roger Wright <rhw...@gmail.com> wrote: >>> >>> Our BES server is located in the parent office where the Exchange 2003 >>> FE server resides and the Exchange BE server is in our local office. >>> >>> For the past week or so BB messages are arriving about 10-20 minutes >>> behind the time the messages hit the users's mailboxes on our BE >>> server, for both AT&T and Verizon clients. Our parent office >>> indicates no problem for their users. >>> >>> Does this sound like a FE, BE, or BES issue? >>> >>> >>> >>> Die dulci fruere! >>> >>> Roger Wright >>> ___ >>> >>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> >> >> >> > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
