Getting Synchronization Statistics
You can get public folder synchronization statistics using the Get-MMExPublicFolderStatistics cmdlet. To understand how to configure statistics and how to use it refer to Tuning Statistics.
|
|
IMPORTANT: Currently, regardless of which direction of synchronization is selected, all counters display source item statistics. But you can track all events, if any. |
You can get information about public folder collection using Get-MMExPublicFolderStatistics cmdlet. Currently there is only one public folder collection.
Tuning Statistics
To select what information can be retrieved by cmdlet, use the following command:
Get-MMExPublicFolderStatistics | fl
The list of available fields is displayed.
|
|
TIP: Some hidden fields, like IsSuspended are not displayed, but can be used, as described below. |
To obtain a list public folders to see for what folders synchronization is suspended, run cmdlet Get-MMExPublicFolderStatistics as follows:
Get-MMExPublicFolderStatistics | select Path, DisplayName, IsSuspended.
How to use with PowerShell Out-GridView
You can select type of statistics data to display:
Get-MMExPublicFolderStatistics | select Path, Progress, DiscoveredItems, ProcessedItems, FailedItems, LastProcessedTime, LastError, DisplayName, FolderID | Out-GridView
This command display statistics for the public folder including the following data:
- Path specifies the location of the folder in the folder hierarchy, for example, \Legal\Cases.
- Progress specifies current synchronization progress of a public folder. It is calculated as the ratio of number of items already processed by the agent to the total number of discovered items. Note that this number can also decrease when, for example, a new content is added causing number of discovered items to increase.
- DiscoveredItems specifies the number of items discovered in the public folder
- ProcessedItems specifies the number of the number of items processed in the public folder
- FailedItems specifies the number of the number of items that failed to be processed in the public folder
- LastProcessedTime specifies timestamp that indicates when last processing of a public folder was completed. The time zone is the same as used in console.
- LastError specifies the error message of the last appeared error (if any) in the current or previous migration sessions. After the error is fixed, the fields gets cleared.
- DisplayName specifies displayName property of a user who owns the public folder
- FolderID specifies public folder identifier
How to use with PowerShell Out-GridView -PassThru
To initiate resynchronization for the public folders that match selected criteria, take the following actions:
Request statistics using Get-MMExPublicFolderStatistics, select problem folders, press OK
Get-MMExPublicFolderStatistics | select Path, Progress, DiscoveredItems, ProcessedItems, FailedItems, LastProcessedTime, LastError, DisplayName, FolderID | Out-GridView -PassThru |Restart-MMExPublicFolderMigration
Migration was restarted for the item 'F1' (#7) from the collection 'PFColl_DMMCONSOLE' (#2).
Migration was restarted for the item 'IPM_SUBTREE' (#4) from the collection 'PFColl_DMMCONSOLE' (#2).
Migration was restarted for the item 'Root01' (#6) from the collection 'PFColl_DMMCONSOLE' (#2).
Specific Case Workarounds
|
|
IMPORTANT: Public Folders are matched by their EntryId values. Source EntryID and target EntryID pairs are stored in project database. In case of any EntryID change, refer to this section to work it around manually. |
The following cases might need additional settings:
The following cases need to be worked around manually:
Resolving the public folder synchronization issues for specific environments:
The public folder deleted
If the source or target public folder deleted (hard or soft), the deleted public folder be handled automatically depending on the UsePublicFolderRecycleBin parameter of migration project. The following cases are possible:
- If source public folder has been deleted including all subfolders and migration project parameter UsePublicFolderRecycleBin set as True (default), then matched target public folder with all subfolders will be moved to the target Migration Manager Recycle Bin folder. If the Migration Manager Recycle Bin public folder does not exist, it will be created automatically. In case the Migration Manager Recycle Bin folder already contains the deleted public folder, both versions will be retained, but a later version will have an added number tag for the folder name.
- If target public folder has been deleted including all subfolders, and migration project parameter UsePublicFolderRecycleBin set as True, and two-way synchronization is enabled, all matched source public folder with all subfolders will be moved to the source Migration Manager Recycle Bin folder. If the Migration Manager Recycle Bin public folder does not exist, it will be created automatically. In case the Migration Manager Recycle Bin folder already contains this deleted public folder, both versions will be retained, but a later version will have an added number tag for the folder name.
- If public folder has been deleted in source and target, this deleted folder will not appear in source and target Migration Manager Recycle Bin folder.
|
|
TIP: To avoid storing deleted public folders, set UsePublicFolderRecycleBin to False. |