The Public Folder job seems to be processing the Public Folders slowly. When examining a Public Folder agent log(s) the following messages are found:
"SyncMachine::Init TraceMsg 2203 Locking tracking database 'C:\emwstp.dat'. "
"FileResource::CMutex::IsLocked TraceMsg 4300 Waiting for the resource to be unlocked."
The Public Folder agents are trying to use the same resources such as the tracking database, emwstp.dat and the mailbox on the server.
The Public Folder Source Agent (PFSA) and Public Folder Target Agent (PFTA) cannot run simultaneously on the same server. When one of the agents is running, the other one must wait for it to complete its session. While waiting for the resource to be unlocked, the agents do not stop for the synchronization interval unless their sleep is scheduled for that time. As soon as the resource is unlocked by one agent, another one immediately starts processing the resource.
This issue is planned to be fixed in a later version of QMM.
Here are some suggestions for setting the agents.
If this is an initial sync of the Public Folders then the public folders will need to be migrated to the target server. If no mailbox have been switched and there is no users on the target server using the public folders, then the best thing is to stop the agents which are related to the target server. This would be as follows:
Source server
PFSA - on
PFTA - off
Transmission agent - on
Target server
PFSA - off
PFTA - on
Transmission agent - off
Once mailboxes have been switched to the target server and users on the target server are using public folders then turn on the target related agents.
If there are users already migrated on the target and using the public folders then the sleep time for the agents needs to be staggered. These are only suggestions and depending on the number of public folders the times may need to adjusted.
Source server
PFSA - sleep - 5 minutes
PFTA - sleep - 15 minutes
Transmission agent - on
Target server
PFSA - sleep - 15 minutes
PFTA - sleep - 5 minutes
Transmission agent - on
Again these are only suggestions. After the initial sync and when the agents are in delta mode, the PFSA needs to search all of the public folders to see what has changed. It may take considerable time if the public folder store is large and there are a lot of items in each folder.
Please see the following solutions for important info on how public folders are processed.
SOL60567 - Does the PF agent copy entire PF hierarchy first or does it gradually progresses folder by folder? - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL60567
SOL60565 - PF (Public Folders) Agents logic when PST size limit is reached - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL60565
SOL60455 - Public Folder full re-synchronization and agents behavior during a resynchronization - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL60455
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center