EV 6.0 : whats happenign with the sync job?

[Matthew_Millers]

Hi,

How do i find out exactly what is happening with the synchronization job? Can i turn up any logging to a file or something?

I checked the MSMQ folders, is a6 the correct one for sync? At the moment is 2, what does that mean exactly? Is this how many mailboxes it has to sync?

Matthew

[Micah_Wyenn]

Matt,
If you're interested in progress, you can watch a dtrace of the archivetask. However, even that won't give you the best status in the world, just let you know when it's essentially finished. I guess we should really ask what your needs actually are.

micah

[Matthew_Millers]

Hi,

I have another forum question open for this, but basically we were using the trigger file, which did not appear to be working. I deleted the trigger file before a incremental job ran, some time later we noticed high rpc activity on the exchange server, exmon cam back with the EV server as the top 10 users.

Why would this cause such an issue? What is actually happening? I assume it is the sync task, but i may need to run dtrace to confirm.

Matthew

[Matthew_Millers]

Hi,

I have dtraced the archive process, even though the job is out of schedule, i see the following section for a lot of mailboxes, could someone tell me what these are?

26884618:14:39.293 (ArchiveTask)<10156>EV:MCAA::GUP() - is using Policy : Default Exchange Mailbox Policy
26884718:14:39.293 (ArchiveTask)<10156>EV:H:CArchivingAgent::PostProcessArchivedItem() |Attempting to delete the body of the shortcut |
26884818:14:39.293 (ArchiveTask)<10156>EV:MRemoveTransactionIDFromMsg : Property not present .
26884918:14:39.293 (ArchiveTask)<10156>EV:MAddProps: Processing: (null)
26885018:14:39.293 (ArchiveTask)<10156>EV:MAddProps: Using 1 additional shortcut properties
26885218:14:39.309 (ArchiveTask)<10156>EV:MCBaseDirectoryServiceWrapper::CreateDirectoryService(): Using local directory connection
26886718:14:39.340 (ArchiveTask)<10156>EV:MCBaseDirectoryServiceWrapper::CreateDirectoryService(): Using local directory connection
26888318:14:39.371 (ArchiveTask)<8236>EV:H:CArchivingAgent::PostProcessArchivedItem() |Getting the value of the createShortcut flag from the Shortcut message |
26888418:14:39.387 (ArchiveTask)<10156>EV:H:CArchivingAgent::PostProcessArchivedItem() |Return the MAPI session to the session pool |
26888518:14:39.387 (ArchiveTask)<10156>EV:MCArchivingAgent::IncrementOpsLeadingToRecycle - Current Count Recycle at |
26888618:14:39.387 (ArchiveTask)<10156>EV:H:CArchivingAgent::PostProcessArchivedItem() |Exiting routine |
26888718:14:39.387 (ArchiveTask)<10156>EV:H:AgentMessageDispenser::ActivateObject() |Exiting routine at point A |
26888818:14:39.387 (ArchiveTask)<10156>EV:M:AgentMessageDispenser::ProcessNextMessage() |ActivateObject has returned successfully |
26888918:14:39.387 (ArchiveTask)<1380>EV:H:CArchivingAgent::PostProcessArchivedItem() |Getting the value of the createShortcut flag from the Shortcut message |
26889018:14:39.387 (ArchiveTask)<10156>EV:M:AgentMessageDispenser::ProcessNextMessage() |Retrieved a message successfully from the queue |
26889118:14:39.387 (ArchiveTask)<10156>EV:M:AgentMessageDispenser::ProcessNextMessage() |Read new message or a message that is within its retry limit (). |About to process the message body |
26889218:14:39.387 (ArchiveTask)<10156>EV:H:AgentMessageDispenser::ActivateObject() |Entering routine |
26889318:14:39.387 (ArchiveTask)<10156>EV:M:AgentMessageDispenser::ActivateObject() |Message type indicator = MsgID_RemoveBody |
26889418:14:39.387 (ArchiveTask)<10156>EV:L:AgentMessageDispenser::ActivateObject() |Called server side object, with arguments: |m_pIArchivingAgentUpdate->PostProcessArchivedItem(OriginatingAgent = "1F30B75872C488B409C317E769939669D1011z00EVSite",| m_pIShortcutAccessor,| m_pILocation,| SavesetID = "380000000000000~200701222337190000~0~16A262D2AFDE491E8B67A2BD5152C62",| VaultID = "1AED7C5C081F37C4EA01B976195AADBF01110000EVSite",| nRetryCount = 0,| NULL);| |



Thanks
Matthew

[Michael_Bilsbor]

Hi,

That snippet shows
PostProcessArchivedItem()

which means it's turning an archive pending item into a shortcut.
It does that type of operation in preference to other requests.
So for example if there are requests on the a1 queue it will process them in preference to a6

[Matthew_Millers]

Hi,

Should it be performing these actions outside of the task window?

Regards
Matthew

[Michael_Bilsbor]

Hi,
Yes, we will always try turning items into shortcuts if there are requests to process.
So it means that at the time perhaps this was just after your backups had occurred and the task was receiveing requests to turn the items just backed up into shortcuts.

[Matthew_Millers]

Hi,

One last question, what trace option would i set in dtrace to see these actions taking place? I am tracing the ArchiveTask but do not see any activity.

Matthew

[Michael_Bilsbor]

yes archivetask is correct
so if you do not see any dtrace it's not doing anything.