PST Management Remains A Problem for Exchange 2010

Exchange 2010 lets users import their PST data to their primary mailbox or their archiving mailbox. The PST import feature is run from the Exchange Management Console and it can also be scripted using PowerShell.
The many problems of PST files are well understood. However, uploading them back into Exchange isn't always the right choice:

  • The PST import tool works one file at a time. Depending on the number of PSTs, this can take a lot of time.
  • The PST import tool cannot browse and find PST files on its own. PST location is required, hence it involves end user involvement.
  • PST contents are loaded back into Exchange Stores. Depending on the total amount of PST data, the total capacity required can be huge.

The key questions to ask include:

  • How many PST files exist and what is the total quantity of data?
  • Considering the PST import tool performs one file at a time, how long will it take you to complete the job?
  • Considering the total amount of PST data, what will the resulting impact be on Exchange storage, availability and disaster recovery?

If you want to eliminate PST files, but not restore the PST contents back into Exchange, several third-party applications can help.  A new one is TransVault Insight.

Bob Spurzem --- In addition to his role as Ferris analyst, Bob is director of product marketing at Iron Mountain Digital Division, which was recently purchased by Autonomy.

Post a comment

You must be logged in to post a comment. To comment, first join our community.