Certain Archived Items have an Incorrect ArchivedDate and IDCheckSumHigh within the Saveset Table

Article:TECH209243  |  Created: 2013-08-01  |  Updated: 2014-05-02  |  Article URL http://www.symantec.com/docs/TECH209243
Article Type
Technical Solution


Certain  Archived Items have an incorrect ArchivedDate stored in Saveset Table  (within the VaultStore SQL Database).

For example, an Item is archived on the 24th of April 2012.

  1. The location on Disk is:

    Ptn X\2012\04-24\x\xx

  2. Within the Saveset table, the ArchivedDate field should be recorded as the 23rd of April:

    2012-04-24 07:28:25

    However, the date is being recorded as the 23rd:

    2012-04-23 16:35:00Z

  3. If Collection is enabled, the file will then be collected under the following location:

    Ptn x\2012\04-24\x\Collection10.CAB

This problem will give the impression that the Saveset on Disk has actually been manually moved to a different location. 


A repair with EVSVR currently does not work as EVSVR is picking the date as the 23rd of April.



Error ID 6838 can be logged in the Enterprise Vault (EV) Event log
(In this instance, Collection is Enabled)

Type:  Error
Date:  2/13/2013
Time:  4:54:13 PM
Event:  6838
Source:  Enterprise Vault
Category: Storage Online
User:  N/A
Computer: EVServer.local
Failed to recall a Saveset from its Collection.

Reason: The system cannot find the file specified.  (0x80070002)
Relative Saveset Filename: 2011\09-18\5\E34\5E347D5058FF4A96AA5453C92C72B870.DVS
Relative Collection Filename: 2011\09-18\5\Collection30171.cab
PartitionEntryID: 123458187A90D44095A62D654312E28D1q10000EV
PartitionGUID: 12345187A90D44095A62D654312E28D
Partition Root Path: E:\Enterprise Vault Stores\2011EV
Secondary Location:
Migrated File Id:
Reference: NSDR/LMF

For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=


The issue has been reported on the following versions of Enterprise Vault

  1. 9.0.x
  2. 10.0.x
  3. 11.0.x

Only partitions using NTFS File System have been seen to experience this issue


Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see http://www.symantec.com

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. 

Supplemental Materials


Saveset records in VSDB have incorrect Archivedate and IDCheckSumHigh

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

Terms of use for this information are found in Legal Notices