In addition to PST archiving and search operations, the PST Processor can also perform mass migration of items from a PST. When an archiving policy is configured with the migrate action, the PST Processor moves all message links and other PST items into a designated folder in the user's mailbox.
A typical scenario is to configure one PST policy to archive, and a separate one to migrate with the store criteria set to all PST items archived. Periodically run each policy, and once a PST is fully archived, the message links are moved into the owner's mailbox.
Use the following steps to configure the destination folder in the user's mailbox that holds the migrated PST items:
- Log in to the ArchiveOne Admin console.
- Right-click Coupled PSTs, and click PST Processor Configuration.
- Right-click the Coupled PSTs node, choose PST Processor Configuration, choose a configuration, and click Edit.
- Click the Miscellaneous tab, and enter the desired folder name in the Migration root folder name field.
- Click OK to save the new destination folder name.
- Click Close to close the PST Processor Configuration dialog.
The next time the PST Processor runs, it reads the new configuration settings and data is migrated to the new root folder.
The messages move from the PST file into the PST owner's mailbox as follows:
- The folder name configured as the Migration root folder name is created in the mailbox root (at the same level as the Inbox folder)
- A subfolder is created using the PST display name, for example, Personal folders
- A subfolder hierarchy matching the same hierarchy in the PST file is created as the data is migrated
Note that if the user has two PST files with the same display name, the PSTs are combined into the same hierarchy when the data is migrated into the mailbox.
Mailbox Quota Limits
If you are using to move data into the user's mailbox and the mailbox has a storage limit, be aware that the data migration may exceed the quota limit. Barracuda recommends archiving and stubbing the data in the PST file to reduce the data size migrated to the user's mailbox. If you are unable to increase the user's mailbox quota limit, and the volume of PST data you want to migrate would exceed this limit, consider:
- Only archiving the PST file data and not migrating any data to the user's mailbox. Once the data is archived, the user can access it from the Archive Search website; it is not necessary to have a message stub in the mailbox to retrieve data; data can also be retrieved by browsing or searching from the Archive Search website.
- Archiving all the data in the PST file, but only migrating some of the data to the user's mailbox. For example, set the migration policy criteria with a date range so only the most recent data (for example, the last 6 months) is migrated to the user's mailbox. The user then has a small volume of stubs for recent data in their mailbox for ease of retrieval. As the entire PST file was archived, any older data can be located by using the Archive Search website.