cancel
Showing results for 
Search instead for 
Did you mean: 

Cab files being deleted by the Collection management job

nils35
Level 4

Hi,

When the Collections job runs, 190 cab files are being deleted from the file system on the EV server. The following is shown in a dtrace when this happens:

1632 10:14:38.411  [3996] (StorageFileWatch) <4624> EV:M CMigratorHelper::DeleteFiles : Attempting to delete file D:\EV_Vaultstores\File_ptn5\2006\01\17\Collection15861.CAB from Partition 14CA49A41A2206345B907702CFD7D6ABF1q10000bgo_vault
1633 10:14:38.411  [3996] (StorageFileWatch) <4624> EV:L EVCommon::DeleteFile : FileName = D:\EV_Vaultstores\File_ptn5\2006\01\17\Collection15861.CAB
 

The following is shown in the event log:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Storage File Watch
Event ID: 13360
Date:  12/1/2014
Time:  10:00:01 AM
User:  N/A
Computer: BGO-P-VAULT-03
Description:
An error was detected while accessing the Vault Database 'EVFileSystemVaultStore' (Internal reference: .\ADODataAccess.cpp (CADODataAccess::ExecuteSQLCommand) [lines {1392,1394,1409,1427}] built Oct  6 11:22:46 2010):

Description: 

The DELETE statement conflicted with the REFERENCE constraint "FK_CollectionIdentity_Collection". The conflict occurred in database "EVFileSystemVaultStore", table "dbo.Saveset", column 'CollectionIdentity'.
 
 
SQL Command:
 EVManageCollections
 
 
Additional Microsoft supplied information:
 
Source:       Microsoft OLE DB Provider for SQL Server
Number:       0x80040e2f
SQL State:    23000
Native Error: 00000547
HRESULT  0x80040e2f
 

Event Type: Error
Event Source: Enterprise Vault
Event Category: Storage File Watch
Event ID: 6796
Date:  12/1/2014
Time:  10:00:01 AM
User:  N/A
Computer: BGO-P-VAULT-03
Description:
A COM exception has been raised.
<0x80040e2f>
Internal reference
.\VaultStoreDB.cpp (CVaultStoreDB::DeleteCollection) [lines {5892,5902,5905,5906,5907,5910}] built Oct  6 11:28:33 2010
 
An exception is raised when a process encounters an unexpected fault.

 

8 REPLIES 8

AndrewB
Moderator
Moderator
Partner    VIP    Accredited

perhaps something else like discovery accelerator or compliance accelerator is using the archive?

nils35
Level 4

I don't understand how that should make the Collection job delete 190 cab files? Do you have any more information? Note that if I restore the cab files from backup, they are deleted again at 10 AM the next day as that is when the Collections job is set to start. Thanks.

GabeV
Level 6
Employee Accredited

Hello nils35,

Looking at the folder path, these collections were created in 2006 (2006\01\17). Do you have Storage Expiry enabled? You can verify if Storage Expiry is enabled in the site settings. If so, it would explain why the CAB files are being removed.

GertjanA
Level 6
Partner    VIP    Accredited Certified

Keeping in mind the article written by JW3 (https://www-secure.symantec.com/connect/articles/how-collections-and-sparse-collections-work), I believe it is safe to assume that these cabfiles are being deleted because they do not contain valid archved files anymore.

This is what GabeV is saying. You might require assistance from support, to examine why the cabfiles are being deleted (to check if they are indeed no longer needed), and to investigate why they give a problem when being deleted.

 

Regards. Gertjan

nils35
Level 4

Hi,

Thanks for your reply. Storage Expiry is not enabled. We have run expiry manually in report mode a few times and the report came up with 0 items expired each time as we expected.

nils35
Level 4

Thanks for replying. The files do contain valid files as we get errors when trying to restore files. When I restore the cab files, restoring the files works fine, but then the cab files are deleted again each day.

I have had an open support case with Symantec for several weeks without much progress. It was finally escalated so hopefully they will figure something out soon.

TheKremlin
Level 3
Partner Accredited

Ever get this resolved? What was the cause?

nils35
Level 4

Hello,

Still not resolved. Symantec Support are still working on it and hopefully they will call me today with good news.