This article explains how and when this happens, through the use of two examples. During these tests, we have selected the option to finalize PSTs in Stage 1, as shown below:
If that option is not selected then no PSTs will be moved from the temporary PST location to the PST Output Path until Stage 2 commands run to perform that task.
Let’s take two example archives, as shown below:
The first archive is about 4.5 Gb, which is more than double the default PST Rollover Threshold of 2 Gb. So we would expect multiple PST files to be generated during this export. (As the screenshot shows, that did happen).
The second archive is only just over 300 Mb. So we would expect only a single PST file to be generated.
During the test migration, auto-enable for stage 2 was not enabled.
At the end of stage 1, what we had on the PST Output Path is this:
We have no PSTs from the second, smaller archive.
We have all except one PST file from the larger archive.
If we look at the temporary location where PSTs reside whilst they’re being built, then we see this:
What this means is that Archive Shuttle will move all except the last PST from the temporary PST location to the PST Output Path, during Stage 1. If the archive being migrated only has one PST, then that PST will not move in Stage 1. If the archive being migrated has 8 PSTs (or X PSTs) then 7 PSTs (or X-1 PSTs) will be moved during Stage 1.
The final PST will move during Stage 2.
The idea behind this process is that the staging area, or temporary PST output location do not get filled up with PST files which are complete.
Archive Shuttle will move all except the ‘last’ PST file for an archive from the temporary PST location to the PST Output Path during Stage 1. If the archive being migrated has 8 PSTs (or X PSTs) then 7 PSTs (or X-1 PSTs) will be moved during Stage 1.
With large archives (1 million+ items) more than one PST may remain in the temporary PST location, and will not be closed, and moved during Stage 1.