Under certain circumstances, importing a .pst file in Symantec Enterprise Vault (EV) 8.0 through the Administration Console using a configuration (.cfg) file may generate a SUCCESS in the migration report even though the .pst is not properly imported.

Article:TECH67522  |  Created: 2009-01-04  |  Updated: 2014-02-26  |  Article URL http://www.symantec.com/docs/TECH67522
Article Type
Technical Solution


Issue



Under certain circumstances, importing a .pst file in Symantec Enterprise Vault (EV) 8.0 through the Administration Console using a configuration (.cfg) file may generate a SUCCESS in the migration report even though the .pst is not properly imported.


Error



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-7287


Cause



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.
 

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.

Symantec has uncovered an issue where the TID character change was not correctly converted during the import.
 

The Export Archive functionality is used when customers have a requirement to move an archive from one Enterprise Vault (EV) server/site to another, perhaps due to geographical relocation of a user. This move often mirrors a user's mailbox move within Exchange.


What is Affected
The following version of Symantec Enterprise Vault is affected:
Enterprise Vault for Microsoft Exchange 8.0
How to Determine if Affected
The following two scenarios are affected when using a .cfg file.

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

2. Pre-Enterprise Vault 8.0 archived data exported from an EV 8.0 installation and imported into another 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

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.

 


Solution



This issue has been addressed as part of the following releases:

Enterprise Vault 8.0 Hotfix:
http://entsupport.symantec.com/docs/319373

This Hotfix will ensure that importing using a configuration file completes successfully after applying the Hotfix. However, it will not fix any issues resulting from previous import attempts.


Enterprise Vault 8.0 SP1 - Release Details
http://www.symantec.com/docs/TECH63621


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.


How to Subscribe to Software Alerts:
If this TechNote was not received from the Symantec Email Notification Service as a Software Alert, please subscribe to receive alerts. 

Supplemental Materials

SourceETrack
Value1499601
Description

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



Legacy ID



318602


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


Terms of use for this information are found in Legal Notices