How disk space might be consumed on closed EV Vault partitions (4293860)

Issue
Administrators may notice that free disk space reduces unexpectedly on closed EV Vault partitions containing Collection (.CAB) files.
The EV Export module may log the following error:

2017-02-10 08:43:18Z|5240| 53|ERROR| Process|Error occured. ArchiveID: [xxxxxxxxxxxxxxxxxxxxxxxx_vault] | ItemID: [694xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx28] Void Get(Int32)
An internal failure occurred. Internal Error: 'Failed to extract CAB file. [0xc0041b0f]'.
at KVS.EnterpriseVault.Interop.IItem.Get(Int32 DetailLevel)
at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.ContentRetrieverBase.FetchItem(IItem item, Int32 detailLevel)
at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.StandardContentRetriever.FetchItem(IItem item)
at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.ContentRetrieverBase.ProcessAsFile(StagingArea stagingArea, EVExportResult item, String fileName)
at ArchiveShuttle.Module.EVExportModule.ItemContentRetrievers.ContentRetrieverBase.Process(EVArchive archive, Int32 commandId, Int32 mappingId, EVExportResult item, StagingArea stagingArea)

 
Cause
On NTFS partitions where Collections have been enabled, archived data are collected into. CAB files after a period defined by the administrator.  Once this data is collected, subsequent requests to retrieve or restore it, result in this data being extracted from its corresponding CAB file to the closed partition. This data is restored in the form of temporary files with the extensions .archdvs, .archdvssp and .archdvscc.
These temporary files should then be deleted from the partition by Enterprise Vault the next time the Collection process runs if these files have not been accessed in the last 24 hours.  The collection process schedule is defined on the Collections tab in the properties of each partition.
 
Solution
When performing a migration with Archive Shuttle it will, of course, need to retrieve the items inside the CAB files, and it does this by using the EV API. The EV API extracts the items from the CAB files, as described in the previous section. These temporary files may then remain on the partition disk.
If it is determined that there is a significant number of .archdvs, .archdvssp and .archdvscc files on the closed partition’s disk location (One way to determine this is by running the command dir *.archdvs, *.archdvscc, *.archdvssp /S > extractedfiles.txt from the root of the partition’s disk location.) then follow these steps:
 
1) Verify that the Vault Store Database that hosts this partition is not in Backup Mode:

a. On the Enterprise Vault console, click the Vault Store Group that contains the Vault Store.

b. Check the Backup Mode column in the right-hand pane of the Vault Administration Console.

c. If Backup Mode is set for the Vault Store containing the affected partition and there is no backup currently in progress, clear the Backup Mode by right-clicking on the Vault Store and selecting Clear Backup Mode

2) Once Backup Mode is not set, manually run Collections:

a. Open the properties of the affected partition and select the Collections tab.

b. Verify that the daily file collection schedule is set correctly and then click the Run Now button.  An event should then be logged in the Enterprise Vault event log indicating that a Collection run has started.  When this run completes an event will also be logged confirming that the Collection run has completed.

See also Veritas KB article ‘Free disk space reduces unexpectedly on closed NTFS partitions.‘

 
It is also possible to delete the *.archdvs files manually. There are few commands that can be used to clean the *.archdvs files
1) CMD – need to be run on the folder:

del *.archdvs* /s

2) PowerShell – path need to change. Below is just an example:

Remove-Item -path C:\FolderXY\Folder2XY\*.archdvs*

3) Quadrotech has also produced a tool to handle ARCHDVS files to assist in this situation.

See KB article ‘Tool: Handling ARCHDVS files whilst migrating with Archive Shuttle’ for more details.

 
If there is no reduction in the number of *.arch* files after following these steps, please contact Veritas Technical Support.