Problem
Error : “The requested item is no longer in Vault" with an error 6882 is generated when the Enterprise Vault-store database shows different ‘IDPartition’ for an archived data in the ‘Saveset’ & ‘Collection’ table. For Example:-
Saveset Table:-IDtransaction = 701605F7-31A5-676B-81A9-BDDF89C395D1
IDPartition = 1
CollectionIdentity = 10
Collection Table:-CollectionIdentity = 10
IDPartition = 2
RelativeFileName = '2012\05-31\D\Collection10.CAB'
The CAB extraction process uses the IDpartition & RelativeFilename reference of ‘Collection’ table and extract the CAB files in the partition where the collection record exists. During retrieval the extracted DVS file cannot be find in it's partition as the 'Collection' & 'Saveset's IDpartition are different.
Error Message
“The requested item is no longer in vault”, followed by an event id 6882 is generated in the event viewer of Enterprise vault server while retrieving archived items.
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 6882
Task Category: Storage Online
Level: Error
Description:
Unable to complete retrieval request
Reason: The system cannot find the file specified. (0x80070002)
Vault: Case
Vault Id: 150200837B004DD448E010CC793DA8D221110000domain.local
Item Id: 201504017888284~201503250639050000~Z~701605F731A5676B81A9BDDF89C395D1
Reference: Vault/RI
Failed to recall a Saveset from its Collection. Reason: The system cannot find the file specified. (0x80070002) Relative Saveset Filename: 2015\04-01\6\12F\612F93D715AF81B4573F162484C12DC1~D7~11207B57~00~1.DVSSP Relative Collection Filename: '2012\05-31\D\Collection10.CAB'PartitionEntryID: 1782AE53A28A13B46AFB9477413A5346F1q10000domain.local PartitionGUID: 782AE53A28A13B46AFB9477413A5346F Partition Root Path: C:\Enterprise Vault Stores\VS2 Ptn2 Secondary Location: Migrated File Id: Reference: NSDR/LCF
V-437-6882
Cause
This issue occurs due to following reasons:-
A. Exporting of an archive to a PST, making a backup of the exported PST -CFG file and importing this PST(using CFG file) to an archive in multiple attempts.
B. Repeated initiation of a move archive job from the Source to Destination archive for the same OR different Enterprise Vault Directory after opening source archive for usage.
In above two scenarios, if manual / automatic partition rollover happens after the first attempt of migration then Enterprise Vault process incorrectly creates DVS file in newly open partition. The ‘StorageFileWatch’ process then collects & updates the ‘IDPartition’ column of the ‘Collection’ table in the vault store database, however ‘Saveset’ table references still points to the old ‘IDPartition’.
As a result of the above operations the following event is generated in the event viewer.
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Event ID: 13405
Task Category: Storage Online
Level: Error
Description:
A constraint violation error was detected while accessing the Vault Database 'EVVSVS2_2' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [.\ADODataAccess.cpp, lines {1317,1319,1335,1353}, built Jul 10 17:51:36 2013]):
Description:
Enterprise Vault Stored Procedure : uspi_Saveset0, Line 114, Error 2601, Level 14, State 1, Message: Cannot insert duplicate key row in object 'dbo.Saveset' with unique index 'IX_IdTransaction'.
SQL Command:
uspi_Saveset0
V-437-13405
Solution
This issue has been addressed in the following release:
Enterprise Vault 11.0.1 Cumulative Hotfix 2 Release
https://www.veritas.com/docs/000025301
Enterprise Vault 12 release
https://www.veritas.com/docs/000099905
Note: For information on how to obtain Enterprise Vault 12 see: How to obtain the license key and installation download for Veritas products
In order address the above mentioned issue for data archived in earlier version’s please contact Technical support by opening a support case.