How to find the .DVS file name corresponding to an Enterprise Vault archived item (versions 8 and later)
Problem
Enterprise Vault (EV) stores individual items as files with a .DVS extension. This article describes the name and path conventions for these files and how to locate them on disk, for items that were originally archived by EV 8 and later. (For items archived by EV 2007 and earlier, see this article.)Cause
Within EV 8.0, the storage model has changed from previous versions. Prior to EV 8.0, an archived item was contained within a single file with the DVS extension. In EV 8.0 and above, the storage model changed to improve the Single Instance Storage (SIS) capability. This was performed by separating the item into multiple files (.DVS [header], .DVSSP [Shared part] and .DVSCC [converted content]). The DVS file in EV 8.0 and above is unique to the exact item as this contains the message header information only. All other components (Attachments, message body, etc.) may be shared with other items. Regardless if the 'shared parts' (.DVSSP items) are present in other locations, the parent DVS file must be present for proper recombination of the item.
Solution
When an item cannot be retrieved via user or administration actions (Shortcuts or FSA Placeholder objects), it may be necessary to locate the corresponding parent DVS file to determine this is present on storage.
Note : For Microsoft Exchange archiving follow the steps below (Not applicable when Vault Store partition is located on EMC Centera or streamer device).
1. Open Microsoft Outlook and select the archived item.
2. Press CTRL + SHIFT and left-click any one of the EV toolbar buttons to open the EV Diagnostic window.
3. Click the Vault Information button.
4. In the section titled Selected Item Properties, scroll down to the Saveset ID. A character string should be displayed similar to:
Related Knowledge Base Articles
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.