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
Article Type
Technical Solution


Environment

Issue



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.


Solution



Introduction
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.

 
.pst file - Contains the mail items.
 
.cfg file - Contains the Enterprise Vault metadata associated with the mail items and is used mainly to update shortcuts in a mailbox when moved across different sites.
 

 
With the introduction of Enterprise Vault 8.0 and the new Optimized Single Instance Storage (OSIS) storage model, data is now stored in the database with a 32 character transaction ID (TID).  This differs from the pre-EV 8.0 storage model that utilized a 31 character TID. An issue has been identified where the TID character change was not correctly converted during the import.

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:

 
1. A Centera is used as the storage device for the Vault Store partition with Collection Enabled.
 

 
Note: If you are using a non Centera Storage Device for the Vault Store partition(s), please refer to technote  http://www.symantec.com/docs/TECH67522 
 


 
2. Pre-Enterprise Vault 8.0 archived data (e.g. any version prior to EV 8.0) was exported to PST from a pre Enterprise Vault 8.0 installation and then imported into an EV 8.0 installation.
 

 


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.  
 

 
Event Type:    Error
 
Event Source: Enterprise Vault
 
Event Category:  Storage Crawler
 
Event ID:        7116
 
Description:
 
Failed to access file 'C:\NTFSCollections\2009\01-26\9\74A\974A85019D044175A67AA552BDBF2130.DVS'.
 
Reason: The system cannot find the file specified.  [0x80070002]
 
Operation: READ
 
Reference: SDR/LF 
V-437-7116
 

 
Event Type:    Error
 
Event Source: Enterprise Vault
 
Event Category:  Storage Crawler
 
Event ID:        7083
 
Description:
 
Retrieval of saveset failed.
 
Archive Id: 12862D06D96F95346934693C66C1AB12D51A71110000EV_SITE
 
Transaction Id: 974A85019D044175A67AA552BDBF2130
 
Extended information: The system cannot find the file specified.  [0x80070002]
 
Internal Ref: Vault/RI
V-437-7083 

 
Event Type:    Information
 
Event Source: Enterprise Vault
 
Event Category:  Index Server
 
Event ID:        7287
 
Description:
 
Unable to add the item to the index since it is not currently available from the Storage Service:
 
Reason: Error processing saveset [0xc0041923]
 
Attempt: 3
V-437-7286 


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.


Formal Resolution:
This issue is addressed in the following versions of Enterprise Vault:
  
Enterprise Vault 8.0 Sp3 
 


Workaround:
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.

 

Supplemental Materials

Value1499601
Description

PST imported through VAC when using a .cfg file and importing legacy data


Value1824809
Description

PST Imported though VAC when using .cfg file and importing legacy data with centera collection



Legacy ID



332905


Article URL http://www.symantec.com/docs/TECH74835


Terms of use for this information are found in Legal Notices