A mismatch of SQL databases can occur when an EnterpriseVault directory database is restored to a date prior to the latest update of an associated Vault Store database. As a result, items may exist in the Vault Store database, but the associated Archive, ArchiveFolder, or Root entry will not exist in the EnterpriseVaultDirectory database. This can lead to various issues related to retrieving items from storage.
Some of the errors identified are as follows:
1) Event ID: 6794 Error restoring Saveset during export operation. (Can occur when exporting an archive to a PST file or to the original mailbox)
2) ERROR: Failed to get the archive entry id related to the saveset's archive folder id. (Can occur when performing an EVSVR Verify-Complete operation)
3) Event ID: 7119 Secured item verification failed for one or more SIS parts of a saveset. Following further information is available. | Partition Name = VS01 Ptn1 | VaultStoreEntryId = 1FFFFC65619C5F74C8AB4049F74BB921F1210FFFsymc-evlt-dom-1 | Saveset TID = A07D8C3FBE368BA233CBD7A25A510421 | Reason = Error reading Vault Entry from Vault Directory [0xc00418e7] |
4) Event ID: 6511 Error deleting WatchFile database record for missing Saveset file |[Partition: VS01 Ptn1] |[Vault ID: 1700F3E58C45E7F47832774E2A6B7F10B1110000symc-evlt-dom-1] |[Saveset Filename: 2011\01-27\D\07D\A07D8C3FBE368BA233CBD7A25A510421.DVS] |[Transaction ID: A07D8C3FBE368BA233CBD7A25A510421] |
The cause of this issue is a mismatch of databases where items exist in the Vault Store Database, but the associated Archive, ArchiveFolder, or Root entry will not exist in the EnterpriseVaultDirectory database.
This issue has been addressed as part of the following release:
Enterprise Vault 9.0.4 - Release Details
Enterprise Vault 10.0.1 - Release Details