An EVSVR FileSystem DirectoryArchives Repair does not repair certain records

  • Modified Date:
  • Article ID:000088014


EVSVR is used to help in repairing Enterprise Vault (EV) SQL Database Inconsistencies, for example following a Disaster Recovery scenario involving a restore of an older version of the SQL Database.
The DirectoryArchives repair option helps in synchronizing the  Archive (ArchivePoint) and ArchiveFolder (Vault) records between the EnterpriseVaultDirectory and VaultStore Databases.

When configuring the options for a DirectoryArchives Repair, the ArchiveType needs to be specified. I.e.:

  1. ExchangeMailbox
  2. FileSystem

While repairing the database, certain records that have been highlighted as needing repair are simply skipped with no information as to why they were not repaired.


Error Message

No errors are reported.


EVSVR Log Snippet
1. For instance, ArchiveFolder  with issues:

2013-01-23 12:36:37        ArchiveFolder records missing: 470
2013-01-23 12:36:37            Including Archive records: 0
2013-01-23 12:36:37            With Items:                132


2. Considering a small archive - Test2, during step 10 we successfully found an ArchiveFolder EntryID and Folder Path

  Archive EntryId: 14C5E2509B8A127419F97DE715AD0C8DB1110000EVSite, Archive Name: Test2

    ArchiveFolder EntryId: 18780AE54D0B35540BF14A55350C057A71110000EVSite, Identity:      2, Folders:   3, Folder path [I]: \\FileServer1\Test2\Users
    ArchiveFolder EntryId: 19832EF126F14644ABEA9CFBD3819113B1110000EVSite, Identity:      1, Folders:   3, Folder path [I]:  \\FileServer1\Test2\SharedFolders
    Folder paths found: 2, total for this Archive: 2, remaining: 0


3. During the Repair, nothing got repaired  and no errors got logged, especially in Test2 which had 2 records to be repaired and all the previous steps were successful

2013-01-23 12:56:28        Step 11 - Recreate missing ArchiveFolder records
2013-01-23 12:56:28        ------------------------------------------------
2013-01-23 12:56:28 
2013-01-23 12:56:28          [C] - Created
2013-01-23 12:56:28          [R] - Recreated
2013-01-23 12:56:28 
2013-01-23 12:56:28          Archive EntryId: 16D74E755CF240F49B47C58B1F34ACB4A1110000EVSite, Archive Name: Test1
2013-01-23 12:57:00 
2013-01-23 12:57:00            Archive Folder records inserted: 0, existing records reused: 0
2013-01-23 12:57:00 
2013-01-23 12:57:00 
2013-01-23 12:57:00          Archive EntryId: 14C5E2509B8A127419F97DE715AD0C8DB1110000EVSite, Archive Name: Test2
2013-01-23 12:57:01 
2013-01-23 12:57:01            Archive Folder records inserted: 0, existing records reused: 0
2013-01-23 12:57:01 
2013-01-23 12:57:01
2013-01-23 12:57:01          ArchiveFolder records missing:         470
2013-01-23 12:57:01 
2013-01-23 12:57:01          ArchiveFolder records recreated:       0



This issue has been addressed in the following release:

Enterprise Vault 9.0.4 Cumulative Hotfix 5

Enterprise Vault 10.x
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.

Symantec Corporation currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. A link to the patch or hotfix download will be added to this document when it becomes available. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests.  Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk. 


Applies To

The following Enterprise Vault versions for File System Archiving  are affected:

  • EV 9.0.2
  • EV 9.0.3
  • EV 9.0.4


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)