You may be wondering how the item routing for pst migration is happening, this article explains how it is performed by Archive Shuttle.
When you are migrating to PSTs, several tables are populated in the Archive Shuttle Item database, and it can take some time as many variables are in place.
Once the mapping is created and items are collected, the routing will start. For migrations other then PST, items are populated in the ItemRouting table and (for example) for EV migrations in the ItemRoutingEnterpriseVault table. Each target has its own ItemRouting table. In the case of PST migration, there is an additional step happening; not only are the items populated into the ItemRouting table, but also a Subcontainer entry is created in MailNativeSubContainer table, and after that, items are routed to PST subcontainers in ItemRoutingNativeMailSubContainer table.
This is happening after only after following conditions are met:
1) Export module need to be enabled and running – this means if you stop the Export module, the routing can not take place and eventually ingest into PSTs will stop
2) NativeFormatImport module needs to be enabled and running
3) RoutingInProcess Flag in ContainerMappingContentOperations table in Archive Shuttle Directory database need to be Set to 1
You can check the routing progress by executing the query below on Archive Shuttle Item database with using the Container Mapping ID. It will show you how many items are routed per subcontainer, and if there are still some which need to be routed (MailNativeSubContainerId = NULL).
SELECT [MailNativeSubContainerId], COUNT(ir.itemid) as 'num items' FROM [dbo].[ItemRouting] ir LEFT JOIN [dbo].[ItemRoutingNativeMailSubContainer] sc ON ir.ItemRoutingId = sc.ItemRoutingId WHERE ContainerMappingId= XXX -- add container mapping id GROUP BY [MailNativeSubContainerId] ORDER BY MailNativeSubContainerId