10-29-2015 03:15 AM
Hi,
I have an EV 10.0.4 infrastructure which has been archiving from Exchange 2007 just fine. We are currently migrating to Exchange 2013, and to this end have setup new tasks on EV to archive the new Exchange 2013 servers. Permissions are ok as is the Outlook version (2007 SP3 + hotfix), tasks run ok, items are archived from all servers, it just appears the tasks running against the 2013 servers run at a much slower rate.
For instance, jobs for 2007 and 2013 have the same schedule (7pm till 1am), concurrent connections (5) and max items per pass (1000) but the 2013 server jobs look like they only do a single pass on the mailboxes, while 2007 server job appears to continue running untill the windows closes. I'd expect to see the same behaviour on the 2013 server tasks seeing as they are setup the same and in the same site, or am i mistaken?
Enterprise Vault site | EvSite01 |
Start time | 28/10/2015 19:00 |
End time | 28/10/2015 19:10 |
Processing time | 00:10:49 |
Run type | Scheduled |
Run mode | Archiving and shortcut processing |
Run ID | Scheduled_20151028_190005 |
Items archived | 1589 (186.1 MB) |
Enterprise Vault site | EvSite01 |
Start time | 27/10/2015 20:00 |
End time | 28/10/2015 01:06 |
Processing time | 05:06:34 |
Run type | Scheduled |
Run mode | Archiving and shortcut processing |
Run ID | Scheduled_20151027_200001 |
Items archived | 93882 (15710 MB) |
Any ideas or assistence would be appreciated, cant seem to identify why the jobs for 2013 dont continue to run.
Thanks
10-29-2015 08:19 AM
could be a dozen things so before getting to far on guesses, probably best to perform a dtrace during the archiving run and see what's going on with the 2013 task
10-29-2015 10:36 AM
Its a fair comment, i did this on a run now archiving job against one of the 2013 servers, used hte GUI to DTRACE Mailbox Archiving Issues (Exchange ) category. Generated an 84MB log file in 30 mins, yet the archiving task only ran for 2 minutes. Bit of a wood for trees scenario due to the size of the trace, but it seems to keep mentioning domino, things like the below which kind of seems wrong as its definitly an Exchange task.
41027 14:01:28.309 [22032] (ArchiveTask) <23608> EV:L {PropsItem::HasShortcutProps:#149} Shortcut properties are not present (incorrect MAPI type; expecting PT_STRING8).
41028 14:01:28.309 [22032] (ArchiveTask) <23608> EV:L {MigratedDominoItems::IsMigratedDominoShortcut:#198} Missing shortcut properties that are indicative of a migrated Domino shortcut.
41029 14:01:28.309 [22032] (ArchiveTask) <23608> EV:L {MigratedDominoItems::IsMigratedDominoShortcut} (Exit) Status: [Success]
Reading up through the trace potentially issue could be
566131 14:02:41.076 [3092] (StorageArchive) <15328> EV:H Error MAPI_E_NOT_ENOUGH_MEMORY (0x8007000E): Attempting to read the property into a stream...
Lots of information there, just not sure exactly what im looking for, any keywords to check for would be appreciated
Thanks
10-29-2015 11:19 AM
are you seeing anything in the event logs during the run?
that MAPI error has a few different causes such as issues communicating with a domain controller or global catalog. those, off the top of my head, will slow down your archiving considerably.
how much longer are you keeping exchange 2007? any plans to get to EV 11.0.1 so you can use outlook 2013 on the EV server?