PST import may not work with data archived prior to EV 8
|Article:TECH74835|||||Created: 2009-01-15|||||Updated: 2014-02-25|||||Article URL http://www.symantec.com/docs/TECH74835|
PST file may not be imported properly into Enterprise Vault when a configuration (.cfg) file is used with a Centera Device for the Vault Store Partition (with Centera Collection) and may generate a SUCCESS in the migration report even though the .pst is not properly imported.
When using the Export Archive wizard, the export creates a .pst file and .cfg file. When importing a .pst file, using the associated .cfg file, which contains data archived prior to Enterprise Vault 8.0, may generate a "SUCCESS" in the Migration report even though the .pst has not been imported correctly.
Note: The .cfg file does not have to be explicitly specified during the PST import. Enterprise Vault will automatically use the .cfg file if it is present in the same location of the pst being imported.
What is Affected
The following version of Symantec Enterprise Vault is affected:
- Enterprise Vault for Microsoft Exchange 8.0
- Enterprise Vault for Microsoft Exchange 8.0 Sp1
- Enterprise Vault for Microsoft Exchange 8.0 Sp2
How to Determine if Affected
The PST import may fail if the following conditions are met:
The pre-EV 8.0 archived data will not be inserted into the vault store correctly. The data will not be indexed or available via the shortcuts. The following Events will be generated when attempting to import.
In addition, the items which has not be processed will also remain in the Collection Area.
How to check if Centera Collections is enabled
1. In the Vault Admin Console, expand the Site Name and Vault Store Groups
2. Expand your Vault Store Group and the Vault Store.
3. On the right-hand side, go to the properties of the active partition and select the Collections tab.
This issue is addressed in the following versions of Enterprise Vault:
This issue only occurs when a configuration file is used as part of the import process. Therefore, by not using the configuration file the import will complete successfully. However, this means that existing shortcuts in the mailbox will not be updated and will therefore be orphaned and not work.
1. In the directory where the .pst file is located rename the corresponding .cfg file to .old. (Example of files: User1.pst and User1.cfg)
2. Open the Administration Console, expand the site, click on Archives, click Action and Import PST... .
3. Select the Vault Store and click Next.
4. Click Add and browse to the location of the .pst file and click Next.
5. Work through the rest of the wizard to complete the import.
Subscribe to this TechNote:
Subscribe to this TechNote for any updates that are made to this article.
Symantec Strongly Recommends the Following Best Practices:
1. Always perform a FULL backup prior to and after any changes to your environment.
2. Always make sure that the environment is running the latest version and patch level.
3. Subscribe to technical articles for updates.
PST imported through VAC when using a .cfg file and importing legacy data
PST Imported though VAC when using .cfg file and importing legacy data with centera collection
Article URL http://www.symantec.com/docs/TECH74835